<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 13, 2015, at 4:13 PM, Burke, Jeff <<a href="mailto:jburke@remap.UCLA.EDU" class="">jburke@remap.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; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<span id="OLK_SRC_BODY_SECTION" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class=""><br class="">
</div>
<div class="">Hi folks,</div>
<div class=""><br class="">
</div>
<div class="">Could you please confirm the default behavior of "on-demand" face creation for applications?</div>
<div class=""><br class="">
</div>
<div class="">My understanding: The face created by default when an application registers a prefix is "on demand", meaning it can be destroyed by NFD if inactive for some timeout period.</div></div></span></div></div></blockquote><div><br class=""></div>Not exactly (may be I misunderstood the question). Whenever face is created by an explicit command, it is “persistent” (we also reserved concept “permanent”, but it is not yet implemented).</div><div><br class=""></div><div>On-demand face is face that is created as a response of incoming tcp connect or packet received on UDP face. Only UDP face can get destroyed, TCP faces exist for as long tcp connection is alive.</div><div><br class=""></div><div>* * *</div><div><br class=""></div><div>If you’re referring to the UDP face from the the other side of tunnel, then yes. That face is on-demand and can be destroyed on the other side if no traffic.</div><div><br class=""></div><div>Remote registration built in into NFD/RIB management can take care of proper refreshing state. This is currently implemented, but requires some conventions on registered namespaces / available keys (it is documented in TR Yanbiao is working).</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class=""><span id="OLK_SRC_BODY_SECTION" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class=""><div class="">
</div>
<div class="">This behavior has caused some troubleshooting challenges with a long-running publisher and occasionally interested consumers. </div></div></span></div></div></blockquote><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class=""><span id="OLK_SRC_BODY_SECTION" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class=""><div class=""><br class="">
</div>
<div class="">Some questions:</div>
<div class=""><br class="">
</div>
<div class="">- Where is this behavior documented? It is mentioned in p10 of the developer's guide, but I can't find either the constant or configuration parameter that sets it. </div></div></span></div></div></blockquote><div><br class=""></div><div>Some documentation regarding default values used is also available in nfd.conf.sample.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class=""><span id="OLK_SRC_BODY_SECTION" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class=""><br class="">
</div>
<div class="">- Is it the case that on-demand faces will not be destroyed if any traffic has traversed them? Or just that no traffic has traversed during the timeout interval? </div></div></span></div></div></blockquote><div><br class=""></div><div>Not sure I understood the question. on-demand udp face will not be destroyed if at least one packet (data/interest) is received during the timeout interval.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class=""><span id="OLK_SRC_BODY_SECTION" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class=""><div class=""><br class="">
</div>
<div class="">- What is the appropriate way to create a face that persists until the process that created it is either destroyed or unregistered the prefix? </div></div></span></div></div></blockquote><div><br class=""></div><div>Rely on remote registration process (I would say this is preferred). Alternatively, this could be something else that periodically send interest towards the remote end.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class=""><span id="OLK_SRC_BODY_SECTION" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class=""><br class="">
</div>
<div class="">Thank you,</div>
<div class="">Jeff</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
</div>
</span>
</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="">http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev<br class=""></div></blockquote></div><br class=""></body></html>