blob: db2e287561c13ecb84f5da2e1f6fde90c0db3fc1 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
|
<?xml version='1.0'?>
<!DOCTYPE rfc SYSTEM 'rfcXXXX.dtd' [
<!ENTITY rfc3068 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3068.xml'>
]>
<rfc ipr='full3978' docName='draft-gsenger-anycast-relay-00'>
<front>
<title>Anycast stream relaying</title>
<author initials='O.G.' surname='Gsenger'
fullname='Othmar Gsenger'>
<organization></organization>
<address>
<postal>
<street>Sporgasse 6</street>
<city>Graz</city>
<code>8010</code>
<country>AT</country>
</postal>
<phone></phone>
<email>otti@wirdorange.org</email>
<uri>http://anytun.org/</uri>
</address>
</author>
<date month='March' year='2007' />
<area>General</area>
<workgroup></workgroup>
<keyword>anytun</keyword>
<keyword>Internet-Draft</keyword>
<keyword>Anycast tunneling / relaying</keyword>
<abstract>
<t>The anycast tunneling (anytun) protocol defines a protocol used for communication between unicast clients and anycast servers. It can be used for tunneling information between 2 clients over the servers or in relay mode to transmit data form the client over the servers to a third party not using the protocol and vice versa.
</t>
</abstract>
</front>
<middle>
<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 title="Operation modes">
<section title="Tunnel modes">
<section title='Tunneling Mode'>
<figure anchor="tunnel_mode">
<preamble>An example of anytun used in tunnel mode</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 tunneling mode the payload of the anytun packet is transmitted from one unicast host to the anycast server. This server makes a routing descision based on the underlying protocol and transmits a new anytun package to one or more clients depending on the routing descition. The server MAY also route the packet to a directly connected network or a service running on the server, but please note, that this is only usefull for anycast host services like DNS and that the services HAVE TO be running on all servers in order to work.</t>
</section>
<section title='Open tunnel mode'>
<figure anchor="open_tunnel_mode">
<preamble>An example of anytun used in open tunnel mode</preamble>
<artwork>
-----------
| RTP | ----------
----------- -> |server 1| ->
| UDP | ---------- -----------
----------- | RTP |
----- | IPv6 | ---------- ----------- -----
| | -> ----------- -> |server 2| -> | UDP* | -> | |
----- | anytun | ---------- ----------- -----
##### ----------- | IPv6* | #####
| UDP | ---------- -----------
client 1 ----------- -> |server 3| -> | ... | client 2
| IPv4 | ----------
-----------
| ... | anycast * changed source address
or port
</artwork>
</figure>
<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'>
<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>
<section title="Transport modes">
<section title="anycast udp mode">
</section>
<section title="unicast tcp with anycast initialisation">
</section>
<section title="full anycast tcp">
<section title="keep alive message request">
<t>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.</t>
</section>
</section>
</section>
</section>
</section>
<section title="Protocol specification">
<section title="Header format">
</section>
</section>
<appendix title='The appan'></appendix>
</middle>
<back>
<references>
&rfc3068; An Anycast Prefix for 6to4 Relay Routers
</references>
</back>
</rfc>
|
