<font size=2 face="sans-serif">Dear James,</font>
<br>
<br><font size=2 face="sans-serif">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).</font>
<br>
<br><font size=2 face="sans-serif">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. </font>
<br><font size=2 face="sans-serif"> </font>
<br><font size=2 face="sans-serif">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.</font>
<br>
<br><font size=2 face="sans-serif">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</font>
<br>
<br><font size=2 face="sans-serif">peoposed text:</font>
<br>
<br><font size=2 face="Helvetica"><u>The CESG Chair role <strike>is to</strike>
in support to the CCSDS Liaison, CMC Chair, is <strike>as required</strike>:</u>
</font>
<ul>
<li><font size=2 face="Helvetica">Participate at the IOAG meetings and
telecons <strike>as required by the CCSDS Liaison.</strike></font>
<li><font size=2 face="Helvetica">Provide technical reports <u>periodically
and</u> as required by the CCSDS Liaison. </font>
<li><font size=2 face="Helvetica">Support the CCSDS Liaison in technical
discussions and queries during meetings / telecons </font>
<li><font size=2 face="Helvetica">Maintain ICPA (IOAG CCSDS Product Agreement)
</font>
<li><font size=2 face="Helvetica">Communicate the IOAG requirements and
suggestions to the relevant CCSDS WGs </font></ul>
<br><font size=2 face="sans-serif">Regards</font>
<br><font size=2 face="sans-serif">Juan</font>
<br>
<br><font size=2 face="sans-serif">Juan Miro</font>
<br><font size=2 face="sans-serif">ESA delegate in the CCSCS Management
Council<br>
Head Ground Systems Engineering Department</font>
<br><font size=2 face="sans-serif">Europan Space Operations Centre<br>
European Space Agency</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Afarin, James
(HQ-CG000)" <james.afarin@nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"Juan.Miro@esa.int"
<Juan.Miro@esa.int>, "Ross, David (HQ-CG000)[Arctic Slope Technical
Services, Inc.]" <david.ross@nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">CMC - CCSDS Management
Council <cmc@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">21/11/2017 14:41</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [CMC] Input
for MoM on CCSDS-IOAG interface</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Helvetica">Hi Juan,</font>
<br><font size=2 face="Helvetica"> </font>
<br><font size=2 face="Helvetica">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.</font>
<br><font size=2 face="Helvetica"> </font>
<br><font size=2 face="Helvetica"> </font>
<br><font size=2 face="Helvetica"> </font>
<br><font size=2 face="Helvetica"><u>The CCSDS liaison with IOAG is the
CMC Chair and covers the following main responsibilities:</u> </font>
<br><font size=2 face="Helvetica"> </font>
<ul>
<li><font size=2 face="Helvetica">Agree on standards to be developed and
relevant priorities </font>
<li><font size=2 face="Helvetica">Clarify resources needed to perform the
tasks and ensure their availability </font>
<li><font size=2 face="Helvetica">Clarify scope of WGs to be established
</font>
<li><font size=2 face="Helvetica">Communicate IOAG inputs to CMC and CESG
Chair </font>
<li><font size=2 face="Helvetica">Support IOAG in preparing IOP meetings
as required</font></ul><font size=2 face="Helvetica"> </font>
<br><font size=2 face="Helvetica"><u>The CESG Chair role is to support
the CCSDS Liaison, CMC Chair, as required:</u> </font>
<ul>
<li><font size=2 face="Helvetica">Participate at the IOAG meetings and
telecons <strike>as required by the CCSDS Liaison.</strike></font>
<li><font size=2 face="Helvetica">Provide technical reports <u>periodically
and</u> as required by the CCSDS Liaison. </font>
<li><font size=2 face="Helvetica">Support the CCSDS Liaison in technical
discussions and queries during meetings / telecons </font>
<li><font size=2 face="Helvetica">Maintain ICPA (IOAG CCSDS Product Agreement)
</font>
<li><font size=2 face="Helvetica">Communicate the IOAG requirements and
suggestions to the relevant CCSDS WGs </font></ul><font size=2 face="Helvetica"> </font>
<br><font size=2 face="Helvetica"> </font>
<br><font size=2 face="Helvetica">Thank you,</font>
<br><font size=2 face="Helvetica"> </font>
<br><font size=2 face="Helvetica">James</font>
<br><font size=2 face="Helvetica"> </font>
<br><font size=2 face="Helvetica">Dr. James Afarin </font>
<br><font size=2 face="Helvetica"><br>
Space Data Standards Manager <br>
Space Communications and Navigation Division<br>
Office: 202-358-5221 <br>
Mobile: 202-549-6496</font>
<br><font size=2 face="Helvetica"> </font>
<br><font size=3 face="Calibri"><b>From: </b>CMC <cmc-bounces@mailman.ccsds.org>
on behalf of Juan Miro <Juan.Miro@esa.int><b><br>
Date: </b>Tuesday, November 14, 2017 at 10:51 AM<b><br>
To: </b>"Ross, David (HQ-CG000)[Arctic Slope Technical Services, Inc.]"
<david.ross@nasa.gov><b><br>
Cc: </b>CMC - CCSDS Management Council <cmc@mailman.ccsds.org><b><br>
Subject: </b>[CMC] Input for MoM on CCSDS-IOAG interface</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="sans-serif">Dear David,</font><font size=2 face="Calibri">
<br>
</font><font size=2 face="sans-serif"><br>
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</font><font size=2 face="Calibri">
<br>
</font><font size=2 face="sans-serif"><br>
Regards</font><font size=2 face="Calibri"> </font><font size=2 face="sans-serif"><br>
Juan</font><font size=2 face="Calibri"> <br>
</font><font size=2 face="sans-serif"><br>
_________________________________________________________________________</font><font size=2 face="Calibri">
<br>
</font><font size=2 face="sans-serif"><b><u><br>
CCSDS Liaison to IAOG</u></b></font><font size=2 face="Calibri"> <br>
</font><font size=2 face="sans-serif"><u><br>
The CCSDS liaison with IOAG is the CMC Chair and covers the following main
responsibilities:</u></font><font size=2 face="Calibri"> </font>
<ul>
<li><font size=2 face="sans-serif">Agree on standards to be developed and
relevant priorities</font><font size=2 face="Calibri"> </font>
<li><font size=2 face="sans-serif">Clarify resources needed to perform
the tasks and ensure their availability</font><font size=2 face="Calibri">
</font>
<li><font size=2 face="sans-serif">Clarify scope of WGs to be established</font><font size=2 face="Calibri">
</font>
<li><font size=2 face="sans-serif">Communicate IOAG inputs to CMC and CESG
Chair</font><font size=2 face="Calibri"> </font>
<li><font size=2 face="sans-serif">Support IOAG in preparing IOP meetings
as required</font></ul><font size=2 face="sans-serif"><u><br>
The role of the CESG Chair in support to the CMC Chair is:</u></font><font size=2 face="Calibri">
</font>
<ul>
<li><font size=2 face="sans-serif">Regular participation to IOAG meeting
and telecons</font><font size=2 face="Calibri"> </font>
<li><font size=2 face="sans-serif">Provide regular reports about CCSDS
progress during meetings / telecons</font><font size=2 face="Calibri">
</font>
<li><font size=2 face="sans-serif">Support technical discussions and queries
during meetings / telecons </font>
<li><font size=2 face="sans-serif">Maintain ICPA (IOAG CCSDS Product Agreement)</font><font size=2 face="Calibri">
</font>
<li><font size=2 face="sans-serif">Inject in relevant CCSDS WGs the IOAG
requirements and suggestions </font></ul><font size=2 face="Courier New">This
message and any attachments are intended for the use of the addressee or
addressees only.</font>
<br><font size=2 face="Courier New">The unauthorised disclosure, use, dissemination
or copying (either in whole or in part) of its</font>
<br><font size=2 face="Courier New">content is not permitted.</font>
<br><font size=2 face="Courier New">If you received this message in error,
please notify the sender and delete it from your system.</font>
<br><font size=2 face="Courier New">Emails can be altered and their integrity
cannot be guaranteed by the sender.</font>
<br><font size=2 face="Courier New"> </font>
<br><font size=2 face="Courier New">Please consider the environment before
printing this email.</font>
<br><font size=2 face="Courier New"> </font>
<br>
<br><PRE>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.
</PRE>