<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=ks_c_5601-1987">

<meta name="Generator" content="Microsoft Word 15 (filtered medium)">

<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}

o\:* {behavior:url(#default#VML);}

w\:* {behavior:url(#default#VML);}

.shape {behavior:url(#default#VML);}

</style><![endif]--><style><!--

/* Font Definitions */

@font-face

        {font-family:Wingdings;

        panose-1:5 0 0 0 0 0 0 0 0 0;}

@font-face

        {font-family:Gulim;

        panose-1:2 11 6 0 0 1 1 1 1 1;}

@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;}

@font-face

        {font-family:"Malgun Gothic";

        panose-1:2 11 5 3 2 0 0 2 0 4;}

@font-face

        {font-family:"\@Malgun Gothic";

        panose-1:2 11 5 3 2 0 0 2 0 4;}

@font-face

        {font-family:"\@Gulim";

        panose-1:2 11 6 0 0 1 1 1 1 1;}

@font-face

        {font-family:GulimChe;}

@font-face

        {font-family:"\@GulimChe";}

/* Style Definitions */

p.MsoNormal, li.MsoNormal, div.MsoNormal

        {margin:0in;

        font-size:12.0pt;

        font-family:"Gulim",sans-serif;

        mso-fareast-language:KO;}

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;}

tt

        {mso-style-priority:99;

        font-family:GulimChe;}

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:"Gulim",sans-serif;

        mso-fareast-language:KO;}

span.EmailStyle21

        {mso-style-type:personal;

        font-family:"Calibri",sans-serif;

        color:windowtext;}

span.EmailStyle22

        {mso-style-type:personal-compose;

        font-family:"Calibri",sans-serif;

        color:windowtext;}

.MsoChpDefault

        {mso-style-type:export-only;

        font-family:"Calibri",sans-serif;}

@page WordSection1

        {size:8.5in 11.0in;

        margin:70.85pt 70.85pt 56.7pt 70.85pt;}

div.WordSection1

        {page:WordSection1;}

/* List Definitions */

@list l0

        {mso-list-id:1734355650;

        mso-list-template-ids:79043504;}

@list l0:level1

        {mso-level-number-format:bullet;

        mso-level-text:\F0B7;

        mso-level-tab-stop:.5in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Symbol;}

@list l0:level2

        {mso-level-number-format:bullet;

        mso-level-text:o;

        mso-level-tab-stop:1.0in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:"Courier New";

        mso-bidi-font-family:"Times New Roman";}

@list l0:level3

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:1.5in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Wingdings;}

@list l0:level4

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:2.0in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Wingdings;}

@list l0:level5

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:2.5in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Wingdings;}

@list l0:level6

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:3.0in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Wingdings;}

@list l0:level7

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:3.5in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Wingdings;}

@list l0:level8

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:4.0in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Wingdings;}

@list l0:level9

        {mso-level-number-format:bullet;

        mso-level-text:\F0A7;

        mso-level-tab-stop:4.5in;

        mso-level-number-position:left;

        text-indent:-.25in;

        mso-ansi-font-size:10.0pt;

        font-family:Wingdings;}

ol

        {margin-bottom:0in;}

ul

        {margin-bottom:0in;}

--></style>

</head>

<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">

<div class="WordSection1">

<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Hi,<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif">Going back to Vints previous email:  agreed; the ACK may exist as a response to a checkpoint/session closure message. In that case, the sender closes the session, receiver takes

 inventory, and responds with 1:n NACKS or a confirmation of closure. <o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif">Otherwise, if we’re considering this proactive-NACK approach, I think we’re starting to converge. To summarize the discussion so far: the hybrid of proactive NACK/periodic ACK

 is really powerful but (as Cheol pointed out) may result in congestion on the noisiest links (which ironically have some of the lowest uplink throughput).  Also, whatever we design shouldn’t add additional configuration complexity.

<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif">One “back of the napkin” idea is to provide a proactive yet sliding NACK window, specified by the sender. Let’s say that you’re sending CP’s at 1hz. The sender sends some signalling

 data to say that it supports NACK, along with a maximum NACK aggregation frequency (let’s say 10hz). On the receiver side, data loss is tracked and (if the number of NACK claims is > 0) sent at 10hz. Some metadata is added to the standard CP to specify the

 serial number of received/pending NACKS. The receiver responds with one claim, specifying the largest contiguous block of data has been received, as well as re-requesting any NACKS that have apparently been missed (as triggered by a timer, etc).<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Determining the efficiency of this mechanism will definitely require further study.<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Thanks,<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Jeremy<o:p></o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>

<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>

<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"> SIS-DTN <sis-dtn-bounces@mailman.ccsds.org>

<b>On Behalf Of </b>Felix Flentge via SIS-DTN<br>

<b>Sent:</b> Tuesday, April 5, 2022 8:10 AM<br>

<b>To:</b> sburleig.sb@gmail.com<br>

<b>Cc:</b> sis-dtn@mailman.ccsds.org; '</span><span lang="KO" style="font-size:11.0pt">备枚雀</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">' <chkoo@kari.re.kr>; SIS-DTN <sis-dtn-bounces@mailman.ccsds.org>; 'Carlo Caini' <carlo.caini@unibo.it><br>

<b>Subject:</b> Re: [Sis-dtn] [EXT] Re: Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing<o:p></o:p></span></p>

</div>

<p class="MsoNormal"><o:p> </o:p></p>

<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hi,</span>

<br>

<br>

<span style="font-size:10.0pt;font-family:"Arial",sans-serif">maybe I am overlooking something: LTP already provides asynchronous reception reports. Whether these are reporting gaps (NAK) or confirm received parts (ACK) seems largely equivalent (the entries

 may just vary by one depending on where we have gaps). When to send these asynchronous reports is and shall be completely up to the receiver.</span>

<br>

<br>

<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Regards,</span> <br>

<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Felix </span><br>

<br>

<br>

<br>

<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"sburleig.sb--- via SIS-DTN" <<a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a>></span>

<br>

<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"'</span><span lang="KO" style="font-size:9.0pt">备枚雀</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">'"

 <<a href="mailto:chkoo@kari.re.kr">chkoo@kari.re.kr</a>>, "'Dr. Keith L Scott'" <<a href="mailto:kscott@mitre.org">kscott@mitre.org</a>>, "'Carlo Caini'" <<a href="mailto:carlo.caini@unibo.it">carlo.caini@unibo.it</a>>, <<a href="mailto:tomaso.decola@dlr.de">tomaso.decola@dlr.de</a>>,

 <<a href="mailto:dstanton@keltik.co.uk">dstanton@keltik.co.uk</a>></span> <br>

<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif"><a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a></span>

<br>

<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">05/04/2022 02:49</span>

<br>

<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Re: [Sis-dtn] [EXT] Re: Positive reception claim vs. Negative reception claim in LTP Report Segment

 preparation and processing</span> <br>

<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Sent by:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"SIS-DTN" <<a href="mailto:sis-dtn-bounces@mailman.ccsds.org">sis-dtn-bounces@mailman.ccsds.org</a>></span>

<o:p></o:p></p>

<div class="MsoNormal" align="center" style="text-align:center">

<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">

</div>

<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Some notes in-line below:</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><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">

</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">备枚雀</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <<a href="mailto:chkoo@kari.re.kr">chkoo@kari.re.kr</a>>

<b><br>

Sent:</b> Monday, April 4, 2022 4:59 PM<b><br>

To:</b> <a href="mailto:sburleig.sb@gmail.com">sburleig.sb@gmail.com</a>; Dr. Keith L Scott <<a href="mailto:kscott@mitre.org">kscott@mitre.org</a>>; Carlo Caini <<a href="mailto:carlo.caini@unibo.it">carlo.caini@unibo.it</a>>;

<a href="mailto:tomaso.decola@dlr.de">tomaso.decola@dlr.de</a>; <a href="mailto:dstanton@keltik.co.uk">

dstanton@keltik.co.uk</a><b><br>

Cc:</b> <a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a><b><br>

Subject:</b> RE: [Sis-dtn] [EXT] Re: Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Malgun Gothic",sans-serif">I think Keith thought it as if the last CP was missing.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">That’s not how I read “will send the whole block and then a CP, which will elicit a RS” but I may have misunderstood.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Malgun Gothic",sans-serif">Immediately NACK RS can save time as amount of the difference between current time and the last CP<span lang="KO">’</span>s arrival time. I think the effect can be negligible

 when bandwidth is very high and a session block length is relatively small, so saving time is order of ms. Of course this effect signifies as big as an RTT when the last CP from a sender is lost during transmission.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Yes, in my example 9.96 seconds, about 2% of a round trip.  I think this is what Carlo was saying.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Malgun Gothic",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Malgun Gothic",sans-serif">But I do like the way of

<span lang="KO">“</span>immediately RS<span lang="KO">”</span>. However the immediately discretionary RS NACK can quickly burn out the return link bandwidth when continuous segment losses are happening while for independent segment loss it will be reasonable.

 There should be some optimization and I think this concept make LTP be expandable in various space environment.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I worry that this would introduce some additional configuration complexity in a protocol that is already very complex to configure.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Malgun Gothic",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Malgun Gothic",sans-serif">Cheol</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Malgun Gothic",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><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">

</span><a href="mailto:sburleig.sb@gmail.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sburleig.sb@gmail.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <</span><a href="mailto:sburleig.sb@gmail.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sburleig.sb@gmail.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>

<b><br>

Sent:</b> Tuesday, April 5, 2022 4:10 AM<b><br>

To:</b> Dr. Keith L Scott <</span><a href="mailto:kscott@mitre.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">kscott@mitre.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>; Carlo Caini <</span><a href="mailto:carlo.caini@unibo.it"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">carlo.caini@unibo.it</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>;

</span><a href="mailto:tomaso.decola@dlr.de"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">tomaso.decola@dlr.de</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">;

</span><span lang="KO" style="font-size:11.0pt">备枚雀</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <</span><a href="mailto:chkoo@kari.re.kr"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">chkoo@kari.re.kr</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>;

</span><a href="mailto:dstanton@keltik.co.uk"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">dstanton@keltik.co.uk</span></a><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>

Cc:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span>

<a href="mailto:sis-dtn@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org</span></a><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>

Subject:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> RE: [Sis-dtn] [EXT] Re: Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Keith, I think this isn’t quite right.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Suppose we’re sending a block that is 1 Megabyte in size, split into 10,000 segments of 100 bytes each.  Suppose the OWLT is 240 seconds and the transmission rate is 800 kbps

 (so 100,000 bytes per second).</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Suppose the 3<sup>rd</sup> segment is lost.  The receiver will detect this loss when the 4<sup>th</sup> segment is received.  That segment will have left the antenna .04 seconds

 after transmission began, and it will arrive at the receiver 240 seconds later.  The receiver will transmit a report segment immediately; let’s ignore the processing and radiation time for issuing the report and say that the report is received at the sender

 240 seconds after the arrival of the 4<sup>th</sup> segment ? so 480.04 seconds after transmission began.  That’s the time at which retransmission can be initiated, right?</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Now suppose there is no further data loss.  The EOB CP leaves the antenna 10 seconds after transmission began and arrives at the receiver 240 seconds later.  The earlier report

 is still en route to the sender, so the lost segment has not yet been retransmitted.  The receiver transmits the CP-triggered report immediately, at 250 seconds after transmission began.  That report is received at the sender 240 seconds after arrival of the

 last segment, so 490 seconds after transmission began; that’s the earliest time at which retransmission can be initiated.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">So it seems to me that the gap-triggered RS has reduced closure latency by 9.96 seconds, not by 1 RTT.  What have I got wrong?</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Scott</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><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"> Dr. Keith L Scott <</span><a href="mailto:kscott@mitre.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">kscott@mitre.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>

<b><br>

Sent:</b> Monday, April 4, 2022 11:50 AM<b><br>

To:</b> Carlo Caini <</span><a href="mailto:carlo.caini@unibo.it"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">carlo.caini@unibo.it</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>;

</span><a href="mailto:tomaso.decola@dlr.de"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">tomaso.decola@dlr.de</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">;

</span><a href="mailto:sburleig.sb@gmail.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sburleig.sb@gmail.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">;

</span><a href="mailto:chkoo@kari.re.kr"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">chkoo@kari.re.kr</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">;

</span><a href="mailto:dstanton@keltik.co.uk"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">dstanton@keltik.co.uk</span></a><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>

Cc:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span>

<a href="mailto:sis-dtn@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org</span></a><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>

Subject:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Re: [Sis-dtn] [EXT] Re: Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I think the 'win' would be (comparing a system that generated proactive NACKs vs. a system that generated a CP only at the end of the block):</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If there are 10,000 LTP segments and the 3rd segment is lost:</span><o:p></o:p></p>

<ul type="disc">

<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">

<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The NACK system will nack it “immediately” and elicit a retransmission.  Increased latency: about 1 segment.</span>

<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">

<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The non-NACK (call it CP-only) system will send the whole block and then a CP, which will elicit a RS and cause the hole to be filled.  Adds 1 RTT (and 1 retransmitted segment) to the block.</span><o:p></o:p></li></ul>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span>

<o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">So the NACK system can save an RTT.  If the loss rate is small (say, the probability of filling all holes in one CP/RS/ReTX event is high) then that’s really all it saves,

 regardless of the number of losses in the block.  If the loss rate is high enough that the expected number of CP/RS/ReTX cycles is higher, the benefit is greater).</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">So in general if there are N segments and p(segment loss) is p, the number of retransmission rounds should be about -log(N)/log(p) + 1</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">N = 10,000</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">P = 0.1</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"># rounds: 5</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">N = 10,000</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">P = 0.01</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"># rounds: 3</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">So a proactive-NACK implementation could potentially save about 5 RTTs over a CP-only implementation (sort of a blatent assumption that none of the losses are ‘too close’

 to the end, but hey).</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">                                v/r,</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">                                --keith</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">On 4/4/22, 1:57 PM, "Carlo Caini" <</span><a href="mailto:carlo.caini@unibo.it"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">carlo.caini@unibo.it</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>

 wrote:</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Dear all,</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">       on terrestrial applications LTP segment may arrive out of order, thus NACK could result in unecessary retranmissions; maybe this is not a problem as it is the same

 in TCP (fast retransmit cannot tolerate more than a disorder of 3 TCP segments).</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    In space, maybe we can assume ordered delivery of LTP segment, thus is true that the LTP receiver could immediately send a NACK as soon as a gap is found (i.e. at the

 first non contigous claim rfeceived), instead of waiting for the CP, thus saving some time; however, the advantage is limited. If we call radiation time the time necessary to tranmit "on air" a block, we could say that the NACK time gain should be on the evarage

 of about a half of the radiatrion time. This saved time should however be compared with the RTT, wich is the minimum time necessary for loss recovery. RTT in space is usually >> radiation time, thus the advantage would be negligible. Maybe it could be useful

 on LEO, where the RTT is small, but we should also have large blocks and slow links...</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Yours,</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">       Carlo</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    ________________________________________</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Da:

</span><a href="mailto:Tomaso.deCola@dlr.de"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">Tomaso.deCola@dlr.de</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> [Tomaso.deCola@dlr.de]</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Inviato: lunedi 4 aprile 2022 17:54</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    A:

</span><a href="mailto:kscott@mitre.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">kscott@mitre.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">;

</span><a href="mailto:sburleig.sb@gmail.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sburleig.sb@gmail.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">; Carlo Caini;

</span><a href="mailto:chkoo@kari.re.kr"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">chkoo@kari.re.kr</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">;

</span><a href="mailto:dstanton@keltik.co.uk"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">dstanton@keltik.co.uk</span></a><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Cc:

</span><a href="mailto:sis-dtn@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org</span></a><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Oggetto: RE: [Sis-dtn] [EXT] Re: Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    (I cc again the whole SIS-DTN mailinglist that apparently disappeared from my initial message)</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    At first glance I don’t see a space network configuration in which the LTP segments belonging to a given LTP block could arrived misordered. Perhaps if LTP is operated

 over UDP also in space (the current spec does not prohibit it to the best of my memory) this could happen but I’d say it is an unlikely configuration.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Tomaso</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    From: Dr. Keith L Scott <</span><a href="mailto:kscott@mitre.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">kscott@mitre.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Sent: Montag, 4. April 2022 17:43</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    To:

</span><a href="mailto:sburleig.sb@gmail.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sburleig.sb@gmail.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">; Cola, Tomaso de <</span><a href="mailto:Tomaso.deCola@dlr.de"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">Tomaso.deCola@dlr.de</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>;

</span><a href="mailto:carlo.caini@unibo.it"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">carlo.caini@unibo.it</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">;

</span><a href="mailto:chkoo@kari.re.kr"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">chkoo@kari.re.kr</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">;

</span><a href="mailto:dstanton@keltik.co.uk"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">dstanton@keltik.co.uk</span></a><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Subject: Re: [Sis-dtn] [EXT] Re: Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    But for CCSDS applications (and LTPv2 is a CCSDS thing not an IETF thing) maybe we make the assumption that segments are not misordered?  Or that the misordering is ‘small’

 so that some sort of timer / couter at the receiver could filter out small anomalies?  (e.g. hold off sending a NACK for 1,000 segments)?</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">                    --keith</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    From: "</span><a href="mailto:sburleig.sb@gmail.com%3cmailto:sburleig.sb@gmail.com%3e"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sburleig.sb@gmail.com<mailto:sburleig.sb@gmail.com></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">"

 <</span><a href="mailto:sburleig.sb@gmail.com%3cmailto:sburleig.sb@gmail.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sburleig.sb@gmail.com<mailto:sburleig.sb@gmail.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Date: Monday, April 4, 2022 at 11:39 AM</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    To: Tomaso de Cola <</span><a href="mailto:Tomaso.deCola@dlr.de%3cmailto:Tomaso.deCola@dlr.de"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">Tomaso.deCola@dlr.de<mailto:Tomaso.deCola@dlr.de</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>,

 Keith Scott <</span><a href="mailto:kscott@mitre.org%3cmailto:kscott@mitre.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">kscott@mitre.org<mailto:kscott@mitre.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>,

 "</span><a href="mailto:carlo.caini@unibo.it%3cmailto:carlo.caini@unibo.it%3e"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">carlo.caini@unibo.it<mailto:carlo.caini@unibo.it></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">"

 <</span><a href="mailto:carlo.caini@unibo.it%3cmailto:carlo.caini@unibo.it"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">carlo.caini@unibo.it<mailto:carlo.caini@unibo.it</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>,

 Cheol Koo <</span><a href="mailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">chkoo@kari.re.kr<mailto:chkoo@kari.re.kr</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>,

 Dai Stanton <</span><a href="mailto:dstanton@keltik.co.uk%3cmailto:dstanton@keltik.co.uk"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">dstanton@keltik.co.uk<mailto:dstanton@keltik.co.uk</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Subject: RE: [Sis-dtn] [EXT] Re: Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Yes, and for good reason: the design of LTP was originally lifted directly from the CFDP Acknowledged Procedures (and thereupon tweaked a bit).  I think the argument against

 proactively reporting negative DS reception claims was that the missing segments might be already en route but slightly delayed due to transmission over a longer path.  In space flight communications this won’t happen because LTP will be running directly over

 the link; when we test LTP on Earth it is somewhat more likely, as LTP is running directly over UDP/IP and in theory those packets might travel over multiple different routes.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Scott</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    From:

</span><a href="mailto:Tomaso.deCola@dlr.de%3cmailto:Tomaso.deCola@dlr.de"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">Tomaso.deCola@dlr.de<mailto:Tomaso.deCola@dlr.de</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>

 <</span><a href="mailto:Tomaso.deCola@dlr.de%3cmailto:Tomaso.deCola@dlr.de"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">Tomaso.deCola@dlr.de<mailto:Tomaso.deCola@dlr.de</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Sent: Monday, April 4, 2022 8:31 AM</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    To:

</span><a href="mailto:kscott@mitre.org%3cmailto:kscott@mitre.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">kscott@mitre.org<mailto:kscott@mitre.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>;

</span><a href="mailto:sburleig.sb@gmail.com%3cmailto:sburleig.sb@gmail.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sburleig.sb@gmail.com<mailto:sburleig.sb@gmail.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>;

</span><a href="mailto:carlo.caini@unibo.it%3cmailto:carlo.caini@unibo.it"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">carlo.caini@unibo.it<mailto:carlo.caini@unibo.it</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>;

</span><a href="mailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">chkoo@kari.re.kr<mailto:chkoo@kari.re.kr</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>;

</span><a href="mailto:dstanton@keltik.co.uk%3cmailto:dstanton@keltik.co.uk"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">dstanton@keltik.co.uk<mailto:dstanton@keltik.co.uk</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Subject: RE: [Sis-dtn] [EXT] Re: Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    This looks similar to CFDP-class 2 with retransmission happening in asynchronous mode, isn’t it?</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Regards,</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Tomaso</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    From: SIS-DTN <</span><a href="mailto:sis-dtn-bounces@mailman.ccsds.org%3cmailto:sis-dtn-bounces@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn-bounces@mailman.ccsds.org<mailto:sis-dtn-bounces@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>

 On Behalf Of Dr. Keith L Scott via SIS-DTN</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Sent: Montag, 4. April 2022 17:28</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    To:

</span><a href="mailto:sburleig.sb@gmail.com%3cmailto:sburleig.sb@gmail.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sburleig.sb@gmail.com<mailto:sburleig.sb@gmail.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>;

 'Carlo Caini' <</span><a href="mailto:carlo.caini@unibo.it%3cmailto:carlo.caini@unibo.it"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">carlo.caini@unibo.it<mailto:carlo.caini@unibo.it</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>;

 '"</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">备枚雀</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">"' <</span><a href="mailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">chkoo@kari.re.kr<mailto:chkoo@kari.re.kr</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>;

 'Keltik' <</span><a href="mailto:dstanton@keltik.co.uk%3cmailto:dstanton@keltik.co.uk"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">dstanton@keltik.co.uk<mailto:dstanton@keltik.co.uk</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Cc:

</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Subject: Re: [Sis-dtn] [EXT] Re: Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    I think maybe a larger opportunity for improvement would be to have a capability for a receiver to proactively NACK segments WITHOUT having to receive a checkpoint first.

  That would allow autonomously sending NACKs during the block transmission (thereby filling holes quickly as they are detected) and then relying on the CP/RS/RA exchange to close out the session.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">                                    --keith</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    From: "</span><a href="mailto:sis-dtn-bounces@mailman.ccsds.org%3cmailto:sis-dtn-bounces@mailman.ccsds.org%3e"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn-bounces@mailman.ccsds.org<mailto:sis-dtn-bounces@mailman.ccsds.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">"

 <</span><a href="mailto:sis-dtn-bounces@mailman.ccsds.org%3cmailto:sis-dtn-bounces@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn-bounces@mailman.ccsds.org<mailto:sis-dtn-bounces@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>

 on behalf of "</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3e"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">"

 <</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Reply-To: "</span><a href="mailto:sburleig.sb@gmail.com%3cmailto:sburleig.sb@gmail.com%3e"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sburleig.sb@gmail.com<mailto:sburleig.sb@gmail.com></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">"

 <</span><a href="mailto:sburleig.sb@gmail.com%3cmailto:sburleig.sb@gmail.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sburleig.sb@gmail.com<mailto:sburleig.sb@gmail.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Date: Monday, April 4, 2022 at 11:21 AM</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    To: 'Carlo Caini' <</span><a href="mailto:carlo.caini@unibo.it%3cmailto:carlo.caini@unibo.it"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">carlo.caini@unibo.it<mailto:carlo.caini@unibo.it</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>,

 Cheol Koo <</span><a href="mailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">chkoo@kari.re.kr<mailto:chkoo@kari.re.kr</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>,

 Dai Stanton <</span><a href="mailto:dstanton@keltik.co.uk%3cmailto:dstanton@keltik.co.uk"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">dstanton@keltik.co.uk<mailto:dstanton@keltik.co.uk</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Cc: "</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3e"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">"

 <</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Subject: [EXT] Re: [Sis-dtn] Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Hi, guys.  I believe we are actually talking about two distinct things here.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    It is true that positive ACKs are required.  Positive acknowledgments turn off the retransmission timers for checkpoints, report segments, and cancellation segments.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Separately, the individual "claims" within a report segment might be either positive or negative.  I agree with Carlo, but think Cheol is correct that negative claims

 can yield a small overhead advantage.  For any LTP transmission whose scope is from block offset P to Q in which there are N gaps:</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    ?       If one of the gaps begins at P and another of the gaps ends at Q, then the report must contain either N negative claims or N - 1 positive claims.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    ?       If no gap begins at P and no gap ends at Q, then the report must contain either N negative claims or N + 1 positive claims.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    ?       If one of the gaps begins at P or one of the gaps ends at Q, but not both, then the report must contain either N negative claims or N positive claims.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    I would expect the second of these cases to occur more frequently than the other two, assuming AOS/LOS events don't occur during the transmission.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    I don't see how either negative or positive claims processing is simpler or easier, though; the representations are equivalent.  Ease of implementation would depend strictly

 on the manner in which segment information is stored and accessed at the sending and receiving ends of the transmission.  I personally found positive claims to be simpler to work with.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Scott</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    -----Original Message-----</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    From: SIS-DTN <</span><a href="mailto:sis-dtn-bounces@mailman.ccsds.org%3cmailto:sis-dtn-bounces@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn-bounces@mailman.ccsds.org<mailto:sis-dtn-bounces@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>

 On Behalf Of Carlo Caini via SIS-DTN</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Sent: Monday, April 4, 2022 5:47 AM</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    To: "</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">备枚雀</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">"

 <</span><a href="mailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">chkoo@kari.re.kr<mailto:chkoo@kari.re.kr</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>;

 Keltik <</span><a href="mailto:dstanton@keltik.co.uk%3cmailto:dstanton@keltik.co.uk"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">dstanton@keltik.co.uk<mailto:dstanton@keltik.co.uk</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Cc:

</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Subject: Re: [Sis-dtn] Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Dear Cheol,</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">         let me consider an LTP block with for example 20 non contigous losses, i.e. 20 gaps. The corresponding RS would include either 20 positive claims (if you have a gap

 at the start or at the end of the block) or 21 cl;aims otherwise.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    With NAK claim you would need 20 megative claims. Is that so different?</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    You can say that it is easier to resend what has been explicietely said is missing, true; however, on the rx side it is easier to say what has been received than what

 is missing; all things considered, I cannot see any signifiocant advantage by excplicietely declaring gaps instead of received chunks.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Yours,</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">       Carlo</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    ________________________________________</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Da: SIS-DTN [sis-dtn-bounces@mailman.ccsds.org] per conto di "</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">备枚雀</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">"

 via SIS-DTN [sis-dtn@mailman.ccsds.org]</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Inviato: lunedi 4 aprile 2022 14:20</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    A: Keltik</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Cc:

</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Oggetto: Re: [Sis-dtn] Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    I think current LTP spec has positive ACK and negative ACK both. So if it is reversed the result will be the same.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Let me bring below example again. To provide claim inforamtion for retransmission of block 1000-2999,</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    <<original-positive ACK>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    lower bound = 0</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    upper bound = 7000</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    negative reception claim count = 2</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    offset = 0      <-- Positive ACK</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    length = 1000  <-- Positive ACK</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    offset = 3000  <-- Positive ACK</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    length = 4000  <-- Positive ACK</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    * Negative ACKs are hidden in separated Positive ACKs.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    <<negative ACK>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    lower bound = 0       <-- Positive ACK</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    upper bound = 7000   <-- Positive ACK</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    negative reception claim count = 1</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    offset = 1000  <-- Negative ACK</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    length = 2000  <-- Negative ACK</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    I think the latter case can work too! Or am I missing something?</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Cheol</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    ---------

</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">盔夯</span><span lang="KO" style="font-size:11.0pt;font-family:"Calibri",sans-serif">

</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">皋老</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> ---------</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">   

</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">焊辰荤恩</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> : Keltik <</span><a href="mailto:dstanton@keltik.co.uk%3cmailto:dstanton@keltik.co.uk"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">dstanton@keltik.co.uk<mailto:dstanton@keltik.co.uk</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">   

</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">罐绰荤恩</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> : Vint Cerf <</span><a href="mailto:vint@google.com%3cmailto:vint@google.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">vint@google.com<mailto:vint@google.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">   

</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">曼炼</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> : <</span><a href="mailto:Felix.Flentge@esa.int%3cmailto:Felix.Flentge@esa.int"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">Felix.Flentge@esa.int<mailto:Felix.Flentge@esa.int</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>,

 <</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>,

 "</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">备枚雀</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">" <</span><a href="mailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">chkoo@kari.re.kr<mailto:chkoo@kari.re.kr</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>

</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">罐篮朝楼</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> : 2022-04-04 (</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">岿</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">)

 19:53:46 </span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">力格</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> : Re: [Sis-dtn] Positive reception claim vs. Negative reception claim in LTP Report Segment

 preparation and processing Scott Burleigh and I went through this developing CFDP/LTP three decades ago. Whilst Negative ACKs can be very efficient for bulk data in the delay/disruption environment, protocol directives such as initiation, metadata exchange,

 end of data, end of transaction, pause, resume etc require positive ACKs. Otherwise the state machines will never close.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Dai</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Sent from my iPhone</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    On 4 Apr 2022, at 11:09, Vint Cerf via SIS-DTN <</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>

 wrote:</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    a system based solely on negative acks will not work.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    v</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    On Mon, Apr 4, 2022 at 6:08 AM Felix Flentge via SIS-DTN <</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>>

 wrote:</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Ah, yes, of course you are right.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    We will look into the negative ACK as part of our LTPv2 prototyping activity.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Regards,</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Felix</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    From:        "</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">备枚雀</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">"

 <</span><a href="mailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">chkoo@kari.re.kr<mailto:chkoo@kari.re.kr<mailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    To:        <</span><a href="mailto:Felix.Flentge@esa.int%3cmailto:Felix.Flentge@esa.int%3cmailto:Felix.Flentge@esa.int%3cmailto:Felix.Flentge@esa.int"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">Felix.Flentge@esa.int<mailto:Felix.Flentge@esa.int<mailto:Felix.Flentge@esa.int%3cmailto:Felix.Flentge@esa.int</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Cc:        "</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3e%3cmailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3e%3e"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org><mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3e></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">"

 <</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Date:        04/04/2022 11:58</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Subject:        RE: Re: [Sis-dtn] Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Sent by:        </span><a href="mailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">chkoo@kari.re.kr<mailto:chkoo@kari.re.kr<mailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    ________________________________</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Hi Felix,</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    I think current LTP spec quite works well with negative claim also. Consider below reception claim according to the LTP spec but negative claim.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    lower bound = 0</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    upper bound = 7000</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    negative reception claim count = 1</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    offset = 1000</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    length = 2000</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    it means a receiver is requesting block of segements which starts at 1000 and length is 2000, i.e., 1000 ~ 2999, for retransmission.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    A sender can safely remove 2 blocks, i.e., 0 - 999 and 3000 - 7000. I think it is simpler, lower overhead and *importantly* easier to calculate (acutally no painful for

 localizing the target segment position).</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Cheol</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    ---------

</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">盔夯</span><span lang="KO" style="font-size:11.0pt;font-family:"Calibri",sans-serif">

</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">皋老</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> ---------</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">   

</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">焊辰荤恩</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> : <</span><a href="mailto:Felix.Flentge@esa.int%3cmailto:Felix.Flentge@esa.int%3cmailto:Felix.Flentge@esa.int%3cmailto:Felix.Flentge@esa.int"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">Felix.Flentge@esa.int<mailto:Felix.Flentge@esa.int<mailto:Felix.Flentge@esa.int%3cmailto:Felix.Flentge@esa.int</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">   

</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">罐绰荤恩</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> : "</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">备枚雀</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">"

 <</span><a href="mailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">chkoo@kari.re.kr<mailto:chkoo@kari.re.kr<mailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">   

</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">曼炼</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> : "</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3e%3cmailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3e%3e"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org><mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3e></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">"

 <</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">   

</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">罐篮朝楼</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> : 2022-04-04 (</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">岿</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">)

 17:40:24</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">   

</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">力格</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> : Re: [Sis-dtn] Positive reception claim vs. Negative reception claim in LTP Report Segment preparation

 and processing Hi Cheol,</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    interesting question. One thing I can think of is that the positive claims would allow you to free memory earlier while for negative claims you need to wait until the

 end of a session.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Regards,</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Felix</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    From:        "</span><span lang="KO" style="font-size:11.0pt;font-family:"Malgun Gothic",sans-serif">备枚雀</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">

 via SIS-DTN" <</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    To:        "</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3e%3cmailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3e%3e"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org><mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3e></span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">"

 <</span><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Date:        04/04/2022 10:15</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Subject:        [Sis-dtn] Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Sent by:        "SIS-DTN" <</span><a href="mailto:sis-dtn-bounces@mailman.ccsds.org%3cmailto:sis-dtn-bounces@mailman.ccsds.org%3cmailto:sis-dtn-bounces@mailman.ccsds.org%3cmailto:sis-dtn-bounces@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">sis-dtn-bounces@mailman.ccsds.org<mailto:sis-dtn-bounces@mailman.ccsds.org<mailto:sis-dtn-bounces@mailman.ccsds.org%3cmailto:sis-dtn-bounces@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    ________________________________</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Greetings,</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    This is Cheol. I am developing an LTP reference implementation. During reading the LTP specification (RFC-5326), the preparation of reception claim in Report Segment makes

 me confusing about why it is positive claim not negative claim for segments that were not received successfully (i.e., NAK).</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    For reference, CFDP’s NAK PDU has the negative claim structure when it is requested to report missing PDUs. Does anyone know about the background of choosing the positive

 claim for NAK operation in LTP?</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    I think negative claim is simpler and more efficient in terms of overhead for sender and receiver both.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    I like to listen experts’ opinion on LTP operation and honestly hope it to be changed in newly coming LTP spec.</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Cheol</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    _______________________________________________</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    SIS-DTN mailing list</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">   

</span><a href="mailto:SIS-DTN@mailman.ccsds.org%3cmailto:SIS-DTN@mailman.ccsds.org%3cmailto:SIS-DTN@mailman.ccsds.org%3cmailto:SIS-DTN@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">SIS-DTN@mailman.ccsds.org<mailto:SIS-DTN@mailman.ccsds.org<mailto:SIS-DTN@mailman.ccsds.org%3cmailto:SIS-DTN@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">   

</span><a href="https://protect2.fireeye.com/v1/url?k=7094fbf6-2f0f91fe-70918a78-ac1f6bdccbcc-0d3d8ac66f4934b2&q=1&e=42cf6e42-dd3d-47b5-ab7c-ec8488c70286&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn%253chttps%3A%2Fprotect2.fireeye.com%2Fv1%2Furl%3Fk%3D933edf14-cca5b51c-933bae9a-ac1f6bdccbcc-93bc8ad36316533d%26q%3D1%26e%3D24a03daf-8e73-4317-a689-3216c529ea83%26u%3Dhttps%253A%252F%252Fmailman.ccsds.org%252Fcgi-bin%252Fmailman%252Flistinfo%252Fsis-dtn%253chttps%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn%253chttps%3A%2Fprotect2.fireeye.com%2Fv1%2Furl%3Fk%3D933edf14-cca5b51c-933bae9a-ac1f6bdccbcc-93bc8ad36316533d%26q%3D1%26e%3D24a03daf-8e73-4317-a689-3216c529ea83%26u%3Dhttps%253A%252F%252Fmailman.ccsds.org%252Fcgi-bin%252Fmailman%252Flistinfo%252Fsis-dtn"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn<https://protect2.fireeye.com/v1/url

 ?k=933edf14-cca5b51c-933bae9a-ac1f6bdccbcc-93bc8ad36316533d&q=1&e=24a03daf-8e73-4317-a689-3216c529ea83&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn<https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn%3chttps:/protect2.fireeye.com/v1/url?k=933edf14-cca5b51c-933bae9a-ac1f6bdccbcc-93bc8ad36316533d&q=1&e=24a03daf-8e73-4317-a689-3216c529ea83&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    _______________________________________________</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    SIS-DTN mailing list</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">   

</span><a href="mailto:SIS-DTN@mailman.ccsds.org%3cmailto:SIS-DTN@mailman.ccsds.org%3cmailto:SIS-DTN@mailman.ccsds.org%3cmailto:SIS-DTN@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">SIS-DTN@mailman.ccsds.org<mailto:SIS-DTN@mailman.ccsds.org<mailto:SIS-DTN@mailman.ccsds.org%3cmailto:SIS-DTN@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">   

</span><a href="https://protect2.fireeye.com/v1/url?k=ef21fc5e-b0ba9656-ef248dd0-ac1f6bdccbcc-64b6674f7e819d0e&q=1&e=42cf6e42-dd3d-47b5-ab7c-ec8488c70286&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn%253chttps%3A%2Fprotect2.fireeye.com%2Fv1%2Furl%3Fk%3D60e1ef17-3f7a851f-60e49e99-ac1f6bdccbcc-0dfe5136ab6b73dc%26q%3D1%26e%3Dcce8b1e1-1ec2-4cdd-855b-994c9a3f58c9%26u%3Dhttps%253A%252F%252Fmailman.ccsds.org%252Fcgi-bin%252Fmailman%252Flistinfo%252Fsis-dtn%253chttps%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn%253chttps%3A%2Fprotect2.fireeye.com%2Fv1%2Furl%3Fk%3D60e1ef17-3f7a851f-60e49e99-ac1f6bdccbcc-0dfe5136ab6b73dc%26q%3D1%26e%3Dcce8b1e1-1ec2-4cdd-855b-994c9a3f58c9%26u%3Dhttps%253A%252F%252Fmailman.ccsds.org%252Fcgi-bin%252Fmailman%252Flistinfo%252Fsis-dtn"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn<https://protect2.fireeye.com/v1/url

 ?k=60e1ef17-3f7a851f-60e49e99-ac1f6bdccbcc-0dfe5136ab6b73dc&q=1&e=cce8b1e1-1ec2-4cdd-855b-994c9a3f58c9&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn<https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn%3chttps:/protect2.fireeye.com/v1/url?k=60e1ef17-3f7a851f-60e49e99-ac1f6bdccbcc-0dfe5136ab6b73dc&q=1&e=cce8b1e1-1ec2-4cdd-855b-994c9a3f58c9&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    --</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Please send any postal/overnight deliveries to:</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    Vint Cerf</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    1435 Woodhurst Blvd</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    McLean, VA 22102</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    703-448-0965</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    until further notice</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    _______________________________________________</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    SIS-DTN mailing list</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">   

</span><a href="mailto:SIS-DTN@mailman.ccsds.org%3cmailto:SIS-DTN@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">SIS-DTN@mailman.ccsds.org<mailto:SIS-DTN@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">   

</span><a href="https://protect2.fireeye.com/v1/url?k=12719fd8-4deaf5d0-1274ee56-ac1f6bdccbcc-05a7930b38352e56&q=1&e=42cf6e42-dd3d-47b5-ab7c-ec8488c70286&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn%253chttps%3A%2Fprotect2.fireeye.com%2Fv1%2Furl%3Fk%3D9ac1f10e-c55a9b06-9ac48080-ac1f6bdccbcc-60db088d278d85f7%26q%3D1%26e%3Dcce8b1e1-1ec2-4cdd-855b-994c9a3f58c9%26u%3Dhttps%253A%252F%252Fmailman.ccsds.org%252Fcgi-bin%252Fmailman%252Flistinfo%252Fsis-dtn%253chttps%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn%253chttps%3A%2Fprotect2.fireeye.com%2Fv1%2Furl%3Fk%3D9ac1f10e-c55a9b06-9ac48080-ac1f6bdccbcc-60db088d278d85f7%26q%3D1%26e%3Dcce8b1e1-1ec2-4cdd-855b-994c9a3f58c9%26u%3Dhttps%253A%252F%252Fmailman.ccsds.org%252Fcgi-bin%252Fmailman%252Flistinfo%252Fsis-dtn"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn<https://protect2.fireeye.com/v1/url

 ?k=9ac1f10e-c55a9b06-9ac48080-ac1f6bdccbcc-60db088d278d85f7&q=1&e=cce8b1e1-1ec2-4cdd-855b-994c9a3f58c9&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn<https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn%3chttps:/protect2.fireeye.com/v1/url?k=9ac1f10e-c55a9b06-9ac48080-ac1f6bdccbcc-60db088d278d85f7&q=1&e=cce8b1e1-1ec2-4cdd-855b-994c9a3f58c9&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    _______________________________________________</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">    SIS-DTN mailing list</span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">   

</span><a href="mailto:SIS-DTN@mailman.ccsds.org%3cmailto:SIS-DTN@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">SIS-DTN@mailman.ccsds.org<mailto:SIS-DTN@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">></span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">   

</span><a href="https://protect2.fireeye.com/v1/url?k=cad01285-954b788d-cad5630b-ac1f6bdccbcc-4b400b0669265909&q=1&e=42cf6e42-dd3d-47b5-ab7c-ec8488c70286&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn</span></a><o:p></o:p></p>

<p style="margin:0in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:GulimChe"><br>

<tt>SIS-DTN mailing list</tt><br>

<tt><a href="mailto:SIS-DTN@mailman.ccsds.org">SIS-DTN@mailman.ccsds.org</a></tt><br>

</span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn</span></tt></a><o:p></o:p></p>

</div>

</body>

</html>