<font size=2 face="sans-serif">Dear all,</font>
<br>
<br><font size=2 face="sans-serif">The BB will be revised only after 5
years once it has been published.</font>
<br><font size=2 face="sans-serif">Thus, putting a statement like "</font><font size=3 face="Times New Roman">Implementation
of the services necessary to manage the parameters contained in the SA
data base is a mission-specific function. Service directives for
managing the SA parameters in-line will be specified in a CCSDS recommendation
currently under development (355.1-B: SDLS Extended Procedures).</font><font size=2 face="sans-serif">"
seems a bit odd. I would formulate it more "timeless".</font>
<br><font size=2 face="sans-serif">Maybe something like "</font><font size=3 face="Times New Roman">Implementation
of the services necessary to manage the parameters contained in the SA
data base is a mission-specific function. Service directives for
managing the SA parameters in-line are specified in the SDLS Extended Procedures
CCSDS recommendation (reference 355.1-B: SDLS Extended Procedures). At
the time of publication of this document, the Extended Procedures book
is still under development .</font><font size=2 face="sans-serif">"
</font>
<br>
<br><font size=2 face="sans-serif">Furthermore, I agree with Ignacios statement
regarding Section 6.1. Unspecified ins better. It may also be worth to
add a reference to Section 3.4.1.</font>
<br>
<br><font size=2 face="sans-serif">Cheers,<br>
Daniel<br>
<br>
<br>
Dr. Daniel Fischer<br>
----------------------------<br>
Data Systems Manager<br>
Ground Systems Engineering Support Office<br>
Ground Systems Engineering Department<br>
Directorate of Human Spaceflight and Operations<br>
<br>
European Space Agency - ESOC<br>
Robert-Bosch-Str. 5<br>
D-64293 Darmstadt - Germany<br>
Tel: +49 (0) 6151 90 2718 - Fax: +49 (0) 6151 90 2718<br>
Web: </font><a href=http://www.esa.int/><font size=2 face="sans-serif">http://www.esa.int</font></a>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Ignacio Aguilar Sanchez/estec/ESA</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"Biggerstaff,
Craig (JSC-CD221)[LOCKHEED MARTIN CORP]" <craig.biggerstaff@nasa.gov>,
</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"Daniel.Fischer@esa.int"
<Daniel.Fischer@esa.int>, "Moury Gilles" <Gilles.Moury@cnes.fr>,
"howie.weiss@sparta.com" <howie.weiss@sparta.com>, "sls-sea-dls@mailman.ccsds.org"
<sls-sea-dls@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">24/08/2015 10:00</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [Sls-sea-dls]
RE: SDLS BB : proposal for PS comments dispositions</font>
<br>
<hr noshade>
<br>
<br><font size=2 face="sans-serif">Dear Craig et al,</font>
<br>
<br>
<br><font size=2 face="sans-serif">The proposed update as well as the responses
to Peter's comments are almost fine with me.</font>
<br>
<br><font size=2 face="sans-serif">My only problem is adding the word 'unspecified'
before 'management' in section 6.1. This language is not consistent with
the language used with the TC, TM and AOS BBs.</font>
<br>
<br><font size=2 face="sans-serif">We have attempted to harmonise the four
standards to the best of our ability. Either we state everywhere that the
management is not specified or we do not. And we do it in the same way.</font>
<br>
<br><font size=2 face="sans-serif">To be clear, each of the four standards
contains a statement in section 1.2 where the absence of specification
for the management activities is stated.</font>
<br><font size=2 face="sans-serif">The word 'unspecified' does not show
up a single time in TC, TM and AOS BBs.</font>
<br>
<br><font size=2 face="sans-serif">In order to avoid additional modifications
on TC, TM and AOS BBs to achieve full consistency with this topic, I would
propose to remove the word 'unspecified'.</font>
<br>
<br>
<br><font size=2 face="sans-serif">Kind regards,</font>
<br>
<br><font size=2 face="sans-serif">Ignacio</font>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Biggerstaff,
Craig (JSC-CD221)[LOCKHEED MARTIN CORP]" <craig.biggerstaff@nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"Moury Gilles"
<Gilles.Moury@cnes.fr>, "Ignacio.Aguilar.Sanchez@esa.int"
<Ignacio.Aguilar.Sanchez@esa.int>, "Daniel.Fischer@esa.int"
<Daniel.Fischer@esa.int>, "howie.weiss@sparta.com" <howie.weiss@sparta.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"sls-sea-dls@mailman.ccsds.org"
<sls-sea-dls@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">21/08/2015 22:55</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[Sls-sea-dls]
RE: SDLS BB : proposal for PS comments dispositions</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">sls-sea-dls-bounces@mailman.ccsds.org</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 color=#004080 face="Calibri">Dear WG members,</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Gilles, thank you for adding
in the proposed dispositions for Peter Shames.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">I have added the NOTE to
section 1.1 to answer Tomaso de Cola’s and Keith Scott’s conditions,
updated figures 2-4,5-1,5-2,5-3, and made one or two minor alterations
to the proposed language to avoid an implicit dependency of 355.0 upon
355.1. If these changes meet with the WG’s satisfaction, I will
forward them to Peter for his review and cc Tom Gannett per the conditional
approval procedures.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Best regards,</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Craig</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 face="Calibri"><b>From:</b> Moury Gilles [</font><a href=mailto:Gilles.Moury@cnes.fr><font size=2 face="Calibri">mailto:Gilles.Moury@cnes.fr</font></a><font size=2 face="Calibri">]
<b><br>
Sent:</b> Friday, August 21, 2015 11:07 AM<b><br>
To:</b> Biggerstaff, Craig (JSC-CD221)[LOCKHEED MARTIN CORP]; Ignacio.Aguilar.Sanchez@esa.int;
Daniel.Fischer@esa.int; howie.weiss@sparta.com<b><br>
Cc:</b> sls-sea-dls@mailman.ccsds.org; sls-sea-dls-bounces@mailman.ccsds.org<b><br>
Subject:</b> SDLS BB : proposal for PS comments dispositions</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 color=#004080 face="Calibri">Dear SDLS WG members,</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Please find attached a redline
version of the SDLS BB with proposed dispositions for Peter Shames comments
(in line with my herebelow mail). The text modifications are tentatively
justified wrt Peter’s comment. We should converge internally to the WG
before sending the proposed redline to Peter Shames. Craig, as technical
editor of the book, could you please take the lead on this ? I am leaving
for one week so will not be able to make any progress.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Best regards,</font>
<br><font size=2 color=#004080 face="Calibri">Gilles</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Arial">Gilles MOURY</font><font size=3 color=#004080 face="Times New Roman">
</font><font size=2 color=#004080 face="Arial"><br>
SDLS WG Co-Chair</font><font size=3 color=#004080 face="Times New Roman">
</font>
<br><font size=2 face="Tahoma"><b>De :</b> </font><a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org"><font size=2 color=blue face="Tahoma"><u>sls-sea-dls-bounces@mailman.ccsds.org</u></font></a><font size=2 face="Tahoma">
[</font><a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org"><font size=2 color=blue face="Tahoma"><u>mailto:sls-sea-dls-bounces@mailman.ccsds.org</u></font></a><font size=2 face="Tahoma">]
<b>De la part de</b> Moury Gilles<b><br>
Envoyé :</b> mercredi 19 août 2015 15:45<b><br>
À :</b> </font><a href=mailto:Daniel.Fischer@esa.int><font size=2 color=blue face="Tahoma"><u>Daniel.Fischer@esa.int</u></font></a><font size=2 face="Tahoma">;
</font><a href=mailto:Ignacio.Aguilar.Sanchez@esa.int><font size=2 color=blue face="Tahoma"><u>Ignacio.Aguilar.Sanchez@esa.int</u></font></a><font size=2 face="Tahoma"><b><br>
Cc :</b> </font><a href="mailto:sls-sea-dls@mailman.ccsds.org"><font size=2 color=blue face="Tahoma"><u>sls-sea-dls@mailman.ccsds.org</u></font></a><font size=2 face="Tahoma">;
</font><a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org"><font size=2 color=blue face="Tahoma"><u>sls-sea-dls-bounces@mailman.ccsds.org</u></font></a><font size=2 face="Tahoma"><b><br>
Objet :</b> RE: [Sls-sea-dls] results of CESG poll for SDLS BB publication</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 color=#004080 face="Calibri">Dear Daniel, Ignacio and
SDLS WG members,</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">I concur with Ignacio and
Daniel proposals for Peter’s comments disposition. More specifically,
taking Peter’s comments one by one (I attach Peter’s commented version
for reference):</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">P 1-1 : OK for the 2 comments</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">P 1-3, 3-1 : The usage of
the term Payload: this term is duly defined upfront in SDLS book and therefore
this definition replaces the CCSDS generic definition in the context of
SDLS. The term is used consistently throughout the document. Besides
the term payload is widely used with that meaning in the COMSEC domain.
I agree with Ignacio and Daniel that we should discuss this with Peter
and advocate for keeping this term. </font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">P 2-1 : Comment not understood.
To be discussed with Peter. In any case we can remove the parenthesis in
the note if that causes problem.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">P 2-2 : I do not support
inserting in SDLS a duplicate of figures 6-1 of TM, TC and AOS books, but
we could simply refer/point to it respectively in sections 2.2.3, 2.2.4
and 2.2.5 with a statement like: “the structure of the TM/TC/AOS Transfer
Frame with SDLS is given in Figure 6-1 of [1]/[2]/[3]. This statement could
also be placed once in section 2.3.1.4 Security Header and Trailer.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">P 2-5 : Figure 2-4 : we need
to change A and B to <u>AOS</u> ApplySecurity payload or return (instead
of <u>TM</u> ApplySecurity …)</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">P2-8, 4-9, 4-12 : NOTE on
sequence number rollover : I would suggest keeping the NOTE but limiting
it to the first sentence (The interpretation of a sequence number rollover
(to zero) is mission specific) and then pointing to a specific SDLS green
book subsection where this is discussed in more details. This would avoid
confusion for implementers making it clear there is no specific recommendation
(should) or permission (may) for that subject in the Blue Book.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">P 3-7, 3-10 : SA management
service: I would propose keeping subsection 3.4.2 intact (SA management
service parameters). Replace the NOTE in 3.4.3 (SA management service directives)
by : “The directives for SA management will be specified in a CCSDS recommendation
currently under development (355.1-B: SDLS extended procedures).” To be
coherent with that, I would replace the second sentence of subsection 3.4.1
by: “The service directives necessary</font>
<br><font size=2 color=#004080 face="Calibri">to manage the SA parameters
will be specified in a CCSDS recommendation currently under development
(355.1-B: SDLS extended procedures)”. As suggested by Daniel, we could
add a column in table 6-1 to indicate the correspondence between parameters
denomination in subsection 3.4.2 and in Table 6-1.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">P 5-1: Peters comment: (no
mention of payload in that section 5 “Use of the services with CCSDS protocols”).
I would propose to show the “ApplySecurity payload” in figures 5-1 (TM
transfer frame), 5-2 (TC), 5-3 (AOS).</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">P 6-1 : OK to add unspecified
(an unspecified management system). For the second comment (abstract SA
data base) I tend to agree with Daniel, the SA data base is not abstract
. It has to be implemented both on-ground and on-board.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">P B-1 : OK to replace “user-supplied
data unit” by “transfer frame data field” to make it unambiguous.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">I hope we can converge with
Peter on commonly agreed dispositions. We need to consolidate first our
WG responses to his comments. Craig : let us know your position wrt the
comments, so we can produce a redline version of the document with our
proposed dispositions and associated explanations inserted.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Best regards,</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Gilles</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Arial">Gilles MOURY</font><font size=3 color=#004080 face="Times New Roman">
</font><font size=2 color=#004080 face="Arial"><br>
CNES Toulouse</font><font size=3 color=#004080 face="Times New Roman">
</font>
<br><font size=2 face="Tahoma"><b>De :</b> </font><a href=mailto:Daniel.Fischer@esa.int><font size=2 color=blue face="Tahoma"><u>Daniel.Fischer@esa.int</u></font></a><font size=2 face="Tahoma">
[</font><a href=mailto:Daniel.Fischer@esa.int><font size=2 color=blue face="Tahoma"><u>mailto:Daniel.Fischer@esa.int</u></font></a><font size=2 face="Tahoma">]
<b><br>
Envoyé :</b> jeudi 13 août 2015 14:51<b><br>
À :</b> </font><a href=mailto:Ignacio.Aguilar.Sanchez@esa.int><font size=2 color=blue face="Tahoma"><u>Ignacio.Aguilar.Sanchez@esa.int</u></font></a><font size=2 face="Tahoma"><b><br>
Cc :</b> Moury Gilles; </font><a href="mailto:sls-sea-dls@mailman.ccsds.org"><font size=2 color=blue face="Tahoma"><u>sls-sea-dls@mailman.ccsds.org</u></font></a><font size=2 face="Tahoma">;
</font><a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org"><font size=2 color=blue face="Tahoma"><u>sls-sea-dls-bounces@mailman.ccsds.org</u></font></a><font size=2 face="Tahoma"><b><br>
Objet :</b> Re: [Sls-sea-dls] results of CESG poll for SDLS BB publication</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Arial">Dear Igancio and all,</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
I checked the comments as well. I agree to all you say below and I have
a few more remarks/ first thoughts based on the comments that Peter put
in-line in the document.</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="Arial"><br>
1) The word payload: While of course it has different meanings, the term
"payload" is very well established in the communication
protocol world. You can find the following definition e.g. on Wikipedia:
</font><font size=2 color=#2f2f2f face="Times New Roman"><b>Payload</b>
in </font><a href=https://en.wikipedia.org/wiki/Computing><font size=2 color=#000080 face="Times New Roman"><u>computing</u></font></a><font size=2 color=#2f2f2f face="Times New Roman">
(sometimes referred to as the actual or body data) is the cargo of a </font><a href=https://en.wikipedia.org/wiki/Data_transmission><font size=2 color=#000080 face="Times New Roman"><u>data
transmission</u></font></a><font size=2 color=#2f2f2f face="Times New Roman">.
It is the part of the transmitted </font><a href=https://en.wikipedia.org/wiki/Data_(computing)><font size=2 color=#000080 face="Times New Roman"><u>data</u></font></a><font size=2 color=#2f2f2f face="Times New Roman">
which is the fundamental purpose of the transmission, to the exclusion
of information sent with it (such as </font><a href=https://en.wikipedia.org/wiki/Header_(computing)><font size=2 color=#000080 face="Times New Roman"><u>headers</u></font></a><font size=2 color=#2f2f2f face="Times New Roman">
or</font><a href=https://en.wikipedia.org/wiki/Metadata><font size=2 color=#000080 face="Times New Roman"><u>metadata</u></font></a><font size=2 color=#2f2f2f face="Times New Roman">,
sometimes referred to as overhead data) solely to facilitate delivery</font><font size=3 face="Times New Roman">.
<br>
</font><font size=2 face="Arial"><br>
2) Regarding the inline comments:</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
P 1-1: I am not sure about both comments. Is this section not a standard
CCSDS section? It reads like one. If yes, I would not bother modifying
it.</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
P 1-3: See payload discussion</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
P 2-1: I am not sure I understand the comment. We simply state that SDLS
is not associated with any other protocol and as an example we bring the
SPP. This may be a misunderstanding. Perhaps Peter confuses an association
with another protocol (e.g. for extended procedures) with the concept of
the underlying data-link layer protocol(s). If this causes too much discussion,
we could even remove the note.</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
P 2-2: Following up on Ignacios comments, i would not include too much
additional information here. We have the Green Book for that. Also, the
other SLS books that have been updated mention SDLS and how it fits in
as well. <br>
P 2-8: OK, I can see where he is coming from regarding the comment on the
counter rollover. However, I think the note is pretty clear on this by
saying the interpretation is mission-specific. We could think about being
more concrete on this in the Green Book (if this is not already the case)
and explain the benefits of not rolling over and how this can related to
key lifetime.</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
P 3-7/3-10: I dont think that this section is an issue. Regarding the parameters,
I think together with Section 6 (Managed Parameters) it makes sense to
have them defined here. The only think that I agree may cause confusion
is the paramater naming. E.g: Section 3.4.2.2 says "SA_authentication_key"
while Section 6 says "Authentication Key". Maybe we could add
a column to the table on Section 6, referring to the names used in Section
3.4.2.2. Regarding Section 3.4.3, I would almost be tempted to remove the
Section from the standard (it is empty and the note will be out of date
once the extended procedures...which are not a "revision" of
the SDLS standard, but an addon...are out. We could pick this up in the
Green Book.</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
P 6-1: (1) Not sure why we should add "unspecified". Did he want
to say st. like "not covered by this standard?"...TBD (2) The
SA database is not abstract. In fact it has to be very concrete if you
want to do an implementation. Our prototype has one. </font><font size=3 face="Times New Roman"><br>
</font><font size=2 face="Arial"><br>
3) I think we should seek to have telcon with Peter not too far in the
future to discuss his comments and not wait three months for the next meetings.
This way, we could speed up the publication process a bit. What do you
think?</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
<br>
Cheers</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
Daniel<br>
<br>
<br>
Dr. Daniel Fischer<br>
----------------------------<br>
Data Systems Manager<br>
Ground Systems Engineering Support Office<br>
Ground Systems Engineering Department<br>
Directorate of Human Spaceflight and Operations<br>
<br>
European Space Agency - ESOC<br>
Robert-Bosch-Str. 5<br>
D-64293 Darmstadt - Germany<br>
Tel: +49 (0) 6151 90 2718 - Fax: +49 (0) 6151 90 2718<br>
Web: </font><a href=http://www.esa.int/><font size=2 color=blue face="Arial"><u>http://www.esa.int</u></font></a><font size=3 face="Times New Roman">
<br>
<br>
<br>
</font><font size=1 color=#5f5f5f face="Arial"><br>
From: </font><a href=mailto:Ignacio.Aguilar.Sanchez@esa.int><font size=1 color=blue face="Arial"><u>Ignacio.Aguilar.Sanchez@esa.int</u></font></a><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="Arial"><br>
To: </font><font size=1 face="Arial">Moury Gilles
<</font><a href=mailto:Gilles.Moury@cnes.fr><font size=1 color=blue face="Arial"><u>Gilles.Moury@cnes.fr</u></font></a><font size=1 face="Arial">>,
</font><font size=1 color=#5f5f5f face="Arial"><br>
Cc: </font><font size=1 face="Arial">"</font><a href="mailto:sls-sea-dls@mailman.ccsds.org"><font size=1 color=blue face="Arial"><u>sls-sea-dls@mailman.ccsds.org</u></font></a><font size=1 face="Arial">"
<</font><a href="mailto:sls-sea-dls@mailman.ccsds.org"><font size=1 color=blue face="Arial"><u>sls-sea-dls@mailman.ccsds.org</u></font></a><font size=1 face="Arial">></font><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="Arial"><br>
Date: </font><font size=1 face="Arial">13/08/2015
13:35</font><font size=3 face="Times New Roman"> </font><font size=1 color=#5f5f5f face="Arial"><br>
Subject: </font><font size=1 face="Arial">Re:
[Sls-sea-dls] results of CESG poll for SDLS BB publication</font><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="Arial"><br>
Sent by: </font><a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org"><font size=1 color=blue face="Arial"><u>sls-sea-dls-bounces@mailman.ccsds.org</u></font></a><font size=3 face="Times New Roman">
</font>
<div align=center>
<hr noshade></div>
<br><font size=3 face="Times New Roman"><br>
<br>
</font><font size=2 face="Courier New"><br>
Dear Gilles and colleagues,<br>
<br>
I believe the comment from Tomaso, supported by Keith, is easy to deal
with<br>
the inclusion of such note.<br>
<br>
Concerning Peter's comments,<br>
<br>
1) We all agreed and supported harmonisation of the SDLS with the SLPs,
Part<br>
of the agreement was the assumption that the potential user shall start<br>
reading the SLPs before getting to the SDLS (since it is a NEW optional
SLP<br>
function). And we (SLP WG + SDLS WG) were very careful in deciding what
to<br>
put where. This can explain why the SDLS does not read so well stand-alone,<br>
as Peter seems to want.<br>
Including the three different scenarios (TC, TM, AOS) with corresponding<br>
drawings into the SDLS will substantially 'inflate' the introduction.<br>
And will risk causing incoherency issues with the SLPs and the still-to-be<br>
published SDLS Green Book.<br>
<br>
I think the issue needs to be re-discussed with Peter since the drawings
are<br>
already at the documents where they are supposed to be.<br>
<br>
2) The word 'payload' is mentioned 72 times in the document. The last mention<br>
is in paragraph B1.1, which is perhaps the one that I can see somewhat<br>
inconsistent but it should be easy to fix. Hence, I beg to disagree with<br>
Peter concerning inconsistency in its use. A different thing is whether<br>
another term could be used to avoid confusion with the classical meaning
of<br>
payload in space missions but I think the meaning in SDLS is pretty clear
and<br>
defined. On his proposals "package" looks too close to "packet"
and "user<br>
provided data" too close to "service data unit" (note that
the 'payload' as<br>
in SDLS context includes the SDU and something else, hence not a valid<br>
substitute).<br>
<br>
Unless someone finds a clear and unambiguous term to replace 'payload'
in the<br>
SDLS context, I would advocate to re-discuss the comment with Peter.<br>
<br>
<br>
3) If the document has to be self-standing concerning its interpretation,<br>
this is definitely a section that I think should stay. It is addressing
a<br>
core element of the SDLS. The Green Book will provide further elaboration
but<br>
a bare minimum is needed to be able to understand and interpret SDLS.<br>
<br>
4) There are three NOTES covering this issue that are consistent. I think
we<br>
did not want to impose requirements in this subject, reason why they are<br>
notes. But we could change it to requirements with the word 'may' to make<br>
them more visible as suggested by Peter.<br>
<br>
I hope the above helps.<br>
<br>
Kind regards,<br>
<br>
Ignacio<br>
<br>
<br>
<br>
From: Moury Gilles
<</font><a href=mailto:Gilles.Moury@cnes.fr><font size=2 color=blue face="Courier New"><u>Gilles.Moury@cnes.fr</u></font></a><font size=2 face="Courier New">><br>
To: "</font><a href="mailto:sls-sea-dls@mailman.ccsds.org"><font size=2 color=blue face="Courier New"><u>sls-sea-dls@mailman.ccsds.org</u></font></a><font size=2 face="Courier New">"
<</font><a href="mailto:sls-sea-dls@mailman.ccsds.org"><font size=2 color=blue face="Courier New"><u>sls-sea-dls@mailman.ccsds.org</u></font></a><font size=2 face="Courier New">><br>
Date: 13/08/2015
11:01<br>
Subject: [Sls-sea-dls]
results of CESG poll for SDLS BB publication<br>
Sent by: </font><a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org"><font size=2 color=blue face="Courier New"><u>sls-sea-dls-bounces@mailman.ccsds.org</u></font></a><font size=2 face="Courier New"><br>
<br>
<br>
<br>
Dear CCSDS SDLS WG member,<br>
<br>
Please find attached 2 files:<br>
<br>
The results of the CESG poll (as of today – it terminates tomorrow)<br>
The commented version of the SDLS Blue Book attached to the comments of
Peter<br>
Shames (SEA AD)<br>
<br>
We have to respond to those comments and resolve them with the issuer before<br>
we can actually publish the BB. Please advise on the way to respond to
those<br>
comments.<br>
<br>
Best regards,<br>
<br>
Gilles MOURY<br>
SDLS WG Co-Chair<br>
=========================================================<br>
Gilles MOURY<br>
CNES Toulouse<br>
Expert
senior "Plateforme Satellite"<br>
Sous-Direction "Techniques Véhicule, Architecture &
Intégration"<br>
DCT/TV-RA - Bpi 1416<br>
18, avenue Edouard Belin<br>
F-31401 TOULOUSE Cedex 9<br>
</font><a href=http://www.cnes.fr/><font size=2 color=blue face="Courier New"><u>http://www.cnes.fr</u></font></a><font size=2 face="Courier New"><br>
tel : +33 (0)5 61 27 3790<br>
fax : +33 (0)5 61 27 4099<br>
sec : +33 (0)5 61 27 3882<br>
mob : +33 (0)6 83 56 0485<br>
=========================================================<br>
<br>
<br>
[attachment "results CESG SDLS BB poll.docx" deleted by Ignacio
Aguilar<br>
Sanchez/estec/ESA] [attachment "355x0b0_CESG_Approval-SEA.pdf"
deleted by<br>
Ignacio Aguilar Sanchez/estec/ESA]<br>
_______________________________________________<br>
SLS-SEA-DLS mailing list</font><font size=2 color=blue face="Courier New"><u><br>
</u></font><a href="mailto:SLS-SEA-DLS@mailman.ccsds.org"><font size=2 color=blue face="Courier New"><u>SLS-SEA-DLS@mailman.ccsds.org</u></font></a><font size=3 color=blue face="Times New Roman"><u><br>
</u></font><a href="http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls"><font size=2 color=blue face="Courier New"><u>http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls</u></font></a><font size=2 face="Courier New"><br>
<br>
This message and any attachments are intended for the use of the addressee
or addressees only.<br>
The unauthorised disclosure, use, dissemination or copying (either in whole
or in part) of its<br>
content is not permitted.<br>
If you received this message in error, please notify the sender and delete
it from your system.<br>
Emails can be altered and their integrity cannot be guaranteed by the sender.<br>
<br>
Please consider the environment before printing this email.<br>
<br>
_______________________________________________<br>
SLS-SEA-DLS mailing list</font><font size=2 color=blue face="Courier New"><u><br>
</u></font><a href="mailto:SLS-SEA-DLS@mailman.ccsds.org"><font size=2 color=blue face="Courier New"><u>SLS-SEA-DLS@mailman.ccsds.org</u></font></a><font size=3 color=blue face="Times New Roman"><u><br>
</u></font><a href="http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls"><font size=2 color=blue face="Courier New"><u>http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls</u></font></a>
<br><font size=2 face="Courier New">This message and any attachments are
intended for the use of the addressee or addressees only.</font>
<br><font size=2 face="Courier New">The unauthorised disclosure, use, dissemination
or copying (either in whole or in part) of its</font>
<br><font size=2 face="Courier New">content is not permitted.</font>
<br><font size=2 face="Courier New">If you received this message in error,
please notify the sender and delete it from your system.</font>
<br><font size=2 face="Courier New">Emails can be altered and their integrity
cannot be guaranteed by the sender.</font>
<br><font size=2 face="Courier New"> </font>
<br><font size=2 face="Courier New">Please consider the environment before
printing this email.[attachment "355x0b0_CESG_Approval with CESG comments
dispositions 2.doc" deleted by Ignacio Aguilar Sanchez/estec/ESA]
</font><tt><font size=2>_______________________________________________<br>
SLS-SEA-DLS mailing list<br>
SLS-SEA-DLS@mailman.ccsds.org<br>
</font></tt><a href="http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls"><tt><font size=2>http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls</font></tt></a><tt><font size=2><br>
</font></tt>
<br><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE>