[Ndn-interest] R: Re: Question about unsatisfied Interests

Wed Oct 15 08:47:19 PDT 2014

I thought the Interest NACK is a type of control message that is not cached in the content store.

That is different than the publisher issuing a Data object of ContentType = NACK.  Or even issuing a Data object with type = Data, but a body like a 403.  I thought that the ContentType = NACK was removed from the NDN spec.

So, Junxiao answer that the NACk could stay in the content store was surprising to me.

Marc

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

Thanks for the replies. Actually I found all I needed in the link provided by Xiaoke. I read that this kind of interest neck is what they propose in the research. What I'd like to know now is: has this been implemented in NDN? I mean, can I rely in this for a future work?

Marco

Inviato da Samsung Mobile.

-------- Messaggio originale --------
Da: Xiaoke Jiang
Data:15/10/2014 17:20 (GMT+01:00)
A: Marco Ulgelmo
Cc: ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>
Oggetto: Re: [Ndn-interest] Question about unsatisfied Interests

Hi Marco,
   This paper   http://named-data.net/wp-content/uploads/comcom-stateful-forwarding.pdf give more details on how stateful data plane helps to get rid of some kinds of attacher.

On Wednesday, 15 October, 2014 at 8:13 am, Junxiao Shi wrote:

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<mailto: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<mailto:Ndn-interest at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest

_______________________________________________
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu<mailto:Ndn-interest at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest

_______________________________________________
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu<mailto: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/0077588c/attachment.html>