
<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="">Hi,<div class=""><br class=""></div><div class="">if I recall correctly, we did not get to use the <span style="font-size: 12.8px;" class="">v2v-net-device transport. We directly modified the net device transport instead (</span><font size="2" class=""><a href="https://github.com/4th-ndn-hackathon/ndnSIM-Mobile-Simulation-Package/commit/d6bce17032111bdf8c170b9c694dced7f0796b14" class="">https://github.com/4th-ndn-hackathon/ndnSIM-Mobile-Simulation-Package/commit/d6bce17032111bdf8c170b9c694dced7f0796b14</a>).</font></div><div class=""><font size="2" class=""><br class=""></font></div><div class=""><font size="2" class="">From the perspective of long term design planning, a Face of NFD will be associated with a link of specific type. This link can be an ad-hoc or a point-to-point link, etc, so this could determine how a strategy makes its decisions. I do not think that an application will be able to know the type of the underlying link (unless it sends a query to NFD somehow — this could be implemented as a hack in ndnSIM if needed).</font></div><div class=""><font size="2" class=""><br class=""></font></div><div class=""><font size="2" class="">We are planning to integrate the latest version of NFD with ndnSIM this fall to be able to use the link type feature in simulations, so please stay tuned.</font></div><div class=""><font size="2" class=""><br class=""></font></div><div class=""><font size="2" class="">Thank you,</font></div><div class=""><font size="2" class=""><br class=""></font><div class="">

<div class=""><div class=""><div class=""><span class="" style="float: none; display: inline !important;">Spyridon (Spyros) Mastorakis</span><br class=""><span class="" style="float: none; display: inline !important;">Personal Website: </span><a href="http://cs.ucla.edu/~mastorakis/" class="">http://cs.ucla.edu/~mastorakis/</a><br class=""><span class="" style="float: none; display: inline !important;">Internet Research Laboratory</span><br class=""><span class="" style="float: none; display: inline !important;">Computer Science Department</span><br class=""><span class="" style="float: none; display: inline !important;">UCLA</span></div></div></div>

</div>

<br class=""><div><blockquote type="cite" class=""><div class="">On Aug 24, 2017, at 9:29 PM, Adhy Satya <<a href="mailto:adhysatya820@gmail.com" class="">adhysatya820@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi <span style="font-size:12.8px" class="">Spyros,</span><div class=""><span style="font-size:12.8px" class=""><br class=""></span></div><div class=""><span style="font-size:12.8px" class="">I downloaded and tested the mobile simulation package code. It's very helpful to me, thanks</span></div><div class=""><span style="font-size:12.8px" class="">My question is how does the application/strategy knows which net-device-face to use, since there are the "original" net-device-transport" and the v2v-net-device-transport.</span></div><div class=""><span style="font-size:12.8px" class=""><br class=""></span></div><div class=""><span style="font-size:12.8px" class="">Thanks</span></div><div class=""><br class=""></div></div></div></blockquote></div><br class=""></div></body></html>