diff options
| -rw-r--r-- | draft-gsenger-anycast-relay-00.txt | 130 | ||||
| -rw-r--r-- | internet-draft-anytun.xml | 43 |
2 files changed, 164 insertions, 9 deletions
diff --git a/draft-gsenger-anycast-relay-00.txt b/draft-gsenger-anycast-relay-00.txt index 5e8484f..b4c2615 100644 --- a/draft-gsenger-anycast-relay-00.txt +++ b/draft-gsenger-anycast-relay-00.txt @@ -315,13 +315,96 @@ Internet-Draft Anycast stream relaying March 2007 2.2. Transport modes + + + + + + + + + + + + + + + + + +Gsenger Expires September 2, 2007 [Page 6] + +Internet-Draft Anycast stream relaying March 2007 + + 2.2.1. anycast udp mode -2.2.2. unicast tcp with anycast initialisation + An example of anytun used with udp transport -2.2.3. full anycast tcp + ----------- ----------- + | RTP | ---------- | RTP | + ----------- -> |server 1| -> ----------- + | UDP | ---------- | UDP | + ----------- ----------- + ----- | IPv6 | ---------- | IPv6 | ----- + | | -> ----------- -> |server 2| -> ----------- -> | | + ----- | anytun | ---------- | anytun | ----- + ##### ----------- ----------- ##### + | UDP | ---------- | UDP | + client 1 ----------- -> |server 3| -> ----------- client 2 + | IPv4 | ---------- | IPv4 | + ----------- ----------- + | ... | anycast | ... | + + Figure 4 + + In anycast udp mode the data between clients and anycast serveres is + carried by udp packets. Packets are routed by the serveres from one + client to another. Because udp is stateless no inforamtion has to be + syncronised + +2.2.2. anycast light udp mode + + An example of anytun used with udp transport -2.2.3.1. keep alive message request + ----------- ----------- + | RTP | ---------- | RTP | + ----------- -> |server 1| -> ----------- + | UDP | ---------- | UDP | + ----------- ----------- + ----- | IPv6 | ---------- | IPv6 | ----- + | | -> ----------- -> |server 2| -> ----------- -> | | + ----- | anytun | ---------- | anytun | ----- + ##### ----------- ----------- ##### + |lightUDP | ---------- |lightUDP | + client 1 ----------- -> |server 3| -> ----------- client 2 + | IPv4 | ---------- | IPv4 | + ----------- ----------- + | ... | anycast | ... | + + Figure 5 + + The light UDP mode is neerly the same as the normal UDP mode, the + + + +Gsenger Expires September 2, 2007 [Page 7] + +Internet-Draft Anycast stream relaying March 2007 + + + only difference is, that the udp size is set to the udp header lenght + and not to the length of the full packet and therefor the checksum is + only calculated for the udo header itself. So there is no error + correction or detection done on the payload. This can be usefull if + realtime data is beeing transimittet or the tunneled protocol does + error correction/detection by itself. + +2.2.3. unicast tcp with anycast initialisation + +2.2.4. full anycast tcp + +2.2.4.1. keep alive message request Most NAT routers need a tcp connection to transmit some packets once in while to stay open. In full anycast tcp mode anytun hast to @@ -332,7 +415,36 @@ Internet-Draft Anycast stream relaying March 2007 -Gsenger Expires September 2, 2007 [Page 6] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +Gsenger Expires September 2, 2007 [Page 8] Internet-Draft Anycast stream relaying March 2007 @@ -388,7 +500,7 @@ Internet-Draft Anycast stream relaying March 2007 -Gsenger Expires September 2, 2007 [Page 7] +Gsenger Expires September 2, 2007 [Page 9] Internet-Draft Anycast stream relaying March 2007 @@ -444,7 +556,7 @@ Appendix A. The appan -Gsenger Expires September 2, 2007 [Page 8] +Gsenger Expires September 2, 2007 [Page 10] Internet-Draft Anycast stream relaying March 2007 @@ -500,7 +612,7 @@ Internet-Draft Anycast stream relaying March 2007 -Gsenger Expires September 2, 2007 [Page 9] +Gsenger Expires September 2, 2007 [Page 11] Internet-Draft Anycast stream relaying March 2007 @@ -556,7 +668,7 @@ Author's Address -Gsenger Expires September 2, 2007 [Page 10] +Gsenger Expires September 2, 2007 [Page 12] Internet-Draft Anycast stream relaying March 2007 @@ -612,5 +724,5 @@ Acknowledgment -Gsenger Expires September 2, 2007 [Page 11] +Gsenger Expires September 2, 2007 [Page 13] diff --git a/internet-draft-anytun.xml b/internet-draft-anytun.xml index 0850d75..1f51649 100644 --- a/internet-draft-anytun.xml +++ b/internet-draft-anytun.xml @@ -126,6 +126,49 @@ controller </section> <section title="Transport modes"> <section title="anycast udp mode"> + <figure anchor="transtort_udp"> + <preamble>An example of anytun used with udp transport</preamble> + <artwork> + ----------- ----------- + | RTP | ---------- | RTP | + ----------- -> |server 1| -> ----------- + | UDP | ---------- | UDP | + ----------- ----------- +----- | IPv6 | ---------- | IPv6 | ----- +| | -> ----------- -> |server 2| -> ----------- -> | | +----- | anytun | ---------- | anytun | ----- +##### ----------- ----------- ##### + | UDP | ---------- | UDP | +client 1 ----------- -> |server 3| -> ----------- client 2 + | IPv4 | ---------- | IPv4 | + ----------- ----------- + | ... | anycast | ... | + </artwork> + </figure> + <t>In anycast udp mode the data between clients and anycast serveres is carried by udp packets. Packets are routed by the serveres from one client to another. Because udp is stateless no inforamtion has to be syncronised</t> + </section> + <section title="anycast light udp mode"> + <figure anchor="transport_lightudp"> + <preamble>An example of anytun used with udp transport</preamble> + <artwork> + ----------- ----------- + | RTP | ---------- | RTP | + ----------- -> |server 1| -> ----------- + | UDP | ---------- | UDP | + ----------- ----------- +----- | IPv6 | ---------- | IPv6 | ----- +| | -> ----------- -> |server 2| -> ----------- -> | | +----- | anytun | ---------- | anytun | ----- +##### ----------- ----------- ##### + |lightUDP | ---------- |lightUDP | +client 1 ----------- -> |server 3| -> ----------- client 2 + | IPv4 | ---------- | IPv4 | + ----------- ----------- + | ... | anycast | ... | + </artwork> + </figure> + + <t>The light UDP mode is neerly the same as the normal UDP mode, the only difference is, that the udp size is set to the udp header lenght and not to the length of the full packet and therefor the checksum is only calculated for the udo header itself. So there is no error correction or detection done on the payload. This can be usefull if realtime data is beeing transimittet or the tunneled protocol does error correction/detection by itself.</t> </section> <section title="unicast tcp with anycast initialisation"> </section> |