<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 20px; font-family: Calibri, sans-serif; ">
<div>Bonjour Gilles,</div>
<div><br>
</div>
<div>Thank you for contribution. Essentially you are saying that the green box in both Figures 6c and 6d should shrink so that it does not expand beyond either the Master Channel Multiplexing Function or the MC Demultiplexing Function. In other words, there
is no interface point for SDLS with either the TC-SDLP 'All frames generation' or 'All Frames receiption' functions. This makes sense. However, Figures 6c and 6d are very nebulous in the sense that there is this "SDLS ApplySecurity Function" seemingly floating
around in space that shows an anchor at the port of "Virtual Channel Multiplexing/Demultiplexing" only for example. The text says it could be in Virtual Channel Generation Function or in the Virtual Channel Multiplexing function. No text talks about the possibility
in the MC Multiplexing function. Also the COP management Function is called out in 6c, but no such reciprocal function exists in 6d. I think we are still lacking a clear explanation of these figures in the text. </div>
<div><br>
</div>
<div>We still need a better way to convey the relationships between the protocols involved including the order of overall processing to the user I.e., between SDLS, COP-1, TC-SDLP. I think some kind of high order diagram and text that shows the order of processing
between them is needed. </div>
<div><br>
</div>
<div>We also need to modify the TC Sync & CC Green book so that we capture the rationale behind our decisions on the order of processing of SDLS, COP-1, TC-SDLP (much of which you have already captured in the meeting minutes of our last TIM, but some business
is yet to be completed).</div>
<div><br>
</div>
<div>Comments anyone ?</div>
<div><br>
</div>
<div>Best regards,</div>
<div><br>
</div>
<div>Greg</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Moury Gilles <<a href="mailto:Gilles.Moury@cnes.fr">Gilles.Moury@cnes.fr</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, March 14, 2013 10:06 AM<br>
<span style="font-weight:bold">To: </span>"Kazz, Greg J (313B)" <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Cc: </span>"Greenberg, Edward (313B)" <<a href="mailto:edward.greenberg@jpl.nasa.gov">edward.greenberg@jpl.nasa.gov</a>>, "Biggerstaff, Craig (JSC-DD12)[LOCKHEED MARTIN CORP]" <<a href="mailto:craig.biggerstaff-1@nasa.gov">craig.biggerstaff-1@nasa.gov</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>>, "<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a>" <<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Subject: </span>RE: Order of Processing COP-1 and SDLS<br>
</div>
<div><br>
</div>
<div 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">
<meta name="Generator" content="Microsoft Word 12 (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;}
/* 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;}
span.EmailStyle18
{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: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]-->
<div lang="FR" link="blue" vlink="purple" style="word-wrap: break-word;-webkit-nbsp-mode: space;-webkit-line-break: after-white-space">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">Dear Greg,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">Please find attached the additions I propose to the TC-SDLP book to avoid users implementing the wrong order of processing between SDLS and "frame
error detection" by TC-SDLP. In fact, the only forbidden configuration for interfacing SDLS function with TC-SDLP functions is interfacing SDLS with "All Frame Generation" at the sending end and "All Frame Reception" at the receiving end. This guarantee that,
at the receiving end, transmission errors are detected and impacted frames discarded first , before SDLS processes the frames, which satisfies our security requirement that transmission errors should be unambiguously separated from security errors.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">I have therefore introduced an additional text in sections 6.3.1 and 6.4.1 to forbid this configuration (see attached redlined file). I think it
covers the point. All comments are welcome.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">Gilles<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10pt; color: rgb(31, 73, 125); font-family: Arial, sans-serif; ">Gilles MOURY</span><span style="color:#1F497D"><br>
</span><span style="font-size: 10pt; color: rgb(31, 73, 125); font-family: Arial, sans-serif; ">CNES Toulouse</span><span style="color:#1F497D"></span><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">De :</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; "> Kazz, Greg J (313B) [<a href="mailto:greg.j.kazz@jpl.nasa.gov">mailto:greg.j.kazz@jpl.nasa.gov</a>]
<br>
<b>Envoyé :</b> lundi 11 mars 2013 23:02<br>
<b>À :</b> Moury Gilles<br>
<b>Cc :</b> Greenberg, Edward (313B); Biggerstaff, Craig (JSC-DD12)[LOCKHEED MARTIN CORP]<br>
<b>Objet :</b> Order of Processing COP-1 and SDLS<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size: 15pt; color: black; font-family: Calibri, sans-serif; ">Gilles,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 15pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 15pt; color: black; font-family: Calibri, sans-serif; ">Correct me if I am wrong, but I did not see a response from you regarding this action item below:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 15pt; color: black; font-family: Calibri, sans-serif; ">We do not have text in the TC SLP section 6 document which deals with this issue yet.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 15pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 15pt; color: black; font-family: Calibri, sans-serif; ">- best regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 15pt; color: black; font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:15.0pt"><span style="font-size: 15pt; color: black; font-family: Calibri, sans-serif; ">Greg<o:p></o:p></span></p>
<table class="TableNormal" border="1" cellspacing="0" cellpadding="0" width="502" style="border-collapse:collapse;border:none">
<tbody>
<tr>
<td width="115" valign="top" style="width:86.4pt;border:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt">
<p class="MsoNormal" align="center" style="text-align:center"><span style="font-size:11.0pt">SDLS0213/01</span><o:p></o:p></p>
<p class="MsoNormal" align="center" style="text-align:center"> <o:p></o:p></p>
</td>
<td width="96" valign="top" style="width:72.0pt;border:solid windowtext 1.0pt;border-left:none;padding:0cm 5.4pt 0cm 5.4pt">
<p class="MsoNormal" align="center" style="text-align:center"><span style="font-size:10.0pt">G. Moury</span><o:p></o:p></p>
</td>
<td width="363" valign="top" style="width:272.25pt;border:solid windowtext 1.0pt;border-left:none;padding:0cm 5.4pt 0cm 5.4pt">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-GB" style="font-size:11.0pt">Propose a solution to explicitly specify the order of processing at the receiving end between TC-COP and SDLS (if not already present in section 6 of TC-SLP)
</span><o:p></o:p></p>
</td>
<td width="95" valign="top" style="width:70.9pt;border:solid windowtext 1.0pt;border-left:none;padding:0cm 5.4pt 0cm 5.4pt">
<p class="MsoNormal" align="center" style="text-align:center"><span style="font-size:11.0pt"> March 8, 2013</span><o:p></o:p></p>
<p class="MsoNormal" align="center" style="text-align:center"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</span>
</body>
</html>