summaryrefslogtreecommitdiff
path: root/draft-gsenger-anycast-relay-00.txt
diff options
context:
space:
mode:
Diffstat (limited to 'draft-gsenger-anycast-relay-00.txt')
-rw-r--r--draft-gsenger-anycast-relay-00.txt84
1 files changed, 42 insertions, 42 deletions
diff --git a/draft-gsenger-anycast-relay-00.txt b/draft-gsenger-anycast-relay-00.txt
index 2bcd57c..3b43fb7 100644
--- a/draft-gsenger-anycast-relay-00.txt
+++ b/draft-gsenger-anycast-relay-00.txt
@@ -202,48 +202,6 @@ Internet-Draft Anycast stream relaying March 2007
The anytun servers act like a source NAT router, therefor for the
destination it saems that it is talking to the client directly.
-1.1.1.3. relay mode
-
- In relay mode the anycast serveres directly repaet the packetes of
- clients, only the source and destination addresses are changed. The
- anytun protocol is only used for controll messages, but not fr
- encapsulation.
-
-1.1.2. Transport modes
-
-1.1.2.1. anycast udp mode
-
-1.1.2.2. unicast tcp with anycast initialisation
-
-
-
-
-
-
-Gsenger Expires September 2, 2007 [Page 4]
-
-Internet-Draft Anycast stream relaying March 2007
-
-
-1.1.2.3. full anycast tcp
-
-1.1.2.3.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
- predict the tcp state including the sequence number. Synconisation
- of the sequence number would be to much overhead, so a keep alive
- intervall is agreed. This interval is used to calculate the sequemce
- number.
-
-
-
-
-
-
-
-
-
@@ -262,17 +220,59 @@ Internet-Draft Anycast stream relaying March 2007
+Gsenger Expires September 2, 2007 [Page 4]
+
+Internet-Draft Anycast stream relaying March 2007
+1.1.1.3. relay mode
+ An example of anytun used in relay mode
+ -----------
+ ----- | RTP | ----------
+ | | ----------- -> |server 1| ->
+ ----- | UDP** | ---------- -----------
+ ##### ----------- | RTP |
+ | IPv6**| ---------- ----------- -----
+ host -> ----------- -> |server 2| -> | UDP* | -> | |
+ not using | ... | ---------- ----------- -----
+ anytun | IPv6* | #####
+ ---------- -----------
+ ----------- -> |server 3| | ... | host
+ ----- | anytun | ---------- not using
+ | | ----------- anytun
+ ----- | IPv4 | anycast
+ ##### -----------
+ connection| ... |
+ controller
+
+ *changed source address or port
+ **changed destination address or port
+
+ Figure 3
+ In relay mode the anycast serveres directly repaet the packetes of
+ clients, only the source and destination addresses are changed. The
+ anytun protocol is only used for controll messages, but not fr
+ encapsulation.
+1.1.2. Transport modes
+1.1.2.1. anycast udp mode
+1.1.2.2. unicast tcp with anycast initialisation
+1.1.2.3. full anycast tcp
+1.1.2.3.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
+ predict the tcp state including the sequence number. Synconisation
+ of the sequence number would be to much overhead, so a keep alive
+ intervall is agreed. This interval is used to calculate the sequemce
+ number.