<span style=" font-size:12pt;font-family:Arial">Dear Peter,</span>
<br>
<br><span style=" font-size:12pt;font-family:Arial">following yesterday
CESG webex and for the sake of clarity, I would like to report on the conclusions
of the discussion on the email below that was caused by some misunderstanding
of yours:</span>
<br>
<br><span style=" font-size:12pt;font-family:Arial">1. It was confirmed
that I received an action from the CESG to request the production of the
TN. This is documented in the approved CESG MoM of Gaithersburg.</span>
<br>
<br><span style=" font-size:12pt;font-family:Arial">2. I have NOT distributed
the TN to the OMG, but only to the SM&C WG and to the CESG requesting
comments by 31Aug (no comment received). Margherita forwarded the TN to
the CMC for information.</span>
<br>
<br><span style=" font-size:12pt;font-family:Arial">This clarifies the
matter. What is still unresolved are: </span>
<br>
<br><span style=" font-size:12pt;font-family:Arial">1. the non-consensus
within the SM&C WG</span>
<br>
<br><span style=" font-size:12pt;font-family:Arial">2. the fact that OMG
has ignored the head up for potential overlapping.</span>
<br>
<br><span style=" font-size:12pt;font-family:Arial">The agreed way forward
will be reported in the CESG Webex MoM.</span>
<br>
<br><span style=" font-size:12pt;font-family:Arial">Regards,</span>
<br>
<br><span style=" font-size:12pt;font-family:Arial">__Mario</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
       </span><span style=" font-size:9pt;font-family:sans-serif">"Shames,
Peter M (312B)" <Peter.M.Shames@jpl.nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
       </span><span style=" font-size:9pt;font-family:sans-serif">"Mario.Merri@esa.int"
<Mario.Merri@esa.int>, "Smith, Danford S. (GSFC-5800)"
<danford.s.smith@nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
       </span><span style=" font-size:9pt;font-family:sans-serif">"brigitte.behal@cnes.fr"
<brigitte.behal@cnes.fr>, "Barkley, Erik J (3970)" <Erik.J.Barkley@jpl.nasa.gov>,
"Afarin, James (HQ-CG000)" <james.afarin@nasa.gov>, Sam
Cooper <sam@brightascension.com>, CESG <cesg-bounces@mailman.ccsds.org>,
"Michael.McKay@esa.int" <Michael.McKay@esa.int></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
       </span><span style=" font-size:9pt;font-family:sans-serif">04/09/2018
22:02</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
       </span><span style=" font-size:9pt;font-family:sans-serif">Re:
[Moims-sc] CCSDS-OMG Liaison: Satellite Command & Control Message Specification
(C2MS)</span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Dear
Mario,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">It's
strange, but different people seem to have quite different memories of
what happened during that CESG meeting.  My notes, written during
the meeting, say this:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#ff1f10;font-family:Calibri"><b><i>Mario
raises issue of “overlap” between the SM&C MAL and the new OMG C2MS
(GMSEC), suggests an analysis paper is needed.  Discussed in CESG,
but no explicit request for resolution or vote in support.  Mario
just says “I’m doing this."</i></b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">So,
according to my notes, and my own recollections, there was no "request
by the CESG" that you do this.  Nor was there even a voice vote
or raising of the hands to indicate that the CESG was in agreement.  You
did not ask for this, you just announced that you were doing it.  This
is not behavior that is consistent with how we normally carry out our business,
and I really must object to you trying to re-write history to suggest otherwise.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">The
fact that you subsequently went ahead and sent this to the OMG with a statement
that it was a CCSDS position is also behavior that is out of the norm.
 There was no CESG nor CCSDS agreement to take this position, this
was your fabrication.  If that biased position paper had been submitted
to OMG as an agency, or even multi-agency, position that would be fine.
 But describing it as a CCDS position, and proposing that we break
our liaison relationship with OMG because you did not like their handling
of this, is also outside the norm of how we do business.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">So
in this case I would say that many of the issues having to do with faults
in "</span><span style=" font-size:12pt;font-family:Arial">nominally
agreed processes between CCSDS and OMG for identifying and openly discussing
overlapping standards" </span><span style=" font-size:11pt;font-family:Calibri">must
lie at your doorstep and cannot be blamed on the OMG.  Nor is it accurate
to state that this was a result of a CESG request or concensus.  It
was not.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Regards,
Peter</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"><b>From:
</b>Mario Merri <Mario.Merri@esa.int><b><br>
Date: </b>Tuesday, September 4, 2018 at 12:32 AM<b><br>
To: </b>Dan Smith <danford.s.smith@nasa.gov><b><br>
Cc: </b>Brigitte Behal <brigitte.behal@cnes.fr>, Erik Barkley <Erik.J.Barkley@jpl.nasa.gov>,
James Afarin <james.afarin@nasa.gov>, Peter Shames <Peter.M.Shames@jpl.nasa.gov>,
Sam Cooper <sam@brightascension.com>, CESG <cesg-bounces@mailman.ccsds.org>,
Michael McKay <Michael.McKay@esa.int><b><br>
Subject: </b>RE: [Moims-sc] CCSDS-OMG Liaison: Satellite Command &
Control Message Specification (C2MS)</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Arial">Dear
Dan,</span><span style=" font-size:11pt;font-family:Calibri"> <br>
</span><span style=" font-size:12pt;font-family:Arial"><br>
I recall that this technical note had been requested by the CESG at the
last meeting in Gaithersburg after my presentation of the report prepared
by the SM&C WG that indicated that 3 agencies believed that, after
the WG discussion that took place at the last technical meeting, there
is a substantial overlapping between work of the WG and the C2MS proposal
submission to OMG. This is clearly an indication of non-consensus in the
WG which needs to be explicitly raised to the CESG for resolution. As you
correctly pointed out, any agency can decide to use whatever system they
prefer, but here we are discussing standards and in this occasion the nominally
agreed processes between CCSDS and OMG for identifying and openly discussing
overlapping standards have not worked.</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:12pt;font-family:Arial"><br>
Regards,</span><span style=" font-size:11pt;font-family:Calibri"> <br>
</span><span style=" font-size:12pt;font-family:Arial"><br>
__Mario</span><span style=" font-size:11pt;font-family:Calibri"> <br>
<br>
<br>
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
From:        </span><span style=" font-size:9pt;font-family:Arial">"Smith,
Danford S. (GSFC-5800)" <danford.s.smith@nasa.gov></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
To:        </span><span style=" font-size:9pt;font-family:Arial">"Mario.Merri@esa.int"
<Mario.Merri@esa.int></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Cc:        </span><span style=" font-size:9pt;font-family:Arial">"brigitte.behal@cnes.fr"
<brigitte.behal@cnes.fr>, Sam Cooper <sam@brightascension.com>,
"Afarin, James (HQ-CG000)" <james.afarin@nasa.gov>, "Shames,
Peter M (JPL-312B)[Jet Propulsion Laboratory]" <peter.m.shames@jpl.nasa.gov>,
"Barkley, Erik J (JPL-3970)[Jet Propulsion Laboratory]" <erik.j.barkley@jpl.nasa.gov>,
"Smith, Danford S. (GSFC-5800)" <danford.s.smith@nasa.gov></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date:        </span><span style=" font-size:9pt;font-family:Arial">28/08/2018
14:29</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject:        </span><span style=" font-size:9pt;font-family:Arial">RE:
[Moims-sc] CCSDS-OMG Liaison: Satellite Command & Control Message  
     Specification (C2MS)</span><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<div align=center>
<hr noshade></div>
<p style="margin-top:0px;margin-Bottom:240px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman">Mario,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman">I
think it is important that every space agency ground system group stay
up to date on what is going on in their industry, so I am glad to see that
CNES and DLR have compared MO and C2MS.  Other than a courtesy between
agencies, I don’t see why the report needs to be shared within agencies
and clearly, there is no reason we should give it to the OMG.   Each
agency can make its own determination of the merits of different approaches
and the validity of claims made in different reports and their own studies.
 Although I disagree with how the report was written, its characterization
of capabilities and limitations of different systems, and the overall tone,
it is not my place to critique work performed outside of the CCSDS WG that
I chair unless it is becoming part of a CCSDS position or will be delivered
on behalf of CCSDS – neither of which should occur in this case.  If
CNES or DLR or ESA wanted correct or clarifying information on C2MS or
on GMSEC, they could have contacted either the OMG or NASA, and neither
was done.  It was not clear that the whitepaper was making any recommendations
regarding the OMG and it is clearly outside of the OMG policies for submitting
comments in a timely manner, so I suggest that the paper be distributed
between agencies at the discretion of the authors and then the action (if
there was one) can be closed.</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman">I
have submitted a more technical and process-oriented response to the NASA
CESG members to support discussions on the topic at the next CESG meeting.</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman">Dan</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt;color:#004080"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt;color:#004080"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:9pt;color:#004080"><b>=========================</b></span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt;color:#004080"><b><i>Dan
Smith</i></b></span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:9pt;color:#004080"><b>NASA/GSFC</b></span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:9pt;color:#004080"><b>Code
580</b></span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:9pt;color:#004080"><b>Bldg
23, Room E443</b></span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:9pt;color:#004080"><b>8800
Greenbelt Road</b></span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:9pt;color:#004080"><b>Greenbelt,
MD  20771</b></span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:9pt;color:#004080"><b>301-286-2230</b></span></p>
<p style=";margin-Bottom:0px"><a href=mailto:Dan.Smith@nasa.gov><span style=" font-size:9pt;color:#0082bf"><b><u>Dan.Smith@nasa.gov</u></b></span></a></p>
<p style="¼(♥ó(♥Ó,Å;margin-Bottom:0px"><span style=" font-size:9pt;color:#004080"><b> </b></span></p>
<p style="¼(♥ó(♥Ó,Å;margin-Bottom:0px"><span style=" font-size:9pt;color:#004080"><b><i>Believe
the science.  There are no “alternative facts”.</i></b></span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt;color:#004080"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"><b>From:</b>
MOIMS-SC [</span><a href="mailto:moims-sc-bounces@mailman.ccsds.org"><span style=" font-size:12pt;color:blue"><u>mailto:moims-sc-bounces@mailman.ccsds.org</u></span></a><span style=" font-size:12pt">]
<b>On Behalf Of </b>Mario.Merri@esa.int<b><br>
Sent:</b> Wednesday, August 01, 2018 3:56 AM<b><br>
To:</b> moims-sc@mailman.ccsds.org<b><br>
Subject:</b> [Moims-sc] CCSDS-OMG Liaison: Satellite Command & Control
Message Specification (C2MS)</span></p>
<p style="¼(♥ó(♥Ó,Å;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="¼(♥ó(♥Ó,Å;margin-Bottom:3600px"><span style=" font-size:12pt;font-family:Arial">Dear
SM&C WG,</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:12pt;font-family:Arial"><br>
<br>
As per CESG Action Item from the Gaithersburg meeting, please find enclosed
the Technical Note describing the overlap between the CCSDS MO Services
and the OMG (proposed) C2MS. The TN has been produced by the active members
of the SM&C WG (except for NASA) under DLR leadership and it is fully
supported by CNES and ESA. The TN has been distributed to the CESG. Since
it relates to the SM&C WG, we would like to share it also with the
WG. Please provide any comment you may have before 31Aug18.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:12pt;font-family:Arial"><br>
<br>
Best regards,</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:12pt;font-family:Arial"><br>
<br>
Brigitte & Mario</span><span style=" font-size:12pt;font-family:Times New Roman">
</span></p>
<p style="▄,Å;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">This
message is intended only for the recipient(s) named above. It may contain
proprietary information and/or</span></p>
<p style="▄,Å;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">protected
content. Any unauthorised disclosure, use, retention or dissemination is
prohibited. If you have received</span></p>
<p style="▄,Å;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">this
e-mail in error, please notify the sender immediately. ESA applies appropriate
organisational measures to protect</span></p>
<p style="▄,Å;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">personal
data, in case of data privacy queries, please contact the ESA Data Protection
Officer (</span><a href=mailto:dpo@esa.int><span style=" font-size:10pt;color:#0082bf;font-family:Courier New"><u>dpo@esa.int</u></span></a><span style=" font-size:10pt;font-family:Courier New">).</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">This
message is intended only for the recipient(s) named above. It may contain
proprietary information and/or</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">protected
content. Any unauthorised disclosure, use, retention or dissemination is
prohibited. If you have received</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">this
e-mail in error, please notify the sender immediately. ESA applies appropriate
organisational measures to protect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">personal
data, in case of data privacy queries, please contact the ESA Data Protection
Officer (dpo@esa.int).</span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p><PRE>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@esa.int).
</PRE>