<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">In my opinion, caching unsolicited data or not should be the choice of each individual node; nothing in the architecture or protocol prevents that.<div><br></div><div>What Junxiao said is probably what the first release of NFD will have. </div><div><br></div><div>Beichuan</div><div><br></div><div><div>On Mar 18, 2014, at 7:57 PM, Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu">shijunxiao@email.arizona.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p dir="ltr">Hi Peter</p><p dir="ltr">In seminar slides you mention that the RTC application in browser may poke Data to a remote forwarder.</p><p dir="ltr">I want to inform you that NFD will not admit any unsolicited Data from non-local face. NFD will admit unsolicited Data from local face, but they will be the first to get evicted when CS is full.</p><p dir="ltr">You should insert Data into a repository instead.</p><p dir="ltr">Yours, Junxiao</p>
_______________________________________________<br>Nfd-dev mailing list<br><a href="mailto:Nfd-dev@lists.cs.ucla.edu">Nfd-dev@lists.cs.ucla.edu</a><br>http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev<br></blockquote></div><br></body></html>