<font size=2 face="sans-serif">Dear James,</font>
<br>
<br><font size=2 face="sans-serif">thank you for your commitment to involve
the CESG Chair in all technical discussions.</font>
<br>
<br><font size=2 face="sans-serif">I wish you well in your new role</font>
<br>
<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<br>
Head Ground Systems Engineering Department</font>
<br><font size=2 face="sans-serif">European 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></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>, "Ross, David (HQ-CG000)[Arctic
Slope Technical Services, Inc.]" <david.ross@nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">20/12/2017 16:38</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">Dear Juan,</font>
<br><font size=2 face="Helvetica"> </font>
<br><font size=2 face="Helvetica">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.</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>Juan Miro <Juan.Miro@esa.int><b><br>
Date: </b>Tuesday, December 19, 2017 at 2:00 PM<b><br>
To: </b>James Afarin <james.afarin@nasa.gov><b><br>
Cc: </b>CMC - CCSDS Management Council <cmc@mailman.ccsds.org>, "Ross,
David (HQ-CG000)[Arctic Slope Technical Services, Inc.]" <david.ross@nasa.gov><b><br>
Subject: </b>Re: [CMC] Input for MoM on CCSDS-IOAG interface</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="sans-serif">Dear James,</font><font size=2 face="Calibri">
<br>
</font><font size=2 face="sans-serif"><br>
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<u> regular</u> 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. </font><font size=2 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
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. </font><font size=2 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
It is clear that you are the only CCSDS interface to IOAG, in particular
when it comes to state CCSDS positions.</font><font size=2 face="Calibri">
<br>
</font><font size=2 face="sans-serif"><br>
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.</font><font size=2 face="Calibri"> <br>
</font><font size=2 face="Helvetica"><u><br>
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<u> regular</u> IOAG
meetings and telecons <strike>as required by the CCSDS Liaison.</strike></font><font size=3 face="Calibri">
</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><font size=2 face="Calibri">
</font>
<li><font size=2 face="Calibri"> </font></ul><font size=2 face="sans-serif">Please
let me know</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>
<br>
<br>
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
From: </font><font size=1 face="sans-serif">"Afarin,
James (HQ-CG000)" <james.afarin@nasa.gov></font><font size=2 face="Calibri">
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
To: </font><font size=1 face="sans-serif">"Juan.Miro@esa.int"
<Juan.Miro@esa.int></font><font size=2 face="Calibri"> </font><font size=1 color=#5f5f5f face="sans-serif"><br>
Cc: </font><font size=1 face="sans-serif">CMC
- CCSDS Management Council <cmc@mailman.ccsds.org>, "Ross, David
(HQ-CG000)[Arctic Slope Technical Services, Inc.]" <david.ross@nasa.gov></font><font size=2 face="Calibri">
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
Date: </font><font size=1 face="sans-serif">06/12/2017
19:48</font><font size=2 face="Calibri"> </font><font size=1 color=#5f5f5f face="sans-serif"><br>
Subject: </font><font size=1 face="sans-serif">Re:
[CMC] Input for MoM on CCSDS-IOAG interface</font><font size=2 face="Calibri">
</font>
<div align=center>
<hr noshade></div>
<br><font size=2 face="Calibri"><br>
<br>
</font><font size=2 face="Calibri"><br>
Dear Juan,</font><font size=2 face="Calibri"> </font><font size=2 face="Calibri"><br>
</font><font size=2 face="Calibri"> </font><font size=2 face="Calibri"><br>
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. </font><font size=2 face="Calibri">
<br>
</font><font size=2 face="Calibri"><br>
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.</font><font size=2 face="Calibri"> </font>
<p><font size=3 face="Calibri"><br>
Thank you</font><font size=2 face="Calibri"> <br>
</font><font size=3 face="Calibri"><br>
James</font><font size=2 face="Calibri"> <br>
</font><font size=3 face="Calibri"><br>
James Afarin <br>
SCaN Standard Manager</font><font size=2 face="Calibri"> </font><font size=3 face="Calibri"><br>
Office: (202) 358-5221</font><font size=2 face="Calibri"> </font><font size=3 face="Calibri"><br>
Mobile: (202) 549-6496</font><font size=2 face="Calibri"> <br>
</font><font size=3 face="Calibri"><br>
Sent from my iPhone</font><font size=2 face="Calibri"> </font><font size=3 face="Calibri"><br>
<br>
On Nov 29, 2017, at 6:26 AM, "</font><a href=mailto:Juan.Miro@esa.int><font size=3 color=blue face="Calibri"><u>Juan.Miro@esa.int</u></font></a><font size=3 face="Calibri">"
<</font><a href=mailto:Juan.Miro@esa.int><font size=3 color=blue face="Calibri"><u>Juan.Miro@esa.int</u></font></a><font size=3 face="Calibri">>
wrote:</font><font size=2 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
Dear James,</font><font size=3 face="Calibri"> </font><font size=2 face="sans-serif"><br>
<br>
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><font size=3 face="Calibri">
</font><font size=2 face="sans-serif"><br>
<br>
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><font size=3 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
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><font size=3 face="Calibri">
</font><font size=2 face="sans-serif"><br>
<br>
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><font size=3 face="Calibri">
</font><font size=2 face="sans-serif"><br>
<br>
peoposed text:</font><font size=3 face="Calibri"> </font><font size=2 face="Helvetica"><u><br>
<br>
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><font size=3 face="Calibri">
</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="sans-serif"><br>
Regards</font><font size=3 face="Calibri"> </font><font size=2 face="sans-serif"><br>
Juan</font><font size=3 face="Calibri"> </font><font size=2 face="sans-serif"><br>
<br>
Juan Miro</font><font size=3 face="Calibri"> </font><font size=2 face="sans-serif"><br>
ESA delegate in the CCSCS Management Council<br>
Head Ground Systems Engineering Department</font><font size=3 face="Calibri">
</font><font size=2 face="sans-serif"><br>
Europan Space Operations Centre<br>
European Space Agency</font><font size=3 face="Calibri"> <br>
<br>
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
<br>
From: </font><font size=1 face="sans-serif">"Afarin,
James (HQ-CG000)" <</font><a href=mailto:james.afarin@nasa.gov><font size=1 color=blue face="sans-serif"><u>james.afarin@nasa.gov</u></font></a><font size=1 face="sans-serif">></font><font size=3 face="Calibri">
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
To: </font><font size=1 face="sans-serif">"</font><a href=mailto:Juan.Miro@esa.int><font size=1 color=blue face="sans-serif"><u>Juan.Miro@esa.int</u></font></a><font size=1 face="sans-serif">"
<</font><a href=mailto:Juan.Miro@esa.int><font size=1 color=blue face="sans-serif"><u>Juan.Miro@esa.int</u></font></a><font size=1 face="sans-serif">>,
"Ross, David (HQ-CG000)[Arctic Slope Technical Services, Inc.]"
<</font><a href=mailto:david.ross@nasa.gov><font size=1 color=blue face="sans-serif"><u>david.ross@nasa.gov</u></font></a><font size=1 face="sans-serif">></font><font size=3 face="Calibri">
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
Cc: </font><font size=1 face="sans-serif">CMC
- CCSDS Management Council <</font><a href=mailto:cmc@mailman.ccsds.org><font size=1 color=blue face="sans-serif"><u>cmc@mailman.ccsds.org</u></font></a><font size=1 face="sans-serif">></font><font size=3 face="Calibri">
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
Date: </font><font size=1 face="sans-serif">21/11/2017
14:41</font><font size=3 face="Calibri"> </font><font size=1 color=#5f5f5f face="sans-serif"><br>
Subject: </font><font size=1 face="sans-serif">Re:
[CMC] Input for MoM on CCSDS-IOAG interface</font><font size=3 face="Calibri">
</font>
<div align=center>
<hr noshade></div>
<br><font size=3 face="Calibri"><br>
</font><font size=2 face="Helvetica"><br>
<br>
Hi Juan,</font><font size=3 face="Calibri"> <br>
</font><font size=2 face="Helvetica"><br>
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><font size=3 face="Calibri">
<br>
<br>
<br>
</font><font size=2 face="Helvetica"><u><br>
The CCSDS liaison with IOAG is the CMC Chair and covers the following main
responsibilities:</u> </font><font size=3 face="Calibri"><br>
</font><font size=2 face="Calibri"> </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><font size=3 face="Calibri">
</font><font size=2 face="Helvetica"><u><br>
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><font size=3 face="Calibri">
</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><font size=3 face="Calibri">
<br>
</font><font size=2 face="Helvetica"><br>
Thank you,</font><font size=3 face="Calibri"> <br>
</font><font size=2 face="Helvetica"><br>
James</font><font size=3 face="Calibri"> <br>
</font><font size=2 face="Helvetica"><br>
Dr. James Afarin <br>
<br>
Space Data Standards Manager <br>
Space Communications and Navigation Division<br>
Office: 202-358-5221 <br>
Mobile: 202-549-6496</font><font size=3 face="Calibri"> <br>
<b><br>
From: </b>CMC <</font><a href="mailto:cmc-bounces@mailman.ccsds.org"><font size=3 color=blue face="Calibri"><u>cmc-bounces@mailman.ccsds.org</u></font></a><font size=3 face="Calibri">>
on behalf of Juan Miro <</font><a href=mailto:Juan.Miro@esa.int><font size=3 color=blue face="Calibri"><u>Juan.Miro@esa.int</u></font></a><font size=3 face="Calibri">><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.]"
<</font><a href=mailto:david.ross@nasa.gov><font size=3 color=blue face="Calibri"><u>david.ross@nasa.gov</u></font></a><font size=3 face="Calibri">><b><br>
Cc: </b>CMC - CCSDS Management Council <</font><a href=mailto:cmc@mailman.ccsds.org><font size=3 color=blue face="Calibri"><u>cmc@mailman.ccsds.org</u></font></a><font size=3 face="Calibri">><b><br>
Subject: </b>[CMC] Input for MoM on CCSDS-IOAG interface <br>
</font><font size=2 face="sans-serif"><br>
Dear David,</font><font size=2 face="Calibri"> </font><font size=2 face="sans-serif"><br>
<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">
</font><font size=2 face="sans-serif"><br>
<br>
Regards</font><font size=2 face="Calibri"> </font><font size=2 face="sans-serif"><br>
Juan</font><font size=2 face="Calibri"> </font><font size=2 face="sans-serif"><br>
<br>
_________________________________________________________________________</font><font size=2 face="Calibri">
</font><font size=2 face="sans-serif"><b><u><br>
<br>
CCSDS Liaison to IAOG</u></b></font><font size=2 face="Calibri"> </font><font size=2 face="sans-serif"><u><br>
<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><font size=3 face="Calibri"> </font><font size=2 face="Courier New"><br>
The unauthorised disclosure, use, dissemination or copying (either in whole
or in part) of its</font><font size=3 face="Calibri"> </font><font size=2 face="Courier New"><br>
content is not permitted.</font><font size=3 face="Calibri"> </font><font size=2 face="Courier New"><br>
If you received this message in error, please notify the sender and delete
it from your system.</font><font size=3 face="Calibri"> </font><font size=2 face="Courier New"><br>
Emails can be altered and their integrity cannot be guaranteed by the sender.</font><font size=3 face="Calibri">
<br>
</font><font size=2 face="Courier New"><br>
Please consider the environment before printing this email.</font><font size=3 face="Calibri">
<br>
</font><font size=2 face="Calibri"><br>
</font><font size=3 face="Courier New"><br>
This message and any attachments are intended for the use of the addressee
or addressees only.<br>
The unauthorised disclosure, use, dissemination or copying (either in whole
or in part) of its<br>
content is not permitted.<br>
If you received this message in error, please notify the sender and delete
it from your system.<br>
Emails can be altered and their integrity cannot be guaranteed by the sender.<br>
<br>
Please consider the environment before printing this email.<br>
<br>
</font>
<br><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>