[CESG] [EXTERNAL] Re: CESG-P-2020-12-006 Approval to publish CCSDS 922.3-B-1, Cross Support Transfer Service—Forward Frame Service ( Blue Book, Issue 1)

Thu Mar 11 11:26:15 UTC 2021

Peter,
        the updates have been visible to me only when -  following the 
announcement of conditions met - I asked them to Tom.
I do not know whether anybody else in CESG (apart from CSS AD and DAD, I 
would guess) could see them.

As I read your mail I perceive that everybody else (i.e. WG, CSS, other 
CESGers) is guilty but you.
However, never mind.

Clearly the rules only require to close condition and go ahead with next 
poll without more review from CESG.
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).

I am reporting what I see as an issue with "heavy" changes after "heavy" 
Conditions.
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.
IMO, the mechanism of CESG conditions was thought to address changes with 
"reasonable/limited scope". 
IMO, when changes exceed a "reasonable/limited scope" the document should 
return to CESG Poll (or even to Agency Review in some cases).

If nobody else can see this issue except me, then... peace and love.

Best regards

Gian Paolo

From:   "Shames, Peter M (US 312B)" <peter.m.shames at jpl.nasa.gov>
To:     "Gian.Paolo.Calzolari at esa.int" <Gian.Paolo.Calzolari at esa.int>, 
"cesg at mailman.ccsds.org" <cesg at mailman.ccsds.org>
Cc:     "Thomas Gannett" <thomas.gannett at tgannett.net>
Date:   11-03-21 00:10
Subject:        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)

Hi Gippo,

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.

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.

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.

So, just what exactly is the problem here?

Peter

From: CESG <cesg-bounces at mailman.ccsds.org> on behalf of Gian Paolo 
Calzolari <Gian.Paolo.Calzolari at esa.int>
Date: Wednesday, March 10, 2021 at 7:35 AM
To: CCSDS Engineering Steering Group - CESG Exec <cesg at mailman.ccsds.org>
Cc: Tom Gannett <thomas.gannett at tgannett.net>
Subject: [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)

Dear All, 
        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. 

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. 
Frankly speaking I think there is something very wrong in this approach. 

Best regards 

Gian Paolo 

From:        "Thomas Gannett" <thomas.gannett at tgannett.net> 
To:        cesg at mailman.ccsds.org 
Date:        07-03-21 16:48 
Subject:        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) 
Sent by:        "CESG" <cesg-bounces at mailman.ccsds.org> 

Dear CESG Members,

Conditions for approval of CCSDS 922.3-B-1, Cross 
Support Transfer Service—Forward Frame Service 
(Blue Book, Issue 1) have been disposed to the 
satisfaction of the AD(s) who voted to approve 
with conditions. The Secretariat will now proceed 
with CMC polling to authorize publication.

Thomas Gannett
thomas.gannett at tgannett.net
+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] _______________________________________________
CESG mailing list
CESG at mailman.ccsds.org
https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg

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 at esa.int).

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 at esa.int).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20210311/7dc182ca/attachment-0001.htm>