<span style=" font-size:10pt;font-family:sans-serif">Hello<br>
</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Quick answers
to your comment.</span>
<br><span style=" font-size:10pt;font-family:sans-serif"><br>
1) DDOR patterns used operationally ALL follow that pattern:</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Start =  
     BOT + time to execute any previous scan + fixed
time margin to point to the next target.<br>
End =        BOT + time to execute any previous
scan + fixed time margin to point to the next target. + duration of the
scan.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">I can not remember
anything else since ESTRACK has started providing DDOR services for multiple
agency. This pattern is a de-facto standard.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">If someday, someone
as the very unusual need to have target with odd absolute time computation,
he just need to send multiple single target request. Mentioning absolute
time (computed from the formula above). In the past, request template was
written with absolute time, with the only result of producing copy/paste/manual
editing incoherency with no added value.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">What matter for
DDOR is that all stations start/end at the same time. Absolute time is
the outcome of the process, not an input.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Their is no outgoing
station for DDOR. DDOR is DL only.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">2) The receiver_2
refers to the <u>on board receiver</u>. This information drives the which
DL frequency and DDOR tones that will be used for that support. </span>
<br><span style=" font-size:10pt;font-family:sans-serif">I agree that to
be more generic, the element <receiver> could be rename to something
more neutral. e.g <configuration> </span>
<br><span style=" font-size:10pt;font-family:sans-serif">It is safe to
assume that most satellites will have more than one transponder and/or
DDOR tones options.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">3) I assume that
the SMURF already specify the aperture(s) requested.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">My draft cover
only the information which are needed to specify a DDOR support within
a SMURF.</span>
<br><span style=" font-size:10pt;font-family:sans-serif"><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>
<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">"Barkley,
Erik J (US 3970)" <erik.j.barkley@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">"EXTERNAL-Unal,
Martin P (9110-Affiliate)" <Martin.Unal@esa.int></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
       </span><span style=" font-size:9pt;font-family:sans-serif">"CCSDS
Service Mgmt WG" <smwg@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
       </span><span style=" font-size:9pt;font-family:sans-serif">21/05/2020
23:43</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:
[cssm] Fw: DDOR configuration template</span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">Dear
Martin,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">Now
that I finally have a copy of what you sent to Colin, of course, I have
some comments :-)</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">First,
the instance document is not quite proper XML -- at least as Oxygen on
this end looks at it. Please see the screenshot below. Attached is what
I believe to be a properly formed version of the instance document.  </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">To
set the context, as I recall, the basic question was whether or not we
needed to look at another standard or augmentation to the SMURF to accommodate
the interagency ground sequence for conducting a DDOR observation. I think
the answer tends to be yes to the general question here. Presumably the
spacecraft event sequence will cover when DOR tones are on/off but then
of course there is the scan pattern and that has to be coordinated between
multiple agencies. I think the instance you have submitted is a step in
the right direction.  Here are some comments, questions, observations:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<br><span style=" font-size:10pt;font-family:sans-serif">1.    
   </span><span style=" font-size:14pt;color:#004080;font-family:Georgia">It
seems like this is something of a cross between a template and a fully
stated instance. For each of the targets to be in the scan pattern, there
appears to be a presumption that the scan will start at BOT plus the delay.
Is it fair to assume that the DDOR supports for a mission will always fit
this kind of pattern?  I suspect the answer is no and that there are
either multiple patterns.  At a minimum, depending upon whether the
groundstation is the "incoming" groundstation with regard to
communications geometry or the "outgoing" groundstation then
this would probably also have to have something that is stated as the offset
relative to the EOT? Or perhaps we should think about allowing absolute
times to be stated?</span>
<br><span style=" font-size:10pt;font-family:sans-serif">2.    
   </span><span style=" font-size:14pt;color:#004080;font-family:Georgia">Recevier_2
-- this seems like an internal concern to the implementation -- I think
for international standard the main thing would be to have the scan pattern
identified and not which particular (open-loop) receiver is being used.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">3.    
   </span><span style=" font-size:14pt;color:#004080;font-family:Georgia">Given
that DDOR requires a fair amount of interagency coordination and there
are constraints with regard to communication geometries and quasar of visibility,
should there be some sort of provision for indicating the ground stations
involved in this? I'm not sure that this is really needed but then again
it does seem like if we are doing this interagency the data standard has
to allow for being very precise and clear as to the exact apertures being
requested to support the scan pattern -- that of course could be indicated
in the aperture constraints of the SMURF.</span>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">Assuming
you can attend our teleconference on May 26, I look forward to discussing
this further.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">-Erik</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><img src=cid:_4_19A7FDBC19AB6ED4005163E5C1258574 style="border:0px solid;"></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:</b>
SMWG <smwg-bounces@mailman.ccsds.org> <b>On Behalf Of </b>Colin.Haddow@esa.int<b><br>
Sent:</b> Thursday, May 7, 2020 08:18<b><br>
To:</b> smwg@mailman.ccsds.org<b><br>
Subject:</b> [EXTERNAL] [cssm] Fw: DDOR configuration template</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:10pt;font-family:Arial"><br>
<br>
---------------------------------------------------------------------------------------------------------<br>
Dr. Colin R. Haddow,<br>
HSO-GI, European Space Agency,<br>
European Space Operations Centre,<br>
Robert-Bosch-Str 5,<br>
64293 Darmstadt,<br>
Germany.<br>
<br>
Phone; +49 6151 90 2896<br>
Fax;      +49 6151 90 3010<br>
E-Mail;  </span><a href=mailto:colin.haddow@esa.int><span style=" font-size:10pt;color:#0082bf;font-family:Arial"><u>colin.haddow@esa.int</u></span></a><span style=" font-size:10pt;font-family:Arial"><br>
---------------------------------------------------------------------------------------------------------</span><span style=" font-size:11pt;font-family:Calibri"><br>
</span><span style=" font-size:9pt;color:#800080;font-family:Arial"><br>
----- Forwarded by Colin Haddow/esoc/ESA on 07/05/2020 17:17 -----</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
From:        </span><span style=" font-size:9pt;font-family:Arial">Martin
Unal/esoc/ESA</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">Colin
Haddow/esoc/ESA@ESA</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">Holger
Dreihahn/esoc/ESA@ESA</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">06/11/2019
17:24</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">DDOR
configuration template</span><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<div align=center>
<hr noshade></div>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Hello</span><span style=" font-size:11pt;font-family:Calibri"><br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
I have drafted a proposal of xml layout for DDOR support based on our experience
on ESTRACK</span><span style=" font-size:11pt;font-family:Calibri"> <br>
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
This need to be tune to the SMURF, but all the element of information shall
be there.</span><span style=" font-size:11pt;font-family:Calibri"> <br>
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
>From our operational experience, using the formulare in the magenta leave
room to build invalid contradicting entries. <br>
And it did happen many time.</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
This minimum set of value, together with the element contain in the SMURF
request could be used to write the old text format in the magenta book
(see below) to support backward compatibility if needed.</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
For memory</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:10pt;font-family:Arial"><br>
</span><span style=" font-size:12pt;font-family:Times New Roman"><b><br>
C1 EXAMPLE 1</b></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:12pt;font-family:Times New Roman"><b><br>
<Maven-Abbrev>_DDOR_2014_228_2014_250_v2.des</b></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
$ddorGroundObservationsEventSequence</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
RequestId = 2014-205T15:50:00;</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
FormatVersion = 1;</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
orginatingOrganization = DSN;</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
MissionId = <Maven-Abbrev>;</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
$START</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:8pt;font-family:Courier New"><br>
ddorConfigProfileId = 202F2;</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
ScIndex____ScId____DorOn____DorOff =</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
SC01 <Maven-Abbrev> 2014-228T02:25:00 2014-228T03:25:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
;</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:8pt;font-family:Courier New"><br>
QuIndex____QuId____QuFlux =</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
QU01 P_1504-167 0.52</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
;</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:8pt;font-family:Courier New"><br>
TrkStnId____TrackStart____TrackEnd =</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
<Site1>-<Apper1> 2014-228T02:25:00 2014-228T03:25:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
<Site2>-<Apper2> 2014-228T02:25:00 2014-228T03:25:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
<Site3>-<Apper3> 2014-228T02:25:00 2014-228T03:25:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
;</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:8pt;font-family:Courier New"><br>
DdorEpoch = 2014-228T02:25:00;</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
ScanNum____ScanSource____ScanStart____Duration =</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
1 SC01 00:00:00 00:01:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
2 QU01 00:03:00 00:05:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
3 SC01 00:10:00 00:06:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
4 QU01 00:18:00 00:07:30</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
5 SC01 00:27:30 00:06:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
6 QU01 00:35:30 00:07:30</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
7 SC01 00:45:00 00:06:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
8 QU01 00:53:00 00:05:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
;</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:8pt;font-family:Courier New"><br>
$END</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:8pt;font-family:Courier New"><br>
$START</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:8pt;font-family:Courier New"><br>
ddorConfigProfileId = 202F2;</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
ScIndex____ScId____DorOn____DorOff =</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
SC01 <Maven-Abbrev> 2014-250T01:25:00 2014-250T02:25:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
;</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:8pt;font-family:Courier New"><br>
QuIndex____QuId____QuFlux =</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
QU01 P_1519-273 1.12</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
;</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:8pt;font-family:Courier New"><br>
TrkStnId____TrackStart____TrackEnd =</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
<Site1>-<Apper1> 2014-250T01:25:00 2014-250T02:25:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
<Site2>-<Apper2> 2014-250T01:25:00 2014-250T02:25:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
<Site3>-<Apper3> 2014-250T01:25:00 2014-250T02:25:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
;</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:8pt;font-family:Courier New"><br>
DdorEpoch = 2014-250T01:25:00;</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
ScanNum____ScanSource____ScanStart____Duration =</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
1 SC01 00:00:00 00:01:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
2 QU01 00:03:00 00:05:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
3 SC01 00:10:00 00:06:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
4 QU01 00:18:00 00:07:30</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
5 SC01 00:27:30 00:06:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
6 QU01 00:35:30 00:07:30</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
7 SC01 00:45:00 00:06:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
8 QU01 00:53:00 00:05:00</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;font-family:Courier New"><br>
;</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:8pt;font-family:Courier New"><br>
$END</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:8pt;font-family:Courier New"><br>
$$EOF</span><span style=" font-size:10pt;font-family:Arial"><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><span style=" font-size:11pt;font-family:Calibri">
</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 (</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">).[attachment
"DDOR-request-element-eb.xml" deleted by Martin Unal/esoc/ESA]
</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>