[CESG] IOAG Liaison request

[Shames, Peter M (312B)]

Dear Nestor,

During the recent CCSDS working meetings the topic of creating a SANA registry that, for each mission, listed the CCSDS standards used by that mission. This was initially raised by Mario during the joint SEA / MOIMS meeting. The suggestion at that point was that this could be linked to the already existing SCID registry.

During the CESG meeting this topic was brought up again and at that point the statement was made that the IOAG was already working on some such registry and the proposal was made to request that the IOAG take this aspect on as well.

In CCSDS we do not have any formal method for sending requests from the CCSDS back to the IOAG, the flow always seems to be in the other direction.  But this seems like a request that should go the other way, thus I am addressing it to you, as the CCSDS Liaison to the IOAG.  If it were in the form of a resolution it might look like this:

The CCSDS CESG,

CONSIDERING that:

The CESG has discussed a proposal to register the standards used by CCSDS compliant missions, and that
The IOAG member organizations have operational knowledge of spacecraft communications characteristics, and that
The IOAG is developing, or has developed, a registry of such service usage for active missions, and that
The IOAG has created registries in the SANA for their own purposes.

And RECOGNISING that:

The IOAG member organizations are in the best position to know the spacecraft communications characteristics for each of their spacecraft, and that
The SANA can support both public and private registries for use by the CCSDS and IOAG communities.

RESOLVES to request:

That the IOAG create (or make available) a registry for their active spacecraft that identifies spacecraft communications characteristics including the standards in use, and that
The registry be supported by the SANA, and that
The IOAG makes this registry available to the CCSDS community.

Cheers, Peter


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20160419/493f1bfe/attachment.html>