<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=utf-8">
<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:NotesEsa;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:139662862;
mso-list-template-ids:-1918230376;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:1663578939;
mso-list-template-ids:1577242444;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi Ignacio & Craig,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is turning out to be a very good collaboration between SLDS and SLP WGs.
<o:p></o:p></p>
<p class="MsoNormal">As long as you show Time with in arrow moving from left to right, I believe you do not have to swap swim lanes to fix the perception that Ignacio points out below.<o:p></o:p></p>
<p class="MsoNormal">Clearly, we have to convey the inner processing loop is the COP, which is surrounded by the outer processing loop of SDLS. I think the diagram does this, but showing time explicitly moving Left to Right will clarify that point.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Attached is also a set of send and receive side tables that complements Craig’s diagram. I have integrated Gian Paolo’s comments into it now. These tables provide detail and references to each of the steps in Craig’s diagram. However, that
additional detail should not be numbered in the table (only listed as un-numbered steps) so that it doesn’t confuse the order of processing.) I think it does make sense to combine encoding and randomization into one box as G.P. suggests but keep the note
concerning the order between the two. However, given the importance of the SDLS functions in this diagram, “Apply Security” should remain numbered as a major function i.e., #2, as well as “Process Security” (which will now be renumbered as number 18). Please
see revised attachment.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal">Greg<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">SLS-SEA-DLS <sls-sea-dls-bounces@mailman.ccsds.org> on behalf of "Ignacio.Aguilar.Sanchez@esa.int" <Ignacio.Aguilar.Sanchez@esa.int><br>
<b>Date: </b>Sunday, May 9, 2021 at 11:05 PM<br>
<b>To: </b>"Biggerstaff, Craig (JSC-CD42)[SGT, INC]" <craig.biggerstaff@nasa.gov><br>
<b>Cc: </b>"sls-sea-dls@mailman.ccsds.org" <sls-sea-dls@mailman.ccsds.org><br>
<b>Subject: </b>Re: [Sls-sea-dls] [EXTERNAL] TR: CCSDS Order of Processing: Figure 6-3 in CCSDS 232.0 and Figure 3-3 in CCSDS 350.5-G<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Craig,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Thanks for the update.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Just one more thing that I see now that I did not see before, sorry!</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The current ordering of lanes would suggest that SDLS processing takes place before COP-1 at reception (opposite order at sending side).
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This would convey a wrong message since security processing can only take place at reception once transmission error control has been completed.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Security is only processed at reception on data that has a sufficiently low undetected error rate.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I believe a swap of SDLS and COP-1 lanes is sufficient to fix this.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">We can help as well with the text describing the drawing.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Kind regards,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Ignacio</span> <br>
<br>
<img width="92" height="33" style="width:.9583in;height:.3437in" id="_x0000_i1031" src="cid:image001.gif@01D74579.62689760"><span style="font-size:12.0pt"> </span>
<br>
<br>
<b><span style="font-size:9.0pt;font-family:"NotesEsa",serif;color:#4F4F4F">Ignacio Aguilar Sánchez</span></b>
<br>
<span style="font-size:9.0pt;font-family:"NotesEsa",serif;color:#4F4F4F">Communication Systems Engineer</span>
<br>
<span style="font-size:9.0pt;font-family:"NotesEsa",serif;color:#4F4F4F">Electrical Engineering Department</span>
<br>
<br>
<span style="font-size:9.0pt;font-family:"NotesEsa",serif;color:#4F4F4F">European Space Research and Technology Centre<br>
Keplerlaan 1, PO Box 299, 2200 AG Noordwijk, The Netherlands</span> <br>
<span style="font-size:9.0pt;font-family:"NotesEsa",serif;color:#4F4F4F">Tel. (31) 71 565 5695</span>
<br>
<span style="font-size:9.0pt;font-family:"NotesEsa",serif;color:#4F4F4F">Fax (31) 71 565 5418</span>
<br>
<span style="font-size:9.0pt;font-family:"NotesEsa",serif;color:#4F4F4F">Email: ignacio.aguilar.sanchez@esa.int<br>
</span><a href="https://urldefense.us/v3/__http:/www.esa.int__;!!PvBDto6Hs4WbVuu7!f2RDZSbDqQP6R8RYEaBVnKXm-96d0iWq7zgLgm_5cb7VdV_fKIwQtBeg-uvBQ0xqdX1u42G1$"><span style="font-size:9.0pt;font-family:"NotesEsa",serif">www.esa.int</span></a>
<br>
<br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Biggerstaff, Craig (JSC-CD42)[SGT, INC]" <craig.biggerstaff@nasa.gov></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Ignacio.Aguilar.Sanchez@esa.int" <Ignacio.Aguilar.Sanchez@esa.int></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Moury Gilles" <Gilles.Moury@cnes.fr>, "sls-sea-dls@mailman.ccsds.org" <sls-sea-dls@mailman.ccsds.org></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">07/05/2021 20:46</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">RE: [Sls-sea-dls] [EXTERNAL] TR: CCSDS Order of Processing: Figure 6-3 in CCSDS 232.0 and Figure 3-3
in CCSDS 350.5-G</span> <o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in"><span style="color:#004080">Ignacio, thanks for your comments. I definitely agree that RF & Modulation should be a separate ‘lane’, and corrected that oversight in the latest version (attached). At the recommendation of some C&S WG members
(whose discussion prompted this diagram in the first place), I also added a legend, a note on BCH ordering, and numbering of sequential flow. I did not incorporate your other suggestions, as the diagram can’t include much more visual information without losing
easy readability.</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">Best regards,</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">Craig</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><b>From:</b> Ignacio.Aguilar.Sanchez@esa.int <Ignacio.Aguilar.Sanchez@esa.int>
<b><br>
Sent:</b> Thursday, May 6, 2021 1:46 AM<b><br>
To:</b> Biggerstaff, Craig (JSC-CD42)[SGT, INC] <craig.biggerstaff@nasa.gov><b><br>
Cc:</b> Moury Gilles <Gilles.Moury@cnes.fr>; sls-sea-dls@mailman.ccsds.org<b><br>
Subject:</b> Re: [Sls-sea-dls] [EXTERNAL] TR: CCSDS Order of Processing: Figure 6-3 in CCSDS 232.0 and Figure 3-3 in CCSDS 350.5-G<o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">I like the drawing, Craig.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
A few possible improvements suggested:</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
- placement of the Mod and Demod boxes in a new layer above "C&S", which is "RF & Modulation";</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
- addition of internal interfaces like the "RF lock" and "Bit Lock" from the Demod box to the CLCW or the control frames towards FARM-1 as directives (not data traffic);</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
- addition of text above the solid arrows that directly connect from VC Gen to VC Mux and from VC Demux to VC Rec to explain the perceived absence of COP-1 processing;</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
- consideration/illustration of distinct control frame, expedited-service frame and sequence-controlled frame processing (may overlap with the two previous comments);</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
- addition of external interfaces (e.g. to the redundant Demod to obtain their "RF Lock" and "Bit Lock", directives to manage FOP-1, Apply Security, FARM-1, Process Security).</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Let us know if the above helps.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Kind regards,</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Ignacio</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
<br>
</span><img border="0" width="92" height="33" style="width:.9583in;height:.3437in" id="_x0000_i1029" src="cid:image001.gif@01D74579.62689760"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> <br>
</span><b><span style="font-size:9.0pt;font-family:"NotesEsa",serif;color:#4F4F4F"><br>
Ignacio Aguilar Sánchez</span></b><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"NotesEsa",serif;color:#4F4F4F"><br>
Communication Systems Engineer</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"NotesEsa",serif;color:#4F4F4F"><br>
Electrical Engineering Department</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:9.0pt;font-family:"NotesEsa",serif;color:#4F4F4F"><br>
European Space Research and Technology Centre<br>
Keplerlaan 1, PO Box 299, 2200 AG Noordwijk, The Netherlands</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"NotesEsa",serif;color:#4F4F4F"><br>
Tel. (31) 71 565 5695</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"NotesEsa",serif;color:#4F4F4F"><br>
Fax (31) 71 565 5418</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"NotesEsa",serif;color:#4F4F4F"><br>
Email: </span><a href="mailto:ignacio.aguilar.sanchez@esa.int"><span style="font-size:9.0pt;font-family:"NotesEsa",serif">ignacio.aguilar.sanchez@esa.int</span></a><u><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:blue"><br>
</span></u><a href="https://urldefense.us/v3/__https:/gcc02.safelinks.protection.outlook.com/?url=http*3A*2F*2Fwww.esa.int*2F&data=04*7C01*7Ccraig.biggerstaff*40nasa.gov*7Ca0b54883dbdb4059510a08d9105a9665*7C7005d45845be48ae8140d43da96dd17b*7C0*7C0*7C637558803540802107*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=W8xm55SVMfY8B6yj2pf2yhDcwVkJFK5ODMhVTOoz7xk*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSU!!PvBDto6Hs4WbVuu7!f2RDZSbDqQP6R8RYEaBVnKXm-96d0iWq7zgLgm_5cb7VdV_fKIwQtBeg-uvBQ0xqdRQajSyM$"><span style="font-size:9.0pt;font-family:"NotesEsa",serif">www.esa.int</span></a><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
<br>
<br>
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Biggerstaff, Craig\(JSC-CD42\)\[SGT, INC\] via SLS-SEA-DLS" <</span><a href="mailto:sls-sea-dls@mailman.ccsds.org"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">sls-sea-dls@mailman.ccsds.org</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Moury Gilles" <</span><a href="mailto:Gilles.Moury@cnes.fr"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Gilles.Moury@cnes.fr</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>,
"</span><a href="mailto:sls-sea-dls@mailman.ccsds.org"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">sls-sea-dls@mailman.ccsds.org</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">" <</span><a href="mailto:sls-sea-dls@mailman.ccsds.org"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">sls-sea-dls@mailman.ccsds.org</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">05/05/2021 22:14</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Re: [Sls-sea-dls] [EXTERNAL] TR: CCSDS Order of Processing: Figure 6-3 in CCSDS 232.0 and Figure 3-3 in CCSDS 350.5-G</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Sent by: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"SLS-SEA-DLS" <</span><a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">sls-sea-dls-bounces@mailman.ccsds.org</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:2.5in;margin-left:0in">
<span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">Dear SDLS WG members,</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">I have lately received a few (internal NASA) questions regarding the order of processing between SDLS and COP, similar to discussions in the WG earlier. Since we already discussed adding clarifying text in
the next SDLS Green Book revision, attached is a diagram I created to illustrate the flow and interactions between protocol sub-layers. If the WG finds this helpful, we could consider it (or something similar) for inclusion along with the clarifying text.</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">Best regards,</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><b><span style="font-family:"Arial",sans-serif;color:#5F5F5F">Craig Biggerstaff</span></b><o:p></o:p></p>
<p style="margin:0in"><span style="font-family:"Arial",sans-serif;color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><img border="0" width="86" height="48" style="width:.8958in;height:.5in" id="_x0000_i1027" src="cid:image002.jpg@01D74579.62689760" alt="KBR - Copy"><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">KBR | Senior Engineer Specialist, Mission Systems Operations Contract</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">2101 NASA Parkway, Mail Code CD4 | Houston, Texas 77058 | USA</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Office: +1 281.483.2027 | </span><a href="mailto:craig.biggerstaff@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#0082BF">craig.biggerstaff@nasa.gov</span></a><o:p></o:p></p>
<p class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#004080"> </span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<p style="margin:0in"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution,
or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><b>From:</b> SLS-SEA-DLS <<a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org">sls-sea-dls-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b>Moury Gilles<b><br>
Sent:</b> Friday, February 5, 2021 11:44 AM<b><br>
To:</b> <a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a><b><br>
Subject:</b> [EXTERNAL] [Sls-sea-dls] TR: CCSDS Order of Processing: Figure 6-3 in CCSDS 232.0 and Figure 3-3 in CCSDS 350.5-G<o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">Dear SDLS WG member,</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">The order of processing between SDLS and the COP in TC has raised questions by implementing projects. To clarify the matter and provide a complete justification, Greg Kazz (SLP WG chairman) proposes to include
an additional paragraph in the SDLS Green Book (355.0-G) (see exchange of mails hereafter). A text along the following lines is proposed to be inserted in front of Figure 3-3 on page 3-10:</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">“There are several reasons for this ordering of SDLS and COP functions :</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="color:#004080">COP-1, being a go-back-N retransmission protocol, will eventually replay TC frames. SDLS is a function providing anti-replay protection, integrity and confidentiality. Therefore if FOP is applied before SDLS at the sending end, and
SDLS before FARM at the receiving end, SDLS at the receiving end will discard all replayed frames by COP-1, thus defeating the COP.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="color:#004080">SDLS at the receiving end checks integrity of TC frames by checking the MAC. The MAC is a very powerful error detecting code (in fact much more powerful than the BCH code). Therefore, SDLS receiving end will discard all TC frames
impacted by transmission errors, if the FARM is applied after SDLS. This has two impacts :</span><span style="font-size:12.0pt">
</span><o:p></o:p>
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo1">
<span style="color:#004080">Accountability of transmission errors vs security related events cannot be made : all errors are detected by SDLS and therefore classified as security events</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo1">
<span style="color:#004080">COP-1 will replay those SDLS rejected frames, because the FARM will never see them. Those replayed TC frames will be later rejected as replay by SDLS.”</span><o:p></o:p></li></ul>
</li></ul>
<p class="MsoNormal"><span style="color:#004080"> </span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">SDLS GB (355.0-G-1) is due for 5-year review in 2023. Nevertheless, GB do not have the same stability requirement as Blue Book and could possibly be updated more frequently. The proposal I would like to submit
to the WG is to prepare an update of the GB this year to include this justification and any other clarifications/additions/updates that might be beneficial. Of course the proposed text is to be discussed and tuned so that it fits properly in that section.</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">Please do not hesitate to comment on that proposal so that we can initiate or not this GB update.</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">Best regards,</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">Gilles Moury</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">SDLS WG chair</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#004080">Gilles MOURY</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#004080">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#004080"><br>
CNES Toulouse</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#004080">
</span><o:p></o:p></p>
<p style="margin:0in"><b>De :</b> Kazz, Greg J (US 312B) <<a href="mailto:greg.j.kazz@jpl.nasa.gov"><span style="color:#0082BF">greg.j.kazz@jpl.nasa.gov</span></a>>
<b><br>
Envoyé :</b> jeudi 21 janvier 2021 18:12<b><br>
À :</b> Biggerstaff, Craig (JSC-CD42)[SGT, INC] <<a href="mailto:craig.biggerstaff@nasa.gov"><span style="color:#0082BF">craig.biggerstaff@nasa.gov</span></a>>; Moury Gilles <<a href="mailto:Gilles.Moury@cnes.fr"><span style="color:#0082BF">Gilles.Moury@cnes.fr</span></a>>;
Weiss, Howard <<a href="mailto:Howard.Weiss@parsons.com"><span style="color:#0082BF">Howard.Weiss@parsons.com</span></a>>;
<a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="color:#0082BF">Gian.Paolo.Calzolari@esa.int</span></a><b><br>
Cc :</b> Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="color:#0082BF">peter.m.shames@jpl.nasa.gov</span></a>>; Sank, Victor J. (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC] <<a href="mailto:victor.j.sank@nasa.gov"><span style="color:#0082BF">victor.j.sank@nasa.gov</span></a>>;
Andres, Brent (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC] <<a href="mailto:brent.r.andres@nasa.gov"><span style="color:#0082BF">brent.r.andres@nasa.gov</span></a>>; Matthew Cosby <<a href="mailto:Matt.Cosby@Goonhilly.org"><span style="color:#0082BF">Matt.Cosby@Goonhilly.org</span></a>>;
Thomas Gannett <<a href="mailto:thomas.gannett@tgannett.net"><span style="color:#0082BF">thomas.gannett@tgannett.net</span></a>><b><br>
Objet :</b> Re: CCSDS Order of Processing: Figure 6-3 in CCSDS 232.0 and Figure 3-3 in CCSDS 350.5-G<o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in">That would be in 2023, 3 years from now…since security is on everybody’s plate these days, I highly recommend it get updated this year. It is a Green book, so I would hope we have more discretion and flexibility in updating them more frequently
than the blue books. I understand the rationale for not updating blue books that often.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">Thanks!<br>
Greg<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt">"Biggerstaff, Craig (JSC-CD42)[SGT, INC]" <</span><a href="mailto:craig.biggerstaff@nasa.gov"><span style="font-size:12.0pt;color:#0082BF">craig.biggerstaff@nasa.gov</span></a><span style="font-size:12.0pt">><b><br>
Date: </b>Thursday, January 21, 2021 at 8:53 AM<b><br>
To: </b>"Kazz, Greg J (US 312B)" <</span><a href="mailto:greg.j.kazz@jpl.nasa.gov"><span style="font-size:12.0pt;color:#0082BF">greg.j.kazz@jpl.nasa.gov</span></a><span style="font-size:12.0pt">>, Moury Gilles <</span><a href="mailto:Gilles.Moury@cnes.fr"><span style="font-size:12.0pt;color:#0082BF">Gilles.Moury@cnes.fr</span></a><span style="font-size:12.0pt">>,
"Weiss, Howard" <</span><a href="mailto:Howard.Weiss@parsons.com"><span style="font-size:12.0pt;color:#0082BF">Howard.Weiss@parsons.com</span></a><span style="font-size:12.0pt">><b><br>
Cc: </b>"Shames, Peter M (US 312B)" <</span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="font-size:12.0pt;color:#0082BF">peter.m.shames@jpl.nasa.gov</span></a><span style="font-size:12.0pt">>, "</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="font-size:12.0pt;color:#0082BF">Gian.Paolo.Calzolari@esa.int</span></a><span style="font-size:12.0pt">"
<</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="font-size:12.0pt;color:#0082BF">Gian.Paolo.Calzolari@esa.int</span></a><span style="font-size:12.0pt">>, "Sank, Victor J. (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC]" <</span><a href="mailto:victor.j.sank@nasa.gov"><span style="font-size:12.0pt;color:#0082BF">victor.j.sank@nasa.gov</span></a><span style="font-size:12.0pt">>,
"Andres, Brent (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC]" <</span><a href="mailto:brent.r.andres@nasa.gov"><span style="font-size:12.0pt;color:#0082BF">brent.r.andres@nasa.gov</span></a><span style="font-size:12.0pt">>, Matthew Cosby <</span><a href="mailto:Matt.Cosby@Goonhilly.org"><span style="font-size:12.0pt;color:#0082BF">Matt.Cosby@Goonhilly.org</span></a><span style="font-size:12.0pt">>,
Thomas Gannett <</span><a href="mailto:thomas.gannett@tgannett.net"><span style="font-size:12.0pt;color:#0082BF">thomas.gannett@tgannett.net</span></a><span style="font-size:12.0pt">><b><br>
Subject: </b>RE: CCSDS Order of Processing: Figure 6-3 in CCSDS 232.0 and Figure 3-3 in CCSDS 350.5-G</span><o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">I agree with incorporating Gilles’ text. The normal opportunity to do this would be the Green Book’s 5-year review/revision cycle.</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">Best regards,</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">Craig</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><b>From:</b> Kazz, Greg J (US 312B) <<a href="mailto:greg.j.kazz@jpl.nasa.gov"><span style="color:#0082BF">greg.j.kazz@jpl.nasa.gov</span></a>>
<b><br>
Sent:</b> Wednesday, January 20, 2021 6:15 PM<b><br>
To:</b> Moury Gilles <<a href="mailto:Gilles.Moury@cnes.fr"><span style="color:#0082BF">Gilles.Moury@cnes.fr</span></a>>; Biggerstaff, Craig (JSC-CD42)[SGT, INC] <<a href="mailto:craig.biggerstaff@nasa.gov"><span style="color:#0082BF">craig.biggerstaff@nasa.gov</span></a>>;
Weiss, Howard <<a href="mailto:Howard.Weiss@parsons.com"><span style="color:#0082BF">Howard.Weiss@parsons.com</span></a>><b><br>
Cc:</b> Shames, Peter M (JPL-312B)[JPL Employee] <<a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="color:#0082BF">peter.m.shames@jpl.nasa.gov</span></a>>;
<a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="color:#0082BF">Gian.Paolo.Calzolari@esa.int</span></a>; Sank, Victor J. (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC] <<a href="mailto:victor.j.sank@nasa.gov"><span style="color:#0082BF">victor.j.sank@nasa.gov</span></a>>;
Andres, Brent (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC] <<a href="mailto:brent.r.andres@nasa.gov"><span style="color:#0082BF">brent.r.andres@nasa.gov</span></a>>; Matthew Cosby <<a href="mailto:Matt.Cosby@Goonhilly.org"><span style="color:#0082BF">Matt.Cosby@Goonhilly.org</span></a>>;
Thomas Gannett <<a href="mailto:thomas.gannett@tgannett.net"><span style="color:#0082BF">thomas.gannett@tgannett.net</span></a>><b><br>
Subject:</b> CCSDS Order of Processing: Figure 6-3 in CCSDS 232.0 and Figure 3-3 in CCSDS 350.5-G<o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:14.0pt">Gilles, Craig, and Howie,</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:14.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:14.0pt">What Gilles provided me, Victor, and Brent (highlighted below, i.e., his bullet points) was an excellent explanation, as to why the COP has to be applied
<i>after</i> SDLS at the sending end. And because this topic seems to come up again and again at least at NASA and perhaps at other agencies as well, I strongly recommend that we take Gilles’ text below and put it into a new paragraph in front of figure 3-3
on p. 3-10 in CCSDS 350.5-G (June 2018) to augment the rationale for that figure. I believe it will be useful for user’s to understand the rationale for processing between COP and SDLS. Note that figure 3-3 is identical to figure 6-3 in CCSDS 232.0.</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:14.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:14.0pt">What does the SDLS WG think of this recommendation ?</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:14.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:14.0pt">Best regards,</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:14.0pt">Greg</span><o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt">Moury Gilles <</span><a href="mailto:Gilles.Moury@cnes.fr"><span style="font-size:12.0pt;color:#0082BF">Gilles.Moury@cnes.fr</span></a><span style="font-size:12.0pt">><b><br>
Date: </b>Tuesday, January 12, 2021 at 3:57 AM<b><br>
To: </b>"Kazz, Greg J (US 312B)" <</span><a href="mailto:greg.j.kazz@jpl.nasa.gov"><span style="font-size:12.0pt;color:#0082BF">greg.j.kazz@jpl.nasa.gov</span></a><span style="font-size:12.0pt">><b><br>
Cc: </b>"Sank, Victor J. (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC]" <</span><a href="mailto:victor.j.sank@nasa.gov"><span style="font-size:12.0pt;color:#0082BF">victor.j.sank@nasa.gov</span></a><span style="font-size:12.0pt">><b><br>
Subject: </b>[EXTERNAL] RE: CCSDS Order of Processing: Figure 6-3 in CCSDS 232.0</span><o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">Dear Greg and Victor,</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">All my best wishes for 2021 ! I hope we can meet in person this year !</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">There are several reasons for this ordering of SDLS and COP functions :</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="color:#004080">COP-1, being a go-back-N retransmission protocol, will eventually replay TC frames. SDLS is a function providing anti-replay protection, integrity and confidentiality. Therefore if FOP is applied before SDLS at the sending end, and
SDLS before FARM at the receiving end, SDLS at the receiving end will discard all replayed frames by COP-1, thus defeating the COP.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="color:#004080">SDLS at the receiving end checks integrity of TC frames by checking the MAC. The MAC is a very powerful error detecting code (in fact much more powerful than the BCH code). Therefore, SDLS receiving end will discard all TC frames
impacted by transmission errors, if the FARM is applied after SDLS. This has two impacts :</span><span style="font-size:12.0pt">
</span><o:p></o:p>
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
<span style="color:#004080">Accountability of transmission errors vs security related events cannot be made : all errors are detected by SDLS and therefore classified as security events</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2">
<span style="color:#004080">COP-1 will replay those SDLS rejected frames, because the FARM will never see them. Those replayed TC frames will be later rejected as replay by SDLS.</span><o:p></o:p></li></ul>
</li></ul>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:#004080"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#004080">I hope this clarifies the matter.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">Best regards,</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080">Gilles</span><o:p></o:p></p>
<p style="margin:0in"><span style="color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#004080">Gilles MOURY</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#004080">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#004080"><br>
CNES Toulouse</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#004080">
</span><o:p></o:p></p>
<p style="margin:0in"><b>De :</b> Kazz, Greg J (US 312B) <<a href="mailto:greg.j.kazz@jpl.nasa.gov"><span style="color:#0082BF">greg.j.kazz@jpl.nasa.gov</span></a>>
<b><br>
Envoyé :</b> dimanche 10 janvier 2021 18:52<b><br>
À :</b> Moury Gilles <<a href="mailto:Gilles.Moury@cnes.fr"><span style="color:#0082BF">Gilles.Moury@cnes.fr</span></a>><b><br>
Cc :</b> Sank, Victor J. (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC] <<a href="mailto:victor.j.sank@nasa.gov"><span style="color:#0082BF">victor.j.sank@nasa.gov</span></a>><b><br>
Objet :</b> CCSDS Order of Processing: Figure 6-3 in CCSDS 232.0<o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Happy New Year, Gilles !</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Victor Sank and I have a question for you, which I would like to ask you again to confirm my understanding, or correct my thinking.</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Why must the FOP on the ground be done after SDLS is applied ? In other words, “why can’t the Frame Sequence Number in the Transfer Frame Primary Header, be input/applied prior to the SDSL ApplySecurity?
“ </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">I vaguely remember you saying something like, if the order were reversed (do FOP first, and then SDLS), there would be no way to know why a transfer frame was rejected and therefore the project would not
have the accountability it needs to take the correct action. There would be <i>no definitive</i> accountability as to
<i>why </i>a given<i> </i>transfer frames was rejected i.e., was it first rejected by SDLS because of an intentional cyber attack or was it just a non-cyber related incident detected by SDLS security (e.g., bit flips due to a regular noisy channel). By executing
the FOP-1 and the FARM-1 together as a pair, i.e., back to back as Figure 6-3 shows, you get clean accountability back from SDLS and also from the FARM (if the frame passes SDLS, then the FARM can determine if any other COP rules have been violated or not,
independent of SDLS). </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Is my explanation above also your understanding ?</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Best regards,</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Greg</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in">Greg Kazz<o:p></o:p></p>
<p style="margin:0in">Principal Engineer<o:p></o:p></p>
<p style="margin:0in">Technical Group Supervisor,<o:p></o:p></p>
<p style="margin:0in">PSSE/EEISE/PPSE (312B)<o:p></o:p></p>
<p style="margin:0in">Jet Propulsion Laboratory<img border="0" width="1366" height="892" style="width:14.2291in;height:9.2916in" id="_x0000_i1025" src="cid:image003.png@01D74579.62689760"><o:p></o:p></p>
<p style="margin:0in">4800 Oak Grove Dr., M/S 301-490<o:p></o:p></p>
<p style="margin:0in">Pasadena, CA 91109<o:p></o:p></p>
<p style="margin:0in">1+(818)393 6529(voice)<o:p></o:p></p>
<p style="margin:0in">1+(818)393 6871(fax)<o:p></o:p></p>
<p style="margin:0in">email: <a href="mailto:greg.j.kazz@jpl.nasa.gov"><span style="color:#0082BF">greg.j.kazz@jpl.nasa.gov</span></a>
<o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> [attachment "SDLS & COP interactions.vsd" deleted by Ignacio Aguilar Sanchez/estec/ESA]
</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:2.5in;margin-left:0in">
<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="font-size:12.0pt;font-family:"Times New Roman",serif;color:blue"><br>
</span></u><a href="https://urldefense.us/v3/__https:/gcc02.safelinks.protection.outlook.com/?url=https*3A*2F*2Fmailman.ccsds.org*2Fcgi-bin*2Fmailman*2Flistinfo*2Fsls-sea-dls&data=04*7C01*7Ccraig.biggerstaff*40nasa.gov*7Ca0b54883dbdb4059510a08d9105a9665*7C7005d45845be48ae8140d43da96dd17b*7C0*7C0*7C637558803540812068*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=NXlTXAvmEgFvnVbIg20Cg*2BNVoO5zRD0te5Gik7fQiOs*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUl!!PvBDto6Hs4WbVuu7!f2RDZSbDqQP6R8RYEaBVnKXm-96d0iWq7zgLgm_5cb7VdV_fKIwQtBeg-uvBQ0xqda0fDOIB$"><span style="font-size:10.0pt;font-family:"Courier New"">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls</span></a><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Courier New"">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Courier New"">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Courier New"">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Courier New"">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (</span><a href="mailto:dpo@esa.int"><span style="font-size:10.0pt;font-family:"Courier New"">dpo@esa.int</span></a><span style="font-size:10.0pt;font-family:"Courier New"">).[attachment
"SDLS & COP interactions 2.png" deleted by Ignacio Aguilar Sanchez/estec/ESA] </span>
<o:p></o:p></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).<o:p></o:p></pre>
</div>
</body>
</html>