diff options
| author | Othmar Gsenger <otti@anytun.org> | 2007-04-02 18:50:12 +0000 |
|---|---|---|
| committer | Othmar Gsenger <otti@anytun.org> | 2007-04-02 18:50:12 +0000 |
| commit | 5f523b56d4c53017962b9678bfb18ace7c71c84e (patch) | |
| tree | 48f65c52a6319384eadea077f6e3f3b87bb36e23 /internet-draft-anytun.xml | |
| parent | untestet xml (diff) | |
keep alive
Diffstat (limited to 'internet-draft-anytun.xml')
| -rw-r--r-- | internet-draft-anytun.xml | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/internet-draft-anytun.xml b/internet-draft-anytun.xml index 9cf2175..2ecac5c 100644 --- a/internet-draft-anytun.xml +++ b/internet-draft-anytun.xml @@ -42,7 +42,6 @@ <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"> @@ -63,7 +62,12 @@ <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"> |