[Css-csts] keep services and Framework separate

[Ray, Timothy J. (GSFC-5830)]

Dear WG,

It seems sensible to keep Service-level specifications separate from our Framework specification.  Benefits of this approach include being able to add a new service (or modify an existing service) without modifying the Framework specification.  Here are some examples of Service-level specification that are in version 0.19 of our Framework specification - these examples are all in the appendices that define ASN.1:

Page C-7:
--PROTOTYPES SERVICES OBJECT IDENTIFIERS
protoIdentifiers   OBJECT IDENTIFIER ::= {framework 1}
Note:  I think it makes sense to *keep* the 'servicesIdentifiers' object because it serves as the root of all services.
Note:  I think the 'protoIdentifiers' can be kept

Pages D-11 through D-12:
D2.2 SERVICE TYPE IDENTIFIERS
(this whole section)

I suggest that we define each service's object-identifier values within the specification for that service.

(Please forgive me if this idea has already been discussed and decided.)

Best regards,
Tim



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20090909/a49942a7/attachment.htm