<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:"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: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",serif;}
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;}
--></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 Gippo,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for the feedback. I purposely shifted this meeting as late as I could to avoid other working meetings. Now it seems that other Areas WG did the same and we have this unfortunate mash-up. Shifting earlier does not seem like it
will work either, so it may have to be later, after the CESG, which will be unfortunate. That said, I think it is more important to get the feedback on what we are doing than it is to push ahead with a lightly attended meeting just to meet a schedule.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The other point you made, about meeting with each group separately, is just too much of a burden for my small WG. My preferred approach is to present this whole approach once, to everyone at once, and then deal with any specific issues
that do arise on an area by area basis.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal"><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">Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><br>
<b>Date: </b>Friday, May 7, 2021 at 12:51 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org>, Colin Haddow <Colin.Haddow@esa.int>, Erik Barkley <erik.j.barkley@jpl.nasa.gov>, Gilles Moury <Gilles.Moury@cnes.fr>, Klaus-Juergen Schulz <Klaus-Juergen.Schulz@esa.int>, Scott
Burleigh <scott.c.burleigh@jpl.nasa.gov>, SEA-exec SEA-exec <sea-exec@mailman.ccsds.org>, "Tomaso.deCola@dlr.de" <Tomaso.deCola@dlr.de><br>
<b>Subject: </b>[EXTERNAL] Re: Request for a brief coordination meeting on SCCS-ARD planned changes<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">Peter,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> please note that two out of the three dates you propose are coincident with the SLS Plenary planned for 1st and 2nd June.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I will ask SLSers to check their availability to represent the WGs but I cannot ensure a wide reply and most likely not for today.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Moreover, forgive me for my imprudence but wouldn't be simpler organising bilateral meeting with your WG and each affected WG?</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Just my cent...</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Regards</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Gian Paolo</span> <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">"Shames, Peter M (US 312B)" <peter.m.shames@jpl.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">"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:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span><span style="font-size:9.0pt;font-family:"Arial",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:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">05-05-21 23:41</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">Request for a brief coordination meeting on SCCS-ARD planned changes</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">Dear SLS, CSS, SIS, and SEA colleagues,<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">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.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">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.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">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. <o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">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. <o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><b><i>Replies, please, by CoB, Friday, 7 May 2021.</i></b><o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">Thanks, Peter<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><a href="https://urldefense.us/v3/__https:/doodle.com/poll/47wupegzugffhyiy?utm_source=poll&utm_medium=link__;!!PvBDto6Hs4WbVuu7!btveytXmiAyvmMuUYYNRgOrmQmMXLY56oK_G2KtpC0LWSDg_qdN8njwMFzkt6qBspI3dWJ6K$"><b><span style="color:#0082BF">https://doodle.com/poll/47wupegzugffhyiy?utm_source=poll&utm_medium=link</span></b></a><o:p></o:p></p>
<p style="margin:0in"><b> </b><o:p></o:p></p>
<p style="margin:0in"><b> </b><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>