<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)">
<style><!--
/* Font Definitions */
@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";}
span.EmailStyle18
{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;}
--></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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dear Daniel,<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">Thank you for this updated and now complete version of the SDLS Extended Procedures draft red book. I will review the document and encourage WG
members to do likewise so we can spot any coherency or editorial problem. I agree that it will be difficult to converge before the meeting by mail on all the remaining points you listed. Therefore, I will include in the agenda of the San Antonio meeting a
point on the “finalization of SDLS EP red-1”. To maximize our chances to effectively converge on a commonly agreed red-1 book at the end of the meeting, we should make sure we collect all the issues before the meeting. I will also include in the agenda a specific
point on “GVCID and unambiguous identification of VCs in bidirectional links”, this point to be discussed jointly with SLP WG.<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">Best regards,<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">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: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">SDLS WG Chair</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 [mailto:sls-sea-dls-bounces@mailman.ccsds.org]
<b>De la part de</b> Daniel.Fischer@esa.int<br>
<b>Envoyé :</b> mercredi 12 avril 2017 10:49<br>
<b>À :</b> sls-sea-dls@mailman.ccsds.org<br>
<b>Objet :</b> [Sls-sea-dls] SDLS Extended Prcocedures Red Book Draft 1.3<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"">I have finished the update of the SDLS Extended Procedures Draft Red Book. Please find it attached.</span>
<br>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Updates included:</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">- Definition of managed parameters for Key Management</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">- Definition of managed parameters for SU Management and Control</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">- Inclusion of Key Management and SU Management and Control PDUs in the PICS</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">- Completed Security Section</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">- Updated Baseline Mode (DK comments, Inclusion of CRC definition provided by Gilles (D 4.3))</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Please note: This is a HUGE document. I am pretty sure there are still a not of small problems in it. If you have some time, could you please check the document for things like this?</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
I am afraid we are not ready for Red Book Status yet. In recent discussions on the mailing list and also with industry a number of questions popped up that need to be clarified first.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">1) SA Management Discussion</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">It was pointed out that the way how keys can be changed on a running SA may not be practicable. At the moment, this requires four SA procedures to be executed. (1) Stoop SA, (2) Expire SA (3) Rekey
SA (4) Start SA. However, it may be preferable to be able to change the keys "on the fly" without having to shut down the SA. This would make key changing much simpler.
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">2) OTAR/Key Verification Procedures Discussion</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">The rationale for us to introduce the CRC check was to be able to execute the Key Verification without having to start the lifetime of the key that is being checked. Industry however pointed out
that (1) These kind of checks are usually done by the spacecraft anyway on its memory and (2) That a CRC is not secure and will not guarantee that keys cannot be modified onboard the spacecraft. Instead they suggested to go back to the old Challenge/Response
concept but only execute that prior to activating the session key for operations anyway. In this way, the start of the key lifetime is not a problem.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">3) Use of Master Keys</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">We have specified which procedures are considered sensitive. Industry pointed out that it is still not clear which procedures requires protection under a master key (so far only the OTAR specifies
that directly) and in general what the master keys are being used for. Some of this is in the Symmetric Key Management Book however we should think about if we want to have other procedures especially protected under the use of a master key.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">4) Association of ARC to Key instead of SPI</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Industry suggested to associate the ARC to a key rather than an SPI. They argue that is is a more natural connection since a new key would also start a new ARC (TBD). I personally disagree with
this but I think its worth discussing this in the group.</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">5) Frame Security Report</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Industry appreciates the concept but has argued that the inclusion of additional error sources (and thus more flags and reduced bits from SN) should be included such as (a) bad MAC, (b) invalid
Key/SA state, (c) invalid frame length. For me this makes sense.</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">6) Unique Identification of Sender and Receiver VCs.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">David has raised the point once more that sender and receiver VCs can currently not be distinguished (since the GVCID is not unique for up and downlinks). A discussion with SLS should take place
in the meeting to find a solution for this since it does not only touch the Extended Procedures.
</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Small things to be approved by the WG:</span> <br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">- There seems to be a possible misunderstanding regarding the reserved SPIs. Industry thought that it always has to be exactly the two reserved ones for EP and no more. We may want to add a clarification.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">- Discussion on the extend to which the security log is specified in the Extended procedures. Ed suggested the global definition of a GVCIDS and GVCIDR which I personally find a good solution.</span>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">While this looks like a lot of discussion material, I think we will actually be able to finalise the discussions in the next meeting and then publish the Red Book afterwards.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Cheers,<br>
Daniel</span> <br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""> </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><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.<br>
</span></i><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>