[Sls-sea-dls] [EXTERNAL] SDLS Green Book issue 2 : WG resolution to publish for area approval

Thu Oct 13 16:16:47 UTC 2022

Hi Gilles,

Thanks for the notice.  I can make some time available Monday or Tuesday if you have any questions for me.

See you in Toulouse, Peter

From: Gilles Moury <Gilles.Moury at cnes.fr>
Date: Thursday, October 13, 2022 at 8:00 AM
To: Peter Shames <peter.m.shames at jpl.nasa.gov>
Cc: "sls-sea-dls at mailman.ccsds.org" <sls-sea-dls at mailman.ccsds.org>
Subject: TR: [EXTERNAL] SDLS Green Book issue 2 : WG resolution to publish for area approval

Dear Peter,
We will go through your remarks/issues at the upcoming meeting next week. Hopefully, we will decide on a way forward for all of them.
See you next week in Toulouse,
Gilles

Gilles MOURY
CNES Toulouse
De : Shames, Peter M (US 312B) <peter.m.shames at jpl.nasa.gov>
Envoyé : samedi 8 octobre 2022 19:35
À : Moury Gilles <Gilles.Moury at cnes.fr>; Ignacio Aguilar-Sanchez <ignacio.aguilar.sanchez at esa.int>
Cc : Weiss, Howard <Howard.Weiss at parsons.com>; Kazz, Greg (US 312B) <greg.j.kazz at jpl.nasa.gov>
Objet : Re: [EXTERNAL] SDLS Green Book issue 2 : WG resolution to publish for area approval
Importance : Haute

Dear Gilles, Ignacio, et al,

As I noted earlier I found a number of issues in this document that I thought needed to be addressed.  Some of those are noted below.  I am attaching the marked up document here.  To be transparent I will state that I only read through sec 1-3 and stopped at sec 4.  So I primarily gave attention to the introductory, explanatory, non-normative parts of this non-normative document.

That said, I believe that as you remedy the issues that I have pointed out that you will identify aspects of the latter chapters that also need to be fixed.  My recommendation is that you make note of each of these kinds of changes that you identify and apply them, uniformly, throughout all of the sections of the document.  Some of these items that I found appeared to be inconsistencies from section to section that were derived from the changes in the protocol set, and coding sets, and directionality caused by the later addition of new standards that were not smoothly integrated into the whole document.  For example, USLP, in particular, seems to have been added in without due consideration being given to the fact that it can be used in both forward and return directions, and with newer codes than Reed-Solomon.

Here are my high level observations:

  1.  It appears that the inclusion of AOS and USLP in this discussion is less than thorough.  Since both of them are now documented for use on the forward link, for “telecommanding” the treatment of them in that context should, in my opinion, be more thorough and careful.
  2.  There is a lot of casual use of TC and TM when it appears that telecommand and telemetry are really mean.  Likewise these words appear capitalized, implying the protocols, rather than lower case, implying the functions.  This should be cleared up.
  3.  There are a lot of references to the use of Reed Solomon which appear to make the assumption that this is the only forward coding allowed.  I believe that we now allow LDPC as well on the forward path, so this should be cleaned up too.
  4.  There is a fair amount of “we may do this” language in the document which seems to be a hold-over from White Book days.  This should be cleaned up.  It makes the document sound tentative.
  5.  It is not clear from the document if it is possible to apply these same link layer security approaches over an inter satellite link (ISL).  That kind of deployment, of course, would bring all kinds of key management complexities, and the whole use of terms like “telemetry” vs “telecommand” would need to be clarified, but in principle, given the essential protocol features, it should be possible to use it in this way.  Is this intended, or even possible?

There is more, but these are the top items that I identified in reading through the document.  By the way, I do think that this is a really good piece of work technically, I just think we need to do a better job of explaining what it is, how it is intended to work, and where it may be applied.

Best regards, Peter

From: Peter Shames <peter.m.shames at jpl.nasa.gov<mailto:peter.m.shames at jpl.nasa.gov>>
Date: Thursday, October 6, 2022 at 10:35 AM
To: Gilles Moury <Gilles.Moury at cnes.fr<mailto:Gilles.Moury at cnes.fr>>, Ignacio Aguilar-Sanchez <ignacio.aguilar.sanchez at esa.int<mailto:ignacio.aguilar.sanchez at esa.int>>
Cc: Howie Weiss <Howard.Weiss at parsons.com<mailto:Howard.Weiss at parsons.com>>
Subject: Re: [EXTERNAL] SDLS Green Book issue 2 : WG resolution to publish for area approval

Dear Gilles and Ignacio,

This is just a quick “head’s up” that in reading through this draft of the SDLS GB I have found a quite large number of editorial issues.  Many of these seem to be caused by the inclusion in the current draft of language that appears to have been in there from “white book” days.  Words like “we may do this” or “we think we will do that”.  I think this is the time to clean that sort of thing up.

I also found references to SLE services that will never be defined (according to the CSS area) and several uses of non standard terms when agreed terms are already defined (authenticity vs authentication, TCR instead of TT&C, etc).

Having found many of these issues in the first few pages (I am only up to page 2-11) I will continue to look through the rest of the doc and then send it back to you with a request to clean it all up.

Thanks, Peter

From: Gilles Moury <Gilles.Moury at cnes.fr<mailto:Gilles.Moury at cnes.fr>>
Date: Thursday, October 6, 2022 at 8:07 AM
To: Ignacio Aguilar-Sanchez <ignacio.aguilar.sanchez at esa.int<mailto:ignacio.aguilar.sanchez at esa.int>>, Peter Shames <peter.m.shames at jpl.nasa.gov<mailto:peter.m.shames at jpl.nasa.gov>>
Cc: Howie Weiss <Howard.Weiss at parsons.com<mailto:Howard.Weiss at parsons.com>>
Subject: [EXTERNAL] SDLS Green Book issue 2 : WG resolution to publish for area approval

Dear Ignacio and Peter,
Please find attached an SDLS WG resolution to publish SDLS Green Book Issue 2, together with the final draft of the updated document. Please indicate at your earliest convenience whether you approve this resolution requesting CESG/CMC publication poll.

Best regards,
Gilles
Gilles MOURY
SDLS WG Chairman
De : Moury Gilles
Envoyé : jeudi 6 octobre 2022 16:54
À : sls-sea-dls at mailman.ccsds.org<mailto:sls-sea-dls at mailman.ccsds.org>
Objet : SDLS Green Book issue 2 : WG resolution to publish

Dear SDLS WG member,
Please find attached the WG resolution to publish SDLS Green Book Issue 2 (final draft attached) submitted to SLS and SEA area directors.
Best regards,
Gilles

Gilles MOURY
SDLS WG Chairman
De : SLS-SEA-DLS <sls-sea-dls-bounces at mailman.ccsds.org<mailto:sls-sea-dls-bounces at mailman.ccsds.org>> De la part de Moury Gilles via SLS-SEA-DLS
Envoyé : jeudi 4 août 2022 19:07
À : sls-sea-dls at mailman.ccsds.org<mailto:sls-sea-dls at mailman.ccsds.org>
Objet : [Sls-sea-dls] SDLS Green Book issue 2 : final draft for review by the WG

Dear SDLS WG member,

As agreed at our last meeting, please find attached for review by the WG the final draft of the SDLS Core Protocol Green Book Issue 2 which includes various updates concerning :

  *   Addition of USLP as SDLS compatible data link protocol
  *   Reference to SDLS Extended Procedures for key and SA management

Please provide your comments before end September so we can issue the WG resolution for publication of this document before our fall meeting.

Best regards,
Gilles Moury
CCSDS SDLS WG Chairman.

[cid:image001.png at 01D8DEE4.84C173D0]
Gilles MOURY
Senior Adviser On-Board Architecture & Avionics
Architecture, Validation & Integration Department
18 avenue Edouard Belin 31401 Toulouse Cedex 9
[cid:image002.png at 01D8DEE4.84C173D0] +33 (0)5 61 27 37 90 / [cid:image003.png at 01D8DEE4.84C173D0]  +33 (0)6 83 56 04 85
[cid:image004.png at 01D8DEE4.84C173D0] gilles.moury at cnes.fr<mailto:gilles.moury at cnes.fr>
[cid:image005.png at 01D8DEE4.84C173D0] cnes.fr<https://urldefense.us/v3/__http:/cnes.fr/__;!!PvBDto6Hs4WbVuu7!Yniosxqp1uSEqDjdc3K75OjGaZ-EtAmxPRk5UCSnAcPYf1cu7FycIeHouxhO8OyQyK-RsNM7$>
[cid:image006.png at 01D8DEE4.84C173D0]<https://urldefense.us/v3/__https:/www.facebook.com/CNESFrance/__;!!PvBDto6Hs4WbVuu7!Yniosxqp1uSEqDjdc3K75OjGaZ-EtAmxPRk5UCSnAcPYf1cu7FycIeHouxhO8OyQyJaVXJMP$>  [cid:image007.png at 01D8DEE4.84C173D0] <https://urldefense.us/v3/__https:/www.instagram.com/cnes_france/__;!!PvBDto6Hs4WbVuu7!Yniosxqp1uSEqDjdc3K75OjGaZ-EtAmxPRk5UCSnAcPYf1cu7FycIeHouxhO8OyQyLwgnXh0$>   [cid:image008.png at 01D8DEE4.84C173D0] <https://urldefense.us/v3/__https:/twitter.com/cnes__;!!PvBDto6Hs4WbVuu7!Yniosxqp1uSEqDjdc3K75OjGaZ-EtAmxPRk5UCSnAcPYf1cu7FycIeHouxhO8OyQyN-6DUnz$>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sls-sea-dls/attachments/20221013/ddaa4b3a/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8699 bytes
Desc: image001.png
URL: <http://mailman.ccsds.org/pipermail/sls-sea-dls/attachments/20221013/ddaa4b3a/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 483 bytes
Desc: image002.png
URL: <http://mailman.ccsds.org/pipermail/sls-sea-dls/attachments/20221013/ddaa4b3a/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 535 bytes
Desc: image003.png
URL: <http://mailman.ccsds.org/pipermail/sls-sea-dls/attachments/20221013/ddaa4b3a/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 531 bytes
Desc: image004.png
URL: <http://mailman.ccsds.org/pipermail/sls-sea-dls/attachments/20221013/ddaa4b3a/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 529 bytes
Desc: image005.png
URL: <http://mailman.ccsds.org/pipermail/sls-sea-dls/attachments/20221013/ddaa4b3a/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 810 bytes
Desc: image006.png
URL: <http://mailman.ccsds.org/pipermail/sls-sea-dls/attachments/20221013/ddaa4b3a/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 879 bytes
Desc: image007.png
URL: <http://mailman.ccsds.org/pipermail/sls-sea-dls/attachments/20221013/ddaa4b3a/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 861 bytes
Desc: image008.png
URL: <http://mailman.ccsds.org/pipermail/sls-sea-dls/attachments/20221013/ddaa4b3a/attachment-0015.png>