1. Preliminary Assessment of the CCSDS SANA Registry Management Policy on the SFW Document
April 2016

2. Registry Categories
The SFW deals with all three categories:
“enterprise” because it builds the SII using OIDs from that category
“global” as it intensely uses OIDs and the overall OID tree that is under CCSDS purview falls into this category
“local” as the management of the OID subtrees where the document assigns OIDs can be delegated to the CSS Area or for now even to the CSTS WG

3. Enterprise Category
It is understandable that the RMP document has been written with a CCSDS centric view, which may create problems when cross-support involves an organization that is not associated with the CCSDS
Example: Spacecraft. Can one create an entry which has an OID but no SCID? Who would have the authority to request such entry for a non-CCSDS spacecraft? Note: A work-around based on a bilaterally agreed pseudo OID is feasible
Concern: By when can we assume that the spacecraft registry contains OIDs? Can we already get the URL for inclusion in the SFW?
Same question regarding the Facility element of the SII which shall come from the Service Site and Aperture Registry

4. Global Category
In essence no impact assuming that we can reach agreement that the management of the OID subtrees used by the SFW and the FRs and the management of the FR registry is delegated to the CSS Area. Such delegation is foreseen in the RMP
However, I’m not clear about the following requirement in the RMP: Any CCSDS Recommended Standard requiring a new OID (sub-)type in the OID Registry shall document it in a CCSDS Recommended Standard and review it with the SSG. What is a new OID (sub-)type?

5. Local Category
Here some tweaking of words will be necessary so that the specification of the registry policy is aligned with the RMP. Suggested wording taken from the RMP: The registration rule will be type b) Change requires an engineering review by a designated expert
However, the following RMP requirement might be not commensurate with our FR registry needs: … changes to existing registries must be specified in a CCSDS Blue Book or Magenta Book. …

6. We should discuss this aspect with Peter Shames:
Local Category
The SFW stipulates for now that the agenciesFunctionalities subtree is split into agency specific subtrees and that agencies shall interact directly with SANA to get FRs registered
We should discuss this aspect with Peter Shames:
Does the agency specific nature move this to the enterprise category of registries?
Can we still regard this to be an Area level issue?
Would it be acceptable that we require agencies wishing to register an FR to have to go via the Area rather than directly to SANA
How can we keep the OID tree structure clean (external OID reference for identifying the agency)?