[CESG] [EXTERNAL] 131.3 unresolved Poll: SLS position paper

Wed Apr 15 12:25:35 UTC 2020

Dear Peter, 
I take note of the NASA Position Paper that you delivered with your e-mail 
on 3rd April.

I remark that the right forum for an Agency's position paper is within the 
affected  WG(s) and Area. Only after the relevant technical discussion in 
those forums has taken place , the CESG may/will intervene, if needed.
The CESG is , in fact,  supposed to sort out technical  issues that may 
arise between Areas ( or between WGs).  It is not supposed to decide upon 
a roadmap for technical documentation, when that  roadmap – which entails 
the way forward, the concept papers(s), the new projects, etc. - needs to 
be  produced as the result of an Agency's position paper. 
It is only within the WGs that all (interested) Agencies are represented 
and can fairly support the discussion.

I notice that the NASA's Position Paper implies a re-assessment of the 
approach for  the (set of ) coding-related document(s), whilst the 
existing approach did get WG’s consensus in previous CCSDS sessions, 
notably Berlin and Mountain View, if I remember well. 
Accordingly, I request that whichever re-assessment is supposed to be done 
now , it shall be done first in the appropriate forum (=WG/Area). 
Again, the CESG will then discuss the outcome of the WGs’ re-assessment, 
if needed.

Concerning the unresolved Poll for the DBV-S2 standard, which has been 
produced according to the existing roadmap, I do not see another option 
than escalating the decision to the CMC, given that at this point in time 
this is no longer a technical discussion, and that there is no consensus 
within the CESG

Kind regards.
Margherita
--------------------------------------------------------------
Margherita di Giulio
Ground Station Systems Division
Backend Software Section (OPS-GSB)

European Space Agency ESA/ESOC
Robert-Bosch-Str. 5
D-64293 Darmstadt - Germany
Tel: +49-6151-902779
e-mail: Margherita.di.Giulio at esa.int

From:   "Shames, Peter M (US 312B)" <peter.m.shames at jpl.nasa.gov>
To:     "Margherita.di.Giulio at esa.int" <Margherita.di.Giulio at esa.int>, 
"CCSDS Engineering Steering Group - CESG Exec" <cesg at mailman.ccsds.org>
Cc:     "Massimo.Bertinelli at esa.int" <Massimo.Bertinelli at esa.int>, "Moury 
Gilles" <Gilles.Moury at cnes.fr>, "Hamkins, Jon (US 3300)" 
<jon.hamkins at jpl.nasa.gov>, "Andrews, Kenneth S (US 332B)" 
<kenneth.s.andrews at jpl.nasa.gov>, "Victor Sank" <victor.j.sank at nasa.gov>, 
"Kazz, Greg J (US 312B)" <greg.j.kazz at jpl.nasa.gov>, "Bernie Edwards" 
<bernard.l.edwards at nasa.gov>, "Lee, Dennis K (US 332G)" 
<dennis.k.lee at jpl.nasa.gov>
Date:   03/04/2020 22:14
Subject:        Re: [EXTERNAL] [CESG] 131.3 unresolved Poll: SLS position 
paper

Dear Margherita and CESG members,

During yesterday's CESG WebEx I said that I would provide a revision of 
the original NASA position paper on how to resolve this issue.  That is 
attached.  It is a refinement of the position that we presented before, 
and it specifically tries to address the technical issues that Gilles and 
others have raised.

You will see that this is endorsed by the relevant set of NASA 
participants in the RFM, C&S, SLP, and Opt WGs.  They all had a role in 
refining and reviewing these materials.

Lastly, you will find in the backup an analysis showing the difference in 
outcome between the approach proposed here and what would result from the 
present trajectory as documented in Gilles note.  We all believe that what 
was, in effect, implied by the changes to the DBV-S2 standard really 
represent what should be an architecturally significant shift in how the 
SLS standards, as a group, may be applied to future missions. 

We will be missing a significant opportunity if we do not take the time 
now to adopt this as a uniform position across all of the affected SLS 
standards.

While we all must respect the crucial role of the CCSDS Working Groups in 
developing and validating technically sound standards, we must also 
remember that the CESG has been assigned the role for ensuring technical 
quality, coherence, and consistency across the standards and across the 
areas.
2.3.2.3 CESG Responsibilities 
The CESG is specifically responsible for the following: 
a)  maintaining and upholding the overall technical quality and 
consistency of the evolving set of CCSDS Recommended Standards and 
Practices; 
And that required CESG review is the context within which these issues 
were identified.  This is not just a Working Group issue.

Best regards, Peter

From: CESG <cesg-bounces at mailman.ccsds.org> on behalf of Gilles Moury 
<Gilles.Moury at cnes.fr>
Date: Saturday, March 28, 2020 at 11:25 AM
To: "Margherita.di.Giulio at esa.int" <Margherita.di.Giulio at esa.int>
Cc: "Massimo.Bertinelli at esa.int" <Massimo.Bertinelli at esa.int>, CCSDS 
Engineering Steering Group - CESG Exec <cesg at mailman.ccsds.org>
Subject: [EXTERNAL] [CESG] 131.3 unresolved Poll: SLS position paper

Dear Margherita,

I hope you and your family are able to stay safe & healthy.

As a response to action item taken during March 10 CESG telecon, please 
find attached SLS position paper regarding 131.3 unresolved poll.

Best regards,

Gilles

Gilles MOURY
Senior Adviser On-Board Architecture & Avionics
Architecture, Validation & Integration Department 
18 avenue Edouard Belin 31401 Toulouse Cedex 9
 +33 (0)5 61 27 37 90 / +33 (0)6 83 56 04 85
 gilles.moury at cnes.fr 
 cnes.fr 

 [attachment "NASA refined ALACAMAD approach 3Apr20.pptx" deleted by 
Margherita di Giulio/esoc/ESA] 

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/cesg/attachments/20200415/c3e0df0d/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 3398 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20200415/c3e0df0d/attachment-0008.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 746 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20200415/c3e0df0d/attachment-0009.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 743 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20200415/c3e0df0d/attachment-0010.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 741 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20200415/c3e0df0d/attachment-0011.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 743 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20200415/c3e0df0d/attachment-0012.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 786 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20200415/c3e0df0d/attachment-0013.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 796 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20200415/c3e0df0d/attachment-0014.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 793 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20200415/c3e0df0d/attachment-0015.jpe>