<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>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? </div><div><br></div><div>Marco</div><div><br></div><div><br></div><div><div style="font-size:9px;color:#575757">Inviato da Samsung Mobile.</div></div><br><br><div>-------- Messaggio originale --------</div><div>Da: Xiaoke Jiang <shock.jiang@gmail.com> </div><div>Data:15/10/2014 17:20 (GMT+01:00) </div><div>A: Marco Ulgelmo <marco.ulge@gmail.com> </div><div>Cc: ndn-interest@lists.cs.ucla.edu </div><div>Oggetto: Re: [Ndn-interest] Question about unsatisfied Interests </div><div><br></div><div style="font-family: Helvetica; font-size: 13px;">Hi Marco,</div><div style="font-family: Helvetica; font-size: 13px;"> This paper <a href="http://named-data.net/wp-content/uploads/comcom-stateful-forwarding.pdf">http://named-data.net/wp-content/uploads/comcom-stateful-forwarding.pdf</a> give more details on how stateful data plane helps to get rid of some kinds of attacher.</div>
<p style="color: #A0A0A8;"><br></p><p style="color: #A0A0A8;">On Wednesday, 15 October, 2014 at 8:13 am, Junxiao Shi wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div dir="ltr">Hi Marco<div><br></div><div>If Router2 has a Route toward the ContentProvider for this Name, it cannot detect the content doesn't exist.</div><div><br></div><div>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.</div><div>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.</div><div><br></div><div>Yours, Junxiao</div></div><div><br><div>On Wed, Oct 15, 2014 at 8:01 AM, Marco Ulgelmo <span dir="ltr"><<a href="mailto:marco.ulge@gmail.com" target="_blank">marco.ulge@gmail.com</a>></span> wrote:<br><blockquote type="cite"><div><div dir="ltr"><div><div><div><div><div><div><div>Hello,<br><br></div>I've recently began studying how NDN works and i have a question about unsatisfied Interests.<br><br>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<br><br></div>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.<br><br></div>Considering the following scenario:<br><br></div>Interest -> Router1 -> Router2 -> Content Provider.<br><br></div>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)?<br><br></div>Thanks,<br><br></div>Marco<br></div>
<br>_______________________________________________<br>
Ndn-interest mailing list<br>
<a href="mailto:Ndn-interest@lists.cs.ucla.edu">Ndn-interest@lists.cs.ucla.edu</a><br>
<a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest" target="_blank">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</a><br>
<br></div></blockquote></div><br></div>
</div><div><div>_______________________________________________</div><div>Ndn-interest mailing list</div><div><a href="mailto:Ndn-interest@lists.cs.ucla.edu">Ndn-interest@lists.cs.ucla.edu</a></div><div><a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>
</body>