[CMC] Input for MoM on CCSDS-IOAG interface
Juan.Miro at esa.int
Juan.Miro at esa.int
Wed Dec 20 19:11:40 UTC 2017
Dear James,
thank you for your commitment to involve the CESG Chair in all technical
discussions.
I wish you well in your new role
Regards
Juan
Juan Miro
Head Ground Systems Engineering Department
European 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>
Cc: CMC - CCSDS Management Council <cmc at mailman.ccsds.org>, "Ross,
David (HQ-CG000)[Arctic Slope Technical Services, Inc.]"
<david.ross at nasa.gov>
Date: 20/12/2017 16:38
Subject: Re: [CMC] Input for MoM on CCSDS-IOAG interface
Dear Juan,
Thank you for your input. I agree that CESG chair should participate in
all technical discussion. I will continue to invite her promptly and
efficiently to all technical discussions. As always only the CCSDS
liaison will be regular invited to the IOAG meetings and I will include
the CESG chair for any and all technical discussions. This is the spirit
and reality of the CMC agreement and I am honoring it. I wish you all
Merry Christmas and Happy New Year.
Thank you,
James
Dr. James Afarin
Space Data Standards Manager
Space Communications and Navigation Division
Office: 202-358-5221
Mobile: 202-549-6496
From: Juan Miro <Juan.Miro at esa.int>
Date: Tuesday, December 19, 2017 at 2:00 PM
To: James Afarin <james.afarin at nasa.gov>
Cc: CMC - CCSDS Management Council <cmc at mailman.ccsds.org>, "Ross, David
(HQ-CG000)[Arctic Slope Technical Services, Inc.]" <david.ross at nasa.gov>
Subject: Re: [CMC] Input for MoM on CCSDS-IOAG interface
Dear James,
as discussed last week on the phone, and I believe agreed, the CESG Chair
should support you in your role as IOAG liaison; and this should include
attending the regular webex-conferences organised by IOAG, and as well as
providing a progress report during such meetings (with your previous
approval). This is also what we discussed during the last CMC meeting, and
the spirit in which you obtained the support of the CMC. You may have
other meetings with IOAG for which technical support is not necessarily
required, and then it is at your discretion to invite the CESG Chair to
participate.
I understand you have the firm intention to involve the CESG Chair in
technical matters, but the example of the recent IOAG invitation shows
that Margherita should be in the IOAG distribution list per default, so as
to ensure she gets the invitation timely without you having to forward it.
This will also allow her to get the inputs from IOAG first hand without
any loss of information, which is crucial for the CESG to adequately
respond to the IOAG requests and inputs.
It is clear that you are the only CCSDS interface to IOAG, in particular
when it comes to state CCSDS positions.
I hope with this clarification we can finally agree on the following text
for the MoM of the last CMC, that by the way, to my knowledge, have not
yet been circulated.
The CESG Chair role is to in support to the CCSDS Liaison, CMC Chair, is
as required:
Participate at the regular 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
Please let me know
Regards
Juan
From: "Afarin, James (HQ-CG000)" <james.afarin at nasa.gov>
To: "Juan.Miro at esa.int" <Juan.Miro at esa.int>
Cc: CMC - CCSDS Management Council <cmc at mailman.ccsds.org>, "Ross,
David (HQ-CG000)[Arctic Slope Technical Services, Inc.]"
<david.ross at nasa.gov>
Date: 06/12/2017 19:48
Subject: Re: [CMC] Input for MoM on CCSDS-IOAG interface
Dear Juan,
I have not violated any agreement. The only agreement that we had in the
CMC was that I will defer all technical issues to the CESG chair and I
will do so. There will be management meetings when the attendance by me,
the CCSDS Liaison, alone is sufficient to represent the CCSDS, and there
is no need for the CESG Chair or any other CCSDS members to be present on
behalf of the CCSDS. That is entirely appropriate. We agreed that the
CESG role is to support the CCSDS liaison and nothing else.
No one should give the impression that the CESG Chair is the CCSDS
technical liaison to the IOAG. As always, there will be only one CCSDS
liaison to IOAG.
Thank you
James
James Afarin
SCaN Standard Manager
Office: (202) 358-5221
Mobile: (202) 549-6496
Sent from my iPhone
On Nov 29, 2017, at 6:26 AM, "Juan.Miro at esa.int" <Juan.Miro at esa.int>
wrote:
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.
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/20171220/c58a1701/attachment.html>
More information about the CMC
mailing list