diff options
author | Othmar Gsenger <otti@anytun.org> | 2007-04-14 17:59:10 +0000 |
---|---|---|
committer | Othmar Gsenger <otti@anytun.org> | 2007-04-14 17:59:10 +0000 |
commit | bd9d4d27cfd60b6b7620f189edf526cf31028ae8 (patch) | |
tree | e6f374a4a8c628a112b9a7b1383b44b341cfc586 /internet-draft-anytun.xml | |
parent | typo (diff) |
tcp start
Diffstat (limited to 'internet-draft-anytun.xml')
-rw-r--r-- | internet-draft-anytun.xml | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/internet-draft-anytun.xml b/internet-draft-anytun.xml index e621581..ea9ce44 100644 --- a/internet-draft-anytun.xml +++ b/internet-draft-anytun.xml @@ -173,6 +173,10 @@ client 1 ----------- -> |server 3| -> ----------- client 2 <section title="unicast tcp with anycast initialisation"> </section> <section title="full anycast tcp"> + <section title="Introduction"> + <t>TCP is statefull, this is a big problem, because everey anycast server hast to know the tcp state. The TCP state has to be synced between the servers, that meens a lot of overhead. To keep this amount small and therefor make anycast TCP connections efficient some tricks SHOULD be used. + </t> + </section> <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> |