<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: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:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{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-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">CSTSWG colleagues ---<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">At yesterday’s CSTSWG (11 May), I took the action to check if the errors in the SANA Registry CSS OID subtree and the Functional Resource registry are still present.
Unfortunately, they still are. This shouldn’t be a surprise since the registry was last updated on 14 January and I wrote my last email on the subject on 4 March (see below).<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">But what I find strange is that I was not able to get the same “view” of the OID tree that Holger shared during our meeting. For example, when I view the OID
tree using Chrome on Windows, I see all of the parameters (Holger sees no parameters) and I see both 401
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%">Transmission and Reception FR Sets, but the labels are all fouled up – e.g., “CCSDS 401 Physical
Channel Reception” is labelled “stratum” and “Physical Channel” is labeled “resource_set”. Also, the FR Sets and their OIDs are displayed all out of order.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%">As I said in my email of 4 March, I don’t have the time or resources to try to discover
and catalog all of the errors. It’s a mess.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%">John</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%"><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"> John Pietras
<br>
<b>Sent:</b> Thursday, March 4, 2021 11:59 AM<br>
<b>To:</b> Holger.Dreihahn@esa.int<br>
<b>Cc:</b> Erik.J.Barkley@jpl.nasa.gov<br>
<b>Subject:</b> RE: SANA CSS OID Registry is still partially wrong<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hi, Holger. I think that point 1 is something that they just fixed in the past few weeks (i.e., since I sent my email below). However, even there, it has two
minor “errors” – if we want the OID tree to be consistent with the SFW, the label for 1.3.112.4.4.2 should be “crossSupportResources”, not “crossSupport Resources”, and the label for 1.3.112.4.4.2.1 should be “crossSupportFunctionalities” not “Functional Resources”.
But yes, if these two label/classifier issues are cleaned up, point 1 has basically already been addressed.<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:#1F4E79">However, I see from this latest change that they added information to the OID tree itself (which, as I recall, is what we asked them to do). Unfortunately, there
are many glitches with that, regarding “stratum” vs “resource set”. In most cases, they got the “stratum” and “resource set” labels wrong. E.g., “AOS Space Link Protocol Transmission” is listed as the “stratum” and under it “Space Link Protocol” is listed
as the “resource set” (they are of course reversed). See also CCSDS 401 Physical Channel Reception, CCSDS 401 Physical Channel Reception,
<span style="background:white">Cfdp File Data Production, </span>Fixed Length Frame (FLF) Unified Space Link Protocol Transmission, Fixed Length Frame Synchronization, Channel Encoding, and OID Generation, Fixed-Length Frame (FLF) Synchronization and Channel
Decoding, <span style="background:white">Frame Data Sink, </span>Monitored Data CSTS, and Real-Time Radiometric Data Collection.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79">It’s also not clear what the logic is for the ordering – the OIDs are all out of sequence. That may be to try to align the tree in alphabetical order of the OID
labels (classifiers) but even that isn’t followed. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79">Sorry to throw this new set of problems back to you.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79">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> Thursday, March 4, 2021 11:21 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><br>
<b>Subject:</b> RE: SANA CSS OID Registry is still partially wrong<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">HiJohn,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I was just about to forward the email, but looking at the CSS OID Structure I see:</span>
<br>
<img border="0" width="1180" height="339" id="_x0000_i1025" src="cid:image001.jpg@01D74716.7E2ED510"><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">So your point 1 is addressed, right?</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">For point 2 - 4, yes, it looks wrong.</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>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | H-293<br>
+49 6151 90 2233 | </span><a href="https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.esa.int%2Fesoc&data=04%7C01%7Cjohn.pietras%40gst.com%7C2e53035c36dd4544cac008d8df298437%7C17917f83951e48839dd6b11685623b38%7C1%7C0%7C637504716720045186%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ioX4whDty%2BHGyZ8DAvnjzlQZwOmGcHo7kle8fZPWEE0%3D&reserved=0"><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>></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">"<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">Date: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">04/03/2021 17:12</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">RE: SANA CSS OID Registry is still partially wrong</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-family:"Calibri",sans-serif;color:#004080">Thanks, Holger. I had mentioned to Peter that we were having some difficulty getting SANA to get the OID registry right, and he of course was interested. I told him that we were still trying to work
the issue “through the proper channels”, but if we can’t get out of this “I fixed it/no you really didn’t” loop we may have to escalate the concern.
</span><br>
<span style="font-family:"Calibri",sans-serif;color:#004080"> </span> <br>
<span style="font-family:"Calibri",sans-serif;color:#004080">Best regards,</span>
<br>
<span style="font-family:"Calibri",sans-serif;color:#004080">John</span> <br>
<span style="font-family:"Calibri",sans-serif;color:#004080"> </span> <br>
<b><span style="font-family:"Calibri",sans-serif">From:</span></b><span style="font-family:"Calibri",sans-serif">
<a href="mailto:Holger.Dreihahn@esa.int">Holger.Dreihahn@esa.int</a> [</span><a href="mailto:Holger.Dreihahn@esa.int"><span style="font-family:"Calibri",sans-serif">mailto:Holger.Dreihahn@esa.int</span></a><span style="font-family:"Calibri",sans-serif">]
<b><br>
Sent:</b> Thursday, March 4, 2021 11:02 AM<b><br>
To:</b> John Pietras <<a href="mailto:john.pietras@gst.com">john.pietras@gst.com</a>><b><br>
Cc:</b> <a href="mailto:Erik.J.Barkley@jpl.nasa.gov">Erik.J.Barkley@jpl.nasa.gov</a><b><br>
Subject:</b> RE: SANA CSS OID Registry is still partially wrong</span> <br>
<br>
<span style="font-family:"Arial",sans-serif">Hi John,</span> <span style="font-family:"Arial",sans-serif">
<br>
I will forward it to SANA, but they are not really responsive. For our FRM request they just replied that this is 'new' and will be addressed at some point. The question when is not answered.</span>
<br>
<span style="font-family:"Arial",sans-serif"><br>
Best regards,</span> <span style="font-family:"Arial",sans-serif"><br>
Holger</span> <br>
<span style="font-family:"Arial",sans-serif"><br>
Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | H-293<br>
+49 6151 90 2233 | </span><a href="https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.esa.int%2Fesoc&data=04%7C01%7Cjohn.pietras%40gst.com%7C2e53035c36dd4544cac008d8df298437%7C17917f83951e48839dd6b11685623b38%7C1%7C0%7C637504716720045186%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ioX4whDty%2BHGyZ8DAvnjzlQZwOmGcHo7kle8fZPWEE0%3D&reserved=0"><span style="font-family:"Arial",sans-serif">http://www.esa.int/esoc</span></a>
<br>
<br>
<br>
<span style="font-family:"Arial",sans-serif;color:#5F5F5F"><br>
From: </span><span style="font-family:"Arial",sans-serif">"John Pietras" <</span><a href="mailto:john.pietras@gst.com"><span style="font-family:"Arial",sans-serif">john.pietras@gst.com</span></a><span style="font-family:"Arial",sans-serif">></span>
<span style="font-family:"Arial",sans-serif;color:#5F5F5F"><br>
To: </span><span style="font-family:"Arial",sans-serif">"</span><a href="mailto:Holger.Dreihahn@esa.int"><span style="font-family:"Arial",sans-serif">Holger.Dreihahn@esa.int</span></a><span style="font-family:"Arial",sans-serif">" <</span><a href="mailto:Holger.Dreihahn@esa.int"><span style="font-family:"Arial",sans-serif">Holger.Dreihahn@esa.int</span></a><span style="font-family:"Arial",sans-serif">></span>
<span style="font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Cc: </span><span style="font-family:"Arial",sans-serif">"</span><a href="mailto:Erik.J.Barkley@jpl.nasa.gov"><span style="font-family:"Arial",sans-serif">Erik.J.Barkley@jpl.nasa.gov</span></a><span style="font-family:"Arial",sans-serif">" <</span><a href="mailto:Erik.J.Barkley@jpl.nasa.gov"><span style="font-family:"Arial",sans-serif">Erik.J.Barkley@jpl.nasa.gov</span></a><span style="font-family:"Arial",sans-serif">></span>
<span style="font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Date: </span><span style="font-family:"Arial",sans-serif">04/03/2021 16:57</span>
<span style="font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Subject: </span><span style="font-family:"Arial",sans-serif">RE: SANA CSS OID Registry is still partially wrong</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" 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;color:#004080"><br>
Hi, Holger.</span> <span style="font-family:"Calibri",sans-serif;color:#004080"><br>
I just remembered that I sent this to you a few weeks ago. Have you had the chance to forward the comments to the SANA guys, and if so have they responded in any way?</span>
<span style="font-family:"Calibri",sans-serif;color:#004080"><br>
</span> <span style="font-family:"Calibri",sans-serif;color:#004080"><br>
Thanks.</span> <span style="font-family:"Calibri",sans-serif;color:#004080"><br>
</span> <span style="font-family:"Calibri",sans-serif;color:#004080"><br>
Best regards,</span> <span style="font-family:"Calibri",sans-serif;color:#004080">
<br>
John <br>
</span> <b><span style="font-family:"Calibri",sans-serif"><br>
From:</span></b><span style="font-family:"Calibri",sans-serif"> John Pietras <b><br>
Sent:</b> Friday, February 19, 2021 12:08 PM<b><br>
To:</b> </span><a href="mailto:Holger.Dreihahn@esa.int"><span style="font-family:"Calibri",sans-serif">Holger.Dreihahn@esa.int</span></a><b><span style="font-family:"Calibri",sans-serif"><br>
Cc:</span></b><span style="font-family:"Calibri",sans-serif"> </span><a href="mailto:Erik.J.Barkley@jpl.nasa.gov"><span style="font-family:"Calibri",sans-serif">Erik.J.Barkley@jpl.nasa.gov</span></a><b><span style="font-family:"Calibri",sans-serif"><br>
Subject:</span></b><span style="font-family:"Calibri",sans-serif"> SANA CSS OID Registry is still partially wrong</span>
<span style="font-family:"Calibri",sans-serif"><br>
</span> <span style="font-family:"Calibri",sans-serif"><br>
Hi, Holger.</span> <span style="font-family:"Calibri",sans-serif"><br>
I just checked the SANA registry to see (among other things) if they’ve fixed the problems with what used to be called the CSTS OID registry. The registry was indeed updated on 2021-01-13 an renamed “CSS OID Subtree”, but there are still multiple problems with
it:</span> <span style="font-family:"Calibri",sans-serif"><br>
1. Although it purports to be the “CSS OID”, it still starts with the subnodes of the
<b>csts</b> node (i.e., the<b> framework</b> subnode, 1.3.112.4.4.1.1), not the <b>
css</b> node itself (1.3.112.4.4) or even the subnodes of the <b>css</b> node (<b>csts</b>, 1.3.112.4.4.1). The problem with that is that the
<b>crossSupportResources</b> (1.3.112.4.4.2) subnode under <b>css</b> is not registered anywhere as far as I can tell. Furthermore, we need to register the
<b>crossSupportFunctionalities</b> (1.3.112.4.4.2.1) and <b>agenciesFunctionalities</b> (1.3.112.4.4.2.2) subnodes under
<b>crossSupportResources</b>. Futhermore, because SANA ha not registered either the
<b>css</b> OID or the <b>csts</b> OID itself as being under the authority of CSSA, it appears that SANA could unilaterally assign the 1.3.112.4.4.2 subnode to some other (non-CSS) use. Finally, the Authority for this registry is listed as CCSDS.CSS.CSTS – technically,
since it’s supposed to be the CSS OID subtree, I think that the Authority should be CCSDS.CSS. Other OIDs that the Area needs to register should be done so under the css node, and those might not have anything to do with the CSTS WG (an in any case, since
WGs are supposed to be “temporary”, authority over the<b> css</b> node should be with the CSS Area anyway).
<u>Proposed resolution: (a) Get SANA to include the </u>css <u>and </u>csts<u> OIDs in this registry so that CSSA is given control over everything that appears under the
</u>css<u> node; and (b) have the <b>crossSupportResources</b> (1.3.112.4.4.2), <b>
crossSupportFunctionalities</b> (1.3.112.4.4.2.1), and <b>agenciesFunctionalities</b> (1.3.112.4.4.2.2) subnodes added to the OIDs that are registered under the
<b>css </b>node</u>.</span> <span style="font-family:"Calibri",sans-serif"><br>
2. Under the <b>modules</b> subnode, 1.3.112.4.4.1.1.1, the CSS OID registry values start to go wrong with 1.3.112.4.4.1.1.1.3, which should be
<b>common-types</b> but the SANA registry has as <b>service-type</b>. There are multiple other errors under the
<b>modules</b> subnode dealing with missing, misnamed, and/or wrong OID values that I’m not going to identify individually.
<u>Proposed resolution: Get SANA to fix it.</u></span> <span style="font-family:"Calibri",sans-serif">
<br>
3. Under the <b>framework</b> subnode, 1.3.112.4.4.1.1, the CSS OID registry values start to go wrong with 1.3.112.4.4.1.1.2, which should be
<b>operations</b> but the SANA registry has as a totally bizarre <b>attributes</b> node, with
<b>scname,</b> <b>antenna</b>, and <b>tsprofile subnodes</b>. <u>Proposed resolution: Get rid of the
<b>attributes</b> subtree and assign 1.3.112.4.4.1.1.2 to the <b>operations</b> subtree.</u></span>
<span style="font-family:"Calibri",sans-serif"><br>
4. Even once the <b>operations</b> node is correctly given the correct 1.3.112.4.4.1.1.2 OID , what’s under it is screwed up from the very beginning. 1.3.112.4.4.1.1.2.1 should be
<b>bindInvocation</b>, but the first label under the operations node in the CSS OID registry is given as
<b>execDirectiveInvocation</b>. There are numerous other mistakes.<u> Proposed resolution: Get SANA to fix it.</u></span>
<span style="font-family:"Calibri",sans-serif"><br>
At this point, I’ve given up trying to unearth all of the problems with the CSS OID registry as currently published. I don’t know where the problem lies here – does SANA not have the latest OID assignments as made in the SFW, or do they have the information
and are just ignoring it?</span> <span style="font-family:"Calibri",sans-serif">
<br>
Finally, although this is not strictly an issue for the OIDs under the <b>css</b> node, this is a concern for CSSA and CSTSWG anyway. One used to be able to see the complete CCSDS OID tree (i.e., the
<b>ccsds</b> node (1.3.112.4) and everything underneath it. I can no longer find that larger OID tree on the SANA website. Why this is a concern for CSSA/CSTSWG is that as far as SANA is concerned the
<b>space-link-extension</b> node (1.3.112.4.3) is no longer reserved for SLE services. [The allocation of the
<b>space-link-extension</b> node as 1.3.112.4.3 - that is, directly under the <b>
ccsds </b>node – predates the existence of the current “Area” structure of CCSDS, and to my understanding SLE was the first set of CCSDS standards to use ISO OIDs, so they got put directly under
<b>ccsds</b>.] We need to ensure that SANA can’t “give away” 1.3.112.4.3 to some other group. Proposed resolution: Either (a) get SANA to make the full CCSDS OID tree visible on the SANA site, and make sure that 1.3.112.4.3 is already allocated as
<b>space-link-extension</b>, or (b) create a Space Link Extension OID registry with CSSA as the controlling authority.</span>
<span style="font-family:"Calibri",sans-serif"><br>
Best regards,</span> <span style="font-family:"Calibri",sans-serif"><br>
John</span> <span style="font-family:"Calibri",sans-serif"><br>
</span> <br>
<span style="font-family:"Courier New"">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or</span>
<br>
<span style="font-family:"Courier New"">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received</span>
<br>
<span style="font-family:"Courier New"">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect</span>
<br>
<span style="font-family:"Courier New"">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (</span><a href="mailto:dpo@esa.int"><span style="font-family:"Courier New"">dpo@esa.int</span></a><span style="font-family:"Courier New"">).</span>
<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>
</div>
</body>
</html>