DDS-Security 1.0 FTF Avatar
  1. OMG Issue

DDSSEC_ — Do the encode operations prefix the CDR data with a CDR encapsulation header?

Open Closed All
  • Key: DDSSEC_-80
  • Status: closed  
  • Source: Twin Oaks Computing, Inc. ( Mr. Clark Tucker)
  • Summary:

    Do the encode operations (encode_serialized_data(), encode_datawriter_submessage(), encode_datareader_submessage(), encode_rtps_message()) produce a CDR encapsulation header in front of the CDR bytes of EncodeOperationOutputData?

    Recommend clarify the presence of the CDR encapsulation header.
  • Reported: DDS-Security 1.0b1 — Tue, 17 Nov 2015 14:26 GMT
  • Disposition: Resolved — DDS-Security 1.0
  • Disposition Summary:

    Change SerializedData to SerializedPayload

    "SerializedData" is not an RTPS submessage element. The correct name for the RTPS submessage element is "SerializedPayload" (RTPS version 2.2, section 9.4.2.12). So the specification should replace the references to "SerializedData" with "SerializedPayload".

    This affects: 7.3.1, 7.3.2, 7.3.4, 7.3.5, 8.5.1.3, 8.5.1.9.1, 8.5.1.9.9, 8.8.8, 8.8.8.1, 8.8.8.4, 9.4.1.2.1,

  • Updated: Tue, 12 Jul 2016 14:45 GMT