<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=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.ms-sitemapdirectional
{mso-style-name:ms-sitemapdirectional;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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 bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Wolfgang,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">You have been keeping very busy cranking out these SLE Pink Sheets. I hope this next round will result in new Blue Books.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I have taken a quick look at the F-CLTU book this morning to see how you have covered the material in the production-status/PLOP CMM/link events (e.g., frequency
sweep completed) table that we worked on two years ago, and see that you have covered part of the material as NOTEs in Annex B. However, as currently constructed, those NOTEs appear to only describe the effects on F-CLTU production status given that, for example,
the PLOP is in CMM-XYZ. It does not appear to address how the CMM itself is affected by the link events. This is a topic of confusion and interest within parts of NASA that until now have simple offered a forward bitstream service and are just now being required
to implement SLE and in particular the lowest layers of the Telecommand stack needed for F-CLTU. It was the questions that I was getting about this larger set of relationships that I was trying to address and clarify when I developed the set of state tables
that you and I subsequently refined in Cleveland and in the months following the Cleveland meeting. I was a bit disappointed that that larger set of relationships did not get covered in the F-CLTU Pink Book.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">On the other hand, I realize that the relationship of CMM to link events is not really the purview of the F-CLTU and FSP books – it should be defined in the
documents produced by the Space Link Service (SLS) Area. One option would be to follow-up with SLS to see if they would be willing to incorporate the material in their formal documentation. However, as this would be a new topic for them, I anticipate that
it might take some time for them to consider the proposal and get it into their program of work. And SLS might even decline to specify a single definitive set of relationships among CMMs and link events. In the meantime, space data systems are being developed
by people who lack the guidance as to how these various aspects are all supposed to work together.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I propose that the F-CLTU and FSP book contain an informative annex containing the “larger” state table, with the explanation that these are the state relationships
that are assumed by the F-CLTU and FSP books. If and when SLS defines those relationships in normative documentation, future versions of the F-CLTU and FSP books can simply reference those specifications.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Finally, a small technical point on Annex B of the F-CLTU Pink Sheets. Annex B is a normative annex, but the relationships among production status and CMMs
are described in Notes. By definition, Notes are informative – if the material that these Notes contain are supposed to be normative, then they must be documented as requirements and not Notes. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">John
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> css-csts-bounces@mailman.ccsds.org [mailto:css-csts-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Wolfgang Hell<br>
<b>Sent:</b> Monday, September 29, 2014 4:58 AM<br>
<b>To:</b> CCSDS_CSTSWG (css-csts@mailman.ccsds.org)<br>
<b>Subject:</b> [Css-csts] F-CLTU Pink Book<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear CSTS WG Members,<br>
<br>
I have uploaded to the CWE ( <a href="http://cwe.ccsds.org/css">Cross Support Services Area (CSS)</a> >
<a href="http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D">
Documents</a> > <a href="http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DCSTS&View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D">
CSS-CSTS</a> > <a href="http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DCSTS%2FCWE%20Private&View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D">
CWE Private</a> > <span class="ms-sitemapdirectional">SLE Services)</span> the document "Pink FCLTU 912x1b3ec1 20140925" for your review. I believe that this version is consistent with all changes the WG had agreed upon. The remaining SLE book (FSP) will follow
soon. Please note that as work on the Pink Books progresses, further changes in the common ASN.1 modules will become necessary and therefore you should not regard in particular the first ASN.1 module in Pink Books uploaded so far as final.<br>
<br>
Best regards,<br>
Wolfgang <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>