<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<title>RE: [Sis-dtn] Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</title>
<style><!--
/* Font Definitions */
@font-face
{font-family:굴림;
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:"맑은 고딕";
panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
{font-family:"\@맑은 고딕";}
@font-face
{font-family:"\@굴림";
panose-1:2 11 6 0 0 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:12.0pt;
font-family:굴림;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-compose;
font-family:"맑은 고딕";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:3.0cm 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="KO" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">Hi Scott. Good points.<o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">I think extractable information from below examples of ACK/NACK are identical. The ease of interpretation to the structure of ACK/NACK surely
depends on implementation specific. For me, the NACK is simpler to process like as
</span><span style="font-size:10.0pt;font-family:"맑은 고딕"">“<span lang="EN-US">I am 30</span>”<span lang="EN-US"> is simpler answer than
</span>“<span lang="EN-US">I am 2022 </span>–<span lang="EN-US"> 1992</span>”<span lang="EN-US"> for a question of
</span>“<span lang="EN-US">How old are you?</span>”<span lang="EN-US">.<o:p></o:p></span></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕""><o:p> </o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">Cheol<o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕""><o:p> </o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕""><<original-positive ACK>><o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">lower bound = 0<o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">upper bound = 7000<o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">positive reception claim count = 2<o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">offset = 0 <-- Positive ACK<o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">length = 1000 <-- Positive ACK<o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">offset = 3000 <-- Positive ACK<o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">length = 4000 <-- Positive ACK<o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">* Negative ACKs are hidden in separated Positive ACKs.<o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕""><o:p> </o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕""><<negative ACK>><o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">lower bound = 0 <-- Positive ACK<o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">upper bound = 7000 <-- Positive ACK<o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">negative reception claim count = 1<o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">offset = 1000 <-- Negative ACK<o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕"">length = 2000 <-- Negative ACK<o:p></o:p></span></p>
<p class="MsoNormal" style="word-break:break-hangul"><span lang="EN-US" style="font-size:10.0pt;font-family:"맑은 고딕""><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> sburleig.sb@gmail.com <sburleig.sb@gmail.com>
<br>
<b>Sent:</b> Tuesday, April 5, 2022 12:21 AM<br>
<b>To:</b> Carlo Caini <carlo.caini@unibo.it>; </span><span style="font-size:11.0pt">구철회</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <chkoo@kari.re.kr>; Keltik <dstanton@keltik.co.uk><br>
<b>Cc:</b> sis-dtn@mailman.ccsds.org<br>
<b>Subject:</b> RE: [Sis-dtn] Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Hi, guys. I believe we are actually talking about two distinct things here.</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">It is</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">true that</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">positive ACKs are required. </span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">Positive acknowledgments</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">turn off the retransmission timers for checkpoints, report segments, and cancellation segments.</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Separately, the</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">individual "claims" within a report segment might be either positive or negative.</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">I</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">agree with Carlo, but</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">think</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">Cheol is correct that negative claims</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">can</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">yield a small overhead advantage. For any</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">LTP</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">transmission</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">whose</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">scope is from block offset P to Q in which there are N gaps:</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:Symbol">·</span><span lang="EN-US" style="font-family:"Courier New""> </span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">If one of the gaps begins at P and</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">another of the gaps ends at Q, then the report must contain either N negative claims or</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">N - 1 positive claims.</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:Symbol">·</span><span lang="EN-US" style="font-family:"Courier New""> </span><span lang="EN-US">
</span><span lang="EN-US" style="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><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:Symbol">·</span><span lang="EN-US" style="font-family:"Courier New""> </span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">If one of the gaps begins</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">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><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">I would</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">expect the second of these cases to occur more frequently than the other two, assuming AOS/LOS</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">events don't occur during the transmission.</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">I don't see how either negative or positive claims processing is simpler or</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">easier, though; the representations are equivalent. Ease of implementation would</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">depend strictly on the manner in which</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">segment</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">information is stored and</span><span lang="EN-US">
</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">accessed at the sending and receiving ends of the transmission. I personally found positive claims to be simpler to work with.</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Scott</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">-----Original Message-----<br>
From: SIS-DTN <<a href="mailto:sis-dtn-bounces@mailman.ccsds.org">sis-dtn-bounces@mailman.ccsds.org</a>> On Behalf Of Carlo Caini via SIS-DTN<br>
Sent: Monday, April 4, 2022 5:47 AM<br>
To: "</span><span style="font-family:"맑은 고딕"">구철회</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">" <<a href="mailto:chkoo@kari.re.kr">chkoo@kari.re.kr</a>>; Keltik <<a href="mailto:dstanton@keltik.co.uk">dstanton@keltik.co.uk</a>><br>
Cc: <a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a><br>
Subject: Re: [Sis-dtn] Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Dear Cheol,</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="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><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">With NAK claim you would need 20 megative claims. Is that so different?</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="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><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Yours,</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif"> Carlo</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">________________________________________</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Da: SIS-DTN [sis-dtn-bounces@mailman.ccsds.org] per conto di "</span><span style="font-family:"맑은 고딕"">구철회</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">" via SIS-DTN [sis-dtn@mailman.ccsds.org]</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Inviato: lunedì 4 aprile 2022 14:20</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">A: Keltik</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Cc:</span><span lang="EN-US">
<a href="mailto:sis-dtn@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">sis-dtn@mailman.ccsds.org</span></a><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Oggetto: Re: [Sis-dtn] Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="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><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Let me bring below example again. To provide claim inforamtion for retransmission of block 1000-2999,</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif"><<original-positive ACK>></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">lower bound = 0</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">upper bound = 7000</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">negative reception claim count = 2</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">offset = 0 <-- Positive ACK</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">length = 1000 <-- Positive ACK</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">offset = 3000 <-- Positive ACK</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">length = 4000 <-- Positive ACK</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">* Negative ACKs are hidden in separated Positive ACKs.</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif"><<negative ACK>></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">lower bound = 0 <-- Positive ACK</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">upper bound = 7000 <-- Positive ACK</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">negative reception claim count = 1</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">offset = 1000 <-- Negative ACK</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">length = 2000 <-- Negative ACK</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">I think the latter case can work too! Or am I missing something?</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Cheol</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">---------</span><span lang="EN-US">
</span><span style="font-family:"맑은 고딕"">원본</span> <span style="font-family:"맑은 고딕"">
메일</span><span lang="EN-US" style="font-family:"Calibri",sans-serif"> ---------</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span style="font-family:"맑은 고딕"">보낸사람</span><span lang="EN-US" style="font-family:"Calibri",sans-serif"> : Keltik <</span><span lang="EN-US"><a href="mailto:dstanton@keltik.co.uk"><span style="font-family:"Calibri",sans-serif">dstanton@keltik.co.uk</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span style="font-family:"맑은 고딕"">받는사람</span><span lang="EN-US" style="font-family:"Calibri",sans-serif"> : Vint Cerf <</span><span lang="EN-US"><a href="mailto:vint@google.com"><span style="font-family:"Calibri",sans-serif">vint@google.com</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span style="font-family:"맑은 고딕"">참조</span><span lang="EN-US" style="font-family:"Calibri",sans-serif"> : <</span><span lang="EN-US"><a href="mailto:Felix.Flentge@esa.int"><span style="font-family:"Calibri",sans-serif">Felix.Flentge@esa.int</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">>,
<</span><span lang="EN-US"><a href="mailto:sis-dtn@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">sis-dtn@mailman.ccsds.org</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">>, "</span><span style="font-family:"맑은 고딕"">구철회</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">"
<</span><span lang="EN-US"><a href="mailto:chkoo@kari.re.kr"><span style="font-family:"Calibri",sans-serif">chkoo@kari.re.kr</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">></span><span lang="EN-US">
</span><span style="font-family:"맑은 고딕"">받은날짜</span><span lang="EN-US" style="font-family:"Calibri",sans-serif"> : 2022-04-04 (</span><span style="font-family:"맑은 고딕"">월</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">) 19:53:46</span><span lang="EN-US">
</span><span style="font-family:"맑은 고딕"">제목</span><span style="font-family:"Calibri",sans-serif">
<span lang="EN-US">: 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></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Dai</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Sent from my iPhone</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">On 4 Apr 2022, at 11:09, Vint Cerf via SIS-DTN <</span><span lang="EN-US"><a href="mailto:sis-dtn@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">sis-dtn@mailman.ccsds.org</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">>
wrote:</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">a system based solely on negative acks will not work.</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">v</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">On Mon, Apr 4, 2022 at 6:08 AM Felix Flentge via SIS-DTN <</span><span lang="EN-US"><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">>>
wrote:</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Ah, yes, of course you are right.</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">We will look into the negative ACK as part of our LTPv2 prototyping activity.</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Regards,</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Felix</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">From: "</span><span style="font-family:"맑은 고딕"">구철회</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">" <</span><span lang="EN-US"><a href="mailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr"><span style="font-family:"Calibri",sans-serif">chkoo@kari.re.kr<mailto:chkoo@kari.re.kr</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">>></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">To: <</span><span lang="EN-US"><a href="mailto:Felix.Flentge@esa.int%3cmailto:Felix.Flentge@esa.int"><span style="font-family:"Calibri",sans-serif">Felix.Flentge@esa.int<mailto:Felix.Flentge@esa.int</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">>></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Cc: "</span><span lang="EN-US"><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3e"><span style="font-family:"Calibri",sans-serif">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org></span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">"
<</span><span lang="EN-US"><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">>></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Date: 04/04/2022 11:58</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="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><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Sent by: </span><span lang="EN-US">
<a href="mailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr"><span style="font-family:"Calibri",sans-serif">chkoo@kari.re.kr<mailto:chkoo@kari.re.kr</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">________________________________</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Hi Felix,</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="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><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">lower bound = 0</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">upper bound = 7000</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">negative reception claim count = 1</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">offset = 1000</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">length = 2000</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="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><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="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><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Cheol</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">---------</span><span lang="EN-US">
</span><span style="font-family:"맑은 고딕"">원본</span> <span style="font-family:"맑은 고딕"">
메일</span><span lang="EN-US" style="font-family:"Calibri",sans-serif"> ---------</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span style="font-family:"맑은 고딕"">보낸사람</span><span lang="EN-US" style="font-family:"Calibri",sans-serif"> : <</span><span lang="EN-US"><a href="mailto:Felix.Flentge@esa.int%3cmailto:Felix.Flentge@esa.int"><span style="font-family:"Calibri",sans-serif">Felix.Flentge@esa.int<mailto:Felix.Flentge@esa.int</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">>></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span style="font-family:"맑은 고딕"">받는사람</span><span lang="EN-US" style="font-family:"Calibri",sans-serif"> : "</span><span style="font-family:"맑은 고딕"">구철회</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">" <</span><span lang="EN-US"><a href="mailto:chkoo@kari.re.kr%3cmailto:chkoo@kari.re.kr"><span style="font-family:"Calibri",sans-serif">chkoo@kari.re.kr<mailto:chkoo@kari.re.kr</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">>></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span style="font-family:"맑은 고딕"">참조</span><span lang="EN-US" style="font-family:"Calibri",sans-serif"> : "</span><span lang="EN-US"><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3e"><span style="font-family:"Calibri",sans-serif">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org></span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">"
<</span><span lang="EN-US"><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">>></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span style="font-family:"맑은 고딕"">받은날짜</span><span lang="EN-US" style="font-family:"Calibri",sans-serif"> : 2022-04-04 (</span><span style="font-family:"맑은 고딕"">월</span><span lang="EN-US" style="font-family:"Calibri",sans-serif">) 17:40:24</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span style="font-family:"맑은 고딕"">제목</span><span lang="EN-US" style="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><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="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><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Regards,</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Felix</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">From: "</span><span style="font-family:"맑은 고딕"">구철회</span><span lang="EN-US" style="font-family:"Calibri",sans-serif"> via SIS-DTN" <</span><span lang="EN-US"><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">>></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">To: "</span><span lang="EN-US"><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org%3e"><span style="font-family:"Calibri",sans-serif">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org></span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">"
<</span><span lang="EN-US"><a href="mailto:sis-dtn@mailman.ccsds.org%3cmailto:sis-dtn@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">sis-dtn@mailman.ccsds.org<mailto:sis-dtn@mailman.ccsds.org</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">>></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Date: 04/04/2022 10:15</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Subject: [Sis-dtn] Positive reception claim vs. Negative reception claim in LTP Report Segment preparation and processing</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Sent by: "SIS-DTN" <</span><span lang="EN-US"><a href="mailto:sis-dtn-bounces@mailman.ccsds.org%3cmailto:sis-dtn-bounces@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">sis-dtn-bounces@mailman.ccsds.org<mailto:sis-dtn-bounces@mailman.ccsds.org</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">>></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">________________________________</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Greetings,</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="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><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="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><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">I think negative claim is simpler and more efficient in terms of overhead for sender and receiver both.</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="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><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Cheol</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">_______________________________________________</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">SIS-DTN mailing list</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US"><a href="mailto:SIS-DTN@mailman.ccsds.org%3cmailto:SIS-DTN@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">SIS-DTN@mailman.ccsds.org<mailto:SIS-DTN@mailman.ccsds.org</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US"><a href="https://protect2.fireeye.com/v1/url?k=e422173d-bbb97d35-e42766b3-ac1f6bdccbcc-4b540ed55d92467b&q=1&e=3024f3a3-fe85-45f2-9395-b08474fca82b&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn%253Chttps%3A%2F%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-family:"Calibri",sans-serif">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</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">></span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><br>
<br>
<o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">_______________________________________________</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">SIS-DTN mailing list</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US"><a href="mailto:SIS-DTN@mailman.ccsds.org%3cmailto:SIS-DTN@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">SIS-DTN@mailman.ccsds.org<mailto:SIS-DTN@mailman.ccsds.org</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US"><a href="https://protect2.fireeye.com/v1/url?k=273af622-78a19c2a-273f87ac-ac1f6bdccbcc-23cd9ab632b5de33&q=1&e=3024f3a3-fe85-45f2-9395-b08474fca82b&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn%253Chttps%3A%2F%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-family:"Calibri",sans-serif">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</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">></span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">--</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Please send any postal/overnight deliveries to:</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">Vint Cerf</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">1435 Woodhurst Blvd</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">McLean, VA 22102</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">703-448-0965</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">until further notice</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">_______________________________________________</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">SIS-DTN mailing list</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US"><a href="mailto:SIS-DTN@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">SIS-DTN@mailman.ccsds.org</span></a><o:p></o:p></span></p>
<p><span lang="EN-US"><a href="https://protect2.fireeye.com/v1/url?k=539dafc6-0c06c5ce-5398de48-ac1f6bdccbcc-f00c25077ab52195&q=1&e=3024f3a3-fe85-45f2-9395-b08474fca82b&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn%253Chttps%3A%2F%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-family:"Calibri",sans-serif">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</span></a></span><span lang="EN-US" style="font-family:"Calibri",sans-serif">></span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">_______________________________________________</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Calibri",sans-serif">SIS-DTN mailing list</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US"><a href="mailto:SIS-DTN@mailman.ccsds.org"><span style="font-family:"Calibri",sans-serif">SIS-DTN@mailman.ccsds.org</span></a><o:p></o:p></span></p>
<p><span lang="EN-US"><a href="https://protect2.fireeye.com/v1/url?k=7d5619d2-22cd73da-7d53685c-ac1f6bdccbcc-ee6706c0130a4314&q=1&e=3024f3a3-fe85-45f2-9395-b08474fca82b&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn"><span style="font-family:"Calibri",sans-serif">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn</span></a><o:p></o:p></span></p>
</div>
</body>
</html>