C2MS13 — Consider if we should add Ground Telemetry to our set of Messages

This is to consider if we should add the ability for MVAL REQ/RESP/MSG messages to support Ground Telemetry.

Perhaps Processed Telemetry could do this to, though since it is a hybrid between the unprocessed (raw) Telemetry Message and the Mnemonic Value Data Message, perhaps this doesn't make sense (is there ever a raw frame or sample for Ground TLM?).

Of note, all C2MS Messages have the following REQUIRED fields in the header:

• MISSION-ID
• CONSTELLATION-ID
• SAT-ID-PHYSICAL
• SAT-ID-LOGICAL

And in the Subject, all TLM messages have

MISSION, CONST, and SAT as required elements.

A current work-around is to use Mission, Constellation, and Satellite String values to represent something on the ground, such as an antenna, modem, gateway, etc. The question at hand is if we should make this a little more formal.

Options might to to rename the fields to something more generic than Mission, Constellation and Satellite. At issue, though, is how to capture this in a backward-compatible way.

For now, just capturing this for future discussion.