diff options
| -rw-r--r-- | draft-gsenger-anycast-relay-00.txt | 84 | ||||
| -rw-r--r-- | internet-draft-anytun.xml | 25 |
2 files changed, 67 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. diff --git a/internet-draft-anytun.xml b/internet-draft-anytun.xml index 29d83d2..7e5779a 100644 --- a/internet-draft-anytun.xml +++ b/internet-draft-anytun.xml @@ -94,6 +94,31 @@ client 1 ----------- -> |server 3| -> | ... | host <t>In open tunnel mode only one of two clients talking to each other over the servers MUST use the anytun protocol. When a client using the anytun protocol wants to tunnel data, it is building a connection to the anycast servers using the anytun protocol. The anycast servers relay the encapsulated packages directly to the destination without using the anytun protocol. The source address of the datagramm HAS TO be changed to the anycast address of the server. The anytun servers act like a source NAT router, therefor for the destination it saems that it is talking to the client directly.</t> </section> <section title='relay mode'> + <figure anchor="relay_mode"> + <preamble>An example of anytun used in relay mode</preamble> + <artwork> + ----------- +----- | 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 + </artwork> + </figure> <t>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.</t> </section> </section> |