[Sis-dtn] New Draft: COMPRESSED CUSTODY SIGNALING AND BUNDLE STATUS REPORTING

[Felix Flentge]

Hi,

I have just uploaded Draft H of the 'Compressed Custody Signaling And Bundle Status Reporting' Orange Book to CWE:

CompressedBundleStatusReportingAndCustodySignaling_OrangeBook_Draft_H.docx<https://spacecomm.sharepoint.com/:w:/r/sites/SIS/_layouts/15/Doc.aspx?sourcedoc=%7B10790F7B-6318-4BD0-9D53-8813C83BE941%7D&file=CompressedBundleStatusReportingAndCustodySignaling_OrangeBook_Draft_H.docx&action=default&mobileredirect=true>

We have introduced the following changes:


  1.  Based on Brian's proposal to make the reporting even more efficient, Yanik analysed and designed a new way to encode bundle sequences which may contain some gaps (see updated Section 3.3). It is not so easy to come up with some concise language for that, so please let us know if you have suggestions for improvement.


  1.  I took the opportunity to not allow processing of the CREB/CTEB blocks in fragments:

3.4.1          Extension Blocks specified in this specification shall only be added and processed in non-fragmented bundles.

NOTE - As later fragmentation of bundles using the extension blocks specified in this specification may lead to unintended effects such as loss of expected reporting or custody signals as fragmented bundles are never re-assembled (RfC 9171 does only specify Application Data Unit Re-Assembly), it is recommended to set the 'Bundle Must Not be Fragmented' flag at the source if the application of custody transfer or compressed status reporting according to this specification is intended.


  1.  The compressed reporting signal (see 5.2.3) has been changed to include the reporting reason code as integer (and not as an integer interpreted as bit field). Please note that the Status Report Request Flags (5.1.4.1) shall actually be processed as a bit field. However, we align the Bit Number with the reason code integer for consistency.

Regards,
Felix

This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo at esa.int).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sis-dtn/attachments/20250514/f5618559/attachment.htm>