[Css-csts] Proposed topic for next week's CSTSWG telecon

[John Pietras]

CSTSWG colleagues ----
I'd like to propose a topic for next week's CSTSWG telecon.  Peter Shames has commented on the ASN.1 annexes of the FF-CSTS book, noting that there should be some indication that the OIDs defined therein are registered in SANA. My response to him was that technically all CSTS specifications inherit the SANA Considerations of the SFW, and so by knowledgably tracing the "bread crumbs" back to the SFW a reader of a CSTS specification should be able to infer that SANA registers the OIDs (or more accurately, that SANA has been requested to register the OIDs). But I agree that this thin trail might be easy to overlook, and I've proposed adding a new subsection to the SANA Considerations subsection of the FF book:

H2.1  CCSDS CSTS services Registry

As described in H2.3 of reference [1], SANA has established the CSTS services subtree for the registration of OIDs for CSTS types and their associated service-specific parameters, procedures, and ASN.1 modules. This Recommended Standard requests SANA to update the CCSDS OID registry CSTS services subtree to add the OIDs and labels contained in annexes B, C, D, E, and F.



Because this concern applies to all CSTS specifications, I am asking that we discuss it at the telecon. Is my proposed solution adequate and should similar wording be added to all CSTS specifications, or do we need to say something else and/or more?

Best regards,
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/css-csts/attachments/20191126/011b0ca5/attachment-0001.html>