<html 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)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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:1340041770;
mso-list-type:hybrid;
mso-list-template-ids:276067992 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 lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="NL">Dear Erik, Holger, Tom, et al,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="NL"><o:p> </o:p></span></p>
<p class="MsoNormal">Please accept this late input from SEA on this poll. I took the time to actually review the spec in some detail and it took rather longer than I expected. I was hoping that this FF-CSTS spec would meet all of the planned requirements
for this forward frame service. Unless I somehow overlooked some important features that are documented deep in the bowels of this 218 page specification I am afraid that I have to conclude that it has missed the mark.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The “mark” in my understanding, is that this spec was supposed to define the list of features that follows below. These are drawn from the original SISG Space Internetworking Strategy report that first defined the features of this forward
frame service intended to accommodate DTN (and IP) traffic, from the SCCS-ARD/ADD where these features were documented in the context of the rest of the CCSDS protocol stacks and Earth Space Link Terminal (ESLT, otherwise known as a ground station plus its
associated control center elements), and the features that already existed in the EF-CLTU Orange Book that was created because there was no other documented service for handling the synchronous AOS frame protocol for forward links.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Ability to provide an “SLE-like” forward link service for synchronous link protocols, initially AOS, but now to include USLP<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Provide encoding in the ESLT for this forward link frame stream<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Ability to accept input frame streams from more than one user source<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Ability to multiplex frame streams from all of the input sources, including some that are not directly from FF-CSTS itself<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Ability to keep a synchronous forward link filled, if necessary by inserting fill frames in the ESLT<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Ability to integrate the protocol PDUs from DTN, IP, CFDP, or other data sources, from “agents” instantiated in the ESLT, to create frames that encapsulate these PDUs, and to integrate
these in the multiplexed frame stream (see items 3 & 4)<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As best I can tell this spec fails to accomplish items 5 and 6 at all, and it appears to give only passing acknowledgement to items 2 or 4. These are mentioned as being features that are needed somewhere in the ESLT, but there is not a
section of the document, nor even an informative annex, let alone a normative one, that would suggest what was really intended nor how to accomplish it. In my judgement this is a significant oversight and renders this document inadequate to the task at hand
which was to document how these services were to be provisioned and integrated.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Unfortunately, from my point of view, instead of addressing these absolutely required services the document as presented spends a lot of “real estate” documenting how this new service can be made to handle TC forward asynchronous frames.
Since there is already a perfectly serviceable SLE F-CLTU that provides this service this seems like an unnecessary effort. The only conceivable rationale that occurs to me is that this TC forward service is very much like that needed for USLP variable length
frame forward service. That said, I really have to question whether it would have been better to just modify SLE F-CLTU to accommodate USLP variable length frames instead of weighing this document down with this added baggage.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It appears that in this document we got far fewer of the essential features than were required and, at the same time, more features than were really useful.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">While I recognize that a large amount of work has been expended to get this document to this point, in my estimation it falls far short of what is really required. It does not provide all of the features called for in the IOAG SISG, nor
that were documented in the SCCS-ARD Magenta Book, nor does it appear to provide all of the features in the F-CLTU Orange Book which has for years been supporting major operational missions. It was intended to provide services that could meet all of these
requirements, and it seems to have failed to do so.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Accordingly, I cannot support publishing this document in its current form.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">With respect, Peter Shames<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:Helvetica">________________________________________________________<br>
<br>
Peter Shames<br>
CCSDS Systems Engineering Area Director<br>
<br>
Jet Propulsion Laboratory, MS 301-490<br>
California Institute of Technology<br>
Pasadena, CA 91109 USA <br>
<br>
Telephone: +1 818 354-5740, Fax: +1 818 393-6871<br>
<br>
Internet: <a href="Peter.M.Shames@jpl.nasa.gov"><span style="color:blue">Peter.M.Shames@jpl.nasa.gov</span></a><br>
________________________________________________________<br>
<br>
We must recognize the strong and undeniable influence that our language exerts on our ways of thinking and, in fact, delimits the abstract space in which we can formulate - give form to - our thoughts.<br>
<br>
Niklaus Wirth</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>