<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:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (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:Arial;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
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:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle19
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I think it is a good proposal and it is a topic we will address during the SLP WG meeting on Friday AM and perhaps also it could be discussed during the SDLS meeting on Wed.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">However, we don’t have a SLS area joint meeting scheduled in San Antonio.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Perhaps we could take some time on Friday afternoon in the SLS plenary to come up with a joint way forward based upon the discussions in those other two forums.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">G.P. – what do you think?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Thanks!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Greg<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">Moury Gilles <Gilles.Moury@cnes.fr><br>
<b>Date: </b>Tuesday, April 11, 2017 at 4:08 AM<br>
<b>To: </b>"Daniel.Fischer@esa.int" <Daniel.Fischer@esa.int>, "Greenberg, Edward (312B)" <edward.greenberg@jpl.nasa.gov><br>
<b>Cc: </b>Greg Kazz <greg.j.kazz@jpl.nasa.gov>, "sls-sea-dls@mailman.ccsds.org" <sls-sea-dls@mailman.ccsds.org>, Calzolari Gian-Paolo <Gian.Paolo.Calzolari@esa.int><br>
<b>Subject: </b>RE: [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D">Dear Ed,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D">I tend to agree with Daniel : this problem of GVCID ambiguity for bidirectional spacelinks is a general problem that will be encountered not only by SDLS EP (for SA management
procedures) but also for all bidirectional protocols like AOS, USLP for which GVCID does not carry the direction (forward or return) of the VC we are dealing with. The solution you propose to introduce 2 new IDs (GVCIDS, GVCIDR) would solve the ambiguity but
needs to be agreed SLS-wide. Greg and Gian-Paolo: what is your opinion ?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D">Best regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D">Gilles</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Arial;color:#1F497D">Gilles MOURY</span><span style="color:#1F497D">
<br>
</span><span style="font-size:10.0pt;font-family:Arial;color:#1F497D">CNES Toulouse</span><span style="color:#1F497D">
</span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:Tahoma">De :</span></b><span style="font-size:10.0pt;font-family:Tahoma"> Daniel.Fischer@esa.int [mailto:Daniel.Fischer@esa.int]
<br>
<b>Envoyé :</b> mardi 11 avril 2017 12:32<br>
<b>À :</b> Greenberg, Edward (312B)<br>
<b>Cc :</b> Moury Gilles; Kazz, Greg J (312B); sls-sea-dls@mailman.ccsds.org<br>
<b>Objet :</b> RE: [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Arial">Dear Ed,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:Arial">Sorry for not coming back to you earlier. I think we will discuss your recommendation in the upcoming meetings.</span>
<br>
<span style="font-size:10.0pt;font-family:Arial">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.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:Arial">Cheers,</span> <br>
<span style="font-size:10.0pt;font-family:Arial">Daniel</span> <br>
<br>
<b><span style="font-size:7.5pt;font-family:Verdana;color:#00A1E0">Dr. Daniel Fischer</span></b><span style="font-size:7.5pt;font-family:Verdana;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;color:gray">Directorate of Operations</span>
<o:p></o:p></p>
<p><b><span style="font-size:7.5pt;font-family:Verdana;color:gray">ESA - ESOC</span></b><span style="font-size:7.5pt;font-family:Verdana;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;color:gray">Tel. +49 6151 90 2718 | E-mail:
<a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a></span> <br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:Arial">"Greenberg, Edward (312B)" <<a href="mailto:edward.greenberg@jpl.nasa.gov">edward.greenberg@jpl.nasa.gov</a>></span>
<br>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:Arial">Moury Gilles <<a href="mailto:Gilles.Moury@cnes.fr">Gilles.Moury@cnes.fr</a>>, "<a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a>"
<<a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a>>, "<a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a>" <<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;color:#5F5F5F">Cc: </span><span style="font-size:7.5pt;font-family:Arial">"Kazz, Greg J (312B)" <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>></span>
<br>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:Arial">11/04/2017 01:36</span>
<br>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:Arial">RE: [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard</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;color:#004080">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’. </span><br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080"> </span> <br>
<b><span style="font-size:10.0pt;font-family:Tahoma">From:</span></b><span style="font-size:10.0pt;font-family:Tahoma"> Greenberg, Edward (312B)
<b><br>
Sent:</b> Friday, March 31, 2017 2:24 PM<b><br>
To:</b> 'Moury Gilles'; <a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a>;
<a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a><b><br>
Subject:</b> RE: [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080">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. </span>
<br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080"> </span> <br>
<b><span style="font-size:10.0pt;font-family:Tahoma">From:</span></b><span style="font-size:10.0pt;font-family:Tahoma"> SLS-SEA-DLS [</span><a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org"><span style="font-size:10.0pt;font-family:Tahoma">mailto:sls-sea-dls-bounces@mailman.ccsds.org</span></a><span style="font-size:10.0pt;font-family:Tahoma">]
<b>On Behalf Of </b>Moury Gilles<b><br>
Sent:</b> Friday, March 31, 2017 2:00 AM<b><br>
To:</b> </span><a href="mailto:Daniel.Fischer@esa.int"><span style="font-size:10.0pt;font-family:Tahoma">Daniel.Fischer@esa.int</span></a><span style="font-size:10.0pt;font-family:Tahoma">;
</span><a href="mailto:sls-sea-dls@mailman.ccsds.org"><span style="font-size:10.0pt;font-family:Tahoma">sls-sea-dls@mailman.ccsds.org</span></a><b><span style="font-size:10.0pt;font-family:Tahoma"><br>
Subject:</span></b><span style="font-size:10.0pt;font-family:Tahoma"> Re: [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080">Dear all,</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080">My response to David’s questions would be :</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080">Q1 : values 0 and 65535 are reserved (for master keys I understand). Text should be modified.</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080">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.</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080">Q3 : My proposal would be the following:</span>
<br>
<span style="font-size:10.0pt;font-family:Symbol;color:#004080">· </span><span style="font-size:10.0pt;color:#004080"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#004080">
</span><span style="font-size:10.0pt;color:#004080"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#004080">
</span><span style="font-size:10.0pt;color:#004080"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#004080">
</span><span style="font-size:10.0pt;color:#004080"> </span><span style="font-size:10.0pt;font-family:Calibri;color:#004080">For the EP baseline mode, a format is specified for the GVCID/GMAPID field of the Start SA PDU with the following sub-fields:</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New";color:#004080">o </span>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080">TFVN (4 bits)</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New";color:#004080">o </span>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080">SCID (16 bits)</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New";color:#004080">o </span>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080">VCID (6 bits)</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New";color:#004080">o </span>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080">MAPID (6bits)</span>
<br>
<span style="font-size:10.0pt;font-family:Symbol;color:#004080">· </span><span style="font-size:10.0pt;color:#004080"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#004080">
</span><span style="font-size:10.0pt;color:#004080"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#004080">
</span><span style="font-size:10.0pt;color:#004080"> </span><span style="font-size:10.0pt;font-family:Symbol;color:#004080">
</span><span style="font-size:10.0pt;color:#004080"> </span><span style="font-size:10.0pt;font-family:Calibri;color:#004080">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).</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080">Best regards,</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080">Gilles</span> <br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080"> </span> <br>
<span style="font-size:10.0pt;font-family:Arial;color:#004080">Gilles MOURY</span><span style="color:#004080">
</span><span style="font-size:10.0pt;font-family:Arial;color:#004080"><br>
CNES Toulouse</span><span style="color:#004080"> </span><br>
<b><span style="font-size:10.0pt;font-family:Tahoma">De :</span></b><span style="font-size:10.0pt;font-family:Tahoma"> SLS-SEA-DLS [</span><a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org"><span style="font-size:10.0pt;font-family:Tahoma">mailto:sls-sea-dls-bounces@mailman.ccsds.org</span></a><span style="font-size:10.0pt;font-family:Tahoma">]
<b>De la part de</b> </span><a href="mailto:Daniel.Fischer@esa.int"><span style="font-size:10.0pt;font-family:Tahoma">Daniel.Fischer@esa.int</span></a><b><span style="font-size:10.0pt;font-family:Tahoma"><br>
Envoyé :</span></b><span style="font-size:10.0pt;font-family:Tahoma"> vendredi 31 mars 2017 08:57<b><br>
À :</b> </span><a href="mailto:sls-sea-dls@mailman.ccsds.org"><span style="font-size:10.0pt;font-family:Tahoma">sls-sea-dls@mailman.ccsds.org</span></a><b><span style="font-size:10.0pt;font-family:Tahoma"><br>
Objet :</span></b><span style="font-size:10.0pt;font-family:Tahoma"> [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:Arial">Dear all,</span> <br>
<span style="font-size:10.0pt;font-family: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.</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
My take:</span> <span style="font-size:10.0pt;font-family:Arial"><br>
Q1 is a typo and will be corrected. --> No further discussion needed</span> <span style="font-size:10.0pt;font-family:Arial">
<br>
Q2: This should be the case. What do the others think? Do we need to be explicit there?</span>
<span style="font-size:10.0pt;font-family: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?</span>
<br>
<span style="font-size:10.0pt;font-family:Arial"><br>
Cheers,<br>
Daniel.</span> <br>
<b><span style="font-size:7.5pt;font-family:Verdana;color:#00A1E0"><br>
Dr. Daniel Fischer</span></b><span style="font-size:7.5pt;font-family:Verdana;color:gray"><br>
Head of the Engineering Support Section, OPS-GES<br>
Ground Systems Engineering Department</span> <span style="font-size:7.5pt;font-family:Verdana;color:gray">
<br>
Directorate of Operations</span> <o:p></o:p></p>
<p><b><span style="font-size:7.5pt;font-family:Verdana;color:gray">ESA - ESOC</span></b><span style="font-size:7.5pt;font-family:Verdana;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;color:gray">Tel. +49 6151 90 2718 | E-mail:
</span><a href="mailto:Daniel.Fischer@esa.int"><span style="font-size:7.5pt;font-family:Verdana">Daniel.Fischer@esa.int</span></a>
<span style="font-size:7.5pt;font-family:Arial;color:purple"><br>
----- Forwarded by Daniel Fischer/esoc/ESA on 31/03/2017 08:51 -----</span> <br>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
From: </span><a href="mailto:David.Koisser@esa.int"><span style="font-size:7.5pt;font-family:Arial">David.Koisser@esa.int</span></a>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
To: </span><a href="mailto:sls-sea-dls@mailman.ccsds.org"><span style="font-size:7.5pt;font-family:Arial">sls-sea-dls@mailman.ccsds.org</span></a>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
Cc: </span><span style="font-size:7.5pt;font-family:Arial">"John P. Lucas" <</span><a href="mailto:John.P.Lucas@ivv.nasa.gov"><span style="font-size:7.5pt;font-family:Arial">John.P.Lucas@ivv.nasa.gov</span></a><span style="font-size:7.5pt;font-family:Arial">></span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
Date: </span><span style="font-size:7.5pt;font-family:Arial">01/03/2017 11:04</span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
Subject: </span><span style="font-size:7.5pt;font-family:Arial">[Sls-sea-dls] Question regarding the SDLS EP Standard</span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
Sent by: </span><span style="font-size:7.5pt;font-family:Arial">"SLS-SEA-DLS" <</span><a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org"><span style="font-size:7.5pt;font-family:Arial">sls-sea-dls-bounces@mailman.ccsds.org</span></a><span style="font-size:7.5pt;font-family:Arial">></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"><br>
Dear SDLS WG members,</span> <span style="font-size:10.0pt;font-family: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:</span>
<span style="font-size:10.0pt;font-family: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:</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
"Values 0-65535 shall not be used to reference session keys."</span> <span style="font-size:10.0pt;font-family:Arial">
<br>
Which would be all possible Key IDs and leave none for any session keys. Can you clarify?</span>
<span style="font-size:10.0pt;font-family: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)?</span>
<span style="font-size:10.0pt;font-family: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:</span> <span style="font-size:10.0pt;font-family:Arial">
<br>
GVCID = TFVN + SCID + VCID</span> <span style="font-size:10.0pt;font-family:Arial">
<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"><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>
<span style="font-size:10.0pt;font-family:Arial"><br>
<br>
Best Regards,</span> <span style="font-size:10.0pt;font-family:Arial"><br>
David Koisser</span> <span style="font-size:10.0pt;font-family:"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.</span><span style="font-family:"Courier New""><br>
</span><span style="font-size:10.0pt;font-family:"Courier New""><br>
Please consider the environment before printing this email.</span><span style="font-family:"Courier New""><br>
</span><span style="font-size:10.0pt;font-family:"Courier New""><br>
_______________________________________________<br>
SLS-SEA-DLS mailing list<u><span style="color:blue"><br>
</span></u></span><a href="mailto:SLS-SEA-DLS@mailman.ccsds.org"><span style="font-size:10.0pt;font-family:"Courier New"">SLS-SEA-DLS@mailman.ccsds.org</span></a><u><span style="color:blue"><br>
</span></u><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls"><span style="font-size:10.0pt;font-family:"Courier New"">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls</span></a><br>
<span style="font-size:10.0pt;font-family:Arial"><br>
</span><br>
<br>
<b><i><span style="font-size:7.5pt;font-family:Arial;color:gray"><br>
Disclaimer</span></i></b> <i><span style="font-size:7.5pt;font-family:Arial;color:gray"><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.</span></i>
<o:p></o:p></p>
<p style="margin-bottom:12.0pt"><tt><span style="font-size:10.0pt">This message and any attachments are intended for the use of the addressee or addressees only.</span></tt><span style="font-family:"Courier New""><br>
</span><tt><span style="font-size:10.0pt">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span></tt><span style="font-family:"Courier New""><br>
</span><tt><span style="font-size:10.0pt">content is not permitted.</span></tt><span style="font-family:"Courier New""><br>
</span><tt><span style="font-size:10.0pt">If you received this message in error, please notify the sender and delete it from your system.</span></tt><span style="font-family:"Courier New""><br>
</span><tt><span style="font-size:10.0pt">Emails can be altered and their integrity cannot be guaranteed by the sender.</span></tt><span style="font-family:"Courier New""><br>
<br>
</span><tt><span style="font-size:10.0pt">Please consider the environment before printing this email.</span></tt><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:Arial"><br>
</span><br>
<br>
<b><i><span style="font-size:7.5pt;font-family:Arial;color:gray">Disclaimer</span></i></b>
<br>
<i><span style="font-size:7.5pt;font-family:Arial;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>