<span style=" font-size:12pt;font-family:Times New Roman">Dear Peter and
All,</span>
<br><span style=" font-size:12pt;font-family:Times New Roman">I would like
to conclude on this topic </span>
<br><span style=" font-size:12pt;font-family:Times New Roman"> The
discussion has been triggered by the following comment from Jaxa to one
CMC Poll. </span>
<br><span style=" font-size:12pt;font-family:Times New Roman"><i>Section
6.1.4.4 (Page 6-5) states "…Blue Books are required to be prototyped
before final approval and publication…" Resources of Prototype
1 and Prototype 2 are "Not required" for this 5-year review,
however, there is no statement in the CCSDS A02.1-Y-4 whether the prototype
tests are required for the New Projects of the 5-year review. Will
the necessity be identified in the course of the review process?</i> </span>
<br><span style=" font-size:12pt;font-family:Times New Roman">Given that
this comment quoted - and commented - the CCSDS A02.1-Y-4 ,
it is CESG responsibility to provide the answer.</span>
<br><span style=" font-size:12pt;font-family:Times New Roman">The following
text summaries the thread of discussion we have had. If there are no further
comments, I will forward the answer to the Jaxa CMC representative.</span>
<br>
<br><span style=" font-size:12pt;font-family:Times New Roman"><b>-----------------------------------------------------------------------------------------------------------------------------------------</b></span>
<br>
<br><span style=" font-size:12pt;font-family:Times New Roman">1) CESG agreed
to introduce the following clarification into CCSDS A02.1-Y-4 (but changes
will be introduced when the next release of the document is du<i>e) </i></span>
<br><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><i>6.1.4.4
As a result of this difference in
prescriptive content between Blue and Magenta
books, Blue Books are required to be
prototyped before final approval and publication,
but Magenta Books are not required to be prototyped. </i></span><span style=" font-size:12pt;color:red;font-family:Times New Roman"><i>This
applies also to updates of Blue Books, if/when new features are introduced</i></span><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><i>.</i></span><span style=" font-size:12pt;font-family:Times New Roman"><i>
</i></span><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><i><br>
<br>
6.2.7.2.1.1 Revisions of published normative documents shall follow
the procedures in 6.2.2 </i></span><span style=" font-size:12pt;color:red;font-family:Times New Roman"><i>and
6.2.6.</i></span><span style=" font-size:12pt;font-family:Times New Roman"><i>
</i></span>
<br>
<br><span style=" font-size:12pt;font-family:Times New Roman">2) Answer
to the question "<i> Will the necessity be identified in the course
of the review process?</i>" </span>
<br><span style=" font-size:12pt;font-family:Times New Roman">The change
of scope of actual edits to one document with respect to the approved project
in CWE is controlled as follows:</span>
<br><span style=" font-size:12pt;font-family:Times New Roman">1) WG
to get to consensus on the actual changes <br>
2) in case the changes are not trivial, the WG shall modify the approved
CWE Project. Notably, this applies if changes are such to require a change
to the project's resources <br>
3) request approval by CMC. <i><br>
</i></span>
<br><span style=" font-size:12pt;font-family:Times New Roman">-------------------------------------------------------------------------------------------------------------------</span>
<br><span style=" font-size:12pt;font-family:Times New Roman">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\) via CESG" <cesg@mailman.ccsds.org></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></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"Tom
Gannett" <thomas.gannett@tgannett.net>, "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">01/09/2020
18:39</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:
[CESG] Changing scope of actual edits to a document: [EXTERNAL] Fw: [Cesg-all]
Results of CMC Polls</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style=" font-size:9pt;font-family:sans-serif">"CESG"
<cesg-bounces@mailman.ccsds.org></span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Hi
Gippo,</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">Ah.
NOW I think I understand your point of view. It does seem to
be the case that the CWE Project structure, which many (including myself)
view as a "hoop" we need to jump through in order to be allowed
to do the work we want to do (or need to do) to largely be an annoying
formality. It was proposed at one point as a part of strategic planning,
a way of documenting where we collectively wanted to go. In that
it was to replace the Strategic Plan, a document based version with the
same intent. At least that is my understanding of how we got to where
we are.</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 think that we hold that Project definition as being intended to clearly
state what we intend to do and what the subject matter is. We also
intend this Project definition to clearly state the scope, intended outcome,
and schedule. </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">Having
said that, I disagree that "</span><span style=" font-size:10pt;font-family:Arial">once
you have started a CWE Project you can do whatever you like on a given
book". If I were to agree with that statement it would mean
that it would be Ok for an SLS WG to develop a network protocol, or a spacecraft
on-board one. I think that would totally violate what is intended
and that at the very first public meeting where such a shift were reported
that it would result in howls of pain (Ok, maybe THAT is a little extreme),
or at least a strong push back from the offended CCSDS WG and Area, and
likely support from other Areas as well. We do have these agreed
Areas, WG, and "boundaries" and one of the assigned responsibilities
of the CESG is "maintaining orderly progress" (secs 2.3.2.3.g,
I, j).</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">I
can think of two recent examples of how this works:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial"> </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">SOIS
Wireless WG: Created a project to adopt WiFi and 4G/LTE specs (thus
creating a Utilization Profile) for communications in and around orbiting
stations and habitats. Primarily for human use, in suits, and for
use on rovers (etc) local to the habitat. This could easily have
"strayed" into Prox-1 territory, but they have been asked to
constrain their geo-spatial "working envelope" to something like
10 Km, where we expect Prox-1 to be used over 100's to tens of 1000's of
Km. They have also been asked to work with SANA for registries and
with RF&M for spectrum allocation management.</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">SEA
SAWG: Asked by the CMC to create a "CCSDS Architecture". Recognized
that the bottom layers of the stack were already documented in the CCSDS
901.1-M-1, SCCS-ARD (and ADD) that cover SLS, SIS, CSS, and SEA, so focused
only on SOIS and MOIMS. Intended to create a Magenta Book, but recognized
that a lot of the materials that had been published were only Green Books,
so only a Green Book is being published.</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">These
two examples both differ from the original proposed Project, but they also
are within the spirit of what was proposed and stayed within the "bounds"
that were agreed. I think that is fine. I suspect that the
rest of the CESG feels likewise. If not, now might be a good time
to have that discussion.</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">So,
are we really in agreement?</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">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>Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><b><br>
Date: </b>Tuesday, September 1, 2020 at 1:04 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>,
Tom Gannett <thomas.gannett@tgannett.net><b><br>
Subject: </b>Re: Changing scope of actual edits to a document: [CESG] [EXTERNAL]
Fw: [Cesg-all] Results of CMC 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">Peter,</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
listening to many people in CCSDS they simply
consider CWE Project a waste of time.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
If it would appear that once you have started a CWE Project you can do
whatever you like on a given book, such opinion would be reinforced IMO.</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Therefore nice to hear we are in agreement. </span><span style=" font-size:11pt;font-family:Calibri"><br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Regards</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"> <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)" <peter.m.shames@jpl.nasa.gov></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">"Gian.Paolo.Calzolari@esa.int"
<Gian.Paolo.Calzolari@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">"Tom
Gannett" <thomas.gannett@tgannett.net>, "CCSDS 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>
Date: </span><span style=" font-size:9pt;font-family:Arial">31-08-20
18:04</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">Re:
Changing scope of actual edits to a document: [CESG] [EXTERNAL] Fw: [Cesg-all]
Results of CMC Polls</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">Hi
Gippo,</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">I
think we are in agreement. Thanks.</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">What
I am not sure about is what you mean by "</span><span style=" font-size:10pt;font-family:Arial">
ignoring this … would undermine the - already low - confidence of WGs
on CWE</span><span style=" font-size:12pt"> ". Just what do
you mean by this? What "low confidence"? In what
aspect?</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt">Thanks, 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"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"><b>From: </b>Gian
Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><b><br>
Date: </b>Monday, August 31, 2020 at 2:24 AM<b><br>
To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><b><br>
Cc: </b>Tom Gannett <thomas.gannett@tgannett.net>, CCSDS Engineering
Steering Group - CESG Exec <cesg@mailman.ccsds.org><b><br>
Subject: </b>Changing scope of actual edits to a document: [CESG] [EXTERNAL]
Fw: [Cesg-all] Results of CMC Polls</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">Dear
Peter,</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:Arial"><br>
only one "general" comment to your remark
about changing "</span><span style=" font-size:12pt">scope of actual
edits to a document</span><span style=" font-size:10pt;font-family:Arial">"
with respect to the approved CWE Project.</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
We all know that this indeed can happen.</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:Arial"><br>
However I think that we all agree that such change of scope (unless we
talk about "peanuts") shall be properly controlled with <br>
1) proper WG consensus <br>
2) modification of the approved CWE Project (when the change is not trivial)</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:Arial"><br>
3) re approval by CMC (e.g. for changes of resources)</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Of course only step #1 is always required while steps #2 and #3 depend
of the nature of the added changes.</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:Arial"><br>
IMO ignoring this (and I think this is not the case for you) would undermine
the - already low - confidence of WGs on CWE.</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:Arial"><br>
However it looks as we do not need such extreme details in Org&Proc.</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Best regards</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Gian Paolo</span><span style=" font-size:12pt"> <br>
<br>
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
<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:12pt">
</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:12pt">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Cc: </span><span style=" font-size:9pt;font-family:Arial">"Tom
Gannett" <thomas.gannett@tgannett.net>, "CESG -- CCSDS-Engineering
SteeringGroup\(cesg@mailman.ccsds.org\)\(cesg@mailman.ccsds.org\)"
<cesg@mailman.ccsds.org></span><span style=" font-size:12pt"> </span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date: </span><span style=" font-size:9pt;font-family:Arial">29-08-20
00:12</span><span style=" font-size:12pt"> </span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject: </span><span style=" font-size:9pt;font-family:Arial">Re:
[CESG] [EXTERNAL] Fw: [Cesg-all] Results of CMC Polls</span><span style=" font-size:12pt">
</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:12pt">
</span></p>
<div align=center>
<hr noshade></div>
<p style=";margin-Bottom:3600px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt">Dear Margherita,</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 agree that
some sort of modest changes to text could make some similarly modest changes
in clarity. I doubt that it is worth cresting a corrigendum for just
this change, but would agree that these kinds of edits could be added to
a list of similar items and handled all at once. I think Tom Gannett
has such a list, so I have added him to this email reply.</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 would also
comment that it is possible that the scope of actual edits to a document,
as opposed to planned edits, can change once the process has started. It's
sort of like a bathroom remodeling project where you start with just wanting
to paint the walls, and maybe changing the mirror, and you wind up replacing
all of the cabinets and tiles too. Or starting to fix what you think
is a minor leak in the plumbing and discovering that there is now mold
growing and you need to rip out the walls to fix it.</span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt">Maybe those
analogies do not work for you, but these things can happen, so I think
some latitude and flexibility is required. But I do not believe that
we need to say all of that in the Org & Proc.</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,
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"> </span></p>
<p style=";margin-Bottom:0px"><span style=" font-size:12pt"><b>From: </b>"Margherita.di.Giulio@esa.int"
<Margherita.di.Giulio@esa.int><b><br>
Date: </b>Friday, August 28, 2020 at 8:34 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>Re: [EXTERNAL] Fw: [Cesg-all] Results of CMC Polls</span></p>
<br><span style=" font-size:12pt"> </span>
<br><span style=" font-size:10pt;font-family:Arial">Dear Peter,</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:Arial"><br>
The comment form Jaxa states:</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:Arial"><i><br>
Section 6.1.4.4 (Page 6-5) states "…Blue Books are required to be
prototyped before final approval and publication…" Resources
of Prototype 1 and Prototype 2 are "Not required" for this 5-year
review, however, there is no statement in the CCSDS A02.1-Y-4 whether the
prototype tests are required for the New Projects of the 5-year review.
Will the necessity be identified in the course of the review process?</i></span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:Arial"><br>
I agree that the matter is already covered in CCSDS YB, Org & Proc,
however, may be a simple change to the text would avoid misunderstanding
in the future. For instance </span><span style=" font-size:10pt;color:red;font-family:Arial">(in
red)</span><span style=" font-size:10pt;font-family:Arial">:</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;color:blue;font-family:Arial"><br>
6.1.4.4 As a result of this difference
in prescriptive content between Blue and
Magenta books, Blue Books are required
to be prototyped before final approval
and publication, but Magenta Books are not required
to be prototyped. </span><span style=" font-size:10pt;color:red;font-family:Arial">This
applies also to updates of Blue Books, if/when new features are introduced</span><span style=" font-size:10pt;color:blue;font-family:Arial">.</span><span style=" font-size:15pt">
</span><span style=" font-size:10pt;color:blue;font-family:Arial"><br>
<br>
6.2.7.2.1.1 Revisions of published normative documents shall follow
the procedures in 6.2.2 </span><span style=" font-size:10pt;color:red;font-family:Arial">and
6.2.6.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:Arial"><br>
Concerning the question from Jaxa “….<i>Will the necessity be identified
in the course of the review process?”, </i>I think the answer is that
the necessity of prototyping can only be identified at the time the new
project gets established, in that the relevant resources must be identified
– and requested - via project approval. Therefore, this necessity cannot
be identified during the review process.</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:Arial"><br>
Kind regards,<br>
Margherita</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
<br>
--------------------------------------------------------------</span><span style=" font-size:8pt;color:#00a1e0;font-family:Verdana"><b><br>
Margherita di Giulio</b></span><span style=" font-size:12pt"> </span><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><br>
Ground Station Systems Division</span><span style=" font-size:12pt"> </span><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><br>
Backend Software Section (OPS-GSB)</span><span style=" font-size:12pt">
</span><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><b><br>
<br>
<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:12pt"><br>
<br>
<br>
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
<br>
<br>
From: </span><span style=" font-size:9pt;font-family:Arial">"Shames,
Peter M (US 312B)" <peter.m.shames@jpl.nasa.gov></span><span style=" font-size:12pt">
</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:12pt">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Cc: </span><span style=" font-size:9pt;font-family:Arial">"CESG
-- CCSDS-Engineering SteeringGroup(cesg@mailman.ccsds.org)(cesg@mailman.ccsds.org)"
<cesg@mailman.ccsds.org></span><span style=" font-size:12pt"> </span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date: </span><span style=" font-size:9pt;font-family:Arial">27/08/2020
02:02</span><span style=" font-size:12pt"> </span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject: </span><span style=" font-size:9pt;font-family:Arial">Re:
[EXTERNAL] Fw: [Cesg-all] Results of CMC Polls</span><span style=" font-size:12pt">
</span>
<div align=center>
<hr noshade></div>
<br><span style=" font-size:12pt"> </span>
<br><span style=" font-size:12pt">Dear Margherita,</span>
<br><span style=" font-size:12pt"> </span>
<br><span style=" font-size:12pt">This is already covered in the CCSDS
YB, org & Proc, under the subject of "Periodic Review":</span>
<br><span style=" font-size:12pt;color:#0082bf"><b><br>
6.2.7 PERIODIC REVIEW <br>
6.2.7.1 General </b><br>
CCSDS documents shall undergo periodic review within the Area no later
than five years after issue and every five years subsequently. Periodic
review shall result in reconfirmation, revision, or retirement to CCSDS
historical status. </span>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"><br>
If the document is just reconfirmed then there is no need for a new protoyping
effort. If the document is revised in any significant way, especially
is there are any changes to protocols, behavior, PDUs, data formats, signaling,
then that falls under the "Revisions" clause:</span><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<br><span style=" font-size:12pt;color:#0082bf"><b><br>
6.2.7.2 Changes to Documents <br>
6.2.7.2.1 Revisions of Normative Documents <br>
6.2.7.2.1.1 </b>Revisions of published normative documents shall follow
the procedures in 6.2.2. <b><br>
6.2.7.2.1.2 </b>The color designation for draft revisions of normative
documents shall be “Pink” (rather than “Red”). <b><br>
6.2.7.2.1.3 </b>In cases where only limited discrete changes are proposed
to a published normative document, only the pages containing substantive
changes (“Pink Sheets”) may be released for review. </span>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"><br>
The procedures in sec 6.2.2 are those for normal, normative, document processing,
which include prototyping and generation of a test report. I believe
that this is all clearly enough stated and that no changes to CCSDS A02.1-Y-4
are needed.</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:12pt;font-family:Calibri"><br>
</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:12pt;font-family:Calibri"><br>
Do you concur?</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:12pt;font-family:Calibri"><br>
</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:12pt;font-family:Calibri"><br>
Thanks, Peter</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:12pt;font-family:Calibri"><br>
</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:12pt;font-family:Calibri"><br>
</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:12pt;font-family:Calibri"><b><br>
From: </b>"Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int><b><br>
Date: </b>Wednesday, August 26, 2020 at 7:16 AM<b><br>
To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><b><br>
Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><b><br>
Subject: </b>[EXTERNAL] Fw: [Cesg-all] Results of CMC Polls</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:12pt;font-family:Calibri"><br>
</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:10pt;font-family:Arial"><br>
Dear Peter,</span><span style=" font-size:12pt;font-family:Calibri"> </span><span style=" font-size:10pt;font-family:Arial"><br>
the attached notification contains two comments from Jaxa, where
they query about Prototype activities for Blue Books under 5-years review
: the point they make is that CCSDS A02.1-Y-4 does not explicitly mandate
prototype testing for books under 5-years review. Is this need to
be established e.g. during the review process itself ?</span><span style=" font-size:12pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Can you please take a look at the comment ? In case some text needs to
be introduced in CCSDS A02.1-Y-4, can you propose something to CESG
?</span><span style=" font-size:12pt;font-family:Calibri"> </span><span style=" font-size:10pt;font-family:Arial"><br>
Thank you, kind regards,<br>
Margherita</span><span style=" font-size:12pt;font-family:Calibri"> </span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
--------------------------------------------------------------</span><span style=" font-size:8pt;color:#00a1e0;font-family:Verdana"><b><br>
Margherita di Giulio</b></span><span style=" font-size:12pt;font-family:Calibri">
</span><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><br>
Ground Station Systems Division</span><span style=" font-size:12pt;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:12pt;font-family:Calibri">
</span><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><b><br>
<br>
<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:#800080;font-family:Arial"><br>
<br>
<br>
----- Forwarded by Margherita di Giulio/esoc/ESA on 26/08/2020 15:56 -----</span><span style=" font-size:12pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
<br>
From: </span><span style=" font-size:9pt;font-family:Arial">"Stafford
Laura (BTAS)" <Laura.Stafford@btas.com></span><span style=" font-size:12pt;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">"Blackwood,
Michael D via CMC" <CMC@mailman.ccsds.org></span><span style=" font-size:12pt;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">"Blackwood,
Michael D via CESG-All" <cesg-all@mailman.ccsds.org></span><span style=" font-size:12pt;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">25/08/2020
18:19</span><span style=" font-size:12pt;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]
Results of CMC Polls</span><span style=" font-size:12pt;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:12pt;font-family:Calibri">
</span></p>
<div align=center>
<hr noshade></div>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"><br>
<br>
<br>
<br>
CMC E-Poll Identifier: CMC-P-2020-07-002 <br>
Approval of New Projects in the 5.04 Space Link Protocols WG<br>
<br>
Results of CMC poll beginning 7 July 2020 and ending 21 July 2020:<br>
<br>
Adopt: 8 (100%) (CNES, CNSA, CSA, DLR, ESA, INPE, JAXA, NASA)<br>
Adopt Provisionally: 0 (0%)<br>
Reject: 0 (0%)<br>
Reject with Comments: 0 (0%)<br>
<br>
Results are based on responses from 8 out of 11 members (72.72%).<br>
<br>
No response was received from the following Agencies:<br>
<br>
ASI <br>
RFSA <br>
UKSA <br>
<br>
Comments from JAXA: <br>
This comment(/inquiry) is not for this 5-year review Project, but the CCSDS
A02.1-Y-4.<br>
<br>
Section 6.1.4.4 (Page 6-5) states "…Blue Books are required to be
prototyped before final approval and publication…" Resources
of Prototype 1 and Prototype 2 are "Not required" for this 5-year
review, however, there is no statement in the CCSDS A02.1-Y-4 whether the
prototype tests are required for the New Projects of the 5-year review.
Will the necessity be identified in the course of the review process?<br>
<br>
Secretariat Interpretation of Results: Adopted<br>
Resulting CMC Resolution:
CMC-R-2020-08-008<br>
Inferred Secretariat Action:
Approve Project - Done & Working Group Chair address
Comments from JAXA. <br>
<br>
* * * * * * * * * * * * * * * * * * * *<br>
<br>
CMC E-Poll Identifier: CMC-P-2020-07-003 <br>
Approval of New Project in the 5.09 Space Data Link Security WG<br>
<br>
Results of CMC poll beginning 7 July 2020 and ending 21 July 2020:<br>
<br>
Adopt: 8 (100%) (CNES, CNSA, CSA, DLR, ESA, INPE, JAXA, NASA)<br>
Adopt Provisionally: 0 (0%)<br>
Reject: 0 (0%)<br>
Reject with Comments: 0 (0%)<br>
<br>
Results are based on responses from 8 out of 11 members (72.72%).<br>
<br>
No response was received from the following Agencies:<br>
<br>
ASI <br>
RFSA <br>
UKSA <br>
<br>
Comments from JAXA: <br>
This comment(/inquiry) is not for this 5-year review Project, but the CCSDS
A02.1-Y-4.<br>
<br>
Section 6.1.4.4 (Page 6-5) states "…Blue Books are required to be
prototyped before final approval and publication…" Resources
of Prototype 1 and Prototype 2 are "Not required" for this 5-year
review, however, there is no statement in the CCSDS A02.1-Y-4 whether the
prototype tests are required for the New Projects of the 5-year review.
Will the necessity be identified in the course of the review process?<br>
<br>
Secretariat Interpretation of Results: Adopted<br>
Resulting CMC Resolution:
CMC-R-2020-08-009<br>
Inferred Secretariat Action:
Approve Project - Done & Working Group Chair address
Comments from JAXA. <br>
<br>
<br>
* * * * * * * * * * * * * * * * * * * * <br>
CMC E-Poll Identifier: CMC-P-2020-07-004 <br>
CESG Escalation to CMC about Unresolved CESG Poll<br>
<br>
Results of CMC poll beginning 15 July 2020 and ending 29 July 2020:<br>
<br>
Adopt: 8 (100%) (CNES, CNSA, CSA, DLR, ESA, INPE, JAXA, NASA, UKSA)<br>
Adopt Provisionally: 0 (0%)<br>
Reject: 0 (0%)<br>
Reject with Comments: 0 (0%)<br>
<br>
Results are based on responses from 9 out of 11 members (81.81%).<br>
<br>
No response was received from the following Agencies:<br>
<br>
ASI <br>
RFSA <br>
<br>
Comments from ESA: <br>
ESA agree to release the book for Agency Review<br>
<br>
Secretariat Interpretation of Results: Adopted<br>
Resulting CMC Resolution:
CMC-R-2020-08-010<br>
Inferred Secretariat Action:
The Poll conditions raised by the ADs shall be removed, and
the book CCSDS 131.3-P-1.1, shall go ahead to Agency Review. <br>
<br>
* * * * * * * * * * * * * * * * * * * * <br>
<br>
CMC E-Poll Identifier: CMC-P-2020-06-005 <br>
CMC-P-2020-06-005 Charter Modification for the Multispectral Hyperspectral
Data Compression (SLS-MHDC) Working Group<br>
<br>
Results of CMC poll beginning 25 June 2020 and ending 9 July 2020:<br>
<br>
Adopt: 8 (100%) (ASI, CNES, CNSA, CSA, DLR, ESA, INPE, JAXA,)<br>
Adopt Provisionally: 0 (0%)<br>
Reject: 0 (0%)<br>
Reject with Comments: 0 (0%)<br>
<br>
Results are based on responses from 8 out of 11 members (72.72%).<br>
<br>
No response was received from the following Agencies:<br>
<br>
NASA <br>
RFSA <br>
UKSA <br>
<br>
Secretariat Interpretation of Results: Adopted<br>
Resulting CMC Resolution:
CMC-R-2020-08-011<br>
Inferred Secretariat Action:
Approve Charter Once WG Chair Makes Edits - Done </span></p>
<div align=center>
<hr></div>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:8pt;color:red;font-family:Arial"><br>
<br>
CONFIDENTIALITY NOTICE: </span><span style=" font-size:8pt;color:#5f5f5f;font-family:Arial"><i>The
contents of this e-mail message may be privileged, confidential, or otherwise
protected against disclosure or dissemination. If you are not the intended
recipient of this message, any dissemination, distribution or copying is
strictly prohibited. If you have received this message in error, please
delete all copies from your computer system. </i></span><span style=" font-size:10pt;font-family:Courier New"><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://urldefense.us/v3/__https:/mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg-all__;!!PvBDto6Hs4WbVuu7!dJeBXBZ_FfE3ud8YCTVQsvPU4TDjAkQ03Dxpm3VVEALUfHZawp50yxAbjvmP0N8i_19O8T4f$"><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><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<p style="ä,Ç■,Ç■/»;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-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-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-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).</span></p>
<p style="ä,Ç■,Ç■/»;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-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-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-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)._______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org</span><span style=" font-size:12pt;color:blue"><u><br>
</u></span><a href="https://urldefense.us/v3/__https:/mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg__;!!PvBDto6Hs4WbVuu7!dIdICCfFnuXVyRPYGj7g_saMrbAzyqz-G1R_GEbSIo6w3UZIDFCFndxDCWnS4lzJlOxFpczz$"><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-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-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-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-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).</span></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).</span><tt><span style=" font-size:10pt">_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org<br>
</span></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><tt><span style=" font-size:10pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</span></tt></a><tt><span style=" font-size:10pt"><br>
</span></tt></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>