Issue 19694: Locator_t kind needs a reserved range and a range for vendor extensions (ddsi-rtps-rtf) Source: Real-Time Innovations (Mr. Gerardo Pardo-Castellote, ) Nature: Enhancement Severity: Minor Summary: The Locator_t contains an integer field that identifies the type of locator. Currently only the values -1, 0, 1, 2 are defined. Which correspond to reserved values as well as UDPv4 and UDPv6. Future revisions of the protocol may define additional kinds for things like TCP v4, TCPv6, shared memory and other transports. At the same time vendors are using this field to identify their own custom transports. To avoid collisions with future revisions of the protocol, the RTPS specification should reserve a range. For example, all kinds with value less than 0x01000000. These values should be reserved for future revisions of the protocol. Vendors that want to define their custom transport should use Locator_t kind with values 0x01000000. And these values should be interpreted in the context of the RTPS vendorId so that different vendors can use the same value to mean different things. Resolution: Revised Text: Actions taken: December 18, 2014: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 18 Dec 2014 20:33:39 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Gerardo Pardo Employer: RTI mailFrom: gerardo@rti.com Terms_Agreement: I agree Specification: The Real-time Publish-Subscribe Protocol (RTPS) DDS Interoperability Wire Protocol Specification Section: 9.3.2 FormalNumber: formal/2014-09-01 Version: 2.2 Doc_Year: 2014 Doc_Month: September Doc_Day: 01 Page: 154 Title: Locator_t kind needs a reserved range and a range for vendor extensions Nature: Enhancement Severity: Minor CODE: 3TMw8 B1: Report Issue Remote Name: c-98-210-244-71.hsd1.ca.comcast.net Remote User: HTTP User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.38 Safari/537.36 Time: 08:33 PM Description: The Locator_t contains an integer field that identifies the type of locator. Currently only the values -1, 0, 1, 2 are defined. Which correspond to reserved values as well as UDPv4 and UDPv6. Future revisions of the protocol may define additional kinds for things like TCP v4, TCPv6, shared memory and other transports. At the same time vendors are using this field to identify their own custom transports. To avoid collisions with future revisions of the protocol, the RTPS specification should reserve a range. For example, all kinds with value less than 0x01000000. These values should be reserved for future revisions of the protocol. Vendors that want to define their custom transport should use Locator_t kind with values 0x01000000. And these values should be interpreted in the context of the RTPS vendorId so that different vendors can use the same value to mean different things.