-
Key: DDSXTY13-18
-
Status: closed
-
Source: Real-Time Innovations ( Dr. Gerardo Pardo-Castellote, Ph.D.)
-
Summary:
As the spec is currently written, section 7.6.2.1.2
'Use of the RTPS Encapsulation Identifier', it is ambiguous as to which bits are used to encode the padding bytes.RTPS 2.4 is redefining the options field to be an array of two octets rather than a ushort. So XTypes should specify that the lower-order two bits of options[1] are used to encode the number of padding bytes.
-
Reported: DDS-XTypes 1.2 — Wed, 7 Mar 2018 01:49 GMT
-
Disposition: Resolved — DDS-XTypes 1.3
-
Disposition Summary:
Modify 7.6.2.1.2 'Use of the RTPS Encapsulation Identifier'
Modify 7.6.2.1.2 'Use of the RTPS Encapsulation Identifier' to indicate that the options field is octet[2] and that the bits using for padding are the least significant bits of the second byte:
0...2...........8...............16..............24..............32 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | representation_identifier | | X X| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
-
Updated: Tue, 8 Oct 2019 17:55 GMT
DDSXTY13 — Clarify which of the options bits are set to indicate padding bytes
- Key: DDSXTY13-18
- OMG Task Force: DDS-XTYPES 1.3 RTF