[Css-csts] Notes from CSTS Telecon#2

Thu Mar 14 13:23:49 UTC 2019

Erik,
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 https://sanaregistry.org/r/oid (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.

I've appended the email thread identifying this problem and my proposed solution to the bottom of this email.

John

From: CSS-CSTS <css-csts-bounces at mailman.ccsds.org> On Behalf Of Barkley, Erik J (3970) via CSS-CSTS
Sent: Wednesday, March 13, 2019 8:43 PM
To: Holger.Dreihahn at esa.int; css-csts at mailman.ccsds.org
Subject: Re: [Css-csts] Notes from CSTS Telecon#2

Dear Holger,

Re "...Action HD / Observation: In the SANA CSTS OID subtree registry https://sanaregistry.org/r/oid 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 (https://public.ccsds.org/Pubs/313x1y1.pdf).

Best regards,
-Erik

From: CSS-CSTS <css-csts-bounces at mailman.ccsds.org<mailto:css-csts-bounces at mailman.ccsds.org>> On Behalf Of Holger.Dreihahn at esa.int<mailto:Holger.Dreihahn at esa.int>
Sent: Friday, March 1, 2019 01:37
To: css-csts at mailman.ccsds.org<mailto:css-csts at mailman.ccsds.org>
Subject: [Css-csts] Notes from CSTS Telecon#2

Dear CSTS Colleagues,
Please find attached the notes from the CSTS Telecon #2. The document is also on the CWE:
https://cwe.ccsds.org/css/docs/CSS-CSTS/Meeting%20Materials/2019/Telecons/2019-02-28-TeleconferenceNotes-CSTS-WG.docx?Web=1

Comments are welcome.

Best regards,
Holger

Holger Dreihahn
European Spacecraft Operations Centre | European Space Agency | S-431
+49 6151 90 2233 | http://www.esa.int/esoc

This message is intended only for the recipient(s) named above. It may contain proprietary information and/or

protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received

this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect

personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo at esa.int<mailto:dpo at esa.int>).

--- - email thread from February 2018 --------------------------------------------------------------------------

From: John Pietras
Sent: Wednesday, February 07, 2018 9:18 AM
To: Holger.Dreihahn at esa.int
Cc: Erik.J.Barkley at jpl.nasa.gov; Wolfgang Hell <wo_._he at t-online.de>
Subject: RE: SANA "CSTS OID Subtree" fouled up

Dear Holger,
Yes, I think that it's absolutely necessary to get the intermediate  "css" node in there.

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.

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.)

Best regards,
John

From: Holger.Dreihahn at esa.int<mailto:Holger.Dreihahn at esa.int> [mailto:Holger.Dreihahn at esa.int]
Sent: Wednesday, February 07, 2018 2:12 AM
To: John Pietras <john.pietras at gst.com<mailto:john.pietras at gst.com>>
Cc: Erik.J.Barkley at jpl.nasa.gov<mailto:Erik.J.Barkley at jpl.nasa.gov>; Wolfgang Hell <wo_._he at t-online.de<mailto:wo_._he at t-online.de>>
Subject: Re: SANA "CSTS OID Subtree" fouled up

Hi John,
Thanks a lot for the finding. I think we all agree that the 'css' bit must be there by all means?

Regards,
Holger

Holger Dreihahn
European Spacecraft Operations Centre | European Space Agency | S-431
+49 6151 90 2233 | http://www.esa.int/esoc

From:        John Pietras <john.pietras at gst.com<mailto:john.pietras at gst.com>>
To:        "Holger.Dreihahn at esa.int<mailto:Holger.Dreihahn at esa.int>" <Holger.Dreihahn at esa.int<mailto:Holger.Dreihahn at esa.int>>, "Erik.J.Barkley at jpl.nasa.gov<mailto:Erik.J.Barkley at jpl.nasa.gov>" <Erik.J.Barkley at jpl.nasa.gov<mailto:Erik.J.Barkley at jpl.nasa.gov>>
Cc:        Wolfgang Hell <wo_._he at t-online.de<mailto:wo_._he at t-online.de>>
Date:        06/02/2018 20:50
Subject:        SANA "CSTS OID Subtree" fouled up
________________________________

Folks,
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.

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.

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.

Best regards,
John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/css-csts/attachments/20190314/1b1be62d/attachment-0001.html>