<font size=2 face="sans-serif">Hello Peter,</font>
<br><font size=2 face="sans-serif">I bit late but some comments. I think
for my Slide 3 we did not convey the intended message, please have a look.</font>
<br>
<br><font size=2 face="sans-serif">Best regards,</font>
<br><font size=2 face="sans-serif">Holger</font>
<br>
<br><font size=2 face="sans-serif">Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | H-293<br>
+49 6151 90 2233 | </font><a href=http://www.esa.int/esoc><font size=2 face="sans-serif">http://www.esa.int/esoc</font></a>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Shames, Peter
M (US 312B)" <peter.m.shames@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"Barkley, Erik
J (US 3970)" <erik.j.barkley@jpl.nasa.gov>, "Gian Paolo
Calzolari" <Gian.Paolo.Calzolari@esa.int>, "Kazz, Greg
J (US 312B)" <greg.j.kazz@jpl.nasa.gov>, "Wilmot, Jonathan
J. (GSFC-5820)" <jonathan.j.wilmot@nasa.gov>, "Keith Scott"
<kscott@mitre.org>, "Burleigh, Scott C (US 312B)" <scott.c.burleigh@jpl.nasa.gov>,
"Colin Haddow" <Colin.Haddow@esa.int>, "Holger.Dreihahn@esa.int"
<Holger.Dreihahn@esa.int></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"SEA-SA"
<sea-sa@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">21/01/2021 21:24</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [Sea-sa]
DRAFT Meeting Minutes, was Re: [EXTERNAL] Special Working Meeting: SCCS-ARD
discussion - fwd/ret file service</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Calibri">Dear CCSDS ”Special topic” Colleagues,</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Today we held a special Working Meeting
to discuss some issues that came up in the context of the SCCS-ARD, specifically
the forward / return file service and how we can understand (and document)
both what was requested of CCSDS by the IOAG and what has currently been
proposed. What follows are the <b><i>DRAFT</i></b> set of
minutes for that meeting. Your feedback, edits, and corrections are
solicited. By CoB, Friday, 22 Jan 21 please.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Attendees: Keith Scott, Costin Radulescu,
Colin Haddow, Ramon Krosley, Greg Kazz, Jonathan Wilmot, Holger Dreihahn,
Gian Paolo Calzolari, John Pietras, Yonghui Huang</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">The discussion was wide-ranging and covered
the following list of possible <b><u>Options</u></b>:</font>
<br><font size=2 face="sans-serif">1. </font><font size=2 face="Calibri">CFDP
deployed end-to-end, as intended in the CFDP standard, where the CFDP entity
is in the MOC and the MOC communicates with the ESLT using standard SLE
interfaces. The S/C implements CFDP Class 1 or 2. This is an
existing, documented, standardized, CCSDS deployment.</font>
<br><font size=2 face="sans-serif">2. </font><font size=2 face="Calibri">The
“original” IOAG proposal for a forward/return file service that involved
transferring files from the User (EUN, MOC) to the ESLT ( ground station
/ comm complex) and having the ESLT send them via a CFDP entity in the
ESLT to the S/C (SUN). The general agreement is that there are many
aspects of this that are vague and ill-specified. The S/C implements
CFDP Class 1 or 2. See Colin’s diagram. The intent in CCSDS
has been to use TGFT for the file transport between the user MOC and the
ESLT. There is not yet a spec for the TGFT meta-data nor for the
ESLT processing that is required.</font>
<br><font size=2 face="sans-serif">3. </font><font size=2 face="Calibri">There
is also an IOAG fwd/ret “Packet” service that was not really discussed.</font>
<br><font size=2 face="sans-serif">4. </font><font size=2 face="Calibri">A
variant of “standard” CFDP, option 1, as proposed by ESA only for <u>downlink</u>
optimization, that deploys CFDP in the MOC (EUN), and potentially in a
separate MOC “control node”, that uses standard SLE interfaces for transport
of command and telemetry frames, but that also adds a new CFDP buffering
and management feature in the ESLT that examines arriving frames, looks
for the CFDP PDUs in the selected virtual channels, identified missing
PDUs, send notices of the missing data to the “CFDP Control node” which
generates retransmission requests, and send the full CFDP PDU set, more
slowly, to the full CFDP node in the MOC. The S/C implements CFDP
Class 1 or 2. See Holger’s diagram.</font>
<br><font size=2 color=red face="sans-serif"><b>I think that is not what
we intended to describe. For the Purpose of donwlink only the ESLT has
a CFDP entity reconstructing the files. The MOC just 'relays' the CFDP
PDUs sent from the to ESLT. See updated sled 3.</b></font>
<br><font size=2 face="sans-serif">5. </font><font size=2 face="Calibri">A
variant of the “ESA downlink optimizer”, option 4, that also supports
downlink returns from low Earth S/C using multiple ESLTs and aggregates
and synchronizes all of the data in the “full CFDP node” in the MOC.
There appears to be even another variant of this for the use case
where the file data is sent not to the S/C MOC but to a separate instrument
MOC. The S/C implements CFDP Class 1 or 2. See Holger’s diagram,
with mods.</font><font size=2 color=red face="sans-serif"><b> Only CFDP
C2.</b></font>
<br><font size=2 face="sans-serif">6. </font><font size=2 face="Calibri">The
DTN case, using CFDP Class 1 or Class 2 over DTN to provide all of the
end-to-end reliability, routing, store & forward, and data delivery
processing. The S/C implements CFDP Class 1 or 2 over DTN. The ESLT
implements DTN (with the FF-CSTS and frame merging options) and the MOC
implement CFDP Class 1 or 2 over DTN. This is an existing, documented,
standardized, CCSDS deployment.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">There were some items that everyone present
could agree upon:</font>
<br><font size=2 face="sans-serif">1. </font><font size=2 face="Calibri"><b><u>Options</u></b>
1 and 6 are what is currently documented and standardized.</font>
<br><font size=2 face="sans-serif">2. </font><font size=2 face="Calibri">Everyone
agreed that the desired end-point for CCSDS standardization, and for mission
deployment is DTN and CFDP (or other protocols) running over that.</font>
<br><font size=2 face="sans-serif">3. </font><font size=2 face="Calibri">Everyone
agreed that for DTN deployments there will still need to be what was called
“essential command, telemetry, and radiometric” communications, that
these would continue to use SLE & CSTS for cross support, and that
the new, not yet standardized, Last Hop and First Hop services are an essential
part of these deployments.</font>
<br><font size=2 face="sans-serif">4. </font><font size=2 face="Calibri">Everyone
agreed that <b><u>option</u></b> 2, the IOAG proposal is accurately reflected
in Colin’s original diagram.</font>
<br><font size=2 face="sans-serif">5. </font><font size=2 face="Calibri">Everyone
agreed that the <b><u>option</u></b> 2 diagram leaves a lot of room for
interpretation.</font>
<br><font size=2 face="sans-serif">6. </font><font size=2 face="Calibri">Everyone
agreed that we should return to the IOAG and ask for the needed clarification
(or provide that and ask if they concur).</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Other <b><u>observations</u></b> where
there was general agreement, but possibly not full concurrence (TBD).</font>
<br><font size=2 face="sans-serif">1. </font><font size=2 face="Calibri">It
has been noted that many missions (MOC) still want to control, at a micro
level, everything that is sent on the command link to their spacecraft.
This means that <b><u>option</u></b> 1 can be acceptable, but that
<b><u>option</u></b> 2 often gets “push-back”. And this is one
of the strong motivations for <b><u>options</u></b> 4 & 5.</font>
<br><font size=2 face="sans-serif">2. </font><font size=2 face="Calibri">There
is general agreement that there are many aspects of <b><u>option</u></b>
2 that are vague and ill-specified. It seems clear that the fwd/ret
file service, the meta-data, and the ESLT processing functions must be
more clearly specified.</font>
<br><font size=2 face="sans-serif">3. </font><font size=2 face="Calibri">There
is general agreement that some sort of more explicit concept diagrams,
such as were provided for the IOAG SISG first hop/last hop service, are
needed to really document, even conceptually, what is required for any
of these new services.</font>
<br><font size=2 face="sans-serif">4. </font><font size=2 face="Calibri">There
is a broad understanding that for a class of low Earth missions, with short
passes, and limited terrestrial bandwidth relative to high rate downlinks,
that ACK/NAK traffic should be prioritized relative to bulk data. This,
and mission control of the uplink (<b><u>observation</u></b> 1) leads to
the motivations for <b><u>options</u></b> 4 & 5.</font>
<br><font size=2 face="sans-serif">5. </font><font size=2 face="Calibri">There
is a strong</font><font size=2 color=red face="sans-serif"><b> NASA</b></font><font size=2 face="Calibri">
concern that having CCSDS adopt and standardize any of these more exotic
“CFDP variants” or “file services” may have the effect of de-legitimizing
DTN in the eyes of potential users and of further slowing adoption of DTN.
</font>
<br><font size=2 face="sans-serif">6. </font><font size=2 face="Calibri">None
of these options, except DTN, provides a networking service, all are “hacks”</font><font size=2 color=red face="sans-serif"><b>
shouldn't we change that word?</b></font><font size=2 face="Calibri"> to
provide variations on ABA file delivery.</font>
<br><font size=2 face="sans-serif">7. </font><font size=2 face="Calibri"><b><i>NOTE:
It occurs to me that, in addition to protocol stacks, one way to
approach any of this functional specification is to attempt to use
a Functional Resource Model (FRM) style approach to document which functions
are executed and where they are deployed. This should also help flush
out any new, required, functions that are not yet specified in the FRM.</i></b></font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Other general observations for further
discussion:</font>
<br><font size=2 face="sans-serif">1. </font><font size=2 face="Calibri">ESA
has prototyped an “<b><u>option</u></b> 4 (&5)” approach for low
Earth orbit missions with high rate downlinks.</font>
<br><font size=2 face="sans-serif">2. </font><font size=2 face="Calibri">The
DSN</font><font size=2 color=red face="sans-serif"><b> and ESA</b></font><font size=2 face="Calibri">
ha</font><font size=2 color=red face="sans-serif"><b>ve</b></font><font size=2 face="Calibri">
an operational “<b><u>option</u></b> 4” approach that is documented and
in use for some missions.</font>
<br><font size=2 face="sans-serif">3. </font><font size=2 face="Calibri">Some
missions are operating in “<b><u>option</u></b> 1” configurations now,
with reliable CFDP for downlink and now some uplink.</font>
<br><font size=2 face="sans-serif">4. </font><font size=2 face="Calibri">The
ESA approach, and the DSN approach for that matter, could each be documented
as Orange Books. These still involve a lot of the CCSDS machinery
and may not be the best strategic choice for CCSDS to adopt.</font>
<br><font size=2 face="sans-serif">5. </font><font size=2 face="Calibri">Even
the IOAG requested <b><u>Option</u></b> 2 is questionable, for the same
reasons. Developing this new protocol takes resources and there may
not actually be users for it given <b><u>Observation</u></b> 1 & 2.</font>
<br><font size=2 face="sans-serif">6. </font><font size=2 face="Calibri">The
IOAG is not really <b><i>the</i></b> source of requirements for CCSDS.
It is one of the stakeholders, which also include broader agency
requirements, space missions, infrastructure providers, space data
user organizations, and CCSDS internally generated requirements. The
IOAG is stated to be “</font><font size=3>to be a very important source
of multiagency cross-support requirements</font><font size=2 face="Calibri">”,
but it is not the only one.</font>
<br><font size=2 face="sans-serif">7. </font><font size=2 face="Calibri">We
do not know which missions want any of these options.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Future work:</font>
<br><font size=2 face="sans-serif">1. </font><font size=2 face="Calibri">Provide
revised versions of these potential approaches for review</font>
<br><font size=2 face="sans-serif">2. </font><font size=2 face="Calibri">Review
them within CCSDS and then with the IOAG (TBD)</font>
<br><font size=2 face="sans-serif">3. </font><font size=2 face="Calibri">Reach
some agreement within CCSDS on what strategic choices we wish to make and
which of these approaches, if any, should get CCSDS resources</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Once I have your feedback items I’ll incorporate
them and send out a final set of minutes to the rest of the invitees and
the full CESG.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Thanks, Peter</font>
<br>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri"><b>From: </b>SEA-SA <sea-sa-bounces@mailman.ccsds.org>
on behalf of SEA-SA <sea-sa@mailman.ccsds.org><b><br>
Reply-To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><b><br>
Date: </b>Tuesday, January 12, 2021 at 5:33 PM<b><br>
To: </b>Erik Barkley <erik.j.barkley@jpl.nasa.gov>, Gian Paolo Calzolari
<Gian.Paolo.Calzolari@esa.int>, Gilles Moury <Gilles.Moury@cnes.fr>,
Greg Kazz <greg.j.kazz@jpl.nasa.gov>, "Wilmot, Jonathan J. (GSFC-5820)"
<jonathan.j.wilmot@nasa.gov>, Klaus-Juergen Schulz <Klaus-Juergen.Schulz@esa.int>,
Keith Scott <kscott@mitre.org>, Marc Sanchez Net <marc.sanchez.net@jpl.nasa.gov>,
"Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int>,
Scott Burleigh <scott.c.burleigh@jpl.nasa.gov>, SEA-SA <sea-sa@mailman.ccsds.org><b><br>
Subject: </b>[EXTERNAL] [Sea-sa] Special Working Meeting: SCCS-ARD discussion
- fwd/ret file service</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">This special working meeting is to explore
a set of issues that have just some up in the process of tackling the updates
to the Space Communication Cross Support (SCCS) Architecture documents
(ARD / ADD), the SCCS-ARD, CCSDS 901.1-M-1. </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">Missions may use (and ESLTs may implement)
a forward and return “file service”, that uses TGFT to transfer files
from the EUN to the ESLT, along with a CFDP “agent” in the ESLT that
does the actual file delivery transfer, using CFDP, over the space link
to the Space User Node (SUN, otherwise known as the spacecraft). </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">This is some sort of “cross support protocol”
that belongs in the CSS Area, whether it is in the CSTS WG or the SM WG.
That said, it may also require some sort of “control report” interface
to be spliced into the CFDP protocol agent to allow the EUN to be signaled
about intermediate CFDP protocol status, along with some sort of “control
interface” that will allow the CFDP agent, in the ESLT, to be controlled
from the EUN. And there also must be some means for the EUN to tell the
CFDP agent in the ESLT just how to turn that file into CFDP PDUs, link
layer PDUs, encapsulate them, and how to merge them into the uplink traffic
flow. </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">There is some real work to be done if we
are to create a Forward / Return File Service spec that it truly interoperable
and has all these special, and unusual, properties. There is also the related
question of whether this rather narrow standard is a good use of CCSDS
resources instead of adopting CFDP over DTN, which has broader applicability
and already would provide the same functionality, and much more. </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">We do not think we can do this in the SEA
SAWG, this is work that must be done in the other Areas that “own” the
respective sets of standards. At the same time we see some potential for
leveraging work in different areas and integrating it to provide a more
unified end-to-end approach, and that is our express goal as we try to
help sort this out. </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">Proposed agenda: </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">CSS Position on the service </font>
<ul>
<li><font size=3 face="Calibri">ESLT architecture </font>
<li><font size=3 face="Calibri">CFDP agent integration in the ESLT </font>
<li><font size=3 face="Calibri">CFDP signaling changes </font>
<li><font size=3 face="Calibri">Split data delivery approach </font>
<li><font size=3 face="Calibri">Fwd / ret signaling approach </font>
<li><font size=3 face="Calibri">ESLT control approach for configuring and
managing creation / processing of CFDP, encap, frame creation, encode/decode
in the ELST </font></ul><font size=3 face="Calibri">SIS Position on the
service </font>
<ul>
<li><font size=3 face="Calibri">ESLT architecture </font>
<li><font size=3 face="Calibri">DTN agent integration in the ESLT </font>
<li><font size=3 face="Calibri">Split data delivery approach </font>
<li><font size=3 face="Calibri">Fwd / ret signaling approach (if needed)
</font>
<li><font size=3 face="Calibri">ESLT control approach for configuring and
managing creation / processing of DTN bundles, encap, frame creation, encode/decode
in the ELST </font>
<li><font size=3 face="Calibri">CFDP end-to-end flow </font></ul><font size=3 face="Calibri">Discussion
</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">Thanks, Peter </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri"> </font>
<p>
<table width=1154 style="border-collapse:collapse;">
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#4f4f4f face="Arial">Hello,
</font>
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#4f4f4f face="Arial">Peter
Shames invites you to join this WebEx meeting. </font></table>
<br><font size=3 color=white face="Calibri"> </font>
<p>
<table width=1154 style="border-collapse:collapse;">
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#5f5f5f face="Arial"> </font></table>
<br><font size=3 color=white face="Calibri"> </font>
<p>
<table width=100% style="border-collapse:collapse;">
<tr height=8>
<td width=100% style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#4f4f4f face="Arial"><b>SCCS-ARD
discussion - fwd/ret file service</b> </font>
<tr height=8>
<td style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#5f5f5f face="Arial">Wednesday,
January 20, 2021 </font>
<tr height=8>
<td style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#5f5f5f face="Arial">7:00
am | (UTC-08:00) Pacific Time (US & Canada) | 2 hrs </font></table>
<br><font size=3 color=white face="Calibri"> </font>
<p>
<table width=398 style="border-collapse:collapse;">
<tr height=8>
<td width=398 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#5f5f5f face="Arial">Meeting
number (access code): 199 651 5303 </font></table>
<br><font size=3 color=white face="Calibri"> </font>
<p>
<table width=291 style="border-collapse:collapse;">
<tr height=8>
<td width=291 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#5f5f5f face="Arial">Meeting
password: Nm5mpcrZ2r4 </font></table>
<br><font size=3 color=#5f5f5f face="Arial"><br>
</font><font size=3 face="Calibri"><br>
</font>
<p>
<table width=1154 style="border-collapse:collapse;">
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#5f5f5f face="Arial"> </font></table>
<br><font size=3 color=white face="Calibri"> </font>
<p>
<table width=113 style="border-collapse:collapse;">
<tr height=8>
<td width=113 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;">
<table width=113 style="border-collapse:collapse;">
<tr height=8>
<td width=113 bgcolor=#43a942 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;">
<div align=center><a href="https://jpl.webex.com/jpl/j.php?MTID=mda4b7e12e1b6f08131813d6abe9cbeba"><font size=3 color=white face="Arial">Join
meeting</font></a><font size=3 color=#5f5f5f face="Arial"> </font></div></table>
<br></table>
<br><font size=3 color=white face="Calibri"> </font>
<p>
<table width=1154 style="border-collapse:collapse;">
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#5f5f5f face="Arial"> </font>
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 face="Arial"><b>More
ways to join: </b></font>
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 face="Arial"><b>Join
from the meeting link </b></font>
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><a href="https://jpl.webex.com/jpl/j.php?MTID=mda4b7e12e1b6f08131813d6abe9cbeba" target=_blank><font size=3 color=#00bfff face="Arial">https://jpl.webex.com/jpl/j.php?MTID=mda4b7e12e1b6f08131813d6abe9cbeba</font></a><font size=3 color=#5f5f5f face="Arial">
</font></table>
<br><font size=3 color=white face="Calibri"> </font>
<p>
<table width=1154 style="border-collapse:collapse;">
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#5f5f5f face="Arial"> </font></table>
<br><font size=3 color=white face="Calibri"> </font>
<p>
<table width=1154 style="border-collapse:collapse;">
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 face="Arial"><b>Join
by phone </b></font>
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#2f2f2f face="Arial">+1-510-210-8882
USA Toll </font>
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#2f2f2f face="Arial">+44-203-457-5798
U.K. Toll </font>
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><a href="https://jpl.webex.com/jpl/globalcallin.php?MTID=m91ef44b98d71197e079bc4e234fbe055"><font size=3 color=#00bfff face="Arial">Global
call-in numbers</font></a><font size=3 color=#5f5f5f face="Arial"> </font></table>
<br><font size=3 color=white face="Calibri"> </font>
<p>
<table width=1154 style="border-collapse:collapse;">
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#5f5f5f face="Arial"> </font></table>
<br><font size=3 color=white face="Calibri"> </font>
<p>
<table width=1154 style="border-collapse:collapse;">
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#5f5f5f face="Arial"> </font></table>
<br><font size=3 color=white face="Calibri"> </font>
<p>
<table width=1154 style="border-collapse:collapse;">
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#5f5f5f face="Arial"><b>Local:
818-35(4-4044)</b> </font>
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#5f5f5f face="Arial"><b>Toll
Free: 844-JPL-WEBX (844-575-9329)</b> </font></table>
<br><font size=3 color=white face="Calibri"> </font>
<p>
<table width=1154 style="border-collapse:collapse;">
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;">
<table width=1154 style="border-collapse:collapse;">
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#5f5f5f face="Arial"> </font></table>
<br><font size=3 color=#5f5f5f face="Arial">Can't join the meeting? </font></table>
<br><font size=3 color=white face="Calibri"> </font>
<p>
<table width=1154 style="border-collapse:collapse;">
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#5f5f5f face="Arial"> </font></table>
<br><font size=3 color=white face="Calibri"> </font>
<p>
<table width=1154 style="border-collapse:collapse;">
<tr height=8>
<td width=1154 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=3 color=#a2a2a2 face="Arial">IMPORTANT
NOTICE: Please note that this Webex service allows audio and other information
sent during the session to be recorded, which may be discoverable in a
legal matter. By joining this session, you automatically consent to such
recordings. If you do not consent to being recorded, discuss your concerns
with the host or do not join the session. </font></table>
<br><font size=3 color=white face="Calibri"> </font>
<br><font size=3 face="Calibri">_______________________________________________
SEA-SA mailing list SEA-SA@mailman.ccsds.org </font><a href="https://urldefense.us/v3/__https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sea-sa__;!!PvBDto6Hs4WbVuu7!em2PSzY-3YgmNhBZ8GMbajfe4GnHfKMIzo8_su4UM0G_XfgUbH_cn2aT8vyuZnDEboLdxLum$"><font size=3 face="Calibri">https://urldefense.us/v3/__https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sea-sa__;!!PvBDto6Hs4WbVuu7!em2PSzY-3YgmNhBZ8GMbajfe4GnHfKMIzo8_su4UM0G_XfgUbH_cn2aT8vyuZnDEboLdxLum$</font></a><font size=3 face="Calibri">
[attachment "Dreihahn 922x4r1-white 20Jan21-SEA.pptx" deleted
by Holger Dreihahn/esoc/ESA] [attachment "Haddow IOAG File Services
20Jan21-SEA.pptx" deleted by Holger Dreihahn/esoc/ESA] </font>
<br>
<br>
<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>