[Sis-dtn] [EXTERNAL] Re: Special use of sequence number in bundle creation time stamp

Wed Aug 9 15:31:37 UTC 2023

Marc, Felix,

As you could guess, we, GSFC have been advocating for this a few years now. It supports important use cases without needing an extension header and makes it easier to reason about the DTN network. We were just going to make it an NM policy choice. Felix's proposal to use BPCF makes this bundle feature  "parseable" at run-time with backward compatibility with IETF.  I would expect all DTN users to adopt this over time based on the use cases.

This concept was discussed in detail at the recent DTN TIM with NASA consensus on the concepts and approach.

We have a presentation on the use cases that we can discuss at the next meeting.

Kind regards,

     Jonathan Wilmot

CCSDS SOIS Area Director
GSFC DTN Systems Engineer
cFS Architecture
Cell 301-751-2658

From: Marc Blanchet <marc.blanchet at viagenie.ca>
Sent: Wednesday, August 9, 2023 10:58 AM
To: Felix Flentge <Felix.Flentge at esa.int>
Cc: Dr. Keith L Scott via SIS-DTN <sis-dtn at mailman.ccsds.org>; Singh, Somendra {Simon} (GSFC-5820) <simon.singh at nasa.gov>; Wilmot, Jonathan J. (GSFC-580.0)[VANTAGE SYSTEMS INC] <jonathan.j.wilmot at nasa.gov>
Subject: [EXTERNAL] Re: [Sis-dtn] Special use of sequence number in bundle creation time stamp

CAUTION: This email originated from outside of NASA.  Please take care when clicking links or opening attachments.  Use the "Report Message" button to report suspicious messages to the NASA SOC.

Le 9 août 2023 à 10:42, Felix Flentge via SIS-DTN <sis-dtn at mailman.ccsds.org<mailto:sis-dtn at mailman.ccsds.org>> a écrit :

Dear All,

...

  1.  If we want to use BPCF, what is the way to specify this? Should we / do we need to go IETF or could CCSDS be sufficient (to start with)? Ideally we would use some of the reserved first 16 bits (e.g. Bit 7 - 10)

Bundle Processing Control Flags are managed in an IANA registry (https://www.iana.org/assignments/bundle/bundle.xhtml#processing-control). The current policy says: "Specification Required". That means that one can request new values if it can be demonstrated that a specification requires it (i.e. one would have to provide the URL of an SDO document). So it could be done either in IETF or CCSDS.  And when specification is done, then send a request to IANA for registering the values.  The designated experts  (identified in the meta data of the registry)  may be requested to review the specification document if it is not clear for the values requested from the IANA staff perspective. A point to note: in typical registries, a requestor is not asking specific bits or code points. IANA does assign them "for you". One of the reasons is that they may currently have other parallel requests for the same registry being processed and the fact that one look at the registry with available values does not really reflect reality. But if one really wants specific bits, then in the request to IANA, one has to justify (on the engineering side) why these specific bits/code points. In that context, the designated experts will likely be asked to confirm the engineering justification.

This note is to help people understand the process.

Marc (who helped on contract IANA for 15 years... and started SANA using IANA as an inspiration...)

  1.
  2.  No matter whether we want to use BCPF or not, I think something should end up in the CCSDS BB as soon as possible. So, maybe there is a chance for a late RID (if it does not delay the overall publication process). We should start discussing (maybe tomorrow).

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<mailto:dpo at esa.int>). _______________________________________________
SIS-DTN mailing list
SIS-DTN at mailman.ccsds.org<mailto:SIS-DTN at mailman.ccsds.org>
https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sis-dtn/attachments/20230809/c8845c26/attachment-0001.htm>