[Sls-slp] Technical Corrigenda for USLP (732.1-B) needed when 4 SLS area proximity books released

[Clemens Heese]

Dear Greg,

Thanks for the heads up.
Can we publish this as a technical corrigendum? The last times this went swiftly.
The question we have to answer is: Does the update break backwards interoperability?

Can you please send me a formulation upfront in case it does not break it to prepare the TC?

Thanks,

Clemens

From: KAZZ, GREG J. (MSFC-HP27)[MOSSI2] <greg.j.kazz at nasa.gov>
Date: Friday, 21. August 2026 at 21:44
To: Clemens Heese <Clemens.Heese at esa.int>; jean-luc.issler at cnes.fr <jean-luc.issler at cnes.fr>
Cc: Kazz, Greg (US 312B) via SLS-SLP <sls-slp at mailman.ccsds.org>
Subject: Technical Corrigenda for USLP (732.1-B) needed when 4 SLS area proximity books released

Dear Clemens and Jean-Luc,

Just a heads up about publishing an update to USLP, 732.1-B, at the same time that we publish the 4 link layer documents (Prox-1 series plus 235.1).
The reason is that USLP contains many references to COP-P, which used to be in 211.0-B, but has been moved to 235.1. Without an update, this book will have many false references. In addition, it gives us the opportunity to include a few technical corrigenda that the SLP WG have been collecting for USLP such as 1) MAP ID = 0, when no maps are present (3.6.2 & 4.2.7.2); 4.1.4.2.2.2.2 No segmentation (SDLS does not provide a control command), and a few more, which I have the full list.

My point is that we would need priority from the editors to update USLP concurrently with those other 4 books as well. I hope we will have full editorial support by then.

Best regards,
Greg K
NASA/MSFC
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/sls-slp/attachments/20260824/e30bcaa7/attachment.htm>