<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:x="urn:schemas-microsoft-com:office:excel" 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;
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.EmailStyle22
{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:27923499;
mso-list-type:hybrid;
mso-list-template-ids:2031535680 1177714278 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:818;
mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
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">
<div class="WordSection1">
<p class="MsoNormal">Gippo, et al,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As part of tracking the acceptance of these changes to resolutions from this email into the spreadsheet I have colored all of the ones that I believe are resolved, or that we resolved in today's discussion, in
<b><span style="color:#00B050">green</span></b>. In this set from Gippo only the items left in red appear to still be in need of closure. This same color coding is used in the spreadsheet. I have marked any PIDs that I believe are related / identical to
ones we discussed in the same way and referenced the related PIDs where we agreed to any needed changes. Only those remaining in
<b><span style="color:red">red</span></b><span style="color:red"> </span>appear to be unresolved.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If you find any discrepancies in this please bring them to our collective attention.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Now it is up to Mario and Erik to identify if they agree with the proposed dispositions for their PIDs in the attached, updated, spreadsheet. They agreed to do this via email.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As we discussed, if we can resolve these remaining issues via email we will declare "Done". If not we will have a follow-up WebEx in the coming week, tentatively on Wed, 8 April.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We tentatively agreed to address the SLS DVB-S2 PID issues on Thursday, 16 Apr 2020. I commit to having revised materials out for that discussion no later than tomorrow, 3 April.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, 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">Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><br>
<b>Date: </b>Thursday, April 2, 2020 at 2:42 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>[EXTERNAL] In view of today's discussion: [CESG] Materials for discussion during CESG WebEx on unresolved PIDs, Thursday, 2 Apr 20, 0800 PDT<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 & All,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> please find here below some comments in view of today's discussion.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I hope it helps</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Ciao & stay safe</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Gian Paolo</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">---------------------------------------------------------------------------------</span>
<br>
<br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">313.0-Y-3 PID SLS-04 I note your Proposed / Agreed resolution</span></b><b><span style="color:#00B050">
</span></b><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">Accept the revised language.</span><span style="color:#00B050">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">FROM: The CESG shall review the Candidate registry prior to approving the release of the document for its first Agency review.
</span><span style="color:#00B050"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">TO: The CESG shall review the document (including the Annex with Candidate registry) within the CESG Poll for releasing the document for its first Agency review.</span><span style="color:#00B050">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">This is satisfying this condition</span><span style="color:#00B050">
</span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="color:#00B050">Accept as written based on CESG discussions.
</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">313.0-Y-3 GPC SLS-06 I note your Proposed / Agreed resolution</span></b><span style="color:#00B050">
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">Remove the "NOTE -". Make clear that this is a formal part of the CESG responsibilities.</span><span style="color:#00B050">
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">This is (in principle) satisfying this condition</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">. However it would be nice showing the proposed text
to "</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">Make clear that this is a formal part of the CESG responsibilities</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">"</span>
<o:p></o:p></p>
<p class="MsoNormal"><b><span style="color:#00B050">Accept as written based on CESG discussions.
</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">313.0-Y-3 GPC SLS-11 I note your Proposed / Agreed resolution</span></b><b><span style="color:#00B050">
</span></b><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">Accept with modifications:</span><span style="color:#00B050">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">From:</span><span style="color:#00B050">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">The CESG is responsible for verifying that SANA and registry requirements are met, that the Candidate registry exists and is in appropriate form before approving the document
for first Agency review. The CESG is also responsible for verifying that the registry is in production form prior to approving the final document defining the registry for publication.</span><span style="color:#00B050">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">To:</span><span style="color:#00B050">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">During the CESG poll prior to first Agency review the CESG is responsible for verifying that SANA and registry requirements are met, that the Candidate registry exists and is
in appropriate form before approving the document for first Agency review. During the CESG poll for publication the CESG is responsible for verifying that the registry is in production form prior to approving the final document defining the registry for publication.</span><span style="color:#00B050">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">I still dislike part of the proposed modification.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">In the first sentence I find redundant "<span style="color:#00B050">that the Candidate registry exists and is in appropriate form</span>" as it is an unnecessary detail.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">However I would accept decision by majority of CESG.</span>
<o:p></o:p></p>
<p class="MsoNormal"><b><span style="color:#00B050">Accept as written based on CESG discussions.
</span></b><o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:0in"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin-left:0in;text-indent:0in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="font-family:Wingdings;color:red"><span style="mso-list:Ignore">ð<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><b><u><span style="color:red">Note that there is a workflow issue that TG raised that still need to be resolved.<o:p></o:p></span></u></b></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">313.0-Y-3 GPC SLS-13, I still think the current text is an unnecessary detail.</span></b><b><span style="color:#00B050">
<br>
</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">However I would accept decision by majority of CESG.</span>
<o:p></o:p></p>
<p class="MsoNormal"><b><span style="color:#00B050">Accept as written based on CESG discussions.
</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">313.0-Y-3 GPC SLS-16 needing
<u>CESG discussion</u>, </span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">I remark that the intention is to mirror in Org&Proc (in whatever form) the possibility of creating Expert Groups. If they are assimilated to SIGs (requiring only
AD actions) fine for me amending (the short) section 2.3.5 SPECIAL INTEREST GROUPS (SIGS) instead of (the long) section 5.2.7 SPECIAL INTEREST GROUP MEETINGS that is specifically addressing meetings.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">If the expert group requires CESG or CMC approval, then something dedicated should exist,</span>
<o:p></o:p></p>
<p class="MsoNormal"><b><span style="color:#00B050">Accept as written based on CESG discussions.
</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">313.1-Y-2 MM addressing "see response to 313.0-Y-3, GPC, SLS-16".</span></b><b><span style="color:#00B050">
</span></b><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">It looks to me that the situation of the XML Expert Group (or persistent XML SIG?) shall anyhow be clarified.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">the matter of recoding participants to these Experts Groups shall also be clarified.
</span><br>
<br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050"> 313.2-Y-2 GPC SLS-05 I note your Proposed / Agreed resolution</span></b><b><span style="color:#00B050">
<br>
</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">Section 2.3 is, admitedly, long. It is a non-normative, descriptive, section of the document and these are often "descriptive", as intended by the format. We could, as
you request, create a separate, formal, "contact list" section at the front of section 3 and then just refer to these as "SANA Operator", "SSG", "BETA Registries". Does that scratch your itch?.</span><span style="color:#00B050">
<br>
</span><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">YES. This is satisfying this condition</span></b><span style="color:#00B050">
</span><b><span style="color:red">Modified text to be provided.</span></b><br>
<br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050"> 313.2-Y-2 GPC SLS-01 I note your Proposed / Agreed resolution</span></b><b><span style="color:#00B050">
</span></b><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">Accepted, with modifications:</span><span style="color:#00B050">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">FROM:</span><span style="color:#00B050">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">The registry is expected to be complete and stable prior to the start of Agency review.</span><span style="color:#00B050">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">TO:</span><span style="color:#00B050">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">The registry is expected to be complete and stable (i.e. fully consistent with the draft document) prior to the start of Agency review."</span><span style="color:#00B050">
<br>
</span><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">This is satisfying this condition.</span></b><span style="color:#00B050">
</span><br>
<br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050"> 313.2-Y-2 GPC SLS-02</span></b>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Even if not marked so:
<b><span style="color:fuchsia">This needs CESG discussion.</span></b><span style="color:fuchsia"> </span></span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">However I would accept decision by majority of CESG.</span>
<o:p></o:p></p>
<p class="MsoNormal"><b><span style="color:#00B050">Accept as written. Consistent with resolutions for 313.0-Y-3, GPC, SLS-13, and SLS-16.<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> <b><span style="color:#00B050">313.2-Y-2 GPC SLS-04 I do not agree that we shall remark the obvious, however I do not want to fight for this.</span></b></span><span style="color:#00B050">
</span><br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">This is satisfying this condition.</span></b><span style="color:#00B050">
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> <b>313.2-Y-2 GPC SLS-06</b> <b><span style="color:fuchsia">This needs CESG discussion.</span></b><span style="color:fuchsia"> </span></span>
<o:p></o:p></p>
<p class="MsoNormal"><b><span style="color:#00B050">Accept as written, consistent with 313.0-Y-3, GPC, SLS-13 & SLS-16<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 313.2-Y-2 GPC SLS-08 <span style="color:fuchsia">This needs CESG discussion.</span></span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:fuchsia">
</span> <o:p></o:p></p>
<p class="MsoNormal"><b><span style="color:#00B050">Accept as written, consistent with 313.0-Y-3, GPC, SLS-13 & SLS-16<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 313.2-Y-2 GPC SLS-09</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> <b><span style="color:fuchsia">This needs CESG discussion.</span></b><span style="color:fuchsia">
</span></span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Interoperability Test Reports are WG Chair Responsibility and eventually AD & CESG verify those Test Reports.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">However I find excessive stating asking CESG to verify interactions (i.e. mail exchanges?).</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="color:#00B050">Accept as written, consistent with 313.0-Y-3, GPC, SLS-13 & SLS-16,
</span></b><b><span style="color:red">but see this …</span></b><b><span style="color:#00B050"><o:p></o:p></span></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">If needed Org&Proc section "6.2.6.1 Approval Criteria b) 1) first bullet" (see below) could be amended to add the ned for documenting inclusion/verification
of required interactions.</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:maroon">- the WG Chair is responsible for documenting the specific implementations that qualify the specification for CCSDS Recommended Standard status, along with reports
relevant to their testing; </span><br>
<br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050"> 315.1-Y-1 GPC SLS-06 I note your Proposed / Agreed resolution</span></b><b><span style="color:#00B050">
</span></b><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">..... Sec 3, pg 3-1, To:</span><span style="color:#00B050">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">The following structure is defined for the tree under urn:ccsds. The requestor of a new or changed URN may be a CCSDS Area, Working Group or Agency. The URN registry is a CCSDS
Global registry, as defined in reference [6].</span><span style="color:#00B050">
</span><br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">This is satisfying this condition</span></b><span style="color:#00B050">
</span><br>
<br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> <span style="color:#00B050">315.1-Y-1 GPC SLS-03 See response to 313.0-Y-3, GPC, SLS-16</span></span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">.....
needing <u><span style="color:#00B050">CESG discussion</span></u>, I remark that the intention is to mirror in Org&Proc (in whatever form) the possibility of creating Expert Groups. If they are assimilated to SIGs (requiring only AD actions) fine for me amending
(the short) section 2.3.5 SPECIAL INTEREST GROUPS (SIGS) instead of (the long) section 5.2.7 SPECIAL INTEREST GROUP MEETINGS that is specifically addressing meetings.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">If the expert group requires CESG or CMC approval, then something dedicated should exist,</span>
<o:p></o:p></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#00B050">Accept response to 313.0-Y-3 GPC SLS-16 </span></b><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">--------------------------------------------------------------------------------------------------------------</span>
<br>
<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\) via CESG" <cesg@mailman.ccsds.org></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">"CCSDS Engineering Steering Group - CESG Exec" <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">01-04-20 00:22</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] Materials for discussion during CESG WebEx on unresolved PIDs, Thursday, 2 Apr 20, 0800 PDT</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" <cesg-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">
<o:p> </o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Dear Margherita, et al,<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Attached please find a spreadsheet with the set of unresolved PIDs that were raised during the four recent CESG polls:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">1. </span>Poll CESG-P-2020-02-001, Doc CCSDS 313.0-Y-3, Draft SANA Role, Responsibilities, Policies, and Procedures (largely guidance for the SANA Operator and the CMC, CESG, interactions)
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">2. </span>Poll CESG-P-2020-02-001, Doc CCSDS 313.1-Y-2, Draft Registry Management Policy (describes the overall re-engineering of the set of SANA registries, with emphasis on the Enterprise
and Global sets, and the overall registry use and extension policies) <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">3. </span>Poll CESG-P-2020-02-003, Doc CCSDS 313.2-Y-2, Draft Procedures for SANA Registry Specification (a concise guide for any WG that needs to create or modify a registry, should be the
only doc that most WG need to read) <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">4. </span>Poll CESG-P-2020-02-004, Doc CCSDS 315.1-Y-1, Draft CCSDS URN Namespace Policy (the policy for URNs)
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
There is a total of 25 separate PIDs, but several of them are duplicates from different ADs, or are the same issue raised for different documents. There are proposed resolutions for all of these. I believe that only some of these really need CESG discussion,
and those are so marked in column "J" as "<b><span style="color:red">This needs CESG discussion.</span></b><span style="color:red">
</span>". Others may have different opinions, which I am sure we will discuss. I will remind everyone that there is a separate set of PIDs and resolutions that you have all seen where the resolutions were accepted by the ADs who submitted them. They are
not included here, only the unresolved ones.<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
I only prepared this one spreadsheet. Other materials relating to the rationale for this set of editorial changes were already distributed, as was the entire set of proposed resolutions and AD "reclama" responses.<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
See you all on Thursday.<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Best regards, and take care, Peter<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
[attachment "CESG Poll unresolved issues 313x0,1,2 & 315x1 30Mar20.xlsx" deleted by Gian Paolo Calzolari/esoc/ESA]
<tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>CESG mailing list</tt><br>
<tt>CESG@mailman.ccsds.org</tt><br>
</span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</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>