<span style=" font-size:10pt;font-family:sans-serif">Dear Peter,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">perhaps it was
not clear from my e-mail, but I have no intention to delay the Polls ,
by no means.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">I just wanted
to start a reflection on the production process of the "administrative"
Yellow Books. The aim being, to provide a formal framework to review, or
to contribute to the creation of, the Yellow Books. Presently, this is
entire responsibility of the book editor, formally speaking</span>
<br><span style=" font-size:10pt;font-family:sans-serif">All the above
applies to the production of future books <i>only</i>. Hope this clarifies.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Kind regards,<br>
Margherita</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">--------------------------------------------------------------<br>
</span><span style=" font-size:8pt;color:#00a1e0;font-family:Verdana"><b>Margherita
di Giulio</b></span>
<br><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana">Ground
Station Systems Division</span>
<br><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana">Backend
Software Section (OPS-GSB)</span>
<br>
<br>
<br><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><b>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:sans-serif"><br>
<br>
</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"Shames,
Peter M (US 312B)" <peter.m.shames@jpl.nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">"Margherita.di.Giulio@esa.int"
<Margherita.di.Giulio@esa.int>, "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">12/02/2020
17:35</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:
[EXTERNAL] [CESG] Fw: [Cesg-all] New CESG Polls</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
must admit to being a little puzzled by your comments, but I agree that
this is worthy of discussion. That said, I really do not want to
see these edits to the Yellow Books significantly delayed because they
are intended to clarify procedures for the WG and to remove ambiguities.
The longer we delay cleaning this up the more work we make for the
WG and the CESG.</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">in
the CCSDS Org & Proc doc, A02x1y4c2, the process for this sort of Administrative
Track document that is normative upon CCSDS is quite clear:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<br><span style=" font-size:12pt;color:#0082bf"><b>6.1.6 ADMINISTRATIVE
TRACK </b></span>
<br><span style=" font-size:12pt;color:#0082bf">The Administrative Track
consists of the following: – CCSDS Record (Yellow Book). </span>
<br><span style=" font-size:12pt;color:#0082bf">…</span>
<br><span style=" font-size:12pt;color:#0082bf">Yellow Books may also be
used to document CCSDS internal processes, procedures, and controlling
guidelines. This document is itself a CCSDS Yellow Book, and it is a controlling
document describing CCSDS procedures. Any CCSDS Yellow Book that is normative
upon CCSDS itself requires CESG and CMC approval polling. </span>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">The
issues that we have had with the ambiguities were brought up in the CESG
meeting as part of the SEA overall report, (see attached d01-SANA-SSG).
There was a separate SANA Issues presentation to the CESG that addressed
in more detail the issues and the specific changes that were in discussion
(see attached "SANA-SSG-Issues & Proposal"). The CESG
had some comments and they were addressed in the version of the materials
I attached here. These documents were prepared by the SEA SAWG and
were reviewed within the SANA Steering Group (SSG) which includes SANA,
Secretariat, and CESG members from several agencies. Several working
telecons were held with the SSG, Secretariat, and the SANA Operator to
make sure that the actual process and steps was properly described so that
Working groups would have no ambiguities to wrestle with.</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
believe that the normal course of approval for such Administrative Track
documents that are normative on CCSDS is the one that we are on. This
is what we followed for the original versions of these documents and I
can see no reason why these updates should not follow the same documented
process. These Yellow Books are supposed to be reviewed and approved,
or not, by the CESG, and then concurred, or not, by the CMC. </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">That
said, I do agree that there are a number of documents in the review queue,
all of which properly require the attention of the CESG. I suggest
the following approach, at least for these:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:sans-serif">1.
</span><span style=" font-size:11pt;font-family:Calibri">That
the review period, at least for these documents, can be extended by a week.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:sans-serif">2.
</span><span style=" font-size:11pt;font-family:Calibri">That
a vote of "Abstain, does not affect my area" not be allowed.
Every Area that uses registries will be affected by these.</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
do not think that it will be helpful, nor a contribution to the smooth
workings of the CCSDS, to delay this until the Spring meeting.</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">Very
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>CESG <cesg-bounces@mailman.ccsds.org> on behalf of "Margherita.di.Giulio@esa.int"
<Margherita.di.Giulio@esa.int><b><br>
Date: </b>Wednesday, February 12, 2020 at 7:19 AM<b><br>
To: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><b><br>
Subject: </b>[EXTERNAL] [CESG] Fw: [Cesg-all] New CESG 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, dear CESG colleagues,</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
looking at the (attached) list of Polls, I noticed the number of Yellow
Books that are in the publication poll, that is, they have reached
their final stage.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
I was reflecting on the fact that for Yellow Books - those YB belonging
to the administrative track - the normal practises foreseen for the
other books are not required. Namely, it is not required to::</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
- create a draft project</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
- have it approved by the CMC</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
- run the Agency Review of the draft document</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
This means, that the Yellow Books only become (formally) "visible"
when they are ready for publication (or equivalently, when the ADs issues
the relevant resolution).</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Given the increasing importance- and number ! - of the Yellow Books,
and acknowledging their key role in governing the CCSDS practises, I would
like to reassess the production steps of the Yellow Books <br>
I mean that, there should be a sort of milestone, where assessment/review
gets requested. This could involve, for instance, the ADs.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
(If I remember well, this was informally done only when the Org & Proc
book was established.).</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
For YB all we have today is that some sort of assessment
can only be done during the polling process by the ADs ( by issuing PIDs).
However this can't be considered a mean to review the document.
</span><span style=" font-size:11pt;font-family:Calibri"><br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
I will bring this point to discussion, either at the next Telecon, or at
the Spring Meeting.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
Meanwhile, please let me know if you have comments or proposals,</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
Kind regard,<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>
</span><span style=" font-size:9pt;color:#800080;font-family:Arial"><br>
----- Forwarded by Margherita di Giulio/esoc/ESA on 12/02/2020 10:51 -----</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
From: </span><span style=" font-size:9pt;font-family:Arial">"CCSDS
Secretariat" <thomas.gannett@tgannett.net></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">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>
Cc: </span><span style=" font-size:9pt;font-family:Arial">cesg-all@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">05/02/2020
00:48</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">[Cesg-all]
New CESG Polls</span><span style=" font-size:11pt;font-family:Calibri">
</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: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"><br>
<br>
</span><span style=" font-size:10pt;font-family:Courier New"><br>
Dear CESG Members,<br>
<br>
Seven new CESG polls have been posted to the CWE:<br>
<br>
- CESG-P-2020-02-001 Approval to publish CCSDS <br>
313.0-Y-3, Space Assigned Numbers Authority <br>
(SANA)—Role, Responsibilities, Policies, and Procedures Yellow Book, Issue
3)<br>
- CESG-P-2020-02-002 Approval to publish CCSDS <br>
313.1-Y-2, CCSDS SANA Registry Management Policy Yellow Book, Issue 2)<br>
- CESG-P-2020-02-003 Approval to publish CCSDS <br>
313.2-Y-2, Procedures for SANA Registry Specification Yellow Book, Issue
2)<br>
- CESG-P-2020-02-004 Approval to publish CCSDS <br>
315.1-Y-1, CCSDS URN Namespace Policy (Yellow Book, Issue 1)<br>
- CESG-P-2020-02-005 Approval to publish CCSDS <br>
500.2-G-2, Navigation Data Messages Overview (Green Book, Issue 2)<br>
- CESG-P-2020-02-006 Approval to publish CCSDS <br>
920.0-G-1, Cross Support Transfer Service <br>
Specification Framework Concept (Green Book, Issue 1)<br>
- CESG-P-2020-02-007 Approval to publish CCSDS <br>
660.2-G-2, XML Telemetric and Command Exchange (XTCE) (Green Book, Issue
2)<br>
<br>
These polls can be accessed via the following link:<br>
</span><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><br>
</u></span><a href=https://public.ccsds.org/polls/SitePages/CESG%20Open%20Polls.aspx><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>https://public.ccsds.org/polls/SitePages/CESG%20Open%20Polls.aspx</u></span></a><span style=" font-size:10pt;font-family:Courier New"><br>
<br>
The closure date for these polls is 18 February 2020<br>
<br>
NOTE TO CC RECIPIENTS: Only Area Directors and <br>
Deputy Area Directors vote on CESG polls.<br>
_______________________________________________<br>
CESG-All mailing list<br>
CESG-All@mailman.ccsds.org</span><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><br>
</u></span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg-all"><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-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).[attachment "SANA-SSG Issues & Proposal
13Nov19.pptx" deleted by Margherita di Giulio/esoc/ESA] [attachment
"d01-SANA-SSG-Report-to-CMC Fall 2019v1.pptx" deleted by Margherita
di Giulio/esoc/ESA] </span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>