====== OMG: RTPS TCP/IP PSM for DDS Interoperability ======
[[ddsf:public:guidebook:06_append:01_family_of_standards:start| return to the DDS Family of Standards ]]

<table>
<caption>Data sheet for RTPS TCP/IP PSM for DDS Interoperability RFP </caption>
| Title                | TCP/IP Platform-Specific Model (PSM) for the DDS Real-Time Publish Subscribe (RTPS) Protocol  |
| Acronym              | RTPS TCP/IP PSM                                                                               |
| Version              |                                                                                               |
| OMG Document Number  | mars/17-09-24                                                                                 |
| Release Date         | 29 September 2017                                                                             |
| About RFP            | https://www.omg.org/techprocess/meetings/schedule/RTPS_TCP-IP_PSM_for_DDS_Interop_RFP.html    |
| Document             | https://www.omg.org/cgi-bin/doc?mars/17-09-24.pdf                                             |
</table>

  : **Note**: The following is an excerpt from the actual document. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference.

===== Motivation =====
  : //The [[ddsf:public:guidebook:06_append:glossary:d:data_distribution_service_dds]] [[ddsf:public:guidebook:06_append:glossary:r:rtps| Real-time Publish-Subscribe wire protocol]] [[ddsf:public:guidebook:06_append:01_family_of_standards:01_core:ddsi_rtps| (DDSI-RTPS)]]
specification defines a set of requirements for a [[ddsf:public:guidebook:06_append:glossary:w:wireprotocol|wire protocol]] suitable for the
Data Distribution Service (DDS). Primary considerations in the design of the
[[ddsf:public:guidebook:06_append:glossary:r:rtps]] wire protocol are: [[ddsf:public:guidebook:06_append:glossary:p:performance|performance]], configurability (tuning quality-of-service), [[ddsf:public:guidebook:06_append:glossary:f:faulttolerance|fault-tolerance]] (no single points of failure), extensibility (support new
transports), plug-and-play connectivity (automatic discovery), [[ddsf:public:guidebook:06_append:glossary:m:modularity|modularity]],
[[ddsf:public:guidebook:06_append:glossary:s:scalable|scalability]], and [[ddsf:public:guidebook:06_append:glossary:t:typesafe|type safety]].//

  : //[[ddsf:public:guidebook:06_append:glossary:r:rtps| RTPS]] imposes very little requirements on the underlying transport: a
connectionless service capable of sending packets [[ddsf:public:guidebook:06_append:glossary:b:besteffort|best-effort]] is sufficient. A
connection-oriented protocol can be used but is not required. The mechanisms of
the underlying protocol map to the generalized notions of the RTPS [[ddsf:public:guidebook:06_append:glossary:p:pim]].//

  : //The original [[ddsf:public:guidebook:06_append:01_family_of_standards:01_core:ddsi_rtps| DDSI-RTPS]] specification defined a [[ddsf:public:guidebook:06_append:glossary:p:psm]] built upon the [[ddsf:public:guidebook:06_append:glossary:u:udp]] because of its simplicity,
universal [[ddsf:public:guidebook:06_append:glossary:a:availability|availability]], best-effort and connectionless capabilities, predictable
behavior, scalability, and [[ddsf:public:guidebook:06_append:glossary:m:multicast|multicast]] support.//

  : //However, some [[ddsf:public:guidebook:06_append:glossary:d:data_distribution_service_dds]] systems would benefit from an RTPS PSM built upon the
[[ddsf:public:guidebook:06_append:glossary:t:tcp]]. Among other scenarios, a TCP PSM
would be better suited for communication through firewalls, where often UDP
traffic is filtered; could leverage existing TCP-based [[ddsf:public:guidebook:06_append:glossary:l:loadbal|load-balancing]]
infrastructure; and would allow DDS to be deployed in some applications where
governance mandates TCP exclusively. Therefore, the [[ddsf:public:guidebook:06_append:glossary:g:goal|goal]] of this [[ddsf:public:guidebook:06_append:glossary:r:rfp]] is to meet
the requirements set forth by the RTPS PIM with minimum possible overhead
using TCP.//


/**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
/* To add a discussion page to this page, comment out the line that says 
  ~~DISCUSSION:off~~
*/
~~DISCUSSION:on|Outstanding Issues~~
~~DISCUSSION:off~~