<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1255362620;
mso-list-type:hybrid;
mso-list-template-ids:-1768766120 67895297 67895299 67895301 67895297 67895299 67895301 67895297 67895299 67895301;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="FR" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dear all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">My response to David’s questions would be :<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Q1 : values 0 and 65535 are reserved (for master keys I understand). Text should be modified.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Q2 : EP baseline mode relies on SDLS baseline mode.
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Q3 : My proposal would be the following:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-US" style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">For the EP baseline mode, a format is specified for the GVCID/GMAPID field of the Start SA PDU with the following sub-fields:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level2 lfo1">
<![if !supportLists]><span lang="EN-US" style="font-size:11.0pt;font-family:"Courier New";color:#1F497D"><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">TFVN (4 bits)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level2 lfo1">
<![if !supportLists]><span lang="EN-US" style="font-size:11.0pt;font-family:"Courier New";color:#1F497D"><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">SCID (16 bits)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level2 lfo1">
<![if !supportLists]><span lang="EN-US" style="font-size:11.0pt;font-family:"Courier New";color:#1F497D"><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">VCID (6 bits)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level2 lfo1">
<![if !supportLists]><span lang="EN-US" style="font-size:11.0pt;font-family:"Courier New";color:#1F497D"><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">MAPID (6bits)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-US" style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Gilles<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">Gilles MOURY</span><span lang="EN-US" style="color:#1F497D">
<br>
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">CNES Toulouse</span><span lang="EN-US" style="color:#1F497D">
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">De :</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> SLS-SEA-DLS [mailto:sls-sea-dls-bounces@mailman.ccsds.org]
<b>De la part de</b> Daniel.Fischer@es</span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">a.int<br>
<b>Envoyé :</b> vendredi 31 mars 2017 08:57<br>
<b>À :</b> sls-sea-dls@mailman.ccsds.org<br>
<b>Objet :</b> [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Dear all,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">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.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">My take:</span> <br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Q1 is a typo and will be corrected. --> No further discussion needed</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Q2: This should be the case. What do the others think? Do we need to be explicit there?</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">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?</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Cheers,<br>
Daniel.</span> <br>
<br>
<b><span style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:#00A1E0">Dr. Daniel Fischer</span></b><span style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray"><br>
Head of the Engineering Support Section, OPS-GES<br>
Ground Systems Engineering Department</span> <br>
<span style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray">Directorate of Operations</span>
<o:p></o:p></p>
<p><b><span style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray">ESA - ESOC</span></b><span style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray"><br>
Robert-Bosch-Str. 5, D-64392 Darmstadt, Germany</span> <o:p></o:p></p>
<p><span style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray">Tel. +49 6151 90 2718 | E-mail:
<a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a></span> <br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:purple">----- Forwarded by Daniel Fischer/esoc/ESA on 31/03/2017 08:51 -----</span>
<br>
<br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif""><a href="mailto:David.Koisser@esa.int">David.Koisser@esa.int</a></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif""><a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Cc: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">"John P. Lucas" <<a href="mailto:John.P.Lucas@ivv.nasa.gov">John.P.Lucas@ivv.nasa.gov</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">01/03/2017 11:04</span>
<br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">[Sls-sea-dls] Question regarding the SDLS EP Standard</span>
<br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Sent by: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">"SLS-SEA-DLS" <<a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org">sls-sea-dls-bounces@mailman.ccsds.org</a>></span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Dear SDLS WG members,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""><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:</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""><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:</span>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
"Values 0-65535 shall not be used to reference session keys."</span> <span style="font-size:10.0pt;font-family:"Arial","sans-serif"">
<br>
Which would be all possible Key IDs and leave none for any session keys. Can you clarify?</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""><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)?</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""><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:
</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""><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:</span> <span style="font-size:10.0pt;font-family:"Arial","sans-serif"">
<br>
GVCID = TFVN + SCID + VCID</span> <span style="font-size:10.0pt;font-family:"Arial","sans-serif"">
<br>
And the 2 bits long TFVN may have the following values: 01 -> AOS; 10 -> Proximity-1; 00 -> TM- *or* TC-SDLP</span>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""><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.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Best Regards,</span> <span style="font-size:10.0pt;font-family:"Arial","sans-serif"">
<br>
David Koisser</span> <br>
<tt>This message and any attachments are intended for the use of the addressee or addressees only.</tt><span style="font-family:"Courier New""><br>
<tt>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</tt><br>
<tt>content is not permitted.</tt><br>
<tt>If you received this message in error, please notify the sender and delete it from your system.</tt><br>
<tt>Emails can be altered and their integrity cannot be guaranteed by the sender.</tt><br>
<br>
<tt>Please consider the environment before printing this email.</tt><br>
<br>
</span><tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>SLS-SEA-DLS mailing list</tt><br>
<tt><a href="mailto:SLS-SEA-DLS@mailman.ccsds.org">SLS-SEA-DLS@mailman.ccsds.org</a></tt><br>
</span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls</span></tt></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
</span><br>
<br>
<b><i><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:gray">Disclaimer</span></i></b>
<br>
<i><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:gray">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.</span></i><o:p></o:p></p>
</div>
</body>
</html>