<span style=" font-size:10pt;font-family:sans-serif">Dear Peter,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
only one "general" comment to your remark
about changing "</span><span style=" font-size:11pt;font-family:Calibri">scope
of actual edits to a document</span><span style=" font-size:10pt;font-family:sans-serif">"
with respect to the approved CWE Project.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">We all know that
this indeed can happen.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">However I think
that we all agree that such change of scope (unless we talk about "peanuts")
shall be properly controlled with </span>
<br><span style=" font-size:10pt;font-family:sans-serif">1) proper WG consensus
</span>
<br><span style=" font-size:10pt;font-family:sans-serif">2) modification
of the approved CWE Project (when the change is not trivial)</span>
<br><span style=" font-size:10pt;font-family:sans-serif">3) re approval
by CMC (e.g. for changes of resources)</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Of course only
step #1 is always required while steps #2 and #3 depend of the nature of
the added changes.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">IMO ignoring this
(and I think this is not the case for you) would undermine the - already
low - confidence of WGs on CWE.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">However it looks
as we do not need such extreme details in Org&Proc.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Best regards</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Gian Paolo</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">"Shames,
Peter M\(US 312B\) via CESG" <cesg@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">"Margherita.di.Giulio@esa.int"
<Margherita.di.Giulio@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">"Tom
Gannett" <thomas.gannett@tgannett.net>, "CESG -- CCSDS-Engineering
SteeringGroup\(cesg@mailman.ccsds.org\)\(cesg@mailman.ccsds.org\)"
<cesg@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">29-08-20
00:12</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:
[CESG] [EXTERNAL] Fw: [Cesg-all] Results of CMC Polls</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style=" font-size:9pt;font-family:sans-serif">"CESG"
<cesg-bounces@mailman.ccsds.org></span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Dear
Margherita,</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:11pt;font-family:Calibri">I
agree that some sort of modest changes to text could make some similarly
modest changes in clarity. I doubt that it is worth cresting a corrigendum
for just this change, but would agree that these kinds of edits could be
added to a list of similar items and handled all at once. I think
Tom Gannett has such a list, so I have added him to this email reply.</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:11pt;font-family:Calibri">I
would also comment that it is possible that the scope of actual edits to
a document, as opposed to planned edits, can change once the process has
started. It's sort of like a bathroom remodeling project where you
start with just wanting to paint the walls, and maybe changing the
mirror, and you wind up replacing all of the cabinets and tiles too. Or
starting to fix what you think is a minor leak in the plumbing and discovering
that there is now mold growing and you need to rip out the walls to fix
it.</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:11pt;font-family:Calibri">Maybe
those analogies do not work for you, but these things can happen, so I
think some latitude and flexibility is required. But I do not believe
that we need to say all of that in the Org & Proc.</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:11pt;font-family:Calibri">Best
regards, Peter</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:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"><b>From:
</b>"Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int><b><br>
Date: </b>Friday, August 28, 2020 at 8:34 AM<b><br>
To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><b><br>
Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><b><br>
Subject: </b>Re: [EXTERNAL] Fw: [Cesg-all] Results of CMC Polls</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">Dear
Peter,</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:10pt;font-family:Arial"><br>
The comment form Jaxa states:</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><i><br>
Section 6.1.4.4 (Page 6-5) states "…Blue Books are required to be
prototyped before final approval and publication…" Resources
of Prototype 1 and Prototype 2 are "Not required" for this 5-year
review, however, there is no statement in the CCSDS A02.1-Y-4 whether the
prototype tests are required for the New Projects of the 5-year review.
Will the necessity be identified in the course of the review process?</i></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
I agree that the matter is already covered in CCSDS YB, Org & Proc,
however, may be a simple change to the text would avoid misunderstanding
in the future. For instance </span><span style=" font-size:10pt;color:red;font-family:Arial">(in
red)</span><span style=" font-size:10pt;font-family:Arial">:</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;color:blue;font-family:Arial"><br>
6.1.4.4 As a result of this difference
in prescriptive content between Blue and
Magenta books, Blue Books are required
to be prototyped before final approval
and publication, but Magenta Books are not required
to be prototyped. </span><span style=" font-size:10pt;color:red;font-family:Arial">This
applies also to updates of Blue Books, if/when new features are introduced</span><span style=" font-size:10pt;color:blue;font-family:Arial">.</span><span style=" font-size:15pt;font-family:Calibri">
</span><span style=" font-size:11pt;font-family:Calibri"><br>
</span><span style=" font-size:10pt;color:blue;font-family:Arial"><br>
6.2.7.2.1.1 Revisions of published normative documents shall follow
the procedures in 6.2.2 </span><span style=" font-size:10pt;color:red;font-family:Arial">and
6.2.6.</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:10pt;font-family:Arial"><br>
Concerning the question from Jaxa “….<i>Will the necessity be identified
in the course of the review process?”, </i>I think the answer is that
the necessity of prototyping can only be identified at the time the new
project gets established, in that the relevant resources must be identified
– and requested - via project approval. Therefore, this necessity cannot
be identified during the review process.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
Kind regards,<br>
Margherita</span><span style=" font-size:11pt;font-family:Calibri"> <br>
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
--------------------------------------------------------------</span><span style=" font-size:8pt;color:#00a1e0;font-family:Verdana"><b><br>
Margherita di Giulio</b></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><br>
Ground Station Systems Division</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><br>
Backend Software Section (OPS-GSB)</span><span style=" font-size:11pt;font-family:Calibri">
<br>
<br>
</span><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><b><br>
European Space Agency ESA/ESOC</b><br>
Robert-Bosch-Str. 5<br>
D-64293 Darmstadt - Germany<br>
Tel: +49-6151-902779<br>
e-mail: Margherita.di.Giulio@esa.int</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
</span><span style=" font-size:11pt;font-family:Calibri"><br>
<br>
<br>
<br>
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
From: </span><span style=" font-size:9pt;font-family:Arial">"Shames,
Peter M (US 312B)" <peter.m.shames@jpl.nasa.gov></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">"Margherita.di.Giulio@esa.int"
<Margherita.di.Giulio@esa.int></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">"CESG
-- CCSDS-Engineering SteeringGroup(cesg@mailman.ccsds.org)(cesg@mailman.ccsds.org)"
<cesg@mailman.ccsds.org></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">27/08/2020
02:02</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">Re:
[EXTERNAL] Fw: [Cesg-all] Results of CMC Polls</span><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<div align=center>
<hr noshade></div>
<p style="margin-top:0px;margin-Bottom:240px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">Dear
Margherita,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">This
is already covered in the CCSDS YB, org & Proc, under the subject of
"Periodic Review":</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#0082bf;font-family:Calibri"><b><br>
6.2.7 PERIODIC REVIEW <br>
6.2.7.1 General </b><br>
CCSDS documents shall undergo periodic review within the Area no later
than five years after issue and every five years subsequently. Periodic
review shall result in reconfirmation, revision, or retirement to CCSDS
historical status. </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt">If the document
is just reconfirmed then there is no need for a new protoyping effort.
If the document is revised in any significant way, especially is
there are any changes to protocols, behavior, PDUs, data formats, signaling,
then that falls under the "Revisions" clause:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#0082bf;font-family:Calibri"><b><br>
6.2.7.2 Changes to Documents <br>
6.2.7.2.1 Revisions of Normative Documents <br>
6.2.7.2.1.1 </b>Revisions of published normative documents shall follow
the procedures in 6.2.2. <b><br>
6.2.7.2.1.2 </b>The color designation for draft revisions of normative
documents shall be “Pink” (rather than “Red”). <b><br>
6.2.7.2.1.3 </b>In cases where only limited discrete changes are proposed
to a published normative document, only the pages containing substantive
changes (“Pink Sheets”) may be released for review. </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt">The procedures
in sec 6.2.2 are those for normal, normative, document processing, which
include prototyping and generation of a test report. I believe that
this is all clearly enough stated and that no changes to CCSDS A02.1-Y-4
are needed.</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt">Do you concur?</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt">Thanks, Peter</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"><b>From: </b>"Margherita.di.Giulio@esa.int"
<Margherita.di.Giulio@esa.int><b><br>
Date: </b>Wednesday, August 26, 2020 at 7:16 AM<b><br>
To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><b><br>
Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><b><br>
Subject: </b>[EXTERNAL] Fw: [Cesg-all] Results of CMC Polls</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">Dear
Peter,</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:Arial"><br>
the attached notification contains two comments from Jaxa, where
they query about Prototype activities for Blue Books under 5-years review
: the point they make is that CCSDS A02.1-Y-4 does not explicitly mandate
prototype testing for books under 5-years review. Is this need to
be established e.g. during the review process itself ?</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Can you please take a look at the comment ? In case some text needs to
be introduced in CCSDS A02.1-Y-4, can you propose something to CESG
?</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:Arial"><br>
Thank you, kind regards,<br>
Margherita</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
--------------------------------------------------------------</span><span style=" font-size:8pt;color:#00a1e0;font-family:Verdana"><b><br>
Margherita di Giulio</b></span><span style=" font-size:12pt"> </span><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><br>
Ground Station Systems Division</span><span style=" font-size:12pt"> </span><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><br>
Backend Software Section (OPS-GSB)</span><span style=" font-size:12pt">
<br>
</span><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><b><br>
<br>
European Space Agency ESA/ESOC</b><br>
Robert-Bosch-Str. 5<br>
D-64293 Darmstadt - Germany<br>
Tel: +49-6151-902779<br>
e-mail: Margherita.di.Giulio@esa.int</span><span style=" font-size:12pt"><br>
</span><span style=" font-size:9pt;color:#800080;font-family:Arial"><br>
<br>
----- Forwarded by Margherita di Giulio/esoc/ESA on 26/08/2020 15:56 -----</span><span style=" font-size:12pt">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
<br>
From: </span><span style=" font-size:9pt;font-family:Arial">"Stafford
Laura (BTAS)" <Laura.Stafford@btas.com></span><span style=" font-size:12pt">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
To: </span><span style=" font-size:9pt;font-family:Arial">"Blackwood,
Michael D via CMC" <CMC@mailman.ccsds.org></span><span style=" font-size:12pt">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Cc: </span><span style=" font-size:9pt;font-family:Arial">"Blackwood,
Michael D via CESG-All" <cesg-all@mailman.ccsds.org></span><span style=" font-size:12pt">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date: </span><span style=" font-size:9pt;font-family:Arial">25/08/2020
18:19</span><span style=" font-size:12pt"> </span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject: </span><span style=" font-size:9pt;font-family:Arial">[Cesg-all]
Results of CMC Polls</span><span style=" font-size:12pt"> </span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Sent by: </span><span style=" font-size:9pt;font-family:Arial">"CESG-All"
<cesg-all-bounces@mailman.ccsds.org></span><span style=" font-size:12pt">
</span></p>
<div align=center>
<hr noshade></div>
<p style=";margin-Bottom:240px"><span style=" font-size:12pt"><br>
<br>
<br>
CMC E-Poll Identifier: CMC-P-2020-07-002 <br>
Approval of New Projects in the 5.04 Space Link Protocols WG<br>
<br>
Results of CMC poll beginning 7 July 2020 and ending 21 July 2020:<br>
<br>
Adopt: 8 (100%) (CNES, CNSA, CSA, DLR, ESA, INPE, JAXA, NASA)<br>
Adopt Provisionally: 0 (0%)<br>
Reject: 0 (0%)<br>
Reject with Comments: 0 (0%)<br>
<br>
Results are based on responses from 8 out of 11 members (72.72%).<br>
<br>
No response was received from the following Agencies:<br>
<br>
ASI <br>
RFSA <br>
UKSA <br>
<br>
Comments from JAXA: <br>
This comment(/inquiry) is not for this 5-year review Project, but the CCSDS
A02.1-Y-4.<br>
<br>
Section 6.1.4.4 (Page 6-5) states "…Blue Books are required to be
prototyped before final approval and publication…" Resources
of Prototype 1 and Prototype 2 are "Not required" for this 5-year
review, however, there is no statement in the CCSDS A02.1-Y-4 whether the
prototype tests are required for the New Projects of the 5-year review.
Will the necessity be identified in the course of the review process?<br>
<br>
Secretariat Interpretation of Results: Adopted<br>
Resulting CMC Resolution:
CMC-R-2020-08-008<br>
Inferred Secretariat Action:
Approve Project - Done & Working Group Chair address
Comments from JAXA. <br>
<br>
* * * * * * * * * * * * * * * * * * * *<br>
<br>
CMC E-Poll Identifier: CMC-P-2020-07-003 <br>
Approval of New Project in the 5.09 Space Data Link Security WG<br>
<br>
Results of CMC poll beginning 7 July 2020 and ending 21 July 2020:<br>
<br>
Adopt: 8 (100%) (CNES, CNSA, CSA, DLR, ESA, INPE, JAXA, NASA)<br>
Adopt Provisionally: 0 (0%)<br>
Reject: 0 (0%)<br>
Reject with Comments: 0 (0%)<br>
<br>
Results are based on responses from 8 out of 11 members (72.72%).<br>
<br>
No response was received from the following Agencies:<br>
<br>
ASI <br>
RFSA <br>
UKSA <br>
<br>
Comments from JAXA: <br>
This comment(/inquiry) is not for this 5-year review Project, but the CCSDS
A02.1-Y-4.<br>
<br>
Section 6.1.4.4 (Page 6-5) states "…Blue Books are required to be
prototyped before final approval and publication…" Resources
of Prototype 1 and Prototype 2 are "Not required" for this 5-year
review, however, there is no statement in the CCSDS A02.1-Y-4 whether the
prototype tests are required for the New Projects of the 5-year review.
Will the necessity be identified in the course of the review process?<br>
<br>
Secretariat Interpretation of Results: Adopted<br>
Resulting CMC Resolution:
CMC-R-2020-08-009<br>
Inferred Secretariat Action:
Approve Project - Done & Working Group Chair address
Comments from JAXA. <br>
<br>
<br>
* * * * * * * * * * * * * * * * * * * * <br>
CMC E-Poll Identifier: CMC-P-2020-07-004 <br>
CESG Escalation to CMC about Unresolved CESG Poll<br>
<br>
Results of CMC poll beginning 15 July 2020 and ending 29 July 2020:<br>
<br>
Adopt: 8 (100%) (CNES, CNSA, CSA, DLR, ESA, INPE, JAXA, NASA, UKSA)<br>
Adopt Provisionally: 0 (0%)<br>
Reject: 0 (0%)<br>
Reject with Comments: 0 (0%)<br>
<br>
Results are based on responses from 9 out of 11 members (81.81%).<br>
<br>
No response was received from the following Agencies:<br>
<br>
ASI <br>
RFSA <br>
<br>
Comments from ESA: <br>
ESA agree to release the book for Agency Review<br>
<br>
Secretariat Interpretation of Results: Adopted<br>
Resulting CMC Resolution:
CMC-R-2020-08-010<br>
Inferred Secretariat Action:
The Poll conditions raised by the ADs shall be removed, and
the book CCSDS 131.3-P-1.1, shall go ahead to Agency Review. <br>
<br>
* * * * * * * * * * * * * * * * * * * * <br>
<br>
CMC E-Poll Identifier: CMC-P-2020-06-005 <br>
CMC-P-2020-06-005 Charter Modification for the Multispectral Hyperspectral
Data Compression (SLS-MHDC) Working Group<br>
<br>
Results of CMC poll beginning 25 June 2020 and ending 9 July 2020:<br>
<br>
Adopt: 8 (100%) (ASI, CNES, CNSA, CSA, DLR, ESA, INPE, JAXA,)<br>
Adopt Provisionally: 0 (0%)<br>
Reject: 0 (0%)<br>
Reject with Comments: 0 (0%)<br>
<br>
Results are based on responses from 8 out of 11 members (72.72%).<br>
<br>
No response was received from the following Agencies:<br>
<br>
NASA <br>
RFSA <br>
UKSA <br>
<br>
Secretariat Interpretation of Results: Adopted<br>
Resulting CMC Resolution:
CMC-R-2020-08-011<br>
Inferred Secretariat Action:
Approve Charter Once WG Chair Makes Edits - Done <br>
</span></p>
<div align=center>
<hr></div>
<p style=";margin-Bottom:3600px"><span style=" font-size:8pt;color:red;font-family:Arial"><br>
CONFIDENTIALITY NOTICE: </span><span style=" font-size:8pt;color:#5f5f5f;font-family:Arial"><i>The
contents of this e-mail message may be privileged, confidential, or otherwise
protected against disclosure or dissemination. If you are not the intended
recipient of this message, any dissemination, distribution or copying is
strictly prohibited. If you have received this message in error, please
delete all copies from your computer system. </i></span><span style=" font-size:10pt;font-family:Courier New"><br>
_______________________________________________<br>
CESG-All mailing list<br>
CESG-All@mailman.ccsds.org</span><span style=" font-size:12pt;color:blue"><u><br>
</u></span><a href="https://urldefense.us/v3/__https:/mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg-all__;!!PvBDto6Hs4WbVuu7!dJeBXBZ_FfE3ud8YCTVQsvPU4TDjAkQ03Dxpm3VVEALUfHZawp50yxAbjvmP0N8i_19O8T4f$"><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg-all</u></span></a></p>
<p style="\,ð;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-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-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-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 (dpo@esa.int).</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 (dpo@esa.int).</span><tt><span style=" font-size:10pt">_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org<br>
</span></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><tt><span style=" font-size:10pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</span></tt></a><tt><span style=" font-size:10pt"><br>
</span></tt></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>