<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div><br>
</div>
<div>Dave,</div>
<div><br>
</div>
<div>Sorry, this is a specific case that indeed requires some backstory:</div>
<div><br>
</div>
<div>- We are only talking about local content injection – i.e., from app to its local daemon.</div>
<div><br>
</div>
<div>- This is a "feature" of NDNx/CCNx used in applications like our rtc implementation to provide a local buffer for publishing. Frames get pushed out as soon as they are captured, and the app itself doesn't have to worry about buffering them. The main
downside is actually that you don't know how long the frames will really stay in the content store.</div>
<div><br>
</div>
<div>- We do something similar (dumping frames as captured) in video playout with a repository. </div>
<div><br>
</div>
<div>- I'm only concerned with preserving support for this in the initial NFD release so we can quickly test the application as is. There are three other solutions that seem better: 1) implement an application-side buffer in the library; we will do this soon;
2) provide an authenticated mechanism to control how the local daemon handles such pushed data; 3) have a fast local repo implementation that can be used for the same purpose.</div>
<div><br>
</div>
<div>But there's no unsolicited content injection into the network.</div>
<div><br>
</div>
<div>Jeff</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>"Dave Oran (oran)" <<a href="mailto:oran@cisco.com">oran@cisco.com</a>><br>
<span style="font-weight:bold">Date: </span>Wed, 19 Mar 2014 11:06:31 +0000<br>
<span style="font-weight:bold">To: </span>Alex Afanasyev <<a href="mailto:alexander.afanasyev@ucla.edu">alexander.afanasyev@ucla.edu</a>><br>
<span style="font-weight:bold">Cc: </span>Jeff Burke <<a href="mailto:jburke@remap.ucla.edu">jburke@remap.ucla.edu</a>>, "<a href="mailto:ndn-app@lists.cs.ucla.edu">ndn-app@lists.cs.ucla.edu</a>" <<a href="mailto:ndn-app@lists.cs.ucla.edu">ndn-app@lists.cs.ucla.edu</a>>,
"Gusev, Peter" <<a href="mailto:peter@remap.ucla.edu">peter@remap.ucla.edu</a>>, "<a href="mailto:bzhang@cs.arizona.edu">bzhang@cs.arizona.edu</a>" <<a href="mailto:bzhang@cs.arizona.edu">bzhang@cs.arizona.edu</a>>, "<a href="mailto:nfd-dev@lists.cs.ucla.edu">nfd-dev@lists.cs.ucla.edu</a>"
<<a href="mailto:nfd-dev@lists.cs.ucla.edu">nfd-dev@lists.cs.ucla.edu</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Ndn-app] [Nfd-dev] NDN-RTC poke Data to CS<br>
</div>
<div><br>
</div>
<div>
<div dir="auto">
<div>Abject confusion.</div>
<div><br>
</div>
<div>I thought one of the deep tenets of NDN was that it would be infeasible to inject unsolicited data into the network, thus eliminating all forms of flooding attacks other than of Interest messages.</div>
<div><br>
</div>
<div>Snooping a broadcast wire is a special case where the data was in fact solicited (and the interest could have been snooped too).</div>
<div><br>
</div>
<div>Sorry, but I clearly have not been privy to any of the backstory here, so it kind of hit me out of the blue.</div>
<div><br>
</div>
<div>DaveO.</div>
<div><br>
On Mar 19, 2014, at 2:39 AM, "Alex Afanasyev" <<a href="mailto:alexander.afanasyev@ucla.edu">alexander.afanasyev@ucla.edu</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div>Hi Jeff,</div>
<div><br>
</div>
<div>Even in the first release, there is no problem with unsolicited data caching for **local** faces (unix socket and tcp connection to localhost address), which should be sufficient for any stand-alone application, including ndnrtc.</div>
<div><br>
</div>
<div>I'm kind of blanking right now on how ndnrtc relates to browser (is it inside browser and can do local connection or javascript will to websockets for that). If it is websocket, then the websocket "proxy" (and/or special face inside NFD---just in case,
this will not be in the first release) can be made "local", so unsolicited caching can be enabled.</div>
<div><br>
</div>
<div>In any case, as Beichuan pointed out, Junxiao described the behavior that will be in the first release, which will have exactly one hard-coded caching policy for the content stored. Next releases would have policies that can be adjusted per node.</div>
<div><br>
</div>
<div>---</div>
<div>Alex</div>
<br>
<div>
<div>On Mar 18, 2014, at 10:44 PM, Burke, Jeff <<a href="mailto:jburke@remap.ucla.edu">jburke@remap.ucla.edu</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div><font face="Calibri,sans-serif">Hi Beichuan,</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">Thanks for the further explanation.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">We would like to run the ndnrtc on NFD as an initial test – should we look for this functionality in the repo or try to provide it in the library? (or both?)</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">thanks,</font></div>
<div><font face="Calibri,sans-serif">Jeff</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div style="font-family: Calibri, sans-serif; font-size: 14px;"><br>
</div>
<span id="OLK_SRC_BODY_SECTION" style="font-family: Calibri, sans-serif; font-size: 14px;">
<div style="font-family: Calibri; font-size: 11pt; text-align: left; border-width: 1pt medium medium; border-style: solid none none; padding: 3pt 0in 0in; border-top-color: rgb(181, 196, 223);">
<span style="font-weight:bold">From: </span>"<a href="mailto:bzhang@cs.arizona.edu">bzhang@cs.arizona.edu</a>" <<a href="mailto:bzhang@cs.arizona.edu">bzhang@cs.arizona.edu</a>><br>
<span style="font-weight:bold">Date: </span>Tue, 18 Mar 2014 22:38:31 -0700<br>
<span style="font-weight:bold">To: </span>Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu">shijunxiao@email.arizona.edu</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:ndn-app@lists.cs.ucla.edu">ndn-app@lists.cs.ucla.edu</a>" <<a href="mailto:ndn-app@lists.cs.ucla.edu">ndn-app@lists.cs.ucla.edu</a>>, Peter Gusev <<a href="mailto:peter@remap.ucla.edu">peter@remap.ucla.edu</a>>,
<<a href="mailto:nfd-dev@lists.cs.ucla.edu">nfd-dev@lists.cs.ucla.edu</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Nfd-dev] NDN-RTC poke Data to CS<br>
</div>
<div><br>
</div>
<div>
<div 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">
<div dir="ltr">Hi Peter</div>
<div dir="ltr">In seminar slides you mention that the RTC application in browser may poke Data to a remote forwarder.</div>
<div 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.</div>
<div dir="ltr">You should insert Data into a repository instead.</div>
<div dir="ltr">Yours, Junxiao</div>
_______________________________________________<br>
Nfd-dev mailing list<br>
<a href="mailto:Nfd-dev@lists.cs.ucla.edu">Nfd-dev@lists.cs.ucla.edu</a><br>
<a href="http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev">http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev</a><br>
</blockquote>
</div>
<br>
</div>
</div>
_______________________________________________ Nfd-dev mailing list <a href="mailto:Nfd-dev@lists.cs.ucla.edu">
Nfd-dev@lists.cs.ucla.edu</a> <a href="http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev">
http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev</a> </span></div>
_______________________________________________<br>
Nfd-dev mailing list<br>
<a href="mailto:Nfd-dev@lists.cs.ucla.edu">Nfd-dev@lists.cs.ucla.edu</a><br>
<a href="http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev">http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Ndn-app mailing list</span><br>
<span><a href="mailto:Ndn-app@lists.cs.ucla.edu">Ndn-app@lists.cs.ucla.edu</a></span><br>
<span><a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-app">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-app</a></span><br>
</div>
</blockquote>
</div>
</div>
</span>
</body>
</html>