[Css-csts] CSTS-specific procedure parameters, events, and directives ASN. modules

[John Pietras]

Yves and CSTSWG colleagues ---
At the Pasadena meeting, we discussed the plan to make the Buffered Tracking Data Message Delivery procedure's tracking-data-types configuration parameter accessible. As a consequence, we have to declare an OID for that parameter (pBTDMDtrackingDataTypes) and a corresponding data syntax type (pBTDMDtrackingDataTypes).

To be consistent with the organization of the CSTS SFW, to register that OID and type syntax we need an MD-CSTS Procedure Parameters, Events, and Directives annex equivalent to annex E.16 in the CSTS SFW. The first part of that annex would be the definition of the OID of the module, which I propose to make

CCSDS-TRACKING-DATA-PROCEDURE-PARAMETERS-EVENTS-DIRECTIVES

{  iso identified-organization (3) standards-producing-organization(112)

   ccsds(4) csts(4)  services (2)  serviceIdentifiers(2) trackingDataService (2)

   trackingDataServiceModules(4) procedureParamEventDirective (3)
}

As this is the first time we have needed such an annex for a derived service, it's not surprising that there is nothing (yet) in the Guidelines regarding such an annex. I think that that one should be included, logically following section 4.12, Procedure PDU Specification Annexes. I propose that the Guidelines specify the template for the module OID declaration as:



CCSDS-<Module Reference Service Component>-PROCEDURE-PARAMETERS-EVENTS-DIRECTIVES

{  iso identified-organization (3) standards-producing-organization(112)

   ccsds(4) csts(4)  services (2)  serviceIdentifiers(2)

   <service identifier> (<service number>)

   <service modules subtree identifier> (4) procedureParamEventDirective (3))

}

Do you agree?

Best regards,
John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/css-csts/attachments/20150420/05c45f12/attachment.html>