diff options
| author | Othmar Gsenger <otti@anytun.org> | 2007-04-03 16:10:04 +0000 |
|---|---|---|
| committer | Othmar Gsenger <otti@anytun.org> | 2007-04-03 16:10:04 +0000 |
| commit | 707feed74f16fac696009e75fed5b4d8c9866672 (patch) | |
| tree | 11879b4ef615a5f00a1344600432b7be8a028cd0 | |
| parent | pfeil vergessen (diff) | |
sections fixed
| -rw-r--r-- | draft-gsenger-anycast-relay-00.txt | 98 | ||||
| -rw-r--r-- | internet-draft-anytun.xml | 2 |
2 files changed, 78 insertions, 22 deletions
diff --git a/draft-gsenger-anycast-relay-00.txt b/draft-gsenger-anycast-relay-00.txt index 9d71bc7..5ece8e2 100644 --- a/draft-gsenger-anycast-relay-00.txt +++ b/draft-gsenger-anycast-relay-00.txt @@ -127,11 +127,53 @@ Internet-Draft Anycast stream relaying March 2007 RFC3068 [1] DTD. -1.1. Operation modes -1.1.1. Tunnel modes -1.1.1.1. Tunneling Mode + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +Gsenger Expires September 2, 2007 [Page 3] + +Internet-Draft Anycast stream relaying March 2007 + + +2. Operation modes + +2.1. Tunnel modes + +2.1.1. Tunneling Mode An example of anytun used in tunnel mode @@ -164,12 +206,26 @@ Internet-Draft Anycast stream relaying March 2007 -Gsenger Expires September 2, 2007 [Page 3] + + + + + + + + + + + + + + +Gsenger Expires September 2, 2007 [Page 4] Internet-Draft Anycast stream relaying March 2007 -1.1.1.2. Open tunnel mode +2.1.2. Open tunnel mode An example of anytun used in open tunnel mode @@ -220,12 +276,12 @@ Internet-Draft Anycast stream relaying March 2007 -Gsenger Expires September 2, 2007 [Page 4] +Gsenger Expires September 2, 2007 [Page 5] Internet-Draft Anycast stream relaying March 2007 -1.1.1.3. relay mode +2.1.3. relay mode An example of anytun used in relay mode @@ -257,15 +313,15 @@ Internet-Draft Anycast stream relaying March 2007 anytun protocol is only used for controll messages, but not fr encapsulation. -1.1.2. Transport modes +2.2. Transport modes -1.1.2.1. anycast udp mode +2.2.1. anycast udp mode -1.1.2.2. unicast tcp with anycast initialisation +2.2.2. unicast tcp with anycast initialisation -1.1.2.3. full anycast tcp +2.2.3. full anycast tcp -1.1.2.3.1. keep alive message request +2.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 @@ -276,14 +332,14 @@ Internet-Draft Anycast stream relaying March 2007 -Gsenger Expires September 2, 2007 [Page 5] +Gsenger Expires September 2, 2007 [Page 6] Internet-Draft Anycast stream relaying March 2007 -2. Protocol specification +3. Protocol specification -2.1. Header format +3.1. Header format @@ -332,7 +388,7 @@ Internet-Draft Anycast stream relaying March 2007 -Gsenger Expires September 2, 2007 [Page 6] +Gsenger Expires September 2, 2007 [Page 7] Internet-Draft Anycast stream relaying March 2007 @@ -388,12 +444,12 @@ Appendix A. The appan -Gsenger Expires September 2, 2007 [Page 7] +Gsenger Expires September 2, 2007 [Page 8] Internet-Draft Anycast stream relaying March 2007 -3. References +4. References [1] Huitema, C., "An Anycast Prefix for 6to4 Relay Routers", RFC 3068, June 2001. @@ -444,7 +500,7 @@ Internet-Draft Anycast stream relaying March 2007 -Gsenger Expires September 2, 2007 [Page 8] +Gsenger Expires September 2, 2007 [Page 9] Internet-Draft Anycast stream relaying March 2007 @@ -500,7 +556,7 @@ Author's Address -Gsenger Expires September 2, 2007 [Page 9] +Gsenger Expires September 2, 2007 [Page 10] Internet-Draft Anycast stream relaying March 2007 @@ -556,5 +612,5 @@ Acknowledgment -Gsenger Expires September 2, 2007 [Page 10] +Gsenger Expires September 2, 2007 [Page 11] diff --git a/internet-draft-anytun.xml b/internet-draft-anytun.xml index 356aee9..b168322 100644 --- a/internet-draft-anytun.xml +++ b/internet-draft-anytun.xml @@ -42,6 +42,7 @@ <section title='Introduction'> <t>anytun defines a Host Anycast Service as defined in rfc1546. It can be used to build high scalable and redundant tunnel services. It supports both UDP and TCP connections. Additionally to the possibility of establashing an unicast TCP connection over an anycast address as suggested in rfc1546, it supports real anycast TCP connections with state syncronisation and heuristic state forecast. It also has a relay mode, that makes it possible, that only one of the connection endpoints has to use the anytun protocol. This can be used to make connections through Firewalls or behind a NAT Router</t> <t><xref target="RFC3068">RFC3068</xref> DTD.</t> + </section> <section title="Operation modes"> <section title="Tunnel modes"> @@ -133,7 +134,6 @@ controller </section> </section> </section> - </section> </section> <section title="Protocol specification"> <section title="Header format"> |