[CMC] Input for MoM on CCSDS-IOAG interface

Tue Nov 28 19:26:39 UTC 2017

Dear James,

I agree that the IOAG liaison is the only contact point in CCSDS regarding 
formal agreements with IOAG but in order for the liaison to work 
effectively there needs to be a well defined support role for the CESG 
Chair. This role shall include the participation in the technical meetings 
and telecons. This was the agreement during the CMC meeting, that led to 
the consensus to nominate you as the IOAG liaison. Some of the rewording 
you propose now is compromising this agreement, as it implies e.g. that 
the CESG Chair will only participate in the IOAG meetings and telecons if 
you require so.  So I cannot agree with the changes to the first bullet 
you propose, and I have marked my proposed changes to your text (see 
below).

I understand this agreement has already been violated  by excluding the 
CESG Chair from the distribution list of the IOAG and therefore from the 
invitations to the IOAG telecons issued recently. I do not agree with 
this. 

I also do not agree for efficiency and transparency reasons that the CESG 
Chair is not in copy of communications coming from the IOAG. One thing is 
to avoid that CCSDS is speaking with two voices to IOAG and another one is 
to cut off the CESG Chair from the inputs and information coming from 
IOAG. It goes without saying that the CESG Chair role is in support to the 
IOAG liaison (CMC Chair) but for this support to be provided effectively, 
the CESG Chair must be fully aware of the background information.

So in the spirit of the agreement during the CMC meeting, that allowed to 
achieve consensus in the poll, I hope you can take into account my inputs

peoposed text:

The CESG Chair role is to in support to the CCSDS Liaison, CMC Chair, is 
as required: 
Participate at the IOAG meetings and telecons as required by the CCSDS 
Liaison.
Provide technical reports periodically and as required by the CCSDS 
Liaison. 
Support the CCSDS Liaison in technical discussions and queries during 
meetings / telecons 
Maintain ICPA (IOAG CCSDS Product Agreement) 
Communicate the IOAG requirements and suggestions to the relevant CCSDS 
WGs 

Regards
Juan

Juan Miro
ESA delegate in the CCSCS Management Council
Head Ground Systems Engineering Department
Europan Space Operations Centre
European Space Agency

From:   "Afarin, James (HQ-CG000)" <james.afarin at nasa.gov>
To:     "Juan.Miro at esa.int" <Juan.Miro at esa.int>, "Ross, David 
(HQ-CG000)[Arctic Slope Technical Services, Inc.]" <david.ross at nasa.gov>
Cc:     CMC - CCSDS Management Council <cmc at mailman.ccsds.org>
Date:   21/11/2017 14:41
Subject:        Re: [CMC] Input for MoM on CCSDS-IOAG interface

Hi Juan,

I made few clarifications on the role of the CESG.  The most important 
aspect is the only avenue to and from IOAG shall be thru the IOAG liaison 
as always.  Please give me your thoughts.

The CCSDS liaison with IOAG is the CMC Chair and covers the following main 
responsibilities: 

Agree on standards to be developed and relevant priorities 
Clarify resources needed to perform the tasks and ensure their 
availability 
Clarify scope of WGs to be established 
Communicate IOAG inputs to CMC and CESG Chair 
Support IOAG in preparing IOP meetings as required

The CESG Chair role is to support the CCSDS Liaison, CMC Chair, as 
required: 
Participate at the IOAG meetings and telecons as required by the CCSDS 
Liaison.
Provide technical reports periodically and as required by the CCSDS 
Liaison. 
Support the CCSDS Liaison in technical discussions and queries during 
meetings / telecons 
Maintain ICPA (IOAG CCSDS Product Agreement) 
Communicate the IOAG requirements and suggestions to the relevant CCSDS 
WGs 

Thank you,

James

Dr. James Afarin 

Space Data Standards Manager 
Space Communications and Navigation Division
Office: 202-358-5221 
Mobile: 202-549-6496

From: CMC <cmc-bounces at mailman.ccsds.org> on behalf of Juan Miro 
<Juan.Miro at esa.int>
Date: Tuesday, November 14, 2017 at 10:51 AM
To: "Ross, David (HQ-CG000)[Arctic Slope Technical Services, Inc.]" 
<david.ross at nasa.gov>
Cc: CMC - CCSDS Management Council <cmc at mailman.ccsds.org>
Subject: [CMC] Input for MoM on CCSDS-IOAG interface

Dear David, 

as agreed by CMC here is my input on the proposed interface between CCSDS 
and IOAG for the corresponding resolution to be included in the  minutes 

Regards 
Juan 

_________________________________________________________________________ 

CCSDS Liaison to IAOG 

The CCSDS liaison with IOAG is the CMC Chair and covers the following main 
responsibilities: 
Agree on standards to be developed and relevant priorities 
Clarify resources needed to perform the tasks and ensure their 
availability 
Clarify scope of WGs to be established 
Communicate IOAG inputs to CMC and CESG Chair 
Support IOAG in preparing IOP meetings as required

The role of the CESG Chair in support to the CMC Chair is: 
Regular participation to IOAG meeting and telecons 
Provide regular reports about CCSDS progress during meetings / telecons 
Support technical discussions and queries during meetings / telecons 
Maintain ICPA (IOAG CCSDS Product Agreement) 
Inject in relevant CCSDS WGs the IOAG requirements and suggestions 
This message and any attachments are intended for the use of the addressee 
or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in 
whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete 
it from your system.
Emails can be altered and their integrity cannot be guaranteed by the 
sender.

Please consider the environment before printing this email.

This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.

Please consider the environment before printing this email.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/cmc/attachments/20171128/4ecd3598/attachment.html>