[Sis-dtn] LTP Corrigendum

[구철회]

Hi Keith.

Thanks for the update! You may want to remove title style for the long explanatory wordings such as 3.10.3 and so on.

IMHO, the contents of green-part data should be self-explanatory so that an application using the green-part data can properly handle the unstable and unreliable stream of data when link disruption or suspension occurs, regardless of whether it carries the same session identifiers or not.

If SENDER or RECEIVER needs the same session identifiers to resume the interrupted operation, I think it works close to the "Orange session" (refer, Multicolor Licklider Transmission Protocol: an LTP version for future interplanetary links, 2021, by ANDREA BISACCHI et al.) because in that case SENDER or RECEIVER needs to know the information for necessary graceful recovery actions for suspension or link disruption during green-part data reception.


Cheol



Message: 1
Date: Thu, 13 Jul 2023 11:05:24 +0200
From: Keith Scott <keithlscott at gmail.com>
To: sis-dtn at mailman.ccsds.org
Subject: [Sis-dtn] LTP Corrigendum
Message-ID:
        <CAHdkBBmVLOPGmWqBwO1S+Qo7E6-+p4c8Q39zqHCbH7Nvq_08Vw at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

All,

I plugged the agreed-upon text for the LTP corrigendum into an edited version of the LTPv1 blue book; results on CWE here <https://protect2.fireeye.com/v1/url?k=43749a4f-1ceff047-4371ebc1-ac1f6bdccbcc-77146fdc4f03da42&q=1&e=317d61e8-4bd1-4628-878f-add4a3c80891&u=https%3A%2F%2Fcwe.ccsds.org%2Fsis%2F_layouts%2F15%2FWopiFrame.aspx%3Fsourcedoc%3D%7B9FC85669-5C0A-4CB9-BFFB-0157F1740334%7D%26file%3D734x1b1_final_w_draft_corrigendum_kls.doc%26action%3Ddefault>
.

I added the omnibus "why do another LTP implementation" in section 2.
Because of the way the document is structured, I don't think it's really possible to scatter the other recommendations close to their respective specification text, so I put them all into a 'Discussion' section at the end of section 3.

This addresses (I think) Cheol's asynchronous (friendly) reports.

ONE ITEM THAT MAY NEED ATTENTION:
We had agreed on text for the green-part data reception section stating:
"If implementers wish to  implement green-part LTP in conjunction with link suspension, they should reuse the session identifiers which were utilized prior to suspension."

Isn't this a requirement on the SENDER?  On reception, the green-part session identifier is passed from the receiving LTP engine to the client and is extracted from the LTP header, right?  The agreed-upon text of the corrigendum sounds (to me) dangerously close to specification text, and I THINK it's a requirement on the sender from 5326, no?  I suggest we cut the sentence above.  If we want to add it as a recommendation for SENDERS, I suggest putting it in its own subsection.  If I'm just clueless, somebody make a suggestion.



    --keith

https://protect2.fireeye.com/v1/url?k=04e01bfc-5b7b71f4-04e56a72-ac1f6bdccbcc-9d8c5006920b6c60&q=1&e=317d61e8-4bd1-4628-878f-add4a3c80891&u=https%3A%2F%2Fcwe.ccsds.org%2Fsis%2F_layouts%2F15%2FWopiFrame.aspx%3Fsourcedoc%3D%7B9FC85669-5C0A-4CB9-BFFB-0157F1740334%7D%26file%3D734x1b1_final_w_draft_corrigendum_kls.doc%26action%3Ddefault
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://protect2.fireeye.com/v1/url?k=a379ceec-fce2a4e4-a37cbf62-ac1f6bdccbcc-f5b02db421b79d72&q=1&e=317d61e8-4bd1-4628-878f-add4a3c80891&u=http%3A%2F%2Fmailman.ccsds.org%2Fpipermail%2Fsis-dtn%2Fattachments%2F20230713%2Ff9e82561%2Fattachment-0001.htm>

------------------------------

Subject: Digest Footer

_______________________________________________
SIS-DTN mailing list
SIS-DTN at mailman.ccsds.org
https://protect2.fireeye.com/v1/url?k=4a7ee75f-15e58d57-4a7b96d1-ac1f6bdccbcc-4f0773ebf7454211&q=1&e=317d61e8-4bd1-4628-878f-add4a3c80891&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn


------------------------------

End of SIS-DTN Digest, Vol 145, Issue 2
***************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sis-dtn/attachments/20230714/178b6b23/attachment-0001.htm>