Issue 12507: Properly assign vendor IDs (dds-interop-rtf) Source: Real-Time Innovations (Mr. Kenneth Brophy, ken@rti.com ken.brophy@rti.com) Nature: Uncategorized Issue Severity: Summary: Summary: Section 9.4.5.1.1 leaves unspecified the list of vendor IDs Resolution: Modify section to include a reference to an appendix or table where all the vendor IDs are listed. Resolution: Modify section to include a reference to an appendix or table where all the vendor IDs are listed. Revised Text: Revised Text: In Section 9.4.5.1.1 (SubmessageId) replace existing sentence: … The current list of vendorId's is provided in TODO. With: The current list of vendorId's is provided in Appendix A Add an appendix A to the document with the following content: Appendix A Reserved Vendor Ids The RTPS Header includes a field that identifies the vendor that implemented the protocol that created the message. See Section 9.4.4. Vendor IDs can only be reserved by implementors that commit to comply with the current major version of the protocol. RTPS protocol implementor are encouraged to contact the OMG to reserve its own vendor ID. To be compliant with the DDS RTPS Interoperability Specificaton a vendor must have a reserved Vendor Id and use it. The vendor ID is of type VendorId_t this is defined in Table 9.4 and contains 2 octets. Table 0-1 Reserved VendorIds Vendor and Product VendorId VENDORID_UNKNOWNSentinel value that indicates an unspecified vendor { 0x00, 0x00 } Real-Time Innovations, Inc. (www.rti.com)RTI Data Distribution Service (NDDS) { 0x00, 0x01 } PrismTech Ltd. (www.prismtech.com)OpenSplice DDS { 0x00, 0x02 } Object Computing Inc. (www.ociweb.com)OpenDDS { 0x00, 0x03 } MilSOFT (http://dds.milsoft.com.tr/en/dds-home.php)MilSOFT DDS { 0x00, 0x04 } Kongsberg (http://www.kongsberg.com)Compass DDS { 0x00, 0x05 } . In order The table below lists the currently-assigned vendorId's that should appear in the RTPS header message as described in Section 9.4.4 struct { octet[2];} VendorId_t; Product, Vendor Name & URL { 0x00, 0x00 } VENDORID_UNKNOWNThis value that indicates an unspecified vendor. { 0x00, 0x01 } RTI Data-Distribution ServiceReal-Time Innovations, Inc.www.rti.com { 0x00, 0x02 } OpenSplice DDSPrismTech Ltd.www.prismtech.com { 0x00, 0x03 } OpenDDSObject Computing Inc.http://www.ociweb.com/ { 0x00, 0x04 } MilSOFT DDSMilSOFThttp://dds.milsoft.com.tr/en/dds-home.php { 0x00, 0x05 } Compas DDSKongsberghttp://www.kongsberg.com Proposed Disposition: Resolved Actions taken: May 20, 2008: received issue Discussion: End of Annotations:===== MG Issue No: 12507R#9 Title: Properly assign vendor IDs Source: Real-Time Innovations, Inc. (Ken Brophy, ken@rti.com) Summary: Section 9.4.5.1.1 leaves unspecified the list of vendor IDs Resolution: Modify section to include a reference to an appendix or table where all the vendor IDs are listed. Revised Text: In Section 9.4.5.1.1 replace existing sentence: . The current list of vendorId.s is provided in TODO. With: The current list of vendorId.s is provided in Appendix A Add an appendix A to the document with the following content: Appendix A Reserved Vendor Ids The RTPS Header includes a field that identifies the vendor that implemented the protocol that created the message. See Section 9.4.4. Vendor IDs can only be reserved by implementors that commit to comply with the current major version of the protocol. RTPS protocol implementor are encouraged to contact the OMG to reserve its own vendor ID. To be compliant with the DDS RTPS Interoperability Specificaton a vendor must have a reserved Vendor Id and use it. The vendor ID is of type VendorId_t this is defined in Table 9.4 and contains 2 octets. Table 0.1 Reserved VendorIds Vendor and Product VendorId VENDORID_UNKNOWNSentinel value that indicates an unspecified vendor { 0x00, 0x00 } Real-Time Innovations, Inc. (www.rti.com)RTI Data Distribution Service (NDDS) { 0x00, 0x01 } PrismTech Ltd. (www.prismtech.com)OpenSplice DDS { 0x00, 0x02 } Object Computing Inc. (www.ociweb.com)OpenDDS { 0x00, 0x03 } MilSOFT (http://dds.milsoft.com.tr/en/dds-home.php)MilSOFT DDS { 0x00, 0x04 } Kongsberg (http://www.kongsberg.com)Compass DDS { 0x00, 0x05 } . In order The table below lists the currently-assigned vendorId.s that should appear in the RTPS header message as described in Section 9.4.4 struct { octet[2];} VendorId_t; Product, Vendor Name & URL { 0x00, 0x00 } VENDORID_UNKNOWNThis value that indicates an unspecified vendor. { 0x00, 0x01 } RTI Data-Distribution ServiceReal-Time Innovations, Inc.www.rti.com { 0x00, 0x02 } OpenSplice DDSPrismTech Ltd.www.prismtech.com { 0x00, 0x03 } OpenDDSObject Computing Inc.http://www.ociweb.com/ { 0x00, 0x04 } MilSOFT DDSMilSOFThttp://dds.milsoft.com.tr/en/dds-home.php { 0x00, 0x05 } Compas DDSKongsberghttp://www.kongsberg.com Disposition: