ddsf:public:guidebook:06_append:01_family_of_standards:05_wip:tcpippsm
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ddsf:public:guidebook:06_append:01_family_of_standards:05_wip:tcpippsm [2021/07/14 15:45] murphy ↷ Links adapted because of a move operation |
ddsf:public:guidebook:06_append:01_family_of_standards:05_wip:tcpippsm [2021/07/14 15:56] (current) murphy ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| ===== Motivation ===== | ===== Motivation ===== | ||
| - | : //The [[ddsf:public:guidebook:06_append:glossary:d:data_distribution_service_dds]] [[ddsf:private: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)]] | + | : //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:private:guidebook:06_append:glossary:w:wireprotocol|wire protocol]] suitable for the | + | 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 | Data Distribution Service (DDS). Primary considerations in the design of the | ||
| - | [[ddsf:private:guidebook:06_append:glossary:r:rtps]] wire protocol are: [[ddsf:private: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 | + | [[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:private:guidebook:06_append:glossary:m:modularity|modularity]], | + | transports), plug-and-play connectivity (automatic discovery), [[ddsf:public:guidebook:06_append:glossary:m:modularity|modularity]], |
| - | [[ddsf:private:guidebook:06_append:glossary:s:scalable|scalability]], and [[ddsf:private:guidebook:06_append:glossary:t:typesafe|type safety]].// | + | [[ddsf:public:guidebook:06_append:glossary:s:scalable|scalability]], and [[ddsf:public:guidebook:06_append:glossary:t:typesafe|type safety]].// |
| - | : //[[ddsf:private:guidebook:06_append:glossary:r:rtps| RTPS]] imposes very little requirements on the underlying transport: a | + | : //[[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 | 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 | 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:private:guidebook:06_append:glossary:p:pim]].// | + | 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:private:guidebook:06_append:glossary:p:psm]] built upon the [[ddsf:private:guidebook:06_append:glossary:u:udp]] because of its simplicity, | + | : //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 | universal [[ddsf:public:guidebook:06_append:glossary:a:availability|availability]], best-effort and connectionless capabilities, predictable | ||
| - | behavior, scalability, and [[ddsf:private:guidebook:06_append:glossary:m:multicast|multicast]] support.// | + | 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 | : //However, some [[ddsf:public:guidebook:06_append:glossary:d:data_distribution_service_dds]] systems would benefit from an RTPS PSM built upon the | ||
| - | [[ddsf:private:guidebook:06_append:glossary:t:tcp]]. Among other scenarios, a TCP PSM | + | [[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 | would be better suited for communication through firewalls, where often UDP | ||
| - | traffic is filtered; could leverage existing TCP-based [[ddsf:private:guidebook:06_append:glossary:l:loadbal|load-balancing]] | + | 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 | 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:private:guidebook:06_append:glossary:r:rfp]] is to meet | + | 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 | the requirements set forth by the RTPS PIM with minimum possible overhead | ||
| using TCP.// | using TCP.// | ||
ddsf/public/guidebook/06_append/01_family_of_standards/05_wip/tcpippsm.1626291918.txt.gz · Last modified: 2021/07/14 15:45 by murphy
