<span style=" font-size:10pt;font-family:sans-serif">For your information</span>
<br><span style=" font-size:10pt;font-family:sans-serif">No reply agreed
yet with Gilles</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Best regards</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Gian Paolo</span>
<br>
<br><span style=" font-size:9pt;color:#800080;font-family:sans-serif">-----
Forwarded by Gian Paolo Calzolari/esoc/ESA on 06-05-21 08:56 -----</span>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"Shames,
Peter M (US 312B)" <peter.m.shames@jpl.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">"Gian
Paolo Calzolari" <Gian.Paolo.Calzolari@esa.int>, "Gilles
Moury" <Gilles.Moury@cnes.fr>, "Barkley, Erik J (US 3970)"
<erik.j.barkley@jpl.nasa.gov>, "Colin Haddow" <Colin.Haddow@esa.int>,
"Burleigh, Scott C (US 312B)" <scott.c.burleigh@jpl.nasa.gov>,
"Tomaso.deCola@dlr.de" <Tomaso.deCola@dlr.de>, "SEA-exec
SEA-exec" <sea-exec@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"Klaus-Juergen
Schulz" <Klaus-Juergen.Schulz@esa.int>, "CCSDS Engineering
Steering Group - CESG Exec" <cesg@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">05-05-21
23:41</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">Request
for a brief coordination meeting on SCCS-ARD planned changes</span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Dear
SLS, CSS, SIS, and SEA colleagues,</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">In
the SEA Systems Architecture WG (SAWG) we are working on a revision of
the Space Communication Cross Support Architecture Requirements Document
(CCSDS SCCS-ARD, 901.1-M-1). That document presently describes how
more than fifty-seven (57) normative CCSDS standards may be fitted together,
like some giant jig-saw puzzle, to mee the needs of users who design and
build flight and ground communications assets. In the time since
that standard was published a number of these normative standards have
been updated, some with new features, and a significant number of new standards
have been published, especially in SLS and CSS, but also in SEA itself.</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">We
have identified some issues with the current document structure that requires
changes to the chapters for clarity of presentation. We have also
identified some complexities introduced by new standards, such as USLP,
optical comm, VCM, and newer security features that are driving a change
in approach. And we are adding all of the new standards that have
been introduced since this document was published.</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">We
would like to present these issues and how we plan to address them
to whichever members of your teams would be willing to participate. This
is an unusual request for a WG, which usually do this sort of work
behind closed doors, but since this document cross cuts all of your WGs
we thought it useful and, we hope, valuable to you. Since we have
focused on ABA deployments the only Area that is not directly affected
yet is SIS. That said, you may still wish to see what we are doing to the
layers that underpin your networking layer standards. </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">I’d
like to schedule this coordination meeting in the week between the end
of the nominal “working meetings” and the CESG /CMC meetings. That
would be the week starting 1 June. Please go to this Doodle poll
and indicate your availability. Please feel free to invite your WG
chairs, and whichever other members of your WGs, you think would be willing
to participate. </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"><b><i>Replies,
please, by CoB, Friday, 7 May 2021.</i></b></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,
Peter</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"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><a href="https://doodle.com/poll/47wupegzugffhyiy?utm_source=poll&utm_medium=link"><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><b><u>https://doodle.com/poll/47wupegzugffhyiy?utm_source=poll&utm_medium=link</u></b></span></a></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b> </b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b> </b></span></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>