<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-7">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Georgia",serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">CESG Chairs,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">I will be on leave during the teleconference in early September, so I am sending an email to note a concern that I have.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">I am concerned about the exchange listed below between our OMG and CCSDS liaisons, particularly with statements that appear to have been issued as the CCSDS liaison without consultation
of at least CESG not to mention CMC. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">There may in fact be issues between MOIMS SM+C WG and OMG SDTF. But CCSDS is not just MOIMS SM+C. My experience is that I have found OMG GEMS standard to be quite complimentary
to the work of the CSS Area and therefore have found the liaison with OMG to be useful. To me it is objectionable for the CCSDS liaison to question the usefulness of the liaison prior to consulting with the rest of CCSDS. From the email exchange it sounds
like OMG provided due process relative to its rules and governance. As such it can be argued that a strategy session inside CCSDS should have occurred to assess the situation, provide an analysis of alternatives and consider other courses of action. For
example, perhaps CCSDS could have considered the opportunities brought forward by their RFC process rather than unilaterally (without any consultation at the level of CESG as far as I can tell), calling the liaison into question. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">For the record, I will note that we (CESG) have indeed been asked to comment and review on an analysis prepared by DLR with regard to the CCSDS MOIMS and OMG SDTF. This is as it
should be. But I want to emphasize this should have occurred prior to any further exchange in the name of liaison for the all of CCSDS.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">-Erik
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> CESG <cesg-bounces@mailman.ccsds.org>
<b>On Behalf Of </b>Mario.Merri@esa.int<br>
<b>Sent:</b> Thursday, June 28, 2018 1:27 AM<br>
<b>To:</b> Steve MacLaird <maclaird@omg.org><br>
<b>Cc:</b> cesg@mailman.ccsds.org; Larry L. Johnson <larry@omg.org>; danford.s.smith@nasa.gov; space@omg.org; liaison@omg.org; sam@brightascension.com<br>
<b>Subject:</b> Re: [CESG] FW: CCSDS-OMG Liaison: Satellite Command & Control Message Specification (C2MS)<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">Dear Steve,</span>
<br>
<br>
<span style="font-family:"Arial",sans-serif">it is very disappointing that the OMG, after a strenuous discussion of 1.25 hours on my 10 line email, has decided to move forward without waiting for the analysis in the Technical Note that was announced and is
under finalisation. The motivation adduced for the decision, i.e. that "the consensus of the Space DTF and OMG AB that the note below was your position ...", is offensive and reductionist: I deliberatively did not participate in the WG discussion to avoid
influencing. The outcome of the discussion in the WG, which I reported in my email, is that 3 space agencies out of 4 that are active in the WG, i.e. 75%, had identified notable overlaps: it is not my opinion!
</span><br>
<br>
<span style="font-family:"Arial",sans-serif">Thanks for the offer to provide/clarify the OMG’s P&Ps and processes, but there is no need. I will consult with the CCSDS Engineering Steering Group and question the usefulness of a technical liaison between OMG
and CCSDS in these conditions</span> <br>
<br>
<span style="font-family:"Arial",sans-serif">I will still provide you with the technical note, once available. Please note that the technical note is also a collective work supported by the same 3 agencies and it is not even led by ESA.</span>
<br>
<br>
<span style="font-family:"Arial",sans-serif">Regards,</span> <br>
<br>
<span style="font-family:"Arial",sans-serif">__Mario</span> <br>
<br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Steve MacLaird" <<a href="mailto:maclaird@omg.org">maclaird@omg.org</a>></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif"><<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">22/06/2018 15:35</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">FW: CCSDS-OMG Liaison: Satellite Command & Control Message Specification (C2MS)</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue">Mario –
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue"> I rec’d a bounce back that you did not receive the below email despite the same address.
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:18.0pt;font-family:"Arial",sans-serif;color:red">Steve</span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:#0041C2">Steven A. MacLaird, Col (Ret), USAF</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:#0041C2">Senior Vice President, Gov't & Industry Strategy</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:9.0pt;color:#0041C2">+1 703.231.6335 (USA)</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><img border="0" width="246" height="93" style="width:2.5625in;height:.9687in" id="_x0000_i1026" src="cid:image001.png@01D43574.1DD34310" alt="cid:image001.png@01D3CBF6.CB5D0260"><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> Steve MacLaird [</span><a href="mailto:maclaird@omg.org"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">mailto:maclaird@omg.org</span></a><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">]
<b><br>
Sent:</b> Friday, June 22, 2018 9:22 AM<b><br>
To:</b> 'Mario.Merri@esa.int '<b><br>
Cc:</b> 'Larry Johnson'; 'Kizzort, Brad'; 'Luis Rodriquez'; 'Dan Smith'; 'sam@brightascension.com'; 'cesg@mailman.ccsds.org'; 'Juergen Boldt'<b><br>
Subject:</b> FW: CCSDS-OMG Liaison: Satellite Command & Control Message Specification (C2MS)</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue">Mario –
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue"> I wanted to be the first to notify you of the results of the Object Management Group’s (OMG) Space Domain Task Force (DTF) and Architecture Board (AB) decisions.
Your note created a great deal of conversation, dialog and debate, since receipt while here in Boston at OMG’s Quarterly Technical Committee (TC). </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue"> Two days ago during the Space DTF, they spent an hour discussing your email to determine whether or not to forward onto the AB for vote. The pro’s and con’s were
discussed with the largest concern being if the AB accepted the concerns in your email below and sided with you, the
</span><span style="font-size:11.0pt">MCMS <span style="color:blue">RFC would be dead and never allowed to become an RFP. Therefore the Space DTF’s decision to vote to send to the AB would be very risky and all avenues and scenarios possible were discussed.
In the end, the MCMS RFC was voted to move to the AB. Please note, on Monday June 18<sup>th</sup>, I sent your email below to the AB for their review per the AB Chairman’s request even though it was sent to me versus the formal process and being 7 days late
to the 4 week rule. This allowed all the AB members to review all the documentation before meeting yesterday afternoon and discussed it at the AB Plenary on the 18<sup>th</sup>.</span></span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue"> Today during the AB, they had a lengthy and painful discussion that lasted 1.25 hours on MCMS and your email. Per OMG’s Policies and Procedures (P&P) your email
was reviewed, discussed, debated and alternatives explored. I want to let you know, that in 1.5 hours preceding the MCMS discussion, 4 RFCs and 2 RFPs were reviewed. A motion was made and seconded, discussion followed, amendment made on intellectual property,
and voted on. Before the vote, a dissenting opinion was raised and explored/discussed when a AB Member called the question for vote. Eight (8) votes were for the motion, one (1) against and 1 abstained and the motioned passed to approve the MCMS RFC. </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue"> I, the Space DTF, and OMG value your, ESA’s and CCSDS’s inputs and would like to have a closer collaboration throughout OMG’s and CCSDS processes. It was the
consensus of the Space DTF and OMG AB that the note below was your position and possibly that of ESA’s. Your email was the only note of contention received. If I need to clarify OMG’s P&Ps and processes, I can provide and or put you in touch with the right
contacts to answer your, ESA, CNES or DLA’s questions. Our next meeting will be in September in Ottawa Canada. You can find out more at
</span><a href="http://www.omg.org/"><span style="font-size:11.0pt">www.omg.org</span></a><span style="font-size:11.0pt;color:blue">. </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue">Take Care -
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:18.0pt;font-family:"Arial",sans-serif;color:red">Steve</span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:#0041C2">Steven A. MacLaird, Col (Ret), USAF</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:#0041C2">Senior Vice President, Gov't & Industry Strategy</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:9.0pt;color:#0041C2">+1 703.231.6335 (USA)</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:blue"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><img border="0" width="246" height="93" style="width:2.5625in;height:.9687in" id="_x0000_i1027" src="cid:image001.png@01D43574.1DD34310" alt="cid:image001.png@01D3CBF6.CB5D0260"><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">
</span><a href="mailto:Mario.Merri@esa.int"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Mario.Merri@esa.int</span></a><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> [</span><a href="mailto:Mario.Merri@esa.int"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">mailto:Mario.Merri@esa.int</span></a><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">]
<b><br>
Sent:</b> Thursday, May 24, 2018 4:54 AM<b><br>
To:</b> Steven A. MacLaird<b><br>
Cc:</b> </span><a href="mailto:liaison@omg.org"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">liaison@omg.org</span></a><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">; Larry L. Johnson;
</span><a href="mailto:space@omg.org"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">space@omg.org</span></a><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">;
</span><a href="mailto:danford.s.smith@nasa.gov"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">danford.s.smith@nasa.gov</span></a><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">;
</span><a href="mailto:sam@brightascension.com"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">sam@brightascension.com</span></a><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">;
</span><a href="mailto:cesg@mailman.ccsds.org"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">cesg@mailman.ccsds.org</span></a><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"><br>
Subject:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> CCSDS-OMG Liaison: Satellite Command & Control Message Specification (C2MS)</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial",sans-serif">Dear Steve,</span>
<br>
<span style="font-family:"Arial",sans-serif"><br>
in the context of the CCSDS-OMG liaison I would like to inform you that during the last CCSDS Technical Meetings in Gaithersburg (09-13 April 2018) reservations had been raised on the proposed OMG standard (RFC):</span>
<br>
<b><span style="font-family:"Arial",sans-serif"><br>
Satellite Command & Control Message Specification (C2MS).</span></b> <br>
<span style="font-family:"Arial",sans-serif"><br>
In particular, three space agencies via their members in the CCSDS Spacecraft & Control Working Group have identified notable overlaps between the above perspective document and the on-going work of the working group on Mission Operations (MO) Services. These
Space Agencies (CNES - French Space Agency, DLR - German Space Agency, and ESA - European Space Agency) are producing a Technical Note to substantiate the overlap, which will be available in the second half of June.
</span><br>
<span style="font-family:"Arial",sans-serif"><br>
Clearly, in the spirit of the liaison, both CCSDS and OMG should strive to avoid overlaps and duplications, in favour of reciprocally adopting relevant standards, as already done for instance by the CCSDS with the adoption of the OMG XTCE standard.</span>
<br>
<span style="font-family:"Arial",sans-serif"><br>
Sincerely,</span> <br>
<b><span style="font-family:"Arial",sans-serif"><br>
Mario Merri</span></b> <span style="font-family:"Arial",sans-serif"><br>
CCSDS liaison to OMG</span> <br>
<b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ</span></b> <b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
ESA – European Space Agency</span></b> <br>
<b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#00A1E0"><br>
Dr. Mario MERRI</span></b> <span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray">
<br>
Head of Mission Data Systems Division (OPS-GD)</span> <br>
<span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
Directorate of Operations</span> <b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
European Space Operations Centre - ESOC</span></b> <span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray">
<br>
Robert-Bosch-Str. 5, D-64293 Darmstadt, Germany</span> <span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray">
<br>
Tel +49 (6151) 90 2292 | </span><a href="mailto:Mario.Merri@esa.int"><span style="font-size:8.0pt;font-family:"Verdana",sans-serif">Mario.Merri@esa.int</span></a><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"> </span><span style="font-size:8.0pt;font-family:Symbol;color:gray">|</span><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray">
</span><a href="www.esa.int/esoc"><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray">www.esa.int/esoc</span></a>
<b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ</span></b> <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Courier New"">This message is sent for information and/or discussion purposes only.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Courier New"">It shall neither be binding nor construed as constituting a commitment for ESA.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Courier New"">It is intended only for the recipient(s) named above.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Courier New"">It may contain proprietary information and/or protected content.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Courier New"">Any unauthorised disclosure, use, retention or dissemination is prohibited.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Courier New"">If you have received this e-mail in error, please notify the sender immediately.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Courier New"">ESA applies appropriate organisational measures to protect personal data.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Courier New"">In case of data privacy queries, please contact the ESA Data Protection Officer (</span><a href="mailto:dpo@esa.int"><span style="font-size:10.0pt;font-family:"Courier New"">dpo@esa.int</span></a><span style="font-size:10.0pt;font-family:"Courier New"">).</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Courier New""> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Courier New"">Thank you.</span><o:p></o:p></p>
<pre>This message is sent for information and/or discussion purposes only.<o:p></o:p></pre>
<pre>It shall neither be binding nor construed as constituting a commitment for ESA.<o:p></o:p></pre>
<pre>It is intended only for the recipient(s) named above.<o:p></o:p></pre>
<pre>It may contain proprietary information and/or protected content.<o:p></o:p></pre>
<pre>Any unauthorised disclosure, use, retention or dissemination is prohibited.<o:p></o:p></pre>
<pre>If you have received this e-mail in error, please notify the sender immediately.<o:p></o:p></pre>
<pre>ESA applies appropriate organisational measures to protect personal data.<o:p></o:p></pre>
<pre>In case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thank you.<o:p></o:p></pre>
</div>
</body>
</html>