<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div><br>
</div>
<div>As Junxiao says, reordering of data is necessary and, for example, is handled for video (and audio) in both
<a href="https://github.com/named-data/ndnvideo">NDNVideo</a> and <a href="https://github.com/remap/ndnrtc">
ndnrtc</a>. NDNVideo has a longer playout buffer and thus can handle more out of order packets without impacting playback; ndnrtc is designed with a small buffer for real-time conversations but also handles reordering of data packets. (In these and many other
applications, interest retransmissions in the case of dropped packets also have to be handled.) </div>
<div><br>
</div>
<div>In these apps, interest reordering is not performed at the producer; it is simpler to just publish data to an application memory cache (done in ndnrtc) or ndn repository (done in NDNVideo), and let that store respond to whatever interests come in, regardless
of ordering. So, only the consumer has to reorder data. This might not be the case in some applications that use Interest for control and might worried about the time the interests were issued at the source. </div>
<div><br>
</div>
<div>There is active work to generalize APIs that handle ordering and retransmission, e.g., Ilya Moiseenko's work presented at
<a href="http://www.caida.org/workshops/ndn/1409/">NDNComm 2014</a>. </div>
<div><br>
</div>
<div>Jeff</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu">shijunxiao@email.arizona.edu</a>><br>
<span style="font-weight:bold">Date: </span>Sat, 14 Feb 2015 08:21:08 -0700<br>
<span style="font-weight:bold">To: </span>Nitinder Mohan <<a href="mailto:nitinder1369@iiitd.ac.in">nitinder1369@iiitd.ac.in</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:ndn-interest@lists.cs.ucla.edu">ndn-interest@lists.cs.ucla.edu</a>" <<a href="mailto:ndn-interest@lists.cs.ucla.edu">ndn-interest@lists.cs.ucla.edu</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Ndn-interest] Interest Order Maintaining<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div dir="ltr">
<div>Hi Nitinder</div>
<div><br>
</div>
<div>NDN network does not guarantee in order delivery. An Interest could also be delivered to the producer multiple times.</div>
<div><span style="font-size:12.8000001907349px">The end consumer, either implemented in app or in library, should handle out-of-order packets. This situation is no different from IP.</span><br>
</div>
<div><span style="font-size:12.8000001907349px"><br>
</span></div>
<div>Yours, Junxiao</div>
<div>This is a correction to a previous answer. It replaces all prior answers.<br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, Feb 14, 2015 at 3:50 AM, Nitinder Mohan <span dir="ltr">
<<a href="mailto:nitinder1369@iiitd.ac.in" target="_blank">nitinder1369@iiitd.ac.in</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hello All!
<div><br>
</div>
<div>A curious question comes to my mind regarding routing strategy in NDN. </div>
<div><br>
</div>
<div>Let us assume that there is one consumer and one producer in a network consisting of myriad of routers. If a consumer issues continuous interests for different data packets from the same producer, is it guaranteed that the Interest packets will arrive
at producer in the same order as in which they were published?</div>
<div><br>
</div>
<div>I understand that NDN follows multipath routing and later selects paths from its PIT entry according to performance of returning data. But wouldn't consecutive interests be sent on the same interface presuming there is no change in the network. </div>
<div> <br>
</div>
<div>
<div>
<div>
<div dir="ltr">Thanks and Regards<span class="HOEnZb"><font color="#888888">
<div><br>
</div>
<div>Nitinder Mohan</div>
<div>MTech (CE) IIIT Delhi</div>
<div><a href="http://home.iiitd.edu.in/~nitinder1369/" target="_blank">http://home.iiitd.edu.in/~nitinder1369/</a><br>
</div>
</font></span></div>
</div>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Ndn-interest mailing list<br>
<a href="mailto:Ndn-interest@lists.cs.ucla.edu">Ndn-interest@lists.cs.ucla.edu</a><br>
<a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest" target="_blank">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</a><br>
<br>
</blockquote>
</div>
<br>
</div>
_______________________________________________ Ndn-interest mailing list <a href="mailto:Ndn-interest@lists.cs.ucla.edu">
Ndn-interest@lists.cs.ucla.edu</a> <a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest">
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</a> </blockquote>
</span>
</body>
</html>