<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;}
@font-face
{font-family:TimesNewRomanPS;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:TimesNewRomanPSMT;
panose-1:2 2 6 3 5 4 5 2 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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:796219618;
mso-list-type:hybrid;
mso-list-template-ids:-1000953138 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
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">
<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 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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">in the CCSDS Org & Proc doc, A02x1y4c2, the process for this sort of Administrative Track document that is normative upon CCSDS is quite clear:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin-left:.5in"><b><span style="font-size:12.0pt;font-family:"TimesNewRomanPS",serif;color:#0070C0">6.1.6 ADMINISTRATIVE TRACK
</span></b><span style="color:#0070C0"><o:p></o:p></span></p>
<p style="margin-left:.5in"><span style="font-size:12.0pt;font-family:"TimesNewRomanPSMT",serif;color:#0070C0">The Administrative Track consists of the following: – CCSDS Record (Yellow Book).
<o:p></o:p></span></p>
<p style="margin-left:.5in"><span style="color:#0070C0">…</span><span style="color:#0070C0"><o:p></o:p></span></p>
<p style="margin-left:.5in"><span style="font-size:12.0pt;font-family:"TimesNewRomanPSMT",serif;color:#0070C0">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><span style="color:#0070C0"><o:p></o:p></span></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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:<o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">That the review period, at least for these documents, can be extended by a week.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">That a vote of "Abstain, does not affect my area" not be allowed. Every Area that uses registries will be affected by these.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Very 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">CESG <cesg-bounces@mailman.ccsds.org> on behalf of "Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int><br>
<b>Date: </b>Wednesday, February 12, 2020 at 7:19 AM<br>
<b>To: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Subject: </b>[EXTERNAL] [CESG] Fw: [Cesg-all] New CESG 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, dear CESG colleagues,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 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> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">- create a draft project</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">- have it approved by the CMC</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">- run the Agency Review of the draft document</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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 </span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I mean that, there should be a sort of milestone, where assessment/review gets requested. This could involve, for instance, the ADs.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">(If I remember well, this was informally done only when the Org & Proc book was established.).</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I will bring this point to discussion, either at the next Telecon, or at the Spring Meeting.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Meanwhile, please let me know if you have comments or proposals,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Kind regard,<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>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:purple">----- Forwarded by Margherita di Giulio/esoc/ESA on 12/02/2020 10:51 -----</span>
<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">"CCSDS Secretariat" <thomas.gannett@tgannett.net></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">cesg@mailman.ccsds.org</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-all@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">05/02/2020 00:48</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">[Cesg-all] New CESG Polls</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">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 class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<br>
<br>
<br>
<tt><span style="font-size:10.0pt">Dear CESG Members,</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
<tt>Seven new CESG polls have been posted to the CWE:</tt><br>
<br>
<tt>- CESG-P-2020-02-001 Approval to publish CCSDS </tt><br>
<tt>313.0-Y-3, Space Assigned Numbers Authority </tt><br>
<tt>(SANA)—Role, Responsibilities, Policies, and Procedures Yellow Book, Issue 3)</tt><br>
<tt>- CESG-P-2020-02-002 Approval to publish CCSDS </tt><br>
<tt>313.1-Y-2, CCSDS SANA Registry Management Policy Yellow Book, Issue 2)</tt><br>
<tt>- CESG-P-2020-02-003 Approval to publish CCSDS </tt><br>
<tt>313.2-Y-2, Procedures for SANA Registry Specification Yellow Book, Issue 2)</tt><br>
<tt>- CESG-P-2020-02-004 Approval to publish CCSDS </tt><br>
<tt>315.1-Y-1, CCSDS URN Namespace Policy (Yellow Book, Issue 1)</tt><br>
<tt>- CESG-P-2020-02-005 Approval to publish CCSDS </tt><br>
<tt>500.2-G-2, Navigation Data Messages Overview (Green Book, Issue 2)</tt><br>
<tt>- CESG-P-2020-02-006 Approval to publish CCSDS </tt><br>
<tt>920.0-G-1, Cross Support Transfer Service </tt><br>
<tt>Specification Framework Concept (Green Book, Issue 1)</tt><br>
<tt>- CESG-P-2020-02-007 Approval to publish CCSDS </tt><br>
<tt>660.2-G-2, XML Telemetric and Command Exchange (XTCE) (Green Book, Issue 2)</tt><br>
<br>
<tt>These polls can be accessed via the following link:</tt><br>
<br>
</span><a href="https://public.ccsds.org/polls/SitePages/CESG%20Open%20Polls.aspx"><tt><span style="font-size:10.0pt">https://public.ccsds.org/polls/SitePages/CESG%20Open%20Polls.aspx</span></tt></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
<tt>The closure date for these polls is 18 February 2020</tt><br>
<br>
<tt>NOTE TO CC RECIPIENTS: Only Area Directors and </tt><br>
<tt>Deputy Area Directors vote on CESG polls.</tt><br>
<tt>_______________________________________________</tt><br>
<tt>CESG-All mailing list</tt><br>
<tt>CESG-All@mailman.ccsds.org</tt><br>
</span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg-all"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg-all</span></tt></a><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>