<html 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:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@DengXian";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span lang=FR>Thank you </span>Junxiao,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Well, another problem (from my point of view) will be opened, if the load balancing and alternative path selection is a full responsibility of consumer, so load balancing and congestion should be solved from the application layer with some modification in strategy layer ?<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Best regards,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:shijunxiao@email.arizona.edu">Junxiao Shi</a><br><b>Sent: </b>Tuesday, April 25, 2017 10:59 AM<br><b>To: </b><a href="mailto:n.boubakr@bit.edu.cn">n.boubakr@bit.edu.cn</a>; <a href="mailto:ndn-interest@lists.cs.ucla.edu">ndn-interest@lists.cs.ucla.edu</a><br><b>Subject: </b>Re: [Ndn-interest] NDN Load Balancing and Alternative Path</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi Boubakr<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Yes, load balancing and usage of alternate paths apply to Interest forwarding only, while Data simply follows the reverse of an Interest. There is no "consumer address" in the Data, so that there is no way to send the Data on another path.</p></div><div><p class=MsoNormal>The consumer is ultimately responsible for retrieving the Data it wants. If there is a link failure, the downstream (consumer or otherwise) can retransmit the Interest, in order to reach a node that has the Data (either producer or cache). It is also downstream's responsibility to load balance its Interests among multiple paths, in reaction to congestion marks.</p></div><div><p class=MsoNormal>You may have seen schemes that add a return address to Data packets. Such schemes would not work with Interest aggregation: if the Data is routed via an alternate path according to the return address, other consumers whose Interests have been aggregated could not receive the Data because the Data no longer passes through the node that performed the aggregation.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Yours, Junxiao</p></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Mon, Apr 24, 2017 at 19:49 <<a href="mailto:n.boubakr@bit.edu.cn">n.boubakr@bit.edu.cn</a>> wrote:</p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=MsoNormal>Hello,</p><p class=MsoNormal> </p><p class=MsoNormal>Starting from the point that the Data packet is routed back to consumer using the reverse path of Interest. How can we achieve a load balancing in Data delivery, and how can we migrate from a link to another link in case of link failure.</p><p class=MsoNormal>Another question, most of efforts in NDN congestion control propose using alternative path, how can we use an alternative path and NDN forwarding engine uses the PIT table to deliver data. </p><p class=MsoNormal>The idea of alternative path and load balancing is valid only in Interest path and can not be realized in Data path.</p><p class=MsoNormal> </p></div></div></blockquote></div></div><p class=MsoNormal style='margin-left:4.8pt'>Boubakr Nour (Ph.D Candidate)<br>Beijing Institute of Technology (<span lang=ZH-CN style='font-family:DengXian'>北京理工大学</span>) </p><p class=MsoNormal><o:p> </o:p></p></div></body></html>