<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=utf-8">
<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
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:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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:1528828589;
mso-list-template-ids:1464250760;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:2019387907;
mso-list-template-ids:1627279442;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span class="EmailStyle21">Hi Holger,<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21">I’ve looked over your mods to Slide 3. I think I get the point you are making, but your feedback just brought up other questions. Please take a look at my further notes, on your notes.<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21">Thanks, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">"Holger.Dreihahn@esa.int" <Holger.Dreihahn@esa.int><br>
<b>Date: </b>Monday, February 1, 2021 at 12:46 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>Colin Haddow <Colin.Haddow@esa.int>, Erik Barkley <erik.j.barkley@jpl.nasa.gov>, Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int>, Greg Kazz <greg.j.kazz@jpl.nasa.gov>, "Wilmot, Jonathan J. (GSFC-5820)" <jonathan.j.wilmot@nasa.gov>, Keith Scott
<kscott@mitre.org>, Scott Burleigh <scott.c.burleigh@jpl.nasa.gov>, SEA-SA <sea-sa@mailman.ccsds.org><br>
<b>Subject: </b>Re: [Sea-sa] DRAFT Meeting Minutes, was Re: [EXTERNAL] Special Working Meeting: SCCS-ARD discussion - fwd/ret file service<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hello Peter,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",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.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Best regards,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | H-293<br>
+49 6151 90 2233 | </span><a href="https://urldefense.us/v3/__http:/www.esa.int/esoc__;!!PvBDto6Hs4WbVuu7!aj7XY9QY7vr45vidwI3GbecHC3r2BZsAvAr0hhSUzGimjGCj8sLCPI4jBrAk86HleqMlVFGD$"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">http://www.esa.int/esoc</span></a>
<br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"Shames, Peter M (US 312B)" <peter.m.shames@jpl.nasa.gov></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"Arial",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></span> <br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"SEA-SA" <sea-sa@mailman.ccsds.org></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">21/01/2021 21:24</span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">Re: [Sea-sa] DRAFT Meeting Minutes, was Re: [EXTERNAL] Special Working Meeting: SCCS-ARD discussion
- fwd/ret file service</span> <o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-size:10.0pt">Dear CCSDS ”Special topic” Colleagues,</span> <br>
<span style="font-size:10.0pt"> </span> <br>
<span style="font-size:10.0pt">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.</span>
<br>
<span style="font-size:10.0pt"> </span> <br>
<span style="font-size:10.0pt">Attendees: Keith Scott, Costin Radulescu, Colin Haddow, Ramon Krosley, Greg Kazz, Jonathan Wilmot, Holger Dreihahn, Gian Paolo Calzolari, John Pietras, Yonghui Huang</span>
<br>
<span style="font-size:10.0pt"> </span> <br>
<span style="font-size:10.0pt">The discussion was wide-ranging and covered the following list of possible
<b><u>Options</u></b>:</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">1. </span><span style="font-size:10.0pt">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.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">2. </span><span style="font-size:10.0pt">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.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">3. </span><span style="font-size:10.0pt">There is also an IOAG fwd/ret “Packet” service that was not really discussed.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">4. </span><span style="font-size:10.0pt">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.</span>
<br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:red">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.</span></b> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">5. </span><span style="font-size:10.0pt">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.</span><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:red"> Only CFDP C2.</span></b>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">6. </span><span style="font-size:10.0pt">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.</span>
<br>
<span style="font-size:10.0pt"> </span> <br>
<span style="font-size:10.0pt">There were some items that everyone present could agree upon:</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">1. </span><b><u><span style="font-size:10.0pt">Options</span></u></b><span style="font-size:10.0pt"> 1 and 6 are what is currently documented and standardized.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">2. </span><span style="font-size:10.0pt">Everyone agreed that the desired end-point for CCSDS standardization, and for mission deployment is DTN and CFDP (or other protocols) running over
that.</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">3. </span><span style="font-size:10.0pt">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.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">4. </span><span style="font-size:10.0pt">Everyone agreed that
<b><u>option</u></b> 2, the IOAG proposal is accurately reflected in Colin’s original diagram.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">5. </span><span style="font-size:10.0pt">Everyone agreed that the
<b><u>option</u></b> 2 diagram leaves a lot of room for interpretation.</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">6. </span><span style="font-size:10.0pt">Everyone agreed that we should return to the IOAG and ask for the needed clarification (or provide that and ask if they concur).</span>
<br>
<span style="font-size:10.0pt"> </span> <br>
<span style="font-size:10.0pt">Other <b><u>observations</u></b> where there was general agreement, but possibly not full concurrence (TBD).</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">1. </span><span style="font-size:10.0pt">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.</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">2. </span><span style="font-size:10.0pt">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.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">3. </span><span style="font-size:10.0pt">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.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">4. </span><span style="font-size:10.0pt">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.</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">5. </span><span style="font-size:10.0pt">There is a strong</span><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:red"> NASA</span></b><span style="font-size:10.0pt">
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. </span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">6. </span><span style="font-size:10.0pt">None of these options, except DTN, provides a networking service, all are “hacks”</span><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:red">
shouldn't we change that word?</span></b><span style="font-size:10.0pt"> to provide variations on ABA file delivery.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">7. </span><b><i><span style="font-size:10.0pt">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.</span></i></b>
<br>
<span style="font-size:10.0pt"> </span> <br>
<span style="font-size:10.0pt">Other general observations for further discussion:</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">1. </span><span style="font-size:10.0pt">ESA has prototyped an “<b><u>option</u></b> 4 (&5)” approach for low Earth orbit missions with high rate downlinks.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">2. </span><span style="font-size:10.0pt">The DSN</span><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:red"> and ESA</span></b><span style="font-size:10.0pt"> ha</span><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:red">ve</span></b><span style="font-size:10.0pt">
an operational “<b><u>option</u></b> 4” approach that is documented and in use for some missions.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">3. </span><span style="font-size:10.0pt">Some missions are operating in “<b><u>option</u></b> 1” configurations now, with reliable CFDP for downlink and now some uplink.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">4. </span><span style="font-size:10.0pt">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.</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">5. </span><span style="font-size:10.0pt">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.</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">6. </span><span style="font-size:10.0pt">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 “</span><span style="font-size:12.0pt">to be a very important source of multiagency cross-support requirements</span><span style="font-size:10.0pt">”, but it is not the only one.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">7. </span><span style="font-size:10.0pt">We do not know which missions want any of these options.</span>
<br>
<span style="font-size:10.0pt"> </span> <br>
<span style="font-size:10.0pt">Future work:</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">1. </span><span style="font-size:10.0pt">Provide revised versions of these potential approaches for review</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">2. </span><span style="font-size:10.0pt">Review them within CCSDS and then with the IOAG (TBD)</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">3. </span><span style="font-size:10.0pt">Reach some agreement within CCSDS on what strategic choices we wish to make and which of these approaches, if any, should get CCSDS resources</span>
<br>
<span style="font-size:10.0pt"> </span> <br>
<span style="font-size:10.0pt">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.</span>
<br>
<span style="font-size:10.0pt"> </span> <br>
<span style="font-size:10.0pt">Thanks, Peter</span> <br>
<br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt"> </span> <br>
<b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt">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</span>
<br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">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.
</span> <br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">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).
</span><br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">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. </span>
<br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">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.
</span><br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">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. </span>
<br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">Proposed agenda: </span><br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">CSS Position on the service </span><o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="font-size:12.0pt">ESLT architecture </span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="font-size:12.0pt">CFDP agent integration in the ESLT </span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="font-size:12.0pt">CFDP signaling changes </span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="font-size:12.0pt">Split data delivery approach </span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="font-size:12.0pt">Fwd / ret signaling approach </span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="font-size:12.0pt">ESLT control approach for configuring and managing creation / processing of CFDP, encap, frame creation, encode/decode in the ELST
</span><o:p></o:p></li></ul>
<p class="MsoNormal"><span style="font-size:12.0pt">SIS Position on the service </span>
<o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="font-size:12.0pt">ESLT architecture </span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="font-size:12.0pt">DTN agent integration in the ESLT </span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="font-size:12.0pt">Split data delivery approach </span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="font-size:12.0pt">Fwd / ret signaling approach (if needed) </span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="font-size:12.0pt">ESLT control approach for configuring and managing creation / processing of DTN bundles, encap, frame creation, encode/decode in the ELST
</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="font-size:12.0pt">CFDP end-to-end flow </span><o:p></o:p></li></ul>
<p class="MsoNormal"><span style="font-size:12.0pt">Discussion </span><br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">Thanks, Peter </span><br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt"> </span> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1154" style="width:865.5pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#4F4F4F">Hello, </span>
<o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#4F4F4F">Peter Shames invites you to join this WebEx meeting.
</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p><br>
<span style="font-size:12.0pt;color:white"> </span> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1154" style="width:865.5pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p><span style="color:black"><br>
</span><span style="font-size:12.0pt;color:white"> </span> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="100%" style="width:100.0%;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#4F4F4F">SCCS-ARD discussion - fwd/ret file service</span></b><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#4F4F4F">
</span><o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td style="padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Wednesday, January 20, 2021 </span>
<o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td style="padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">7:00 am | (UTC-08:00) Pacific Time (US & Canada) | 2 hrs </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p><br>
<span style="font-size:12.0pt;color:white"> </span> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="398" style="width:298.5pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="398" style="width:298.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Meeting number (access code): 199 651 5303 </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p><span style="color:black"><br>
</span><span style="font-size:12.0pt;color:white"> </span> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="291" style="width:218.25pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="291" style="width:218.25pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Meeting password: Nm5mpcrZ2r4
</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin-bottom:12.0pt"><br>
<br>
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1154" style="width:865.5pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p><br>
<span style="font-size:12.0pt;color:white"> </span> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="113" style="width:84.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="113" style="width:84.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="113" style="width:84.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="113" style="width:84.75pt;background:#43A942;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" align="center" style="text-align:center"><a href="https://urldefense.us/v3/__https:/jpl.webex.com/jpl/j.php?MTID=mda4b7e12e1b6f08131813d6abe9cbeba__;!!PvBDto6Hs4WbVuu7!aj7XY9QY7vr45vidwI3GbecHC3r2BZsAvAr0hhSUzGimjGCj8sLCPI4jBrAk86HlejHfJOBC$"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:white">Join
meeting</span></a><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">
</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<p><br>
<span style="font-size:12.0pt;color:white"> </span> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1154" style="width:865.5pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"> </span>
<o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Arial",sans-serif">More ways to join:
</span></b><o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Arial",sans-serif">Join from the meeting link
</span></b><o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><a href="https://urldefense.us/v3/__https:/jpl.webex.com/jpl/j.php?MTID=mda4b7e12e1b6f08131813d6abe9cbeba__;!!PvBDto6Hs4WbVuu7!aj7XY9QY7vr45vidwI3GbecHC3r2BZsAvAr0hhSUzGimjGCj8sLCPI4jBrAk86HlejHfJOBC$" target="_blank"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:deepskyblue">https://jpl.webex.com/jpl/j.php?MTID=mda4b7e12e1b6f08131813d6abe9cbeba</span></a><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">
</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p><br>
<span style="font-size:12.0pt;color:white"> </span> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1154" style="width:865.5pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p><br>
<span style="font-size:12.0pt;color:white"> </span> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1154" style="width:865.5pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Arial",sans-serif">Join by phone
</span></b><o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#2F2F2F">+1-510-210-8882 USA Toll
</span><o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#2F2F2F">+44-203-457-5798 U.K. Toll
</span><o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><a href="https://urldefense.us/v3/__https:/jpl.webex.com/jpl/globalcallin.php?MTID=m91ef44b98d71197e079bc4e234fbe055__;!!PvBDto6Hs4WbVuu7!aj7XY9QY7vr45vidwI3GbecHC3r2BZsAvAr0hhSUzGimjGCj8sLCPI4jBrAk86HleuLlExDq$"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:deepskyblue">Global
call-in numbers</span></a><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">
</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p><br>
<span style="font-size:12.0pt;color:white"> </span> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1154" style="width:865.5pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p><br>
<span style="font-size:12.0pt;color:white"> </span> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1154" style="width:865.5pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p><br>
<span style="font-size:12.0pt;color:white"> </span> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1154" style="width:865.5pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Local: 818-35(4-4044)</span></b><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">
</span><o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Toll Free: 844-JPL-WEBX (844-575-9329)</span></b><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">
</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p><br>
<span style="font-size:12.0pt;color:white"> </span> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1154" style="width:865.5pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1154" style="width:865.5pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><br>
<span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Can't join the meeting? </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p><br>
<span style="font-size:12.0pt;color:white"> </span> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1154" style="width:865.5pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p><br>
<span style="font-size:12.0pt;color:white"> </span> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="1154" style="width:865.5pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="1154" style="width:865.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#A2A2A2">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.
</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin-bottom:12.0pt"><br>
<span style="font-size:12.0pt;color:white"> </span> <br>
<span style="font-size:12.0pt">_______________________________________________ SEA-SA mailing list SEA-SA@mailman.ccsds.org
</span><a href="https://urldefense.us/v3/__https:/mailman.ccsds.org/cgi-bin/mailman/listinfo/sea-sa__;!!PvBDto6Hs4WbVuu7!em2PSzY-3YgmNhBZ8GMbajfe4GnHfKMIzo8_su4UM0G_XfgUbH_cn2aT8vyuZnDEboLdxLum$"><span style="font-size:12.0pt">https://urldefense.us/v3/__https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sea-sa__;!!PvBDto6Hs4WbVuu7!em2PSzY-3YgmNhBZ8GMbajfe4GnHfKMIzo8_su4UM0G_XfgUbH_cn2aT8vyuZnDEboLdxLum$</span></a><span style="font-size:12.0pt">
[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]
</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 (dpo@esa.int).<o:p></o:p></pre>
</div>
</body>
</html>