<span style=" font-size:10pt;font-family:sans-serif">Craig,</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Thanks for the
update.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Just one more
thing that I see now that I did not see before, sorry!</span>
<br>
<br><span style=" font-size:10pt;font-family: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:10pt;font-family: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:10pt;font-family: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:10pt;font-family:sans-serif">I believe a swap
of SDLS and COP-1 lanes is sufficient to fix this.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">We can help as
well with the text describing the drawing.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Kind regards,</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Ignacio</span>
<br>
<br><img src=cid:_1_0EF25EEC0EF25A4C00216C23C12586D1 style="border:0px solid;"><span style=" font-size:12pt"> </span>
<br>
<br><span style=" font-size:9pt;color:#4f4f4f;font-family:NotesEsa"><b>Ignacio
Aguilar Sánchez</b></span>
<br><span style=" font-size:9pt;color:#4f4f4f;font-family:NotesEsa">Communication
Systems Engineer</span>
<br><span style=" font-size:9pt;color:#4f4f4f;font-family:NotesEsa">Electrical
Engineering Department</span>
<br>
<br><span style=" font-size:9pt;color:#4f4f4f;font-family:NotesEsa">European
Space Research and Technology Centre<br>
Keplerlaan 1, PO Box 299, 2200 AG Noordwijk, The Netherlands</span>
<br><span style=" font-size:9pt;color:#4f4f4f;font-family:NotesEsa">Tel.
(31) 71 565 5695</span>
<br><span style=" font-size:9pt;color:#4f4f4f;font-family:NotesEsa">Fax
(31) 71 565 5418</span>
<br><span style=" font-size:9pt;color:#4f4f4f;font-family:NotesEsa">Email:
ignacio.aguilar.sanchez@esa.int<br>
</span><a href=www.esa.int><span style=" font-size:9pt;color:blue;font-family:NotesEsa">www.esa.int</span></a>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
       </span><span style=" font-size:9pt;font-family:sans-serif">"Biggerstaff,
Craig (JSC-CD42)[SGT, INC]" <craig.biggerstaff@nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
       </span><span style=" font-size:9pt;font-family:sans-serif">"Ignacio.Aguilar.Sanchez@esa.int"
<Ignacio.Aguilar.Sanchez@esa.int></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
       </span><span style=" font-size:9pt;font-family: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:9pt;color:#5f5f5f;font-family:sans-serif">Date:
       </span><span style=" font-size:9pt;font-family:sans-serif">07/05/2021
20:46</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
       </span><span style=" font-size:9pt;font-family: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>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Craig</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><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</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">I
like the drawing, Craig.</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
A few possible improvements suggested:</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
- placement of the Mod and Demod boxes in a new layer above "C&S",
which is "RF & Modulation";</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><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:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><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:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><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:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><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:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Let us know if the above helps.</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Kind regards,</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Ignacio</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
<br>
</span><img src=cid:_1_0EF1C8880EF1BE3000216C23C12586D1 style="border:0px solid;"><span style=" font-size:12pt;font-family:Times New Roman">
 <br>
</span><span style=" font-size:9pt;color:#4f4f4f;font-family:NotesEsa"><b><br>
Ignacio Aguilar Sánchez</b></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#4f4f4f;font-family:NotesEsa"><br>
Communication Systems Engineer</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#4f4f4f;font-family:NotesEsa"><br>
Electrical Engineering Department</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:9pt;color:#4f4f4f;font-family:NotesEsa"><br>
European Space Research and Technology Centre<br>
Keplerlaan 1, PO Box 299, 2200 AG Noordwijk, The Netherlands</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#4f4f4f;font-family:NotesEsa"><br>
Tel. (31) 71 565 5695</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#4f4f4f;font-family:NotesEsa"><br>
Fax (31) 71 565 5418</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#4f4f4f;font-family:NotesEsa"><br>
Email: </span><a href=mailto:ignacio.aguilar.sanchez@esa.int><span style=" font-size:9pt;color:blue;font-family:NotesEsa"><u>ignacio.aguilar.sanchez@esa.int</u></span></a><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u><br>
</u></span><a href="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"><span style=" font-size:9pt;color:blue;font-family:NotesEsa"><u>www.esa.int</u></span></a><span style=" font-size:12pt;font-family:Times New Roman">
<br>
<br>
<br>
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
From:        </span><span style=" font-size:9pt;font-family:Arial">"Biggerstaff,
Craig\(JSC-CD42\)\[SGT, INC\] via SLS-SEA-DLS" <</span><a href="mailto:sls-sea-dls@mailman.ccsds.org"><span style=" font-size:9pt;color:blue;font-family:Arial"><u>sls-sea-dls@mailman.ccsds.org</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
To:        </span><span style=" font-size:9pt;font-family:Arial">"Moury
Gilles" <</span><a href=mailto:Gilles.Moury@cnes.fr><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Gilles.Moury@cnes.fr</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"</span><a href="mailto:sls-sea-dls@mailman.ccsds.org"><span style=" font-size:9pt;color:blue;font-family:Arial"><u>sls-sea-dls@mailman.ccsds.org</u></span></a><span style=" font-size:9pt;font-family:Arial">"
<</span><a href="mailto:sls-sea-dls@mailman.ccsds.org"><span style=" font-size:9pt;color:blue;font-family:Arial"><u>sls-sea-dls@mailman.ccsds.org</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date:        </span><span style=" font-size:9pt;font-family:Arial">05/05/2021
22:14</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject:        </span><span style=" font-size:9pt;font-family:Arial">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:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Sent by:        </span><span style=" font-size:9pt;font-family:Arial">"SLS-SEA-DLS"
<</span><a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org"><span style=" font-size:9pt;color:blue;font-family:Arial"><u>sls-sea-dls-bounces@mailman.ccsds.org</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span></p>
<div align=center>
<hr noshade></div>
<p style="margin-top:0px;margin-Bottom:240px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Dear
SDLS WG members,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#5f5f5f;font-family:Arial"><b>Craig
Biggerstaff</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Arial"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><img src=cid:_2_0EF095E00EF091D000216C23C12586D1 alt="KBR - Copy" style="border:0px solid;"></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial">KBR
 |  Senior Engineer Specialist, Mission Systems Operations Contract</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial">2101
NASA Parkway, Mail Code CD4  |  Houston, Texas 77058  |
 USA</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial">Office:
+1 281.483.2027  |  </span><a href=mailto:craig.biggerstaff@nasa.gov><span style=" font-size:9pt;color:#0082bf;font-family:Arial"><u>craig.biggerstaff@nasa.gov</u></span></a></p>
<div align=center><span style=" font-size:12pt;color:#004080;font-family:Times New Roman"> </span><span style=" font-size:12pt;font-family:Times New Roman">
</span>
<p style="margin-top:0px;margin-Bottom:0px">
<hr></p></div>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:8pt;color:#5f5f5f;font-family:Arial">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:</b>
SLS-SEA-DLS <</span><a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>sls-sea-dls-bounces@mailman.ccsds.org</u></span></a><span style=" font-size:11pt;font-family:Calibri">>
<b>On Behalf Of </b>Moury Gilles<b><br>
Sent:</b> Friday, February 5, 2021 11:44 AM<b><br>
To:</b> </span><a href="mailto:sls-sea-dls@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>sls-sea-dls@mailman.ccsds.org</u></span></a><span style=" font-size:11pt;font-family:Calibri"><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</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Dear
SDLS WG member,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">“There
are several reasons for this ordering of SDLS and COP functions :</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<ul>
<li><span style=" font-size:11pt;color:#004080;font-family:Calibri">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:12pt;font-family:Times New Roman">
</span>
<li><span style=" font-size:11pt;color:#004080;font-family:Calibri">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:12pt;font-family:Calibri">
</span>
<ul>
<li><span style=" font-size:11pt;color:#004080;font-family:Calibri">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:12pt;font-family:Times New Roman">
</span>
<li><span style=" font-size:11pt;color:#004080;font-family:Calibri">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></ul></ul><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span><span style=" font-size:12pt;font-family:Times New Roman">
</span>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Please
do not hesitate to comment on that proposal so that we can initiate or
not this GB update.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Gilles
Moury</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">SDLS
WG chair</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#004080;font-family:Arial">Gilles
MOURY</span><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">
</span><span style=" font-size:10pt;color:#004080;font-family:Arial"><br>
CNES Toulouse</span><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>De
:</b> Kazz, Greg J (US 312B) <</span><a href=mailto:greg.j.kazz@jpl.nasa.gov><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>greg.j.kazz@jpl.nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">>
<b><br>
Envoyé :</b> jeudi 21 janvier 2021 18:12<b><br>
À :</b> Biggerstaff, Craig (JSC-CD42)[SGT, INC] <</span><a href=mailto:craig.biggerstaff@nasa.gov><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>craig.biggerstaff@nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
Moury Gilles <</span><a href=mailto:Gilles.Moury@cnes.fr><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>Gilles.Moury@cnes.fr</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
Weiss, Howard <</span><a href=mailto:Howard.Weiss@parsons.com><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>Howard.Weiss@parsons.com</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
</span><a href=mailto:Gian.Paolo.Calzolari@esa.int><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>Gian.Paolo.Calzolari@esa.int</u></span></a><span style=" font-size:11pt;font-family:Calibri"><b><br>
Cc :</b> Shames, Peter M (US 312B) <</span><a href=mailto:peter.m.shames@jpl.nasa.gov><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>peter.m.shames@jpl.nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
Sank, Victor J. (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC] <</span><a href=mailto:victor.j.sank@nasa.gov><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>victor.j.sank@nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
Andres, Brent (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC] <</span><a href=mailto:brent.r.andres@nasa.gov><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>brent.r.andres@nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
Matthew Cosby <</span><a href=mailto:Matt.Cosby@Goonhilly.org><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>Matt.Cosby@Goonhilly.org</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
Thomas Gannett <</span><a href=mailto:thomas.gannett@tgannett.net><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>thomas.gannett@tgannett.net</u></span></a><span style=" font-size:11pt;font-family:Calibri">><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</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Thanks!<br>
Greg</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"><b>From:
</b>"Biggerstaff, Craig (JSC-CD42)[SGT, INC]" <</span><a href=mailto:craig.biggerstaff@nasa.gov><span style=" font-size:12pt;color:#0082bf;font-family:Calibri"><u>craig.biggerstaff@nasa.gov</u></span></a><span style=" font-size:12pt;font-family:Calibri">><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:12pt;color:#0082bf;font-family:Calibri"><u>greg.j.kazz@jpl.nasa.gov</u></span></a><span style=" font-size:12pt;font-family:Calibri">>,
Moury Gilles <</span><a href=mailto:Gilles.Moury@cnes.fr><span style=" font-size:12pt;color:#0082bf;font-family:Calibri"><u>Gilles.Moury@cnes.fr</u></span></a><span style=" font-size:12pt;font-family:Calibri">>,
"Weiss, Howard" <</span><a href=mailto:Howard.Weiss@parsons.com><span style=" font-size:12pt;color:#0082bf;font-family:Calibri"><u>Howard.Weiss@parsons.com</u></span></a><span style=" font-size:12pt;font-family:Calibri">><b><br>
Cc: </b>"Shames, Peter M (US 312B)" <</span><a href=mailto:peter.m.shames@jpl.nasa.gov><span style=" font-size:12pt;color:#0082bf;font-family:Calibri"><u>peter.m.shames@jpl.nasa.gov</u></span></a><span style=" font-size:12pt;font-family:Calibri">>,
"</span><a href=mailto:Gian.Paolo.Calzolari@esa.int><span style=" font-size:12pt;color:#0082bf;font-family:Calibri"><u>Gian.Paolo.Calzolari@esa.int</u></span></a><span style=" font-size:12pt;font-family:Calibri">"
<</span><a href=mailto:Gian.Paolo.Calzolari@esa.int><span style=" font-size:12pt;color:#0082bf;font-family:Calibri"><u>Gian.Paolo.Calzolari@esa.int</u></span></a><span style=" font-size:12pt;font-family:Calibri">>,
"Sank, Victor J. (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC]"
<</span><a href=mailto:victor.j.sank@nasa.gov><span style=" font-size:12pt;color:#0082bf;font-family:Calibri"><u>victor.j.sank@nasa.gov</u></span></a><span style=" font-size:12pt;font-family:Calibri">>,
"Andres, Brent (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC]"
<</span><a href=mailto:brent.r.andres@nasa.gov><span style=" font-size:12pt;color:#0082bf;font-family:Calibri"><u>brent.r.andres@nasa.gov</u></span></a><span style=" font-size:12pt;font-family:Calibri">>,
Matthew Cosby <</span><a href=mailto:Matt.Cosby@Goonhilly.org><span style=" font-size:12pt;color:#0082bf;font-family:Calibri"><u>Matt.Cosby@Goonhilly.org</u></span></a><span style=" font-size:12pt;font-family:Calibri">>,
Thomas Gannett <</span><a href=mailto:thomas.gannett@tgannett.net><span style=" font-size:12pt;color:#0082bf;font-family:Calibri"><u>thomas.gannett@tgannett.net</u></span></a><span style=" font-size:12pt;font-family:Calibri">><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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">I
agree with incorporating Gilles’ text.  The normal opportunity to
do this would be the Green Book’s 5-year review/revision cycle.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Craig</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:</b>
Kazz, Greg J (US 312B) <</span><a href=mailto:greg.j.kazz@jpl.nasa.gov><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>greg.j.kazz@jpl.nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">>
<b><br>
Sent:</b> Wednesday, January 20, 2021 6:15 PM<b><br>
To:</b> Moury Gilles <</span><a href=mailto:Gilles.Moury@cnes.fr><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>Gilles.Moury@cnes.fr</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
Biggerstaff, Craig (JSC-CD42)[SGT, INC] <</span><a href=mailto:craig.biggerstaff@nasa.gov><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>craig.biggerstaff@nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
Weiss, Howard <</span><a href=mailto:Howard.Weiss@parsons.com><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>Howard.Weiss@parsons.com</u></span></a><span style=" font-size:11pt;font-family:Calibri">><b><br>
Cc:</b> Shames, Peter M (JPL-312B)[JPL Employee] <</span><a href=mailto:peter.m.shames@jpl.nasa.gov><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>peter.m.shames@jpl.nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
</span><a href=mailto:Gian.Paolo.Calzolari@esa.int><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>Gian.Paolo.Calzolari@esa.int</u></span></a><span style=" font-size:11pt;font-family:Calibri">;
Sank, Victor J. (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC] <</span><a href=mailto:victor.j.sank@nasa.gov><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>victor.j.sank@nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
Andres, Brent (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC] <</span><a href=mailto:brent.r.andres@nasa.gov><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>brent.r.andres@nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
Matthew Cosby <</span><a href=mailto:Matt.Cosby@Goonhilly.org><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>Matt.Cosby@Goonhilly.org</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
Thomas Gannett <</span><a href=mailto:thomas.gannett@tgannett.net><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>thomas.gannett@tgannett.net</u></span></a><span style=" font-size:11pt;font-family:Calibri">><b><br>
Subject:</b> CCSDS Order of Processing: Figure 6-3 in CCSDS 232.0 and Figure
3-3 in CCSDS 350.5-G</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;font-family:Calibri">Gilles,
Craig, and Howie,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;font-family:Calibri">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;font-family:Calibri">What
does the SDLS WG think of this recommendation ?</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;font-family:Calibri">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;font-family:Calibri">Greg</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"><b>From:
</b>Moury Gilles <</span><a href=mailto:Gilles.Moury@cnes.fr><span style=" font-size:12pt;color:#0082bf;font-family:Calibri"><u>Gilles.Moury@cnes.fr</u></span></a><span style=" font-size:12pt;font-family:Calibri">><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:12pt;color:#0082bf;font-family:Calibri"><u>greg.j.kazz@jpl.nasa.gov</u></span></a><span style=" font-size:12pt;font-family:Calibri">><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:12pt;color:#0082bf;font-family:Calibri"><u>victor.j.sank@nasa.gov</u></span></a><span style=" font-size:12pt;font-family:Calibri">><b><br>
Subject: </b>[EXTERNAL] RE: CCSDS Order of Processing: Figure 6-3 in CCSDS
232.0</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Dear
Greg and Victor,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">All
my best wishes for 2021 ! I hope we can meet in person this year !</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">There
are several reasons for this ordering of SDLS and COP functions :</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<ul>
<li><span style=" font-size:11pt;color:#004080;font-family:Calibri">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:12pt;font-family:Times New Roman">
</span>
<li><span style=" font-size:11pt;color:#004080;font-family:Calibri">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:12pt;font-family:Calibri">
</span>
<ul>
<li><span style=" font-size:11pt;color:#004080;font-family:Calibri">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:12pt;font-family:Times New Roman">
</span>
<li><span style=" font-size:11pt;color:#004080;font-family:Calibri">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></ul><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></ul><span style=" font-size:11pt;color:#004080;font-family:Calibri">I
hope this clarifies the matter.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Gilles</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#004080;font-family:Arial">Gilles
MOURY</span><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">
</span><span style=" font-size:10pt;color:#004080;font-family:Arial"><br>
CNES Toulouse</span><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>De
:</b> Kazz, Greg J (US 312B) <</span><a href=mailto:greg.j.kazz@jpl.nasa.gov><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>greg.j.kazz@jpl.nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">>
<b><br>
Envoyé :</b> dimanche 10 janvier 2021 18:52<b><br>
À :</b> Moury Gilles <</span><a href=mailto:Gilles.Moury@cnes.fr><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>Gilles.Moury@cnes.fr</u></span></a><span style=" font-size:11pt;font-family:Calibri">><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:11pt;color:#0082bf;font-family:Calibri"><u>victor.j.sank@nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">><b><br>
Objet :</b> CCSDS Order of Processing: Figure 6-3 in CCSDS 232.0</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri">Happy
New Year, Gilles !</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri">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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri">Is
my explanation above also your understanding ?</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri">Greg</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Greg
Kazz</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Principal
Engineer</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Technical
Group Supervisor,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">PSSE/EEISE/PPSE
(312B)</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Jet
Propulsion Laboratory</span><img src=cid:_4_0F8DC4580F8DC1EC00216C23C12586D1 style="border:0px solid;"></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">4800
Oak Grove Dr., M/S 301-490</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Pasadena,
CA 91109</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">1+(818)393
6529(voice)</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">1+(818)393
6871(fax)</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">email:
</span><a href=mailto:greg.j.kazz@jpl.nasa.gov><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>greg.j.kazz@jpl.nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> [attachment
"SDLS & COP interactions.vsd" deleted by Ignacio Aguilar
Sanchez/estec/ESA] </span></p>
<p style="margin-top:0px;margin-Bottom:240px"><span style=" font-size:10pt;font-family:Courier New"><br>
_______________________________________________<br>
SLS-SEA-DLS mailing list</span><span style=" font-size:10pt;color:blue;font-family:Courier New"><u><br>
</u></span><a href="mailto:SLS-SEA-DLS@mailman.ccsds.org"><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>SLS-SEA-DLS@mailman.ccsds.org</u></span></a><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u><br>
</u></span><a href="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"><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-sea-dls</u></span></a><span style=" font-size:10pt;font-family:Courier New"><br>
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">This
message is intended only for the recipient(s) named above. It may contain
proprietary information and/or</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">protected
content. Any unauthorised disclosure, use, retention or dissemination is
prohibited. If you have received</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">this
e-mail in error, please notify the sender immediately. ESA applies appropriate
organisational measures to protect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;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:10pt;color:blue;font-family:Courier New"><u>dpo@esa.int</u></span></a><span style=" font-size:10pt;font-family:Courier New">).[attachment
"SDLS & COP interactions 2.png" deleted by Ignacio Aguilar
Sanchez/estec/ESA] </span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p> <PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>