Source: Kratos RT Logic, Inc. ( Mike Anderson)
Tracking fields do not specifically belong in a C2MS Message. Rather, there should be a message envelope that contains these fields for the purpose of delivering a contained C2MS message. This "Message Envelope" is the logical place for managing tracking fields and other metadata related to, but not part of a C2MS message body.
This is clear when considering tracking fields, MW-INFO and CONNECTION-ID, which are message-bus handling constructs and have no meaning related to C2 of a satellite.
Note that this concept was originally moved to C2MQ. However, because C2MQ is a long way away and because message envelope is a useful construct within C2MS, it was determined at the Austin (Dec, 2023) C2MS meeting to bring this back in to C2MS and take the envelope concept out of C2MQ (leaving it to cover service-based interactions outside of the messages). Therefore, this is a re-entry of the envelope mechanism.
As part of this effort, we should do the following:
Add fields that allow encryption of content sections of the C2MS message body as well as message signatures or message authentication codes. This would not assume or provide any particular mechanism to encrypt/sign, but would allow for tracking of these fields to aid usage.
The benefit of doing this is to allow the Mission to determine levels of security and secure componentry, but to use the message definition as a way to track this information.
Reported: C2MS 1.0 — Tue, 7 Feb 2023 23:08 GMT
Updated: Thu, 16 Feb 2023 16:40 GMT
C2MS11 — Create an optional Message Envelope to hold Tracking Fields
- Key: C2MS11-130
- OMG Task Force: Command and Control Message Specification (C2MS) 1.1 RTF