DDSSEC11 — Use of Non-Existing Submessage SecureSubMsg and Flag MultiSubmsg

The DDS Security FTF changed some aspects of the construction of submessages eliminating SecureSubMsg and the MultiSubmsg flag. However some of the old language was not removed from the specification. Because of these there a re some sections that need to be modified as they do not completely make sense the way they are written now.

Note that SecureSubMsg and the use of the MultiSubmsg were eliminated by the FTF and they were replaced by the combination of newly created submessage: SecurePrefixSubMsg, SecurePostfixSubmsg, SecureRTPSPrefixSubmsg, SecureRTPSPostfixSubmsg and SecureBodySubMsg.

*Correct use of Non-Existing Submessage SecureSubMsg and Flag MultiSubmsg *

Per the issue description, the following sections need to be corrected:

Remove references to SecureSubMsg and replace with SecureBodySubMsg in:

• Multiple places in: 7.3.6.2 RTPS Submessage: SecureSubMsg
• 7.3.7.5.1 Wire Representation (the submessageId is wrong).
• 8.5.1.9 : multiple places, see MultiSubmsg below
• 8.8.10: multiple places, see MultiSubmsg below

Remove references to MultiSubmsg and replace with the use of prefix/body/postfix pattern in:

• 8.5.1.9.6 Operation: preprocess_secure_submsg: this needs to be modified to explain it now uses a prefix.
• 8.5.1.9.7 Operation: decode_datawriter_submessage: this needs to be modified to explain that it now uses a SecurePrefixSubMsg.
• 8.5.1.9.8 Operation: decode_datareader_submessage: this needs to be modified to explain that it now uses a SecurePrefixSubMsg.