<span style=" font-size:12pt;font-family:Arial">Hi Peter,</span>
<br>
<br><span style=" font-size:12pt;font-family:Arial">My only outstanding
comment (repeated twice) relates to the duplication of information across
documents, which is clearly ever ideal as it is error prone. If, however,
you and Tom are ready to manage this additional burden, I am fine with
that.</span>
<br>
<br><span style=" font-size:12pt;font-family:Arial">Regards,</span>
<br>
<br><span style=" font-size:12pt;font-family:Arial">__Mario</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">"Gian.Paolo.Calzolari@esa.int"
<Gian.Paolo.Calzolari@esa.int>, "Barkley, Erik J (US 3970)"
<erik.j.barkley@jpl.nasa.gov>, "Mario Merri" <Mario.Merri@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">"CCSDS
CESG --" <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">02/04/2020
20:43</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] In view of today's discussion: [CESG] Materials for discussion
during CESG WebEx on unresolved PIDs, Thursday, 2 Apr 20, 0800 PDT</span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Gippo,
et al,</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">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 </span><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>green</b></span><span style=" font-size:11pt;font-family:Calibri">.
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 </span><span style=" font-size:11pt;color:red;font-family:Calibri"><b>red</b>
</span><span style=" font-size:11pt;font-family:Calibri">appear to be unresolved.</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">If
you find any discrepancies in this please bring them to our collective
attention.</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">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.</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">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. </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">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.</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">Thanks,
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>Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><b><br>
Date: </b>Thursday, April 2, 2020 at 2:42 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] In view of today's discussion: [CESG] Materials
for discussion during CESG WebEx on unresolved PIDs, Thursday, 2 Apr 20,
0800 PDT</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 & All,</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
please find here below some comments in view
of today's discussion.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
I hope it helps</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Ciao & stay safe</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Gian Paolo</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:10pt;font-family:Arial"><br>
---------------------------------------------------------------------------------</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><b><br>
313.0-Y-3 PID SLS-04
I note your Proposed / Agreed resolution</b></span><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>
</b></span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
Accept the revised language.</span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
FROM: The CESG shall review the Candidate registry prior to approving the
release of the document for its first Agency review. <br>
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=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
This is satisfying this condition</span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>Accept
as written based on CESG discussions. </b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#008250;font-family:Arial"><b><br>
313.0-Y-3 GPC SLS-06
I note your Proposed / Agreed resolution</b></span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
Remove the "NOTE -". Make clear that this is a formal part
of the CESG responsibilities.</span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
This is (in principle) satisfying this condition</span><span style=" font-size:10pt;color:blue;font-family:Arial">.
However it would be nice showing the proposed text to "</span><span style=" font-size:10pt;color:#008250;font-family:Arial">Make
clear that this is a formal part of the CESG responsibilities</span><span style=" font-size:10pt;color:blue;font-family:Arial">"</span><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>Accept
as written based on CESG discussions. </b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#008250;font-family:Arial"><b><br>
313.0-Y-3 GPC SLS-11
I note your Proposed / Agreed resolution</b></span><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>
</b></span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
Accept with modifications:</span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
From:</span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
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=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
To:</span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
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=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
I still dislike part of the proposed modification.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
In the first sentence I find redundant "</span><span style=" font-size:10pt;color:#008250;font-family:Arial">that
the Candidate registry exists and is in appropriate form</span><span style=" font-size:10pt;font-family:Arial">"
as it is an unnecessary detail.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
However I would accept decision by majority of CESG.</span><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>Accept
as written based on CESG discussions. </b></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;color:red;font-family:Wingdings">ð
</span><span style=" font-size:11pt;color:red;font-family:Calibri"><b><u>Note
that there is a workflow issue that TG raised that still need to be resolved.</u></b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><br>
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><b><br>
313.0-Y-3 GPC SLS-13,
I still think the current text is an unnecessary detail.</b></span><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>
</b></span><span style=" font-size:10pt;font-family:Arial"><br>
However I would accept decision by majority of CESG.</span><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>Accept
as written based on CESG discussions. </b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#008250;font-family:Arial"><b><br>
313.0-Y-3 GPC SLS-16
needing <u>CESG discussion</u>, </b></span><span style=" font-size:10pt;font-family:Arial">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><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
If the expert group requires CESG or CMC approval, then something dedicated
should exist,</span><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>Accept
as written based on CESG discussions. </b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#008250;font-family:Arial"><b><br>
313.1-Y-2 MM addressing
"see response to 313.0-Y-3, GPC, SLS-16".</b></span><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>
</b></span><span style=" font-size:10pt;font-family:Arial"><br>
It looks to me that the situation of the XML Expert Group (or persistent
XML SIG?) shall anyhow be clarified.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
the matter of recoding participants to these Experts Groups shall also
be clarified. </span><span style=" font-size:11pt;font-family:Calibri"><br>
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><b><br>
313.2-Y-2 GPC SLS-05
I note your Proposed / Agreed resolution</b></span><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>
</b></span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
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=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><b><br>
YES. This is satisfying this condition</b></span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:11pt;color:red;font-family:Calibri"><b>Modified
text to be provided.</b></span><span style=" font-size:11pt;font-family:Calibri"><br>
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><b><br>
313.2-Y-2 GPC SLS-01
I note your Proposed / Agreed resolution</b></span><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>
</b></span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
Accepted, with modifications:</span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
FROM:</span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
The registry is expected to be complete and stable prior to the start of
Agency review.</span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
TO:</span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
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=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><b><br>
This is satisfying this condition.</b></span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:11pt;font-family:Calibri"><br>
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><b><br>
313.2-Y-2 GPC SLS-02</b></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
Even if not marked so: </span><span style=" font-size:10pt;color:#ff00ff;font-family:Arial"><b>This
needs CESG discussion.</b> </span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
However I would accept decision by majority of CESG.</span><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>Accept
as written. Consistent with resolutions for 313.0-Y-3, GPC, SLS-13,
and SLS-16.</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial"><br>
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><b>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.</b></span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><b><br>
This is satisfying this condition.</b></span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:11pt;font-family:Calibri"><br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
<b>313.2-Y-2 GPC SLS-06</b>
</span><span style=" font-size:10pt;color:#ff00ff;font-family:Arial"><b>This
needs CESG discussion.</b> </span><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>Accept
as written, consistent with 313.0-Y-3, GPC, SLS-13 & SLS-16</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial"><b><br>
313.2-Y-2 GPC SLS-08
</b></span><span style=" font-size:10pt;color:#ff00ff;font-family:Arial"><b>This
needs CESG discussion.</b> </span><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>Accept
as written, consistent with 313.0-Y-3, GPC, SLS-13 & SLS-16</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial"><b><br>
313.2-Y-2 GPC SLS-09</b>
</span><span style=" font-size:10pt;color:#ff00ff;font-family:Arial"><b>This
needs CESG discussion.</b> </span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
Interoperability Test Reports are WG Chair Responsibility and eventually
AD & CESG verify those Test Reports.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
However I find excessive stating asking CESG to verify interactions (i.e.
mail exchanges?).</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>Accept
as written, consistent with 313.0-Y-3, GPC, SLS-13 & SLS-16, </b></span><span style=" font-size:11pt;color:red;font-family:Calibri"><b>but
see this …</b></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">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><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;color:#800000;font-family:Arial"><br>
- 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><span style=" font-size:11pt;font-family:Calibri"><br>
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><b><br>
315.1-Y-1 GPC SLS-06
I note your Proposed / Agreed resolution</b></span><span style=" font-size:11pt;color:#008250;font-family:Calibri"><b>
</b></span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
..... Sec 3, pg 3-1, To:</span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><br>
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=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:10pt;color:#008250;font-family:Arial"><b><br>
This is satisfying this condition</b></span><span style=" font-size:11pt;color:#008250;font-family:Calibri">
</span><span style=" font-size:11pt;font-family:Calibri"><br>
</span><span style=" font-size:10pt;font-family:Arial"><b><br>
</b></span><span style=" font-size:10pt;color:#008250;font-family:Arial"><b>315.1-Y-1
GPC SLS-03
See response to 313.0-Y-3, GPC, SLS-16</b></span><span style=" font-size:10pt;font-family:Arial">.....
needing </span><span style=" font-size:10pt;color:#008250;font-family:Arial"><u>CESG
discussion</u></span><span style=" font-size:10pt;font-family:Arial">,
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><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
If the expert group requires CESG or CMC approval, then something dedicated
should exist,</span><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"><b> </b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#008250;font-family:Arial"><b>Accept
response to 313.0-Y-3 GPC
SLS-16 </b></span><span style=" font-size:11pt;font-family:Calibri"><br>
</span><span style=" font-size:10pt;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\) via CESG" <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>
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">"CCSDS
Engineering Steering Group - CESG Exec" <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">01-04-20
00:22</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]
Materials for discussion during CESG WebEx on unresolved PIDs, Thursday,
2 Apr 20, 0800 PDT</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"
<cesg-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"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt">Dear
Margherita, et al,</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">Attached
please find a spreadsheet with the set of unresolved PIDs that were raised
during the four recent CESG polls:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial"><br>
1. </span><span style=" font-size:11pt;font-family:Calibri">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) </span><span style=" font-size:10pt;font-family:Arial"><br>
2. </span><span style=" font-size:11pt;font-family:Calibri">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) </span><span style=" font-size:10pt;font-family:Arial"><br>
3. </span><span style=" font-size:11pt;font-family:Calibri">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) </span><span style=" font-size:10pt;font-family:Arial"><br>
4. </span><span style=" font-size:11pt;font-family:Calibri">Poll
CESG-P-2020-02-004, Doc CCSDS 315.1-Y-1, Draft CCSDS URN Namespace Policy
(the policy for URNs) </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt">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 "</span><span style=" font-size:12pt;color:red"><b>This
needs CESG discussion.</b> </span><span style=" font-size:12pt">".
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.</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt">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.</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt">See you all
on Thursday.</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt">Best regards,
and take care, 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"> [attachment
"CESG Poll unresolved issues 313x0,1,2 & 315x1 30Mar20.xlsx"
deleted by Gian Paolo Calzolari/esoc/ESA] </span><span style=" font-size:10pt;font-family:Courier New">_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org</span><span style=" font-size:12pt;color:blue"><u><br>
</u></span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</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 "CESG Poll unresolved issues 313x0,1,2
& 315x1 2Apr20.xlsx" deleted by Mario Merri/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>