<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=us-ascii">
<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:Verdana;
panose-1:2 11 6 4 3 5 4 4 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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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;}
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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Georgia",serif;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-compose;
font-family:"Georgia",serif;
color:windowtext;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:1265381470;
mso-list-type:hybrid;
mso-list-template-ids:-2123445970 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Hello Martin (and my apologies for the earlier incorrect spelling),<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">The DDOR WG Chair (Jim Border) and I have had an exchange with regard to the proposed scan pattern for inclusion in the SMURF. Attached please find a proposed scan
pattern format -- a sample XML instance document and a pictorial representation. This is largely based on the pattern you have proposed.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">The differences, elaborated as comments in the XML instance document, are:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p></o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo1">
<span style="font-size:14.0pt;font-family:"Georgia",serif">Removal of the service indication as the DDOR service would already be indicated in the SMURF<o:p></o:p></span></li><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo1">
<span style="font-size:14.0pt;font-family:"Georgia",serif">Removal of the account of scan targets as each target has an ordinal number assigned to it so it is quite trivial to determine the number of targets if that is needed (and less error-prone)<o:p></o:p></span></li><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo1">
<span style="font-size:14.0pt;font-family:"Georgia",serif">addition of a reference to the carrier configuration profile for the spacecraft(s) participating in the DDOR observation (in turn this will indicate the frequency band as well as provide information
for the DOR tones from the spacecraft(s))<o:p></o:p></span></li><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo1">
<span style="font-size:14.0pt;font-family:"Georgia",serif">The absolute start time for the scan pattern has been added -- this will help to verify that the scan pattern time fits with the set of activities scheduled<o:p></o:p></span></li><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo1">
<span style="font-size:14.0pt;font-family:"Georgia",serif">a slew time that can be stated for each target rather than a uniform slew time – this may allow for optimization such that a DDOR measurement that could not be achieved via fixed slew times can be achieved
if the overall amount of time spent slewing is reduced (of course this would be subject to negotiation, but the purpose here is to allow for expression of the information and not to specify behavior)<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">My sense is that we are close to a very good workable format. I look forward to your comments.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b>From:</b> Martin.Unal@esa.int <Martin.Unal@esa.int> <br>
<b>Sent:</b> Wednesday, June 17, 2020 06:29<br>
<b>To:</b> Barkley, Erik J (US 3970) <erik.j.barkley@jpl.nasa.gov><br>
<b>Cc:</b> CCSDS Service Mgmt WG <smwg@mailman.ccsds.org><br>
<b>Subject:</b> RE: [EXTERNAL] Re: [cssm] Fw: DDOR configuration template<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hello<br>
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I will join late the telecon today. I should be able to make it for the DDOR item in your agenda at 17H55 CET.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I have inserted my answer in
</span><i><span style="font-size:14.0pt;font-family:"Georgia",serif;color:purple"> colour</span></i><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> in your text.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">We have been practicing DDOR support for years, internal ESA and cross agency support. implementation. We have a unique sequence of event template, we use standardise file naming convention for the
raw data. It is simple and it works. I am reluctant to the idea of increasing complexity unless their is a benefit.</span>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
</span><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#004080">I see the DOR tones on/off times as part of the event sequence (which references the configuration profile). Also, from local conversation, it appears that name of the raw observation
files matters for processing by the correlators. That could also go in the configuration profile.</span>
<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><i><span style="font-size:14.0pt;font-family:"Georgia",serif;color:purple">- The time pattern is changing frequently for DDOR. If you want to have an event sequence for each, you will have to create one for nearly
each new support. It may be nice at conceptual level, but is a burden in operation. I recommend the approach to have a single DDOR sequence, with durations as parameters.</span></i><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><i><span style="font-size:14.0pt;font-family:"Georgia",serif;color:purple">- The raw observation file name is not part of the request in the recommended practice CCSDS 506.0-M-2. File name of navigation product matters
for processing, but that's covered in the relevant standard books. Does it really make sense to leave freedom to the user to select the file name of the result in a booking request ? The same logic would then applies to all navigation product. Do you consider
leaving a file name entry for ranging, Doppler, meteo and so on... .</span></i><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#004080">I see the scan pattern as being part of the SMURF -- a question I have here is whether or not the scan pattern can be template-a-sized such
that it is always referred to by some sort of identifier. My sense from the DSN side is that this is not the case as the quasar(s) being utilized very depending upon the mission trajectory etc. I think it will be interesting to discuss further on this at the
teleconference tomorrow if you're available.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><i><span style="font-size:14.0pt;font-family:"Georgia",serif;color:purple">- The Quasars to be used change for each DDOR request. In our implementation the Quasar name are anonymized to Q1/Q2/Q3, depending of how
many Quasar are requested in a given support. It is up to the requester to provide the orbital predicts of the real Quasar under the relevant code name.</span></i><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
<br>
Regards<br>
________________________________________<br>
Mar<b><span style="color:red">C</span></b>in UNAL :)<br>
Ground Operation Manager<br>
Ground Facilities Ops HSO - ONO<br>
H-376<br>
ESOC<br>
Robert-Bosch Strasse 5<br>
64 293 Darmstadt<br>
Germany<br>
Tel +49 6151 90 2959 <br>
________________________________________</span><o:p></o:p></p>
<p class="MsoNormal"><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">"Barkley, Erik J (US 3970)" <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</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">"EXTERNAL-Unal, Martin P (9110-Affiliate)" <<a href="mailto:Martin.Unal@esa.int">Martin.Unal@esa.int</a>></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"CCSDS Service Mgmt WG" <<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</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">17/06/2020 00:02</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">RE: [EXTERNAL] Re: [cssm] Fw: DDOR configuration template</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" 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:14.0pt;font-family:"Georgia",serif;color:#004080">Hello Marcin,</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#004080">Here are some quick responses as to how I think this likely fits within the service management.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#004080">I see the DOR tones as being part of the configuration profile.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#004080">I see the DOR tones on/off times as part of the event sequence (which references the configuration profile). Also, from local conversation,
it appears that name of the raw observation files matters for processing by the correlators. That could also go in the configuration profile.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#004080">I see the scan pattern as being part of the SMURF -- a question I have here is whether or not the scan pattern can be template-a-sized such
that it is always referred to by some sort of identifier. My sense from the DSN side is that this is not the case as the quasar(s) being utilized very depending upon the mission trajectory etc. I think it will be interesting to discuss further on this at the
teleconference tomorrow if you're available.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#004080">Best regards,</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#004080">-Erik</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b>From:</b> SMWG <<a href="mailto:smwg-bounces@mailman.ccsds.org">smwg-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b><a href="mailto:Martin.Unal@esa.int">Martin.Unal@esa.int</a><b><br>
Sent:</b> Wednesday, May 27, 2020 01:26<b><br>
To:</b> Barkley, Erik J (US 3970) <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>><b><br>
Cc:</b> CCSDS Service Mgmt WG <<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>><b><br>
Subject:</b> [EXTERNAL] Re: [cssm] Fw: DDOR configuration template<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:10.0pt;font-family:"Arial",sans-serif">Hello</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Here is a version 2 based on yesterday telecon discussion.</span> <span style="font-size:10.0pt;font-family:"Arial",sans-serif">
<br>
I have changed the configuration item names to</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy"> ddor_configuration</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> and
</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy">spacecraft_configuration</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">.</span>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy"><br>
<configuration_profile</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:purple">
</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:teal">service</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:purple">="deltaDor"</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy">></span>
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:olive"><br>
<!-- DDOR configuration element defines which type of DDOR configurarion shall be used to configure the ground station --></span>
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:olive"><br>
<!-- This can be used to select which type of tones to be used, how many DL band,...--></span>
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:olive"><br>
<!-- The attribute and their value will probably be provider specific --></span> <span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy">
<br>
<ddor_configuration</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:purple">
</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:teal">name</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:purple">="DDOR1"</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy">/></span>
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:olive"><br>
<!-- The spacecraft_configuration can be used to convey information relevant for the station configuration on a per DL basis (if needed)--></span>
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:olive"><br>
<!-- To be open to future multi band DDOR, It is suggest to have an dlIndex--></span>
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:olive"><br>
<!-- The attribute and their value will probably be provider specific --></span> <span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy">
<br>
<spacecraft_configuration</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:purple">
</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:teal">dlIndex</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:purple">="1"
</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:teal">band</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:purple">="Xband"
</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:teal">transmitter</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:purple">="1"</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:navy">/></span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
The main part to agree with the DDOR team concern the DDOR parameter. They are not really concerned by the configuration aspect. This is more an issue between the flight control team and the provider.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
I am still not sure where you want to have it in a SMURF request.</span> <span style="font-size:10.0pt;font-family:"Arial",sans-serif">
<br>
Will it be in provider specific parameter ? In the configuration profile (902x05-Simple-conf-profile-Mission-Agrt) ?</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
<br>
Regards<br>
________________________________________<br>
Martin UNAL<br>
Ground Operation Manager<br>
Ground Facilities Ops HSO - ONO<br>
H-376<br>
ESOC<br>
Robert-Bosch Strasse 5<br>
64 293 Darmstadt<br>
Germany<br>
Tel +49 6151 90 2959 <br>
________________________________________</span><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 intended only for the recipient(s) named above. It may contain proprietary information and/or</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Courier New"">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Courier New"">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;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:10.0pt;font-family:"Courier New";color:#0082BF">dpo@esa.int</span></a><span style="font-size:10.0pt;font-family:"Courier New"">).</span><o:p></o:p></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, 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>
</div>
</body>
</html>