<html class=" clickberry-extension clickberry-extension-standalone" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>
<!--
@font-face
{font-family:Wingdings}
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
{color:#0563C1;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
span.EmailStyle17
{font-family:"Calibri","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none}
.MsoChpDefault
{font-family:"Calibri","sans-serif"}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
ol
{margin-bottom:0in}
ul
{margin-bottom:0in}
-->
</style>
<meta content="clickberry-extension-here">
<style type="text/css" id="owaParaStyle"></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Keith, you're right, there is nothing in the LTP specification that ever compels a receiving LTP engine to deliver green data in transmission order rather than reception order (i.e.,
to reorder received green segments).
<div><br>
</div>
<div>Scott<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF460556" style="direction: ltr;"><font face="Tahoma" size="2" color="#000000"><b>From:</b> sis-dtn-bounces@mailman.ccsds.org [sis-dtn-bounces@mailman.ccsds.org] on behalf of Scott, Keith L. [kscott@mitre.org]<br>
<b>Sent:</b> Wednesday, August 06, 2014 10:00 AM<br>
<b>To:</b> sis-dtn@mailman.ccsds.org<br>
<b>Subject:</b> [Sis-dtn] JAXA RID on LTP -- LTP and Sequential Delivery<br>
</font><br>
</div>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:14.0pt">Greetings,</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">Here’s my second question w.r.t. the JAXA RIDs. This one has to do with sequential (which I interpret to mean in-order) delivery with LTP.</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">JAXA-PRA1415-09 states:</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt">Sequential transportation is an essential function to control devices and
</span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt">LTP can provide sequential transportation over single hop with certain parameter of RFC5326.</span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt">This aspect should be described in this document because it is an important potential of LTP.</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">Is there something about RFC5326 that I missed? The Red-part data of a block is delivered atomically (so data is in-order within the Red Part I suppose) but I don’t think LTP guarantees anything beyond that.
In particular:</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:14.0pt; font-family:Symbol"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:14.0pt">The Red Part of a block might be delivered before, after, or in the middle of Green Data for that block.</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:14.0pt; font-family:Symbol"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:14.0pt">The relative arrival times of Red and Green data from multiple blocks transmitted simultaneously are undefined by the spec.</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">The only way I know of to ensure in-order arrival of data would be to use only red data and to wait for the report indicating complete reception of one block before completing transmission of the next (red)
block. That’s possible, but it would be an implementation decision not part of the specification.</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">Am I missing something here?</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">JAXA-PRA1415-10 states:</span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt">To control sequential transportation over multi-hop communication,
</span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt">RFC and Red Book should contain the description of the interface and</span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt">rule as SAP of LTP like the option of Green-Data.
</span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt">LTP can naturally support single hop sequential transportation,
</span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt">but multi hop transportation needs some handling of hop-to-hop interaction.</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">The Delay-Tolerant Payload Conditioning (DTPC) in the BP-for-CCSDS book provides an in-order delivery service. As with the above (09) I don’t think there’s anything in the LTP spec (RFC5326 or LTP-for-CCSDS)
that says anything about providing in-order delivery of LTP blocks (or Green-part segments).</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">Does anyone interpret these differently? If not then I’m going to suggest adding a NOTE specifically stating that in-order delivery is not an LTP service, but multi-hop (or single-hop, if BP is deployed on
both ends of the link) in-order delivery is achievable with BP and DTPC.</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> --keith</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>