[Ndn-interest] Question about unsatisfied Interests

Junxiao Shi shijunxiao at email.arizona.edu
Wed Oct 15 08:13:57 PDT 2014

Hi Marco

If Router2 has a Route toward the ContentProvider for this Name, it cannot
detect the content doesn't exist.

ContentProvider should reply with a provider-generated NACK, which is a
type of Data, that indicates the non-existence of this content. A
provider-generated NACK is cachable on routers.
A future Interest toward this Name would be satisifed by this
provider-generated NACK from the ContentStore, and doesn't have to go to
the ContentProvider.

Yours, Junxiao

On Wed, Oct 15, 2014 at 8:01 AM, Marco Ulgelmo <marco.ulge at gmail.com> wrote:

> Hello,
> I've recently began studying how NDN works and i have a question about
> unsatisfied Interests.
> Lets say that an attacker generates a fake Interest packet that surely
> doesn't exist. Let's assume that this packet is identified by the following
> name: /google/randomtext
> As far as i know i shuold be able to reach /google but i won't be able to
> retrieve the content as it doesn't exist.
> Considering the following scenario:
> Interest -> Router1 -> Router2 -> Content Provider.
> Is Router2 able to determine that the content doesn't exist? Can this
> information be sent back to Router2 from the Content Provider (which surely
> knows that he doesn't have that resource)?
> Thanks,
> Marco
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20141015/e845929b/attachment.html>

More information about the Ndn-interest mailing list