[Sis-dtn] Keith's raw notes from telecon

[Tomaso.deCola at dlr.de]

As to the CMC poll, I see that most of the agencies participated and gave their approval. As such, I’ll check with Brian the way forward to the publication.

Regards,

Tomaso

From: SIS-DTN <sis-dtn-bounces at mailman.ccsds.org> On Behalf Of Keith Scott via SIS-DTN
Sent: Donnerstag, 3. April 2025 17:49
To: sis-dtn at mailman.ccsds.org
Subject: [Sis-dtn] Keith's raw notes from telecon


SIS-DTN

No updates on CMC poll from Tomaso.



Discussion from Joint IETF / CCSDS meeting (monthly / yesterday) -- Tomaso wasn’t there

  *   BPSec issue

  *   Fragment ==> can’t apply security

  *   BPSec ==> can’t fragment



  *   Lars Baumgaertner

  *   Everybody agreed on the problems

  *   Not moving super-fast

  *   Will go for a CCSDS orange book to allow fragmentation and security

  *



Ed: Possible solutions

  1.  you can do bundle-in-bundle encapsulation of fragments, which is heavy-weight.

  1.  A fragmentation-aware security context could be built, but also not optimal

  1.  Orange book



Scott also working on an approach that should pose no additional overhead.



Felix: also discussed yesterday the option to include security on fragments.



Tomaso: Orange book path seems to be the way to go.  Need to create a project.



Conclusion: Tomaso to get an Orange book in process.---

Wilmot: what’s the real use-case for fragmentation?  IPv6 does just fragmentation at source, and we have managed networks so we know the MSS for each link, no?

  *   Yes but, if the path might change, what path MSS do you pick?  You would have to just always choose the smallest.



Conclusion: we’d like to be able to fragment in the network.---

Brian Sipos: IETF Status

  *   ion scheme update is in auth-48

  *   Rick Taylor proposed a unidirectional CLA targeted at e.g. DVB

  *   In call-for-adoption in IETF

  *   DTNMA drafts continue to be refined (really in examples, limits, boundaries -- the ‘meat’ of the documents are pretty set)

  *   IETF had an issue w/ the use of YANG syntax for ADM encoding

  *   Bundle-in-bundle encapsulation was updated

  *   Time-variant routing WG requirements document is about last-call status (not quite, but nearly)



Simon: in the new ipn scheme is dtn:none no longer required?



Ed: 5.2 of the update talks about the null endpoint (as referenced from 9171). dtn:none, ipn:0.0, and ipn:0.0.0 are all the null endpoint.



Alberto: Did testing on ISS with BIBE-CT



JW: Artemis is really excited about using the 3-tuple ipn scheme for their mission.


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