[SEA-exec] Difficult days: Request for a brief coordination meeting on SCCS-ARD planned changes

[Gian.Paolo.Calzolari at esa.int]

Peter,
        please note that two out of the three dates you propose are 
coincident with the SLS Plenary planned for 1st and 2nd June.
Moreover 3rd June is a public holiday (at least in Germany).

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.

Moreover, forgive me for my imprudence but wouldn't be simpler organising 
bilateral meeting with your WG and each affected WG?
Just my cent...

Regards

Gian Paolo



From:   "Shames, Peter M (US 312B)" <peter.m.shames at jpl.nasa.gov>
To:     "Gian Paolo Calzolari" <Gian.Paolo.Calzolari at esa.int>, "Gilles 
Moury" <Gilles.Moury at cnes.fr>, "Barkley, Erik J (US 3970)" 
<erik.j.barkley at jpl.nasa.gov>, "Colin Haddow" <Colin.Haddow at esa.int>, 
"Burleigh, Scott C (US 312B)" <scott.c.burleigh at jpl.nasa.gov>, 
"Tomaso.deCola at dlr.de" <Tomaso.deCola at dlr.de>, "SEA-exec SEA-exec" 
<sea-exec at mailman.ccsds.org>
Cc:     "Klaus-Juergen Schulz" <Klaus-Juergen.Schulz at esa.int>, "CCSDS 
Engineering Steering Group - CESG Exec" <cesg at mailman.ccsds.org>
Date:   05-05-21 23:41
Subject:        Request for a brief coordination meeting on SCCS-ARD 
planned changes



Dear SLS, CSS, SIS, and SEA colleagues,
 
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.
 
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.
 
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. 
 
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. 
 
Replies, please, by CoB, Friday, 7 May 2021.
 
Thanks, Peter
 
 
https://doodle.com/poll/47wupegzugffhyiy?utm_source=poll&utm_medium=link
 
 



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 at esa.int).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sea-exec/attachments/20210507/9eeb0e91/attachment-0001.htm>