[CESG] CESG-P-2024-06-001 Approval to release CCSDS 522.2-R-2, Mission Operations—Mission Data Product Distribution Services (Red Book, Issue 2) for CCSDS Agency review

Tue Oct 29 15:28:27 UTC 2024

Dear CESG Members,

Conditions for approval of CCSDS 522.2-R-2, Mission Operationsâ€”Mission Data Product Distribution Services (Red Book, Issue 2) have been disposed to the satisfaction of the AD(s) who voted to approve with conditions. The Secretariat will now proceed with CMC polling to authorize release for Agency review.
-------------- next part --------------
From:	Tomaso.deCola at dlr.de
Sent:	Tuesday, October 29, 2024 6:58 AM
To:	Mehran.Sarkarati at esa.int
Cc:	costin.radulescu at jpl.nasa.gov; Daniel.Fischer at esa.int; moims-
sc at mailman.ccsds.org; thomas.gannett at tgannett.net
Subject:	RE: CESG-P-2024-06-001 Approval to release CCSDS 522.2-R-2, Mission Operations—
Mission Data Product Distribution Services (Red Book, Issue 2) for CCSDS Agency 
review

Categories:	Poll Condition Closure

Dear Mehran,

Thank you for the clarification and confirming the way to address my points. I’m ok with the proposed 
approach, so that my conditions can be now considered closed.

Regards,

Tomaso

From: Mehran Sarkarati <Mehran.Sarkarati at esa.int>  
Sent: Montag, 28. Oktober 2024 18:07 
To: de Cola, Tomaso <Tomaso.deCola at dlr.de> 
Cc: costin.radulescu at jpl.nasa.gov; Daniel Fischer <Daniel.Fischer at esa.int>; moims-
sc at mailman.ccsds.org; CCSDS Secretariat <thomas.gannett at tgannett.net> 
Subject: FW: CESG-P-2024-06-001 Approval to release CCSDS 522.2-R-2, Mission Operations—Mission 
Data Product Distribution Services (Red Book, Issue 2) for CCSDS Agency review

Dear Tomaso,

Going back through my emails, I could not find any trace of exchanges with you with regard to the 
condition you had raised on the Mission Data Product Distribution Service.

Let me please start with apologizing for this oversight on our side and in case I have missed any emails.
We have resolved the condition of Peter and have his agreement to move forward with the agency review.

The point you had raised is very valid and needs better clarification, which we are happy to implement as 
below.
Please let us know if the following implementation would address sufficiently the condition you had 
raised:

1.	Add text to clarify that only the data type definitions, contained in section 4 are normative: The 
tables and any associated requirements. The UML diagrams are only informative.
2.	Remove comment relating to services - in an earlier version of the document the Information 
Model preceded the Service Specification but this was not edited.

Best Regards
Mehran (on behalf of the SM&C WG)

Dr. Mehran Sarkarati 
Head of Ground Station Engineering Division
Department of Ground Systems Engineering and Innovation
Directorate of Operations 

ESA – European Space Agency 
ESOC I Robert-Bosch-Str. 5, 64293 Darmstadt, Germany 
Tel: +49 6151 903225  
mehran.sarkarati at esa.int    I   www.esa.int

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). 

From:	Mehran Sarkarati <Mehran.Sarkarati at esa.int>
Sent:	Tuesday, October 22, 2024 6:21 AM
To:	Radulescu, Costin (US 9300); Daniel Fischer
Cc:	CCSDS Secretariat
Subject:	Re: CESG-P-2024-06-001 Approval to release CCSDS 522.2-R-2, Mission 
Operations—Mission Data Product Distribution Services (Red Book, 
Issue 2) for CCSDS Agency review

Categories:	Poll Condition Closure

Hi Costin,

Thank you for coordinating this.

@Daniel/Tom: now that Peter has confirmed his raised condition has been satisfied can we 
proceed and kick off the agency review.

Regards
Mehran

From: Radulescu, Costin (US 9300) <cradule at jpl.nasa.gov> 
Sent: Thursday, October 17, 2024 11:20 PM 
To: Shames, Peter M (US 9740) <peter.m.shames at jpl.nasa.gov>; Mehran Sarkarati 
<Mehran.Sarkarati at esa.int> 
Subject: Re: CESG-P-2024-06-001 Approval to release CCSDS 522.2-R-2, Mission Operations—
Mission Data Product Distribution Services (Red Book, Issue 2) for CCSDS Agency review 

Understood Peter.   Thanks for the explanation and approval to move forward.

Best regards,
       -Costin

Costin Radulescu, Deputy Program Manager (NASA/JPL)
Multi-mission Ground Systems and Services Program (MGSS)
Interplanetary Network Directorate (IND/9X)
Costin.Radulescu at JPL.NASA.GOV
818-442-3194

From: Shames, Peter M (US 9740) <peter.m.shames at jpl.nasa.gov> 
Sent: Thursday, October 17, 2024 1:37:42 PM 
To: Radulescu, Costin (US 9300) <cradule at jpl.nasa.gov>; Mehran Sarkarati <Mehran.Sarkarati at esa.int> 
Subject: Re: CESG-P-2024-06-001 Approval to release CCSDS 522.2-R-2, Mission Operations—Mission 
Data Product Distribution Services (Red Book, Issue 2) for CCSDS Agency review 

Hi Costin,

I do understand that there is a trade-off here between complexity and interoperability.  It appears that you 
have chosen to have interoperable service specifications, but are wrestling with the issue of data format 
interoperability (the contents of the service exchange).  This data product interoperability distinction can 
be simply stated as a choice between a data specification formalization that is exchanged as part of a 
protocol interaction and a data specification formalization that is done out of band, “by management”.  

You appear to have chosen the latter and have decided to adopt the approach that “definitions are 
exchanged in ICDs, Mission Databases, XTCE, ….”.   Since we have a number of CCSDS standards that 
operate in this way I will accept it, but I think it is a less effective method than using any of the possible 
self defining, or discoverable, data formats.

Permission to proceed is granted.

Peter

From: Radulescu, Costin (US 9300) <cradule at jpl.nasa.gov> 
Date: Tuesday, October 15, 2024 at 2:55?PM 
To: Shames, Peter M (US 312B) <peter.m.shames at jpl.nasa.gov> 
Subject: RE: CESG-P-2024-06-001 Approval to release CCSDS 522.2-R-2, Mission 
Operations—Mission Data Product Distribution Services (Red Book, Issue 2) for CCSDS 
Agency review
Hi Peter,

I would like to close the loop with you on the responses below before the Fall meetings.   Are you 
satisfied with the explanation(s) below?   Is there anything I could answer or the WG can address to 
successfully close your review?   Thanks much!

Best regards,
                -Costin

From: Mehran Sarkarati <Mehran.Sarkarati at esa.int>  
Sent: Thursday, July 11, 2024 12:05 AM 
To: Shames, Peter M (US 312B) <peter.m.shames at jpl.nasa.gov> 
Cc: Daniel Fischer <Daniel.Fischer at esa.int>; Stefan.Gaertner at dlr.de; Radulescu, Costin (US 9300) 
<cradule at jpl.nasa.gov>; Cesar Coelho <Cesar.Coelho at ext.esa.int>; roger.rocketbrain 
<roger.rocketbrain at btinternet.com>; Peter Collins <Peter.Collins at esa.int>; Churlaud Olivier 
<Olivier.Churlaud at cnes.fr>; Dominik Marszk <Dominik.Marszk at esa.int> 
Subject: [EXTERNAL] FW: CESG-P-2024-06-001 Approval to release CCSDS 522.2-R-2, Mission 
Operations—Mission Data Product Distribution Services (Red Book, Issue 2) for CCSDS Agency review

Dear Peter,

Thank you for reviewing the Mission Product Distribution Service specification and providing comments.
The WG is processing them and will implement and provide more detailed answers.
I had a quick run through the comments and from what I gathered one of the main points is the question 
of what the MPDS is standardizing and what is left to be specified in out-bound-agreements (ICD)s:

a.	The interface for exchanging Mission Products 
b.	The Definition/Specification of what a Product is and how it can be processed/interpreted

This is a very valid question and the WG has discussed it over many years. The version of the MPDS that 
you have reviewed is the 3rd completely reworked version of the book.
The first version of the book had the concepts for both a and b and the idea of a catalogue of products, 
means of retrieving the specification of a given product and standardizing the language in which products 
can be described with pre-defined meta-data, etc.

That version was heavily criticized mainly by NASA WG members to be too complex and not reflecting 
the current operational models and common practices of inter-agency interoperability.
As part of the MO 2.0 efforts, we gathered pain points from all agencies and agreed to focus more on 
standardizing today’s common practices and respecting today’s well established operational concepts.

For the MPDS in particular we analysed use cases from CNES, DLR, ESA and NASA and looked at the 
existing Mission Product Distribution software interfaces. 
The common agreement in the WG has been that for all analysed missions and the existing systems of our 
agencies, the “definition”/Specificaiton of what a product is and how to read/interpret/process it is known 
to both parties (provider and consumer). This is typically captured in ICDs or other standards. Hence the 
WG decision has been to rework the MPDS to this much simplified version that focuses on the (a): 
Standardised interface for exchange of Mission Products and leave (b) to be handled as it is handled 
today.

This is very similar to the rework we have done for Monitoring and Control services, where we removed 
all operations and data types that relate to exchange of “definition” of TM/TC items. The same logic 
applies, since the TM/TC definitions are exchanged in ICDs, Mission Databases, XTCE, ….

I hope this clarifies the rational. I acknowledge that we may need to find better wording to explain this 
more clearly, to avoid a misunderstanding that the service interoperability is limited by this choice as it 
does have a significant added value to standardize interoperable interface between agencies to exchange 
mission products, even if the defintions of the products are captured in other standards, ICDs or known to 
both parties. 

Regards
Mehran

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). 
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). 