<font size=2 face="sans-serif">Peter,</font>
<br><font size=2 face="sans-serif"> I
am sure I really understand what you mean for </font><font size=2 face="Calibri"> "packet
/ file / frame plumbing"</font><font size=2 face="sans-serif">?</font>
<br><font size=2 face="sans-serif">It looks to me that the description
in Catalog 1 for the four files services (two directions x two flavours)
do underline that the service provide will have to do quite some work (plumbing?)
about Space/Encapsulation Packets, reliable/unreliable transfer, COP usage,</font>
<br><font size=2 face="sans-serif">You also say the CSTS F-Frame
is supposed to provide most of this plumbing but yor comment is ot about
IOAG Catalog bu rather about the service an agency should select.</font>
<br><font size=2 face="sans-serif">In fact the IOAG File services suppose
a file is passed from A to B, while F-Frame supposes frames are passed
fromA to B.</font>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br>
<br><font size=2 face="sans-serif">Gian Paolo</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Shames, Peter
M (312B)" <peter.m.shames@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"Nestor.Peccia@esa.int"
<Nestor.Peccia@esa.int>, "CCSDS Engineering Steering Group -
CESG Exec(cesg@mailman.ccsds.org)" <cesg@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">26/09/2016 21:33</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [CESG] IOAG:
Service Catalogue #1</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"CESG"
<cesg-bounces@mailman.ccsds.org></font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Calibri">Nestor,</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">I know that this is a late input, but after
reading the IOAG Svc Cat #1 I have a very real concern that I think needs
to be surfaced. Four new services have been introduced, the "Forward/Return
CFDP-File Service Type" and the "Forward/Return PACKETS-File
Service Type". In reading through the descriptions I find that
they mention certain SM characteristics, but fail to acknowledge the required
presence of a whole lot of "packet / file / frame plumbing" that
is missing in most of our current systems. Of particular concern,
from a standards and logistics point of view, is that these new standards
require a lot of the "plumbing" that CSTS F-Frame is supposed
to provide, but make no mention of that standard. In fact, the precursor
standards, "Forward Synchronous Encoded Frame Service Type" has
been dropped, and what is left is just some sort of weak "forward
reference" to a CSTS F-Frame service.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">I think this is a huge mistake and that
we should push back on it.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Here is the logic behind this:</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">1) FF-CSTS includes
the key services and functions that are required for anything like forward
file, or forward packet, or forward DTN to work.</font>
<br><font size=2 face="Calibri">2) These functions
include, quoting from the report "Users shall be aware that IOAG Service
Catalog 2 foresees a future CSTS Forward Frame Service that is assumed
will provide a forward service for [AOS] and [TC-DLP] frames implementing
multiplexing, frame fill and coding in the provider and implementing the
full stack down to the physical layer."</font>
<br><font size=2 face="Calibri">3) In order to implement
a forward file or packet service all of these functions, <b><i>plus</i></b>
frame creation, must be present in the service provider.</font>
<br><font size=2 face="Calibri">4) It makes little
technical sense to create forward file and forward packet services, as
new separate services that embed all of these function, instead of creating
the FF-CSTS service and then building CFDP and Packet service "plug-ins"
on top of that which use this underlying service.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">In fact, this approach is exactly how the
forward file service is now described in the SCCS-ADD. I draw your
attention to CCSDS 901.1-M-1, sec 5.2.2.2 and sec 6.2.2.2. In fact,
fig 6-4 shows the relationships among SM, CSTS F-Frame, the associated
functions that are required, including ranging, and also SLE R-AF, and
fig 6-8 (ABA ESLT Forward-File Protocol Building Blocks) shows how F-Frame
and Fwd frame are designed to be integrated. Any sort of forward
packet service ought to just be a variant of this.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">My recommendation is that CCSDS push back
on this IOAG Cat 1 request for two new stand alone services and instead
argue that CSTS F-Frame should be done first, and these other new service
built upon that base.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Regards, Peter</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=3 face="Calibri"><b>From: </b>CESG <cesg-bounces@mailman.ccsds.org>
on behalf of Nestor Peccia <Nestor.Peccia@esa.int><b><br>
Date: </b>Thursday, September 15, 2016 at 3:43 AM<b><br>
To: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><b><br>
Subject: </b>[CESG] IOAG: Service Catalogue #1</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 color=red face="sans-serif"><u>REMINDER</u></font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="sans-serif"><br>
Please let me have your comments (in particular from the CSS Area) by 22nd
Sept 2016 cob.</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="sans-serif"><br>
ciao</font><font size=3 face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
nestor</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="sans-serif"><br>
============================</font><font size=3 face="Times New Roman">
</font><font size=2 face="sans-serif"><br>
Dear all,</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="sans-serif"><br>
Please find attached the Service Catalogue #1 that has been approved
by the IOAG. </font><font size=3 face="Times New Roman"><br>
</font><font size=2 face="sans-serif"><br>
You should be aware that the final approval regarding the editorial updates
from NASA is still pending. There is an on-going discussion </font><font size=2 face="Calibri">concerning
service management “function” vs. service management “service”.</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="sans-serif"><br>
However, this version is good enough to be processed by the CESG.</font><font size=3 face="Times New Roman">
<br>
<br>
</font><font size=2 face="sans-serif"><br>
[attachment "IOAG Service Catalog One.v2.0-Approved-20160823.pdf"
deleted by Nestor Peccia/esoc/ESA] <br>
[attachment "IOAG Service Catalog One.v2.0-Approved-20160823withBars.pdf"
deleted by Nestor Peccia/esoc/ESA] </font><font size=3 face="Times New Roman"><br>
</font><font size=2 face="sans-serif"><br>
CESG will address this update during our next webex.</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="sans-serif"><br>
Main changes are :</font><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="sans-serif">1. forward
/ return CFDP file over terrestrial generic file</font><font size=3 face="Times New Roman">
</font>
<br><font size=2 face="sans-serif">2. forward
/ return packet file service over terrestrial generic file</font><font size=3 face="Times New Roman">
</font>
<br><font size=2 face="sans-serif">3. Service
Management functions</font>
<br><font size=3 face="Times New Roman"><br>
</font><font size=2 face="sans-serif"><br>
ciao</font><font size=3 face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
nestor</font><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Courier New">This message and any attachments are
intended for the use of the addressee or addressees only.</font>
<br><font size=2 face="Courier New">The unauthorised disclosure, use, dissemination
or copying (either in whole or in part) of its</font>
<br><font size=2 face="Courier New">content is not permitted.</font>
<br><font size=2 face="Courier New">If you received this message in error,
please notify the sender and delete it from your system.</font>
<br><font size=2 face="Courier New">Emails can be altered and their integrity
cannot be guaranteed by the sender.</font>
<br><font size=2 face="Courier New"> </font>
<br><font size=2 face="Courier New">Please consider the environment before
printing this email.</font><tt><font size=2>_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org<br>
</font></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><tt><font size=2>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</font></tt></a><tt><font size=2><br>
</font></tt>
<br><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE>