<span style=" font-size:10pt;font-family:sans-serif">Peter,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
the updates have been visible to me only when - following
the announcement of conditions met - I asked them to Tom.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">I do not know
whether anybody else in CESG (apart from CSS AD and DAD, I would guess)
could see them.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">As I read your
mail I perceive that everybody else (i.e. WG, CSS, other CESGers) is guilty
but you.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">However, never
mind.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Clearly the rules
only require to close condition and go ahead with next poll without more
review from CESG.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">On the other hand
the rules also require to vote during poll (and not after polls) and -
as CESG agreed - to provide formal PIDs (this was discussed in order to
give real visibility on conditions).</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">I am reporting
what I see as an issue with "heavy" changes after "heavy"
Conditions.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">I would be curios
about knowing who in CESG has been able to fully understand the requested
changes and eventually to track the implemented changes.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">IMO, the mechanism
of CESG conditions was thought to address changes with "reasonable/limited
scope". </span>
<br><span style=" font-size:10pt;font-family:sans-serif">IMO, when changes
exceed a "reasonable/limited scope" the document should return
to CESG Poll (or even to Agency Review in some cases).</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">If nobody else
can see this issue except me, then... peace and love.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Best regards</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Gian Paolo</span>
<br>
<br>
<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>, "cesg@mailman.ccsds.org"
<cesg@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"Thomas
Gannett" <thomas.gannett@tgannett.net></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">11-03-21
00:10</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] Re: [CESG] CESG-P-2020-12-006 Approval to publish CCSDS
922.3-B-1, Cross Support Transfer Service—Forward Frame Service ( Blue
Book, Issue 1)</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">I’m
guessing that these necessary updates were “visible” to you, and the
rest of the CESG, because you were able to state the magnitude of the required
changes. Perhaps you are asking that the CESG be given an opportunity
to re-review the changes in response to the PID. I cannot tell because
you did not address that issue. But the CESG did get to see the changes.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">In
point of fact, the revisions do not make the document “heavily, nor completely
different” from the document that was reviewed. What the changes
do accomplish is to align the description of the service with the functionality
requested in the IOAG SISG report from years ago, which you, yourself,
were a co-author of. What was required were not changes to the FF-CSTS
service provisioning itself, but were clarifications to the service production
that were not otherwise documented anywhere aside from the IOAG SISG report
and the SCCS-ARD. In the absence of these clarifications the functionality
of the service, both provision (which is the core focus of the service
exposed to users) and production (which are the functions that must be
executed to deliver full functionality of frame merging and DTN bundle
agent and CFDP file agent integration) would be inadequately documented.
It would have been left to the users to guess what production functionality
was required or supported. A massive source of ambiguity for a service
that is to be the heart of DTN integration and support in the future ESLTs.</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">What
is wrong with this approach is that the WG failed to incorporate the description
of these critical production functions in the first place, and that the
CESG failed to catch it earlier. I point the finger at myself here,
since I had the opportunity to catch the issue earlier and did, in fact,
point this concern out a couple of years ago. But then, I am only
one of the six Area Directors. It appears that no one else, including
you, who were one of the authors of the IOAG SISG report that defined this
new service, managed to catch this issue until now.</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,
just what exactly is the problem here?</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">Peter</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"><b>From:
</b>CESG <cesg-bounces@mailman.ccsds.org> on behalf of Gian Paolo
Calzolari <Gian.Paolo.Calzolari@esa.int><b><br>
Date: </b>Wednesday, March 10, 2021 at 7:35 AM<b><br>
To: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><b><br>
Cc: </b>Tom Gannett <thomas.gannett@tgannett.net><b><br>
Subject: </b>[EXTERNAL] Re: [CESG] CESG-P-2020-12-006 Approval to publish
CCSDS 922.3-B-1, Cross Support Transfer Service—Forward Frame Service
( Blue Book, Issue 1)</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
All,</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:10pt;font-family:Arial"><br>
I see that there is a 24 pages document only
to explain which changes have been applied (to a 242 pages document) because
of the (late) conditions.</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
The document that will go to CMC - in a way invisible to CESGers - is
now heavily (if not completely) different from the one that was evaluated
by CESG.</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:10pt;font-family:Arial"><br>
Frankly speaking I think there is something very wrong in this approach.</span><span style=" font-size:11pt;font-family:Calibri">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Best 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">"Thomas
Gannett" <thomas.gannett@tgannett.net></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
To: </span><span style=" font-size:9pt;font-family:Arial">cesg@mailman.ccsds.org</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date: </span><span style=" font-size:9pt;font-family:Arial">07-03-21
16:48</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject: </span><span style=" font-size:9pt;font-family:Arial">Re:
[CESG] CESG-P-2020-12-006 Approval to publish CCSDS 922.3-B-1, Cross
Support Transfer Service—Forward Frame Service ( Blue Book, Issue
1)</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"><br>
<br>
</span><span style=" font-size:10pt;font-family:Courier New"><br>
Dear CESG Members,<br>
<br>
Conditions for approval of CCSDS 922.3-B-1, Cross <br>
Support Transfer Service—Forward Frame Service <br>
(Blue Book, Issue 1) have been disposed to the <br>
satisfaction of the AD(s) who voted to approve <br>
with conditions. The Secretariat will now proceed <br>
with CMC polling to authorize publication.<br>
<br>
Thomas Gannett<br>
thomas.gannett@tgannett.net<br>
+1 443 472 0805 [attachment "Re EXTERNAL Response to CSEG Review comments
on the FF-CSTS candidate Blue Book.txt" deleted by Gian Paolo Calzolari/esoc/ESA]
_______________________________________________<br>
CESG mailing list<br>
CESG@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__;!!PvBDto6Hs4WbVuu7!a0qSHP9p17UYLyqsbzP1_BZYMyQz3GAR0v2LqDlVHS-OzHnN8FyD9Bk09_eVYN-oeFQYTiX1$"><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</u></span></a><span style=" font-size:10pt;font-family:Courier New"><br>
</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></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>