<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Sorry, please disconsider this!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Thiago Teixeira
<br>
<b>Sent:</b> Wednesday, January 11, 2017 7:54 PM<br>
<b>To:</b> 'Junxiao Shi' <shijunxiao@email.arizona.edu><br>
<b>Cc:</b> <nfd-dev@lists.cs.ucla.edu> <nfd-dev@lists.cs.ucla.edu>; Teng Liang <philoliang2011@gmail.com><br>
<b>Subject:</b> RE: [Nfd-dev] Ethernet multicast over multiple wireless hops<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Junxiao,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks for your comments.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I noticed that faces that use UDP or TCP tunnels seem to relay information over multiple hops, using the same strategy. Ethernet does not.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Could you clarify why this happens please?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I looked into the NFD Developer Guide and this older post:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="http://www.lists.cs.ucla.edu/pipermail/ndn-interest/2015-June/000720.html">http://www.lists.cs.ucla.edu/pipermail/ndn-interest/2015-June/000720.html</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thank you,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thiago<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Junxiao Shi [<a href="mailto:shijunxiao@email.arizona.edu">mailto:shijunxiao@email.arizona.edu</a>]
<br>
<b>Sent:</b> Wednesday, December 21, 2016 8:46 PM<br>
<b>To:</b> Thiago Teixeira <<a href="mailto:tteixeira@engin.umass.edu">tteixeira@engin.umass.edu</a>><br>
<b>Cc:</b> <<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>>; Teng Liang <<a href="mailto:philoliang2011@gmail.com">philoliang2011@gmail.com</a>><br>
<b>Subject:</b> Re: [Nfd-dev] Ethernet multicast over multiple wireless hops<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi Thiago<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">NFD forwarding as of v0.5.0 is not designed for wireless networks.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Whether an Interest will be forwarded out of the same face as it came in is up to the strategy, as nothing in forwarding pipelines prevents such forwarding.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">For BestRouteStrategy2, delete these lines <a href="https://github.com/named-data/NFD/blob/037f4ab4b62f42447c78d25ede0755f98409c9cb/daemon/fw/best-route-strategy2.cpp#L71-L73">
https://github.com/named-data/NFD/blob/037f4ab4b62f42447c78d25ede0755f98409c9cb/daemon/fw/best-route-strategy2.cpp#L71-L73</a> enables such forwarding.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Incoming Data pipeline will not forward a Data out of the same face as it came in. This can be changed by deleting these lines
<a href="https://github.com/named-data/NFD/blob/037f4ab4b62f42447c78d25ede0755f98409c9cb/daemon/fw/forwarder.cpp#L365-L367">
https://github.com/named-data/NFD/blob/037f4ab4b62f42447c78d25ede0755f98409c9cb/daemon/fw/forwarder.cpp#L365-L367</a><o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I do not know the implication on loop detection and PIT aggregation after those changes are made. I'm CCing Teng Liang who recently implemented a broadcast-based forwarding strategy for sensor networks where each node has only one wireless
NIC, as he may have a better idea on the implication.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Yours, Junxiao<o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Dec 21, 2016 at 3:14 PM, Thiago Teixeira <<a href="mailto:tteixeira@engin.umass.edu" target="_blank">tteixeira@engin.umass.edu</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">I have a topology of five wireless nodes all running NFD v.0.5. on Ubuntu 16.04. I am using Ethernet as the transport method with one multicast group, as follows
<i>face_system.ether. mcast_group 01:00:5E:00:17:AA</i>. <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><o:p> </o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">When I test connectivity using NDN-Ping it works between one hop neighbors, but not over multiple hops. I assume that is because the architecture prevents it from sending Int/Data
packets over the same face it received, in order to prevent loops. Am I right?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>