<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:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<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:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@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:sans-serif;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Courier;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:120077696;
mso-list-type:hybrid;
mso-list-template-ids:-550064156 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Hi Nestor,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I'll try and answer your second question briefly. The forward and return file services have always been a concern of mine, but given the F-Frame service there was a path forward for handling
them within the overall architecture of services. And that is just what is described in the SCCS-ADD and ARD, in the referenced sections.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">What I find as a concern now is the following:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">Yet another new pair of services being proposed<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">An inadequate description of all that is really involved in producing those services<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">3)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">The failure to recognize that the CCSDS (and IOAG) defined and agreed path forward is to use the F-Frame service, and the associated frame creation, frame multiplexing, and frame
encoding, as the underpinning for any of these new ESLT services<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">4)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">The apparent intent to create new, specialized, services that require all of the F-Frame supplied functions, but without creating the F-Frame first<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I think this is a real mistake as it would, if we did it, use more resources, and resources that should first be creating the F-Frame service framework.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I also happen to think that putting packet services in the ESLT, instead of frame services, is a poor choice, for a variety of reasons that I'll explain if you wish. But my main concern
is the one stated above.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Regards, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in">
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">Nestor Peccia <Nestor.Peccia@esa.int><br>
<b>Date: </b>Monday, September 26, 2016 at 6:52 PM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org>, Erik Barkley <erik.j.barkley@jpl.nasa.gov><br>
<b>Subject: </b>Re: [CESG] IOAG: Service Catalogue #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:"sans-serif","serif"">Peter,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">I have just arrived in Canada and saw your mails</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif";color:red">A reference to SCCS in Sc#1 is a good point
</span><span style="font-size:10.0pt;font-family:"sans-serif","serif""> <span style="color:red">I wiill add a comment in the presentation</span></span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">wrt </span><span style="font-size:10.0pt;font-family:Calibri">the inclusion of these forward CFDP and Packet file services</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif";color:red">I must say that they are there (i.e. forward and return file existing as Draft projects in CWE) since years , but they have been now divided each in two.</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif";color:red">They are thought as single hop for an ABA configuration.</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif";color:red">so my question is: why did you not react earlier (i.e. years ago). ? This needs to be discussed further. No update of the presentation.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">ciao</span> <br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">nestor</span> <br>
<br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">"Shames, Peter M (312B)" <peter.m.shames@jpl.nasa.gov></span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">"Nestor.Peccia@esa.int" <Nestor.Peccia@esa.int>, "Barkley, Erik J (3970)" <erik.j.barkley@jpl.nasa.gov></span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">Cc: </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">"CCSDS Engineering Steering Group - CESG Exec(cesg@mailman.ccsds.org)" <cesg@mailman.ccsds.org></span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">26/09/2016 18:48</span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">Re: [CESG] IOAG: Service Catalogue #1</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#AAAAAA" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:Calibri">Hi Nestor,</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">I note that the SCCS docs are not mentioned in the IOAG Service Catalog #1. Since they are the only docs in CCSDS or IOAG that provide an actual description of how all of these pieces can be fit together to
produce systems they probably should figure prominently. Otherwise it's a lot like handing someone a 1000 piece puzzle with no picture of what it is supposed to represent.</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">I have to say that I am also really puzzled by the inclusion of these forward CFDP and Packet file services. We should be aiming for end to end capabilities, not looking for more ways to carve things up .
Did the IOAG provide any rationale for these services?</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">Ciao, Peter</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<b><span style="font-family:Calibri">From: </span></b><span style="font-family:Calibri">CESG <cesg-bounces@mailman.ccsds.org> on behalf of Nestor Peccia <Nestor.Peccia@esa.int><b><br>
Date: </b>Friday, September 16, 2016 at 7:12 AM<b><br>
To: </b>Erik Barkley <erik.j.barkley@jpl.nasa.gov><b><br>
Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><b><br>
Subject: </b>Re: [CESG] IOAG: Service Catalogue #1</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">Margherita and Erik</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
Thanks for the comments. I will include them in the CESG presentation to IOAG</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
Please let me know if my assumption is correct about the additional "draft Projects" to be included, such that our ICPA fully covers all IOAG Serv Cat 1 requests</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
It should also be noted that some of the current "ghost projects" had to be deleted and other updated./ promoted to "Draft Projects"</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif";color:red"><br>
NOTE: <br>
"Ghost projects" were introduced at the time of the ICPA creation (by Mike Kearney and Adrian Hooke) allowing to have a reference for IOAG. If you go to the ICPA by clicking on some of the below described Projects you will get the Project view, even when is
not listed anywhere as approved or draft.</span> <br>
<b><u><span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
CSTS Forward File Service </span></u></b><span style="font-size:10.0pt;font-family:"sans-serif","serif"">
<br>
To be deleted as ghost Project (by Secretariat) and replaced by <span style="color:blue">
2 new Draft Projects (to be created by AD/DAD)</span></span> <br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">1. <span style="color:blue">CSTS Forward CFDP File Service</span></span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">2. <span style="color:blue">CSTS Forward Packets File Service</span></span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""> </span> <b><u><span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
CSTS Return File Service</span></u></b><b><span style="font-size:10.0pt;font-family:"sans-serif","serif"">
</span></b><span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
To be deleted as ghost Project (by Secretariat) and replaced by <span style="color:blue">
2 new Draft Projects (to be created by AD/DAD)</span></span> <br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">1. <span style="color:blue">CSTS Return CFDP File Service</span></span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">2. <span style="color:blue">CSTS Return Packets File Service</span></span>
<br>
<b><u><span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
CSTS D-DOR Data Service</span></u></b><span style="font-size:10.0pt;font-family:"sans-serif","serif"">
<br>
To be checked and updated (if needed) by AD/DAD. <span style="color:blue">Secretariat shall be asked to redefine "ghost Project" as Draft one</span></span>
<br>
<b><u><span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
CSTS Offline Radio Metric Service (Validated Data Radio Metric Service )</span></u></b>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
To be checked and updated (if needed) by AD/DAD. <span style="color:blue">Secretariat shall be asked to redefine "ghost Project" as Draft one</span></span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
ciao</span> <span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
nestor</span> <br>
<span style="font-size:10.0pt;font-family:"Courier New"">This message and any attachments are intended for the use of the addressee or addressees only.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">content is not permitted.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">If you received this message in error, please notify the sender and delete it from your system.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">Emails can be altered and their integrity cannot be guaranteed by the sender.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New""> </span> <br>
<span style="font-size:10.0pt;font-family:"Courier New"">Please consider the environment before printing this email.</span>
<o:p></o:p></p>
<pre>This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre>content is not permitted.<o:p></o:p></pre>
<pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Please consider the environment before printing this email.<o:p></o:p></pre>
</blockquote>
</div>
</body>
</html>