DDSIRTP23 — Some constants specified in PSM table 9.4 conflict with the ones used in wireshark

In table 9.4 the the PSM RTPS define ReliabilityKind_t defines RELIABLE as having the value 3. However the Wireshark packet dissector defines ReliabilityKind_t RELIABLE as having the value 2.

In table 9.4 the PSM RTPS specification defines LOCATOR_KIND_UDPv6 having the value 2. However the Wireshark packet dissector defines LOCATOR_KIND_UDPv6 as having the value 8.

The vendors interoperate and used Wireshark to fine-tune their discovery therefore they are actually using the Wireshark-defined values rather than the ones in table 9.4

Proposed resolution:

Modify Table 9.4 entry for ReliabilityKind_t from:
#define RELIABLE 3

to
#define RELIABLE 2

Modify Table 9.4 entry for Locator_t from:
#define LOCATOR_KIND_UDPv6 2

to
#define LOCATOR_KIND_UDPv6 8

*Change the value of RELIABLE_RELIABILITY and add a description of how it is marshalled *

RELIABLE_RELIABILITY is currently defined with the value 3, however in practice all implementations are using 2, so the value has been changed in the spec.

It was also noted that the values in the RTPS spec differ from the API-level values defined in the DDS spec. Therefore, a description of how to marshal the DDS-defined ReliabilityQosPolicy on the wire.