<font size=2 face="sans-serif">Dear Ed,</font>
<br>
<br><font size=2 face="sans-serif">Sorry for not coming back to you earlier.
I think we will discuss your recommendation in the upcoming meetings.</font>
<br><font size=2 face="sans-serif">In my opinion the scope of the impact
of the new definitions of the GVCIDR/S is not limited to SDLS or SDLS Extended
Procedures and needs to be discussed in a wider frame.</font>
<br>
<br><font size=2 face="sans-serif">Cheers,</font>
<br><font size=2 face="sans-serif">Daniel</font>
<br>
<br><font size=1 color=#00a1e0 face="Verdana"><b>Dr. Daniel Fischer</b></font><font size=1 color=#808080 face="Verdana"><br>
Head of the Engineering Support Section, OPS-GES<br>
Ground Systems Engineering Department</font>
<br><font size=1 color=#808080 face="Verdana">Directorate of Operations</font>
<p><font size=1 color=#808080 face="Verdana"><b>ESA - ESOC</b><br>
Robert-Bosch-Str. 5, D-64392 Darmstadt, Germany</font>
<p><font size=1 color=#808080 face="Verdana">Tel. +49 6151 90 2718 | E-mail:
Daniel.Fischer@esa.int</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Greenberg, Edward
(312B)" <edward.greenberg@jpl.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>,
"Daniel.Fischer@esa.int" <Daniel.Fischer@esa.int>, "sls-sea-dls@mailman.ccsds.org"
<sls-sea-dls@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"Kazz, Greg J
(312B)" <greg.j.kazz@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">11/04/2017 01:36</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">RE: [Sls-sea-dls]
Fw: Question regarding the SDLS EP Standard</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 color=#004080 face="Calibri">I never had a response to
my recommendation. I made this recommendation for compatibility with
AOS, proximity 1 and USLP since these protocols can be used in both directions
thus the PVN is not a discriminator. TM and TC have a 2 bit PVN
and they are both ‘00’. </font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 face="Tahoma"><b>From:</b> Greenberg, Edward (312B) <b><br>
Sent:</b> Friday, March 31, 2017 2:24 PM<b><br>
To:</b> 'Moury Gilles'; Daniel.Fischer@esa.int; sls-sea-dls@mailman.ccsds.org<b><br>
Subject:</b> RE: [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 color=#004080 face="Calibri">The SCID identifies the Spacecraft.
The SOURCE/DESTINATION FLAG identifies the sending side or the receiving
side. Thus by including the SOURCE/DESTINATION FLAG into the GVCID/GMAPID
you determine the sending side GVCID verses the receiving side GVCID. By
simply modifying the term GVCID to GVCIDS for the sending side and GVCIDR
for the receiving side you separate the VCs by directionality which is
exactly what you want. </font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 face="Tahoma"><b>From:</b> SLS-SEA-DLS [</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>On Behalf Of </b>Moury Gilles<b><br>
Sent:</b> Friday, March 31, 2017 2:00 AM<b><br>
To:</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: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"><b><br>
Subject:</b> Re: [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 color=#004080 face="Calibri">Dear all,</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">My response to David’s questions
would be :</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Q1 : values 0 and 65535 are
reserved (for master keys I understand). Text should be modified.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Q2 : EP baseline mode relies
on SDLS baseline mode. SDLS baseline mode uses AES-GCM. In that case, the
SN is replaced by the IV which is 96 bits. Therefore, the Set ARC procedure
of the EP baseline mode is actually setting the IV. I would recommend adding
this clarification in the EP baseline mode specification and changing the
length of the “New anti-replay counter value” field from 64 to 96 bits
for consistency with SDLS baseline mode.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Q3 : My proposal would be
the following:</font>
<br><font size=2 color=#004080 face="Symbol">· </font><font size=2 color=#004080 face="Calibri">For
the EP baseline mode, a format is specified for the GVCID/GMAPID field
of the Start SA PDU with the following sub-fields:</font>
<br><font size=2 color=#004080 face="Courier New">o </font><font size=2 color=#004080 face="Calibri">TFVN
(4 bits)</font>
<br><font size=2 color=#004080 face="Courier New">o </font><font size=2 color=#004080 face="Calibri">SCID
(16 bits)</font>
<br><font size=2 color=#004080 face="Courier New">o </font><font size=2 color=#004080 face="Calibri">VCID
(6 bits)</font>
<br><font size=2 color=#004080 face="Courier New">o </font><font size=2 color=#004080 face="Calibri">MAPID
(6bits)</font>
<br><font size=2 color=#004080 face="Symbol">· </font><font size=2 color=#004080 face="Calibri">Since
we have specified TFVN sub-field length as 4 bits, we have 2 spare bits
there. We could use one of them to distinguish TC from TM : ‘000’ would
code for TC TFVN and ‘100’ would code for TM TFVN, while ‘001’ would
code for AOS and ‘010’ for Prox-1 (which is not covered by SDLS by the
way).</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="Calibri"> </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> SLS-SEA-DLS [</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> </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"><b><br>
Envoyé :</b> vendredi 31 mars 2017 08:57<b><br>
À :</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"><b><br>
Objet :</b> [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Arial">Dear all,</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
Could ask you to take a look at the questions that David sent a while go...some
of them need answers before a red book can be produced.</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
My take:</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
Q1 is a typo and will be corrected. --> No further discussion needed</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
Q2: This should be the case. What do the others think? Do we need to be
explicit there?</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
Q3: This is a critical one and we don't have an answer at the moment. I
remember we discussed this in the WG already but I am not sure we came
to a conclusion. This needs to be clarified in the standard. Any opinions?</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
Cheers,<br>
Daniel.</font><font size=3 face="Times New Roman"> <br>
</font><font size=1 color=#00a1e0 face="Verdana"><b><br>
Dr. Daniel Fischer</b></font><font size=1 color=#808080 face="Verdana"><br>
Head of the Engineering Support Section, OPS-GES<br>
Ground Systems Engineering Department</font><font size=3 face="Times New Roman">
</font><font size=1 color=#808080 face="Verdana"><br>
Directorate of Operations</font><font size=3 face="Times New Roman"> </font>
<p><font size=1 color=#808080 face="Verdana"><b>ESA - ESOC</b><br>
Robert-Bosch-Str. 5, D-64392 Darmstadt, Germany</font><font size=3 face="Times New Roman">
</font>
<p><font size=1 color=#808080 face="Verdana">Tel. +49 6151 90 2718 | E-mail:
</font><a href=mailto:Daniel.Fischer@esa.int><font size=1 color=blue face="Verdana"><u>Daniel.Fischer@esa.int</u></font></a><font size=3 face="Times New Roman">
</font><font size=1 color=#800080 face="Arial"><br>
----- Forwarded by Daniel Fischer/esoc/ESA on 31/03/2017 08:51 -----</font><font size=3 face="Times New Roman">
<br>
</font><font size=1 color=#5f5f5f face="Arial"><br>
From: </font><a href=mailto:David.Koisser@esa.int><font size=1 color=blue face="Arial"><u>David.Koisser@esa.int</u></font></a><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="Arial"><br>
To: </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=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="Arial"><br>
Cc: </font><font size=1 face="Arial">"John
P. Lucas" <</font><a href=mailto:John.P.Lucas@ivv.nasa.gov><font size=1 color=blue face="Arial"><u>John.P.Lucas@ivv.nasa.gov</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">01/03/2017
11:04</font><font size=3 face="Times New Roman"> </font><font size=1 color=#5f5f5f face="Arial"><br>
Subject: </font><font size=1 face="Arial">[Sls-sea-dls]
Question regarding the SDLS EP Standard</font><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="Arial"><br>
Sent by: </font><font size=1 face="Arial">"SLS-SEA-DLS"
<</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=1 face="Arial">></font><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="Calibri"><br>
Dear SDLS WG members,</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
<br>
John and I have completed setting up the interoperability testing environment
and now we are doing a few finishing touches. Whilst doing this a few questions
arose regarding the SDLS EP standard:</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
<br>
1. In Section E4.2.2 (in the baseline mode description of Key Activation)
and the following key procedures, it defines the Key ID fields to have
a length of 16 bits. And then states:</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
"Values 0-65535 shall not be used to reference session keys."</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
Which would be all possible Key IDs and leave none for any session keys.
Can you clarify?</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
<br>
2. While we are fairly sure it is implied: Does the M&C procedure Set
ARC set the IV instead of the SN parameter in the regarding cases (e.g.
AES-GCM)?</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
<br>
3. The standard is not addressing how to distinguish if a GVCID is regarding
the TM or TC channels for the Start SA procedure. An example to clarify:
<br>
<br>
A mission wants a different SA assigned on VC 0 for the uplink (e.g. authentication
only) than the VC 0 for the downlink (e.g. authenticated encryption). To
be able to set this with the Start SA procedure, it needs a way to distinguish
between the TC and TM channel mapping to SPIs. As the GVCID is defined
as:</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
GVCID = TFVN + SCID + VCID</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
And the 2 bits long TFVN may have the following values: 01 -> AOS; 10
-> Proximity-1; 00 -> TM- *or* TC-SDLP</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
The GVCID alone is not enough to distinguish between TC and TM and we are
currently using a custom data structure for unambiguously identifying the
channels in the Start SA procedure.</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
<br>
Best Regards,</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
David Koisser</font><font size=3 face="Times New Roman"> </font><font size=2 face="Courier New"><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.</font><font size=3 face="Courier New"><br>
</font><font size=2 face="Courier New"><br>
Please consider the environment before printing this email.</font><font size=3 face="Courier New"><br>
</font><font size=2 face="Courier New"><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="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls"><font size=2 color=blue face="Courier New"><u>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls</u></font></a><font size=3 face="Times New Roman"><br>
</font><font size=2 face="Arial"><br>
</font><font size=3 face="Times New Roman"><br>
<br>
</font><font size=1 color=#808080 face="Arial"><b><i><br>
Disclaimer</i></b></font><font size=3 face="Times New Roman"> </font><font size=1 color=#808080 face="Arial"><i><br>
This message and any attachments are intended for the use of the addressee
or addressees only. The unauthorized 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.</i></font>
<p><tt><font size=3>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>
</font></tt>
<p>
<p><font size=2 face="sans-serif"><br>
</font>
<br>
<br><font size=1 color=#808080 face="Arial"><b><i>Disclaimer</i></b></font>
<br><font size=1 color=#808080 face="Arial"><i>This message and any attachments
are intended for the use of the addressee or addressees only. The unauthorized
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.</i></font>