<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New",serif;}
tt
{mso-style-priority:99;
font-family:"Courier New",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span class="EmailStyle21">Hi Gippo,<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21">So, just what exactly is the problem here?<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21">Peter<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">CESG <cesg-bounces@mailman.ccsds.org> on behalf of Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><br>
<b>Date: </b>Wednesday, March 10, 2021 at 7:35 AM<br>
<b>To: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Cc: </b>Tom Gannett <thomas.gannett@tgannett.net><br>
<b>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)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear All,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> 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>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Frankly speaking I think there is something very wrong in this approach.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Best regards</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Gian Paolo</span> <br>
<br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Thomas Gannett" <thomas.gannett@tgannett.net></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">cesg@mailman.ccsds.org</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">07-03-21 16:48</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">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>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Sent by: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"CESG" <cesg-bounces@mailman.ccsds.org></span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<tt><span style="font-size:10.0pt">Dear CESG Members,</span></tt><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
<br>
<tt>Conditions for approval of CCSDS 922.3-B-1, Cross </tt><br>
<tt>Support Transfer Service—Forward Frame Service </tt><br>
<tt>(Blue Book, Issue 1) have been disposed to the </tt><br>
<tt>satisfaction of the AD(s) who voted to approve </tt><br>
<tt>with conditions. The Secretariat will now proceed </tt><br>
<tt>with CMC polling to authorize publication.</tt><br>
<br>
<tt>Thomas Gannett</tt><br>
<tt>thomas.gannett@tgannett.net</tt><br>
<tt>+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] _______________________________________________</tt><br>
<tt>CESG mailing list</tt><br>
<tt>CESG@mailman.ccsds.org</tt><br>
</span><a href="https://urldefense.us/v3/__https:/mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg__;!!PvBDto6Hs4WbVuu7!a0qSHP9p17UYLyqsbzP1_BZYMyQz3GAR0v2LqDlVHS-OzHnN8FyD9Bk09_eVYN-oeFQYTiX1$"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</span></tt></a><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
<br>
</span><o:p></o:p></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).<o:p></o:p></pre>
</div>
</body>
</html>