<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 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@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;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoList, li.MsoList, div.MsoList
{mso-style-link:"List Char";
margin-top:9.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
text-align:justify;
text-indent:-.25in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
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;}
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:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.ListChar
{mso-style-name:"List Char";
mso-style-link:List;
font-family:"Times New Roman",serif;}
.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:35546213;
mso-list-type:simple;
mso-list-template-ids:1741066896;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\2013;
mso-level-tab-stop:.25in;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
font-family:"Times New Roman",serif;}
@list l1
{mso-list-id:460416861;
mso-list-type:hybrid;
mso-list-template-ids:508201132 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1: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><!--[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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">CSTSWG colleagues ---<o:p></o:p></p>
<p class="MsoNormal">In the process of preparing the Modified Parameters Examples annex for the SFW, I had the opportunity to review the SANA Considerations in the SFW, which led to a few issues:<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Regarding Service-Specific OIDs (SFW H2.3), the second paragraph states “The recommendations in those Recommended Standards that specify CSTSes based on this document request SANA to update the CCSDS OID registry by adding the OIDs and
labels contained in the CSTS type specific part of the above identified subtree.” As noted in previous emails, there are serious problems with the version of the OID tree that is currently posted in SANA, and there is an action item to get this straightened
out. It would be desirable to have the SANA registry corrected(and populated) before the publication of SFW Blue-2 so that CSTSes could actually be implemented.<o:p></o:p></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoListParagraph">Also, I find the phrasing “The recommendations in those Recommended Standards that specify CSTSes based on this document request SANA to update …” confusing. Are the recommendation in the Recommended Standards making the request,
or are the Recommended Standards themselves making the request? And in either case, none of the current published or draft CSTS specification (MD, TD, or FF) explicitly “make a request” to SANA to update the registry – they simply state what the values are
in their respective normative Object Identifiers sections. Should we add paragraph(s) to the CSTS Blue Book SANA Considerations sections to explicitly make this request of SANA?<o:p></o:p></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Regarding the Functional Resource Registry (SFW H2.4), we have gone from the CSTS service specification Blue Books normatively specifying the root object identifiers in the Object Identifiers annex (as was done in the MD Blue Book and
the TD Red Book) to deferring assignment of these values to the SANA FR Registry (as is done in the FF service book). To reflect this change in approach, the FF SANA Considerations sections contain the following paragraphs, which have no equivalent in the
MD or TD books:<o:p></o:p></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in">The <span style="letter-spacing:-.1pt">
FF-CSTS</span> relies on the SANA Functional Resource registry to register the following:<o:p></o:p></p>
<p class="MsoList" style="margin-left:.75in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">–<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>the <span style="letter-spacing:-.1pt">FF-CSTS</span> Provider
<span style="mso-fareast-language:FR">Functional Resource</span> Type, registered under the
<span style="font-family:"Courier New"">crossSupportFunctionalities</span> with the classifier
<span style="font-family:"Courier New"">ffCstsProvider</span>;<o:p></o:p></p>
<p class="MsoList" style="margin-left:.75in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">–<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>the first node of the <span style="font-family:"Courier New"">
ffCstsProvider</span> subtree ({<span style="font-family:"Courier New"">ffCstsProvider</span><span style="font-family:"Courier New""> 1})</span>, registered with the classifier
<span style="font-family:"Courier New"">ffCstsProviderParametersId</span>;<o:p></o:p></p>
<p class="MsoList" style="margin-left:.75in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">–<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>the second node of the <span style="font-family:"Courier New"">
ffCstsProvider</span> subtree ({<span style="font-family:"Courier New"">ffCstsProvider</span><span style="font-family:"Courier New""> 2})</span>, registered with the classifier
<span style="font-family:"Courier New"">ffCstsProviderEventsId</span>;<o:p></o:p></p>
<p class="MsoList" style="margin-left:.75in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">–<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>the third node of the <span style="font-family:"Courier New"">
ffCstsProvider</span> subtree ({<span style="font-family:"Courier New"">ffCstsProvider</span><span style="font-family:"Courier New""> 3})</span>, registered with the classifier
<span style="font-family:"Courier New"">ffCstsProviderDirectivesId</span>.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:.75in"><o:p> </o:p></p>
<p class="MsoListParagraph">However, unless I am mistaken, the XML files that are sent to the SANA FR registry do not actually register the parametersId, EventsId, and DirectivesId nodes directly under the service classifier, but instead immediately jump over
those nodes directly to the parameters, events, and directives themselves. If my understanding is correct, then it seems like the above lines are *<b>not</b>* correct, and maybe all that we should be asking SANA to register is the FR Type and assume that
the first-subnode OIDs will be intrinsically derived from them based on the rules specified in the SFW. I say “intrinsically” because no one will be able to query the SANA Registry for (for example) <span style="font-family:"Courier New"">ffCstsProviderParametersId</span>
- the relative OID will just be embedded in all of the registered parameter OIDs. Comments?
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoListParagraph">Finally, the TD Book has not yet been published. Should we consider making the change to defer assignment of the FR Type before it is published as Blue-1, or not “rock the boat” and publish it as-is with the understanding that the
FR Type in the SANA Registry will be “forced” to match the value assigned in the TD Book (19)?<o:p></o:p></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoListParagraph">I’m looking forward to your comments.<o:p></o:p></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoListParagraph">Best regards,<o:p></o:p></p>
<p class="MsoListParagraph">John<o:p></o:p></p>
</div>
</body>
</html>