<html 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)">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{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>
</head>
<body lang="EN-US" link="#0563C1" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Dear CCSDS Colleagues,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks to all of you for participating in the prior poll. We have a quorum, and a date, and that is excellent.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">And now we need to shift it again. Say what???<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Seems that the CMC decided (as Gippo warned they might) to use the dates 15-17 June 2021 for their meeting. So now we need to shift it to the following week. So, I must beg your indulgence, and test your patience, as I ask you to follow
the bouncing ball to the next set of possible dates, June 22, 23, or 24. The new Doodle poll link is here:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span style="color:#2E75B6;mso-style-textfill-fill-color:#2E75B6;mso-style-textfill-fill-alpha:100.0%">https://doodle.com/poll/xty3656m6qwrfkfk?utm_source=poll&utm_medium=link</span></b><b><o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for your patience with this process and your support. Maybe THIS time the dates will stick.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><i>Replies please by CoB, Tuesday, 25 May 2021.<o:p></o:p></i></b></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">Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Date: </b>Monday, May 10, 2021 at 1:50 PM<br>
<b>To: </b>Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int>, Gilles Moury <Gilles.Moury@cnes.fr>, Erik Barkley <erik.j.barkley@jpl.nasa.gov>, Colin Haddow <Colin.Haddow@esa.int>, Scott Burleigh <scott.c.burleigh@jpl.nasa.gov>, "Tomaso.deCola@dlr.de" <Tomaso.deCola@dlr.de>,
SEA-exec SEA-exec <sea-exec@mailman.ccsds.org>, SEA-SA <sea-sa@mailman.ccsds.org><br>
<b>Cc: </b>Klaus-Juergen Schulz <Klaus-Juergen.Schulz@esa.int>, CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Subject: </b>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">Dear All,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">My thanks to those of you who did reply and were able to meet on the days we tried to use. From some of the feedback, and the results of the voting, it is clear that almost none of the members of the SLS Area and CSS areas will be able
to participate on those days (see attached results). While I hoped to be able to schedule this before the CESG meeting it is clear that it will need to be held afterwards.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Accordingly I have posted a new Doodle poll for the week <b>
<i>after</i></b> the CESG meeting. Please give this another try.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b><i>Replies, please, by CoB, Friday, 14 May 2021.</i></b><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>
<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">Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Date: </b>Wednesday, May 5, 2021 at 2:41 PM<br>
<b>To: </b>Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int>, Gilles Moury <Gilles.Moury@cnes.fr>, Erik Barkley <erik.j.barkley@jpl.nasa.gov>, Colin Haddow <Colin.Haddow@esa.int>, Scott Burleigh <scott.c.burleigh@jpl.nasa.gov>, "Tomaso.deCola@dlr.de" <Tomaso.deCola@dlr.de>,
SEA-exec SEA-exec <sea-exec@mailman.ccsds.org><br>
<b>Cc: </b>Klaus-Juergen Schulz <Klaus-Juergen.Schulz@esa.int>, CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Subject: </b>Request for a brief coordination meeting on SCCS-ARD planned changes</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal">Dear SLS, CSS, SIS, and SEA colleagues,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">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 class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">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 class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">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 class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">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 class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b><i>Replies, please, by CoB, Friday, 7 May 2021.</i></b><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"><b> </b><o:p></o:p></p>
<p class="MsoNormal"><b> </b><o:p></o:p></p>
</div>
</body>
</html>