<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:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family: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;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Dear Margherita,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards, Peter<o:p></o:p></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" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">"Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int><br>
<b>Date: </b>Friday, August 28, 2020 at 8:34 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Subject: </b>Re: [EXTERNAL] Fw: [Cesg-all] Results of CMC Polls<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear Peter,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The comment form Jaxa states:</span>
<br>
<i><span style="font-size:10.0pt;font-family:"Arial",sans-serif">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?</span></i>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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 style="color:red">(in red)</span>:</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">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:10.0pt;font-family:"Arial",sans-serif;color:red">This applies also to updates of Blue Books, if/when new features are introduced</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">.</span><span style="font-size:15.0pt">
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">6.2.7.2.1.1 Revisions of published normative documents shall follow the procedures in 6.2.2
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:red">and 6.2.6.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Kind regards,<br>
Margherita</span> <br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">--------------------------------------------------------------<br>
</span><b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#00A1E0">Margherita di Giulio</span></b>
<br>
<span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#5F5F5F">Ground Station Systems Division</span>
<br>
<span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#5F5F5F">Backend Software Section (OPS-GSB)</span>
<br>
<br>
<br>
<b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#5F5F5F">European Space Agency ESA/ESOC</span></b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#5F5F5F"><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:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
<br>
</span><br>
<br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Shames, Peter M (US 312B)" <peter.m.shames@jpl.nasa.gov></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"CESG -- CCSDS-Engineering SteeringGroup(cesg@mailman.ccsds.org)(cesg@mailman.ccsds.org)" <cesg@mailman.ccsds.org></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">27/08/2020 02:02</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Re: [EXTERNAL] Fw: [Cesg-all] Results of CMC Polls</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<o:p> </o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
Dear Margherita,<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
This is already covered in the CCSDS YB, org & Proc, under the subject of "Periodic Review":<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<b><span style="font-size:12.0pt;color:#0082BF">6.2.7 PERIODIC REVIEW </span></b><br>
<b><span style="font-size:12.0pt;color:#0082BF">6.2.7.1 General </span></b><br>
<span style="font-size:12.0pt;color:#0082BF">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><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
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:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<b><span style="font-size:12.0pt;color:#0082BF">6.2.7.2 Changes to Documents </span>
</b><br>
<b><span style="font-size:12.0pt;color:#0082BF">6.2.7.2.1 Revisions of Normative Documents
</span></b><br>
<b><span style="font-size:12.0pt;color:#0082BF">6.2.7.2.1.1 </span></b><span style="font-size:12.0pt;color:#0082BF">Revisions of published normative documents shall follow the procedures in 6.2.2.
</span><br>
<b><span style="font-size:12.0pt;color:#0082BF">6.2.7.2.1.2 </span></b><span style="font-size:12.0pt;color:#0082BF">The color designation for draft revisions of normative documents shall be “Pink” (rather than “Red”).
</span><br>
<b><span style="font-size:12.0pt;color:#0082BF">6.2.7.2.1.3 </span></b><span style="font-size:12.0pt;color:#0082BF">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><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
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.<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
Do you concur?<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
Thanks, Peter<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
<b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt">"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><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear Peter,</span> <span style="font-size:10.0pt;font-family:"Arial",sans-serif">
<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>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><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:10.0pt;font-family:"Arial",sans-serif"><br>
Thank you, kind regards,<br>
Margherita</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
--------------------------------------------------------------</span><b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#00A1E0"><br>
Margherita di Giulio</span></b> <span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#5F5F5F">
<br>
Ground Station Systems Division</span> <span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#5F5F5F">
<br>
Backend Software Section (OPS-GSB)</span> <br>
<br>
<b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#5F5F5F"><br>
European Space Agency ESA/ESOC</span></b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#5F5F5F"><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:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
</span><br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:purple"><br>
----- Forwarded by Margherita di Giulio/esoc/ESA on 26/08/2020 15:56 -----</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Stafford Laura (BTAS)" <Laura.Stafford@btas.com></span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Blackwood, Michael D via CMC" <CMC@mailman.ccsds.org></span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Blackwood, Michael D via CESG-All" <cesg-all@mailman.ccsds.org></span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">25/08/2020 18:19</span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">[Cesg-all] Results of CMC Polls</span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Sent by: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"CESG-All" <cesg-all-bounces@mailman.ccsds.org></span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<br>
<br>
<span style="font-size:12.0pt"><br>
CMC E-Poll Identifier: CMC-P-2020-07-002</span> <span style="font-size:12.0pt"><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</span> <span style="font-size:12.0pt"><br>
RFSA</span> <span style="font-size:12.0pt"><br>
UKSA</span> <br>
<span style="font-size:12.0pt"><br>
Comments from JAXA:</span> <span style="font-size:12.0pt"><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.</span>
<span style="font-size:12.0pt"><br>
<br>
* * * * * * * * * * * * * * * * * * * *<br>
<br>
CMC E-Poll Identifier: CMC-P-2020-07-003</span> <span style="font-size:12.0pt"><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</span> <span style="font-size:12.0pt"><br>
RFSA</span> <span style="font-size:12.0pt"><br>
UKSA</span> <br>
<span style="font-size:12.0pt"><br>
Comments from JAXA:</span> <span style="font-size:12.0pt"><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.</span>
<br>
<br>
<span style="font-size:12.0pt"><br>
* * * * * * * * * * * * * * * * * * * *</span> <span style="font-size:12.0pt"><br>
CMC E-Poll Identifier: CMC-P-2020-07-004</span> <span style="font-size:12.0pt"><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</span> <span style="font-size:12.0pt"><br>
RFSA</span> <br>
<span style="font-size:12.0pt"><br>
Comments from ESA:</span> <span style="font-size:12.0pt"><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.
</span><br>
<span style="font-size:12.0pt"><br>
* * * * * * * * * * * * * * * * * * * *</span> <br>
<span style="font-size:12.0pt"><br>
CMC E-Poll Identifier: CMC-P-2020-06-005</span> <span style="font-size:12.0pt"><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</span> <span style="font-size:12.0pt"><br>
RFSA</span> <span style="font-size:12.0pt"><br>
UKSA</span> <span style="font-size:12.0pt"><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
</span><br>
<br>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="100%" align="center">
</div>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:2.5in;margin-left:.5in">
<span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:red"><br>
CONFIDENTIALITY NOTICE: </span><i><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">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.
</span></i><span style="font-size:10.0pt;font-family:"Courier New""><br>
_______________________________________________<br>
CESG-All mailing list<br>
CESG-All@mailman.ccsds.org</span><u><span style="color:blue"><br>
</span></u><a href="https://urldefense.us/v3/__https:/mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg-all__;!!PvBDto6Hs4WbVuu7!dJeBXBZ_FfE3ud8YCTVQsvPU4TDjAkQ03Dxpm3VVEALUfHZawp50yxAbjvmP0N8i_19O8T4f$"><span style="font-size:10.0pt;font-family:"Courier New"">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg-all</span></a><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
<span style="font-size:10.0pt;font-family:"Courier New"">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
<span style="font-size:10.0pt;font-family:"Courier New"">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
<span style="font-size:10.0pt;font-family:"Courier New"">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in">
<span style="font-size:10.0pt;font-family:"Courier New"">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).</span><o:p></o:p></p>
<pre style="margin-left:.5in">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre style="margin-left:.5in">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre style="margin-left:.5in">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre style="margin-left:.5in">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>