-
Key: C2MS11-33
-
Status: closed
-
Source: NASA ( Mr. John Bugenhagen)
-
Summary:
The intent of tracking fields is to reserve them for use by the implementation. So, to be complete, these fields should be added to the specification. If any of these fields were to be inadvertently added to the messages by an application, the implementation (GMSEC API) could potentially overwrite their values.
-
Reported: C2MS 1.0 — Wed, 24 Jun 2020 18:33 GMT
-
Disposition: Transfered — C2MS 1.1b1
-
Disposition Summary:
Move to a TBD Sister SPEC
Tracking fields and encryption handling are likely to become part of the in-RFP C2MQ, so this should be transferred to that spec, rather than being implemented now in C2MS only to remove it soon.
-
Updated: Mon, 16 Sep 2024 14:18 GMT
C2MS11 — Add security fields that GMSEC API inserts into encrypted messages as Tracking Fields in C2MS
- Key: C2MS11-33
- OMG Task Force: Command and Control Message Specification (C2MS) 1.1 RTF