<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Oct 31, 2018, at 12:50 PM, Lixia Zhang <<a href="mailto:lixia@cs.ucla.edu" class="">lixia@cs.ucla.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I'd like to inject the following discussion item for today's call:<div class="">a question from Peter (let me know if I got any detail wrong)</div><div class=""><br class=""></div><div class=""> NDN-RTC</div><div class=""> producer repo</div><div class=""> | |</div><div class="">------------------------------switched Ethernet</div><div class=""> |</div><div class=""> consumer</div><div class=""><br class=""></div><div class="">each of the above boxes has an ethernet face</div><div class="">repo fetches and saves NDN-RTC stream</div><div class="">consumer fetches historical data from repo first, at twice the speed of NDN RTC production rate, so eventually catch up with the real time production.</div><div class=""><br class=""></div><div class="">producer has limited buffering, so one can see 3 phases:</div><div class=""><br class=""></div><div class=""> phase-1 phase-2 phase-3</div><div class="">data in repo only | data in repo & producer | data from producer</div><div class=""><br class=""><div class="">Q1: how best should the consumer use the Ethernet face (it needs to figure out whose MAC address to use for Interest packet, or it should use Ethernet mcast)</div><div class=""><br class=""></div><div class="">Q2: one can also model the process as having 2 phases only--ideally as soon as the consumer catches up with producer, the producer should mcast the data packet, that goes to both consumer and repo. how to implement this?</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class="">On Oct 31, 2018, at 8:00 AM, NFD call notification <<a href="mailto:nfd-call-notification@mail1.yoursunny.com" class="">nfd-call-notification@mail1.yoursunny.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><p class="">Dear folks</p><p class="">This is a reminder of the upcoming NFD call using Bluejeans
<a href="https://bluejeans.com/505221277" class="">https://bluejeans.com/505221277</a>.
The current call time is every Monday and Wednesday 16:00-17:00 CDT.
The current agenda includes the following issues:</p>
<hr class=""><div class="">
<span class="c2">
</span>
<br class="webkit-block-placeholder"></div><div class="">
<span class="c2">
</span>
<br class="webkit-block-placeholder"></div><p class="c0">
<span class="c4">
<a class="c3" href="https://www.google.com/url?q=https://gerrit.named-data.net/%23/c/ndn-cxx/%2B/4876/&sa=D&ust=1541001603160000">https://gerrit.named-data.net/#/c/ndn-cxx/+/4876/</a>
</span>
</p><p class="c0">
<span class="c2">Implementation detail, to test or not to test?</span>
</p><div class="">
<span class="c2">
</span>
<br class="webkit-block-placeholder"></div><p class="c0">
<span class="c4">
<a class="c3" href="https://www.google.com/url?q=https://lists.netsec.colostate.edu/mailman/private/operators/2018-October/001311.html&sa=D&ust=1541001603161000">https://lists.netsec.colostate.edu/mailman/private/operators/2018-October/001311.html</a>
</span>
</p><p class="c0">
<span class="c2">How should NDN-FCH react to node failures?</span>
</p><div class="">
<span class="c2">
</span>
<br class="webkit-block-placeholder"></div>
_______________________________________________<br class="">Nfd-dev mailing list<br class=""><a href="mailto:Nfd-dev@lists.cs.ucla.edu" class="">Nfd-dev@lists.cs.ucla.edu</a><br class=""><a href="http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev" class="">http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev</a><br class=""></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></body></html>