<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:0in;
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:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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;}
/* 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:-.25in;
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:-.25in;
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:-.25in;
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:-.25in;
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:-.25in;
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:-.25in;
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:-.25in;
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:-.25in;
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:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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’.
<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>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Greenberg, Edward (312B)
<br>
<b>Sent:</b> Friday, March 31, 2017 2:24 PM<br>
<b>To:</b> 'Moury Gilles'; Daniel.Fischer@esa.int; sls-sea-dls@mailman.ccsds.org<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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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. <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>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> SLS-SEA-DLS [<a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org">mailto:sls-sea-dls-bounces@mailman.ccsds.org</a>]
<b>On Behalf Of </b>Moury Gilles<br>
<b>Sent:</b> Friday, March 31, 2017 2:00 AM<br>
<b>To:</b> <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><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>
<p class="MsoNormal"><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dear all,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR" 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">My response to David’s questions would be :<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 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 style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Q2 : EP baseline mode relies on SDLS baseline mode.
</span><span 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 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">Q3 : My proposal would be the following:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span 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 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:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2">
<![if !supportLists]><span 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 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:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2">
<![if !supportLists]><span 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 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:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2">
<![if !supportLists]><span 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 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:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2">
<![if !supportLists]><span 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 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:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span 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 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 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">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Gilles<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 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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">Gilles MOURY</span><span style="color:#1F497D">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">CNES Toulouse</span><span style="color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">De :</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> SLS-SEA-DLS [<a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org">mailto:sls-sea-dls-bounces@mailman.ccsds.org</a>]
<b>De la part de</b> <a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@es<span lang="FR">a.int</span></a></span><span lang="FR" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><br>
<b>Envoyé :</b> vendredi 31 mars 2017 08:57<br>
<b>À :</b> <a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a><br>
<b>Objet :</b> [Sls-sea-dls] Fw: Question regarding the SDLS EP Standard<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="FR" style="font-size:10.0pt;font-family:"Arial","sans-serif"">Dear all,</span><span lang="FR">
<br>
<br>
</span><span lang="FR" 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><span lang="FR">
<br>
</span><span lang="FR" style="font-size:10.0pt;font-family:"Arial","sans-serif"">My take:</span><span lang="FR">
<br>
</span><span lang="FR" style="font-size:10.0pt;font-family:"Arial","sans-serif"">Q1 is a typo and will be corrected. --> No further discussion needed</span><span lang="FR">
<br>
</span><span lang="FR" 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><span lang="FR">
<br>
</span><span lang="FR" 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><span lang="FR"> <br>
<br>
</span><span lang="FR" style="font-size:10.0pt;font-family:"Arial","sans-serif"">Cheers,<br>
Daniel.</span><span lang="FR"> <br>
<br>
</span><b><span lang="FR" style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:#00A1E0">Dr. Daniel Fischer</span></b><span lang="FR" 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><span lang="FR"> <br>
</span><span lang="FR" style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray">Directorate of Operations</span><span lang="FR">
<o:p></o:p></span></p>
<p><b><span lang="FR" style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray">ESA - ESOC</span></b><span lang="FR" style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:gray"><br>
Robert-Bosch-Str. 5, D-64392 Darmstadt, Germany</span><span lang="FR"> <o:p></o:p></span></p>
<p><span lang="FR" 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><span lang="FR">
<br>
</span><span lang="FR" 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><span lang="FR">
<br>
<br>
</span><span lang="FR" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">From: </span><span lang="FR" style="font-size:7.5pt;font-family:"Arial","sans-serif""><a href="mailto:David.Koisser@esa.int">David.Koisser@esa.int</a></span><span lang="FR">
<br>
</span><span lang="FR" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">To: </span><span lang="FR" 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><span lang="FR">
<br>
</span><span lang="FR" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Cc: </span><span lang="FR" 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><span lang="FR">
<br>
</span><span lang="FR" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Date: </span><span lang="FR" style="font-size:7.5pt;font-family:"Arial","sans-serif"">01/03/2017 11:04</span><span lang="FR">
<br>
</span><span lang="FR" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Subject: </span><span lang="FR" style="font-size:7.5pt;font-family:"Arial","sans-serif"">[Sls-sea-dls] Question regarding the SDLS EP Standard</span><span lang="FR">
<br>
</span><span lang="FR" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Sent by: </span><span lang="FR" 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><span lang="FR">
<o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span lang="FR">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</span></div>
<p class="MsoNormal"><span lang="FR"><br>
<br>
<br>
</span><span lang="FR" style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Dear SDLS WG members,</span><span lang="FR">
<br>
</span><span lang="FR" 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><span lang="FR">
<br>
</span><span lang="FR" 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 lang="FR">
</span><span lang="FR" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
"Values 0-65535 shall not be used to reference session keys."</span><span lang="FR">
</span><span lang="FR" 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><span lang="FR">
<br>
</span><span lang="FR" 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><span lang="FR">
<br>
</span><span lang="FR" 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><span lang="FR"><br>
</span><span lang="FR" 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 lang="FR"> </span>
<span lang="FR" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
GVCID = TFVN + SCID + VCID</span><span lang="FR"> </span><span lang="FR" 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 lang="FR">
</span><span lang="FR" 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><span lang="FR">
<br>
</span><span lang="FR" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Best Regards,</span><span lang="FR"> </span><span lang="FR" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
David Koisser</span><span lang="FR"> <br>
</span><tt><span lang="FR" style="font-size:10.0pt">This message and any attachments are intended for the use of the addressee or addressees only.</span></tt><span lang="FR" style="font-family:"Courier New""><br>
</span><tt><span lang="FR" style="font-size:10.0pt">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span></tt><span lang="FR" style="font-family:"Courier New""><br>
</span><tt><span lang="FR" style="font-size:10.0pt">content is not permitted.</span></tt><span lang="FR" style="font-family:"Courier New""><br>
</span><tt><span lang="FR" 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 lang="FR" style="font-family:"Courier New""><br>
</span><tt><span lang="FR" style="font-size:10.0pt">Emails can be altered and their integrity cannot be guaranteed by the sender.</span></tt><span lang="FR" style="font-family:"Courier New""><br>
<br>
</span><tt><span lang="FR" style="font-size:10.0pt">Please consider the environment before printing this email.</span></tt><span lang="FR" style="font-family:"Courier New""><br>
<br>
</span><tt><span lang="FR" style="font-size:10.0pt">_______________________________________________</span></tt><span lang="FR" 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><span lang="FR"><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><span lang="FR" style="font-size:10.0pt;font-family:"Courier New""><br>
</span><span lang="FR"><br>
</span><span lang="FR" style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
</span><span lang="FR"><br>
<br>
</span><b><i><span lang="FR" style="font-size:7.5pt;font-family:"Arial","sans-serif";color:gray">Disclaimer</span></i></b><span lang="FR">
<br>
</span><i><span lang="FR" 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><span lang="FR"><o:p></o:p></span></p>
</div>
</body>
</html>