summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOthmar Gsenger <otti@anytun.org>2007-04-14 17:59:10 +0000
committerOthmar Gsenger <otti@anytun.org>2007-04-14 17:59:10 +0000
commitbd9d4d27cfd60b6b7620f189edf526cf31028ae8 (patch)
treee6f374a4a8c628a112b9a7b1383b44b341cfc586
parenttypo (diff)
tcp start
-rw-r--r--draft-gsenger-anycast-relay-00.txt18
-rw-r--r--internet-draft-anytun.xml4
2 files changed, 13 insertions, 9 deletions
diff --git a/draft-gsenger-anycast-relay-00.txt b/draft-gsenger-anycast-relay-00.txt
index eb58788..2f97cb5 100644
--- a/draft-gsenger-anycast-relay-00.txt
+++ b/draft-gsenger-anycast-relay-00.txt
@@ -404,7 +404,15 @@ Internet-Draft Anycast stream relaying March 2007
2.2.4. full anycast tcp
-2.2.4.1. keep alive message request
+2.2.4.1. Introduction
+
+ 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.
+
+2.2.4.2. 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
@@ -436,14 +444,6 @@ Internet-Draft Anycast stream relaying March 2007
-
-
-
-
-
-
-
-
Gsenger Expires September 2, 2007 [Page 8]
Internet-Draft Anycast stream relaying March 2007
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>