<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)">
<!--[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:"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:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 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;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Georgia",serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Georgia",serif;
color:windowtext;}
span.EmailStyle22
{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 lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">Erik, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">What I think Holger is referring to is a discrepancy in the SANA Registry that I flagged last year. What SANA currently lists as the “csts” node in
<a href="https://sanaregistry.org/r/oid"><span style="color:windowtext">https://sanaregistry.org/r/oid</span></a> (1.3.112.4.4) is actually the OID for “css”. “csts” should be 1.3.112.4.4.1, and the whole SANA OID tree below that is hosed as a result.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">I’ve appended the email thread identifying this problem and my proposed solution to the bottom of this email.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">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 #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> CSS-CSTS <css-csts-bounces@mailman.ccsds.org>
<b>On Behalf Of </b>Barkley, Erik J (3970) via CSS-CSTS<br>
<b>Sent:</b> Wednesday, March 13, 2019 8:43 PM<br>
<b>To:</b> Holger.Dreihahn@esa.int; css-csts@mailman.ccsds.org<br>
<b>Subject:</b> Re: [Css-csts] Notes from CSTS Telecon#2<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Dear Holger,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Re “…Action HD / Observation: In the SANA CSTS OID subtree registry
<a href="https://sanaregistry.org/r/oid">https://sanaregistry.org/r/oid</a> has OIDs we do not specify in SFW. It has to be clarified where this is coming from…” my understanding is that everything that gets put into SANA is assigned an OID. So this ends up
meaning, if I interpret it correctly an OID defined by CSTS will in fact have an OID assigned for the purpose of the registry (yes, the OID will have an OID). So I think that means you can see OIDs that were not defined by the SFW per se but rather as part
of registry construction. You may want to check Annex A of the Registry Management Policy (<a href="https://public.ccsds.org/Pubs/313x1y1.pdf">https://public.ccsds.org/Pubs/313x1y1.pdf</a>).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">-Erik
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> CSS-CSTS <<a href="mailto:css-csts-bounces@mailman.ccsds.org">css-csts-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b><a href="mailto:Holger.Dreihahn@esa.int">Holger.Dreihahn@esa.int</a><br>
<b>Sent:</b> Friday, March 1, 2019 01:37<br>
<b>To:</b> <a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a><br>
<b>Subject:</b> [Css-csts] Notes from CSTS Telecon#2<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear CSTS Colleagues,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Please find attached the notes from the CSTS Telecon #2. The document is also on the CWE:</span>
<br>
<a href="https://cwe.ccsds.org/css/docs/CSS-CSTS/Meeting%20Materials/2019/Telecons/2019-02-28-TeleconferenceNotes-CSTS-WG.docx?Web=1"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">https://cwe.ccsds.org/css/docs/CSS-CSTS/Meeting%20Materials/2019/Telecons/2019-02-28-TeleconferenceNotes-CSTS-WG.docx?Web=1</span></a>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Comments are welcome.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Best regards,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger</span> <br>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | S-431<br>
+49 6151 90 2233 | </span><a href="http://www.esa.int/esoc"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">http://www.esa.int/esoc</span></a><o:p></o:p></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre>
<pre><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></pre>
<pre><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></pre>
<pre><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></pre>
<pre><span style="font-size:18.0pt;font-family:"Calibri",sans-serif;color:red">--- - email thread from February 2018 --------------------------------------------------------------------------<o:p></o:p></span></pre>
<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"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> John Pietras
<br>
<b>Sent:</b> Wednesday, February 07, 2018 9:18 AM<br>
<b>To:</b> Holger.Dreihahn@esa.int<br>
<b>Cc:</b> Erik.J.Barkley@jpl.nasa.gov; Wolfgang Hell <wo_._he@t-online.de><br>
<b>Subject:</b> RE: SANA "CSTS OID Subtree" fouled up<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Dear Holger,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Yes, I think that it’s absolutely necessary to get the intermediate “css” node in there.
<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 also suggest changing the name of the registry to “CSS OID Subtree” and add the OIDs for crossSupportResources, crossSupportFunctionalities, and agenciesFunctionalities
nodes. This would flesh out the SANA OID registry with all of the nodes that we have identified and “de facto” registered in the CSTS Framework.<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">Also (also?), the “References” column in the registry is currently blank. This could (should?) be updated with a reference to Annexes D and L of the CSTS SFW.
Note that if the OID tree is expanded to include crossSupportResources and agenciesFunctionalities nodes as suggested above, the “References” entry for the agenciesFunctionalities node could also contain a cross-reference to the Functional Resources registry,
since the FR registry is in fact the elaboration of the agenciesFunctionalities node. We could also put some cross-reference in the “header” of the Functional Resources registry back to the CSS OID Subtree registry in general and to the agenciesFunctionalities
node in particular. (My thought here is to supply the readers/CSTS implementers – many of whom may be unfamiliar with OID concepts -as much help as possible in navigating the registries.)<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>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<a href="mailto:Holger.Dreihahn@esa.int">Holger.Dreihahn@esa.int</a> [<a href="mailto:Holger.Dreihahn@esa.int">mailto:Holger.Dreihahn@esa.int</a>]
<br>
<b>Sent:</b> Wednesday, February 07, 2018 2:12 AM<br>
<b>To:</b> John Pietras <<a href="mailto:john.pietras@gst.com">john.pietras@gst.com</a>><br>
<b>Cc:</b> <a href="mailto:Erik.J.Barkley@jpl.nasa.gov">Erik.J.Barkley@jpl.nasa.gov</a>; Wolfgang Hell <<a href="mailto:wo_._he@t-online.de">wo_._he@t-online.de</a>><br>
<b>Subject:</b> Re: SANA "CSTS OID Subtree" fouled up<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hi John,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Thanks a lot for the finding. I think we all agree that the 'css' bit must be there by all means?</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Regards,</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | S-431<br>
+49 6151 90 2233 | </span><a href="http://www.esa.int/esoc"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">http://www.esa.int/esoc</span></a>
<br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">John Pietras <<a href="mailto:john.pietras@gst.com">john.pietras@gst.com</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"<a href="mailto:Holger.Dreihahn@esa.int">Holger.Dreihahn@esa.int</a>" <<a href="mailto:Holger.Dreihahn@esa.int">Holger.Dreihahn@esa.int</a>>,
"<a href="mailto:Erik.J.Barkley@jpl.nasa.gov">Erik.J.Barkley@jpl.nasa.gov</a>" <<a href="mailto:Erik.J.Barkley@jpl.nasa.gov">Erik.J.Barkley@jpl.nasa.gov</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">Wolfgang Hell <<a href="mailto:wo_._he@t-online.de">wo_._he@t-online.de</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">06/02/2018 20:50</span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">SANA "CSTS OID Subtree" fouled up</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<span style="font-family:"Calibri",sans-serif">Folks,</span> <br>
<span style="font-family:"Calibri",sans-serif">I just happened to look at the SANA “CSTS OID Subtree”, and it’s missing the intermediate “css” node, compared with the OID tree laid out in the CSTS Framework. That is, it lists the “csts” node as 1.3.112.4.4,
which is actually the OID for “css”. “csts” should be 1.3.112.4.4.1, but the SANA registry assigns that OID to the “framework” subtree, and so on.
</span><br>
<span style="font-family:"Calibri",sans-serif"> </span> <br>
<span style="font-family:"Calibri",sans-serif">Also kind of strange – the Registry is listed as Approved, but every single entry has a “Provisional” status. Sounds to me like only the existence of the registry has been approved, but none of its contents.</span>
<br>
<span style="font-family:"Calibri",sans-serif"> </span> <br>
<span style="font-family:"Calibri",sans-serif">Anyway, I thought that the “authorities” (you) should be notified so as to add this to your shopping list of things to be straightened out with SANA.</span>
<br>
<span style="font-family:"Calibri",sans-serif"> </span> <br>
<span style="font-family:"Calibri",sans-serif">Best regards,</span> <br>
<span style="font-family:"Calibri",sans-serif">John</span> <o:p></o:p></p>
<pre><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></pre>
</div>
</body>
</html>