summaryrefslogtreecommitdiff
path: root/draft-gsenger-anycast-relay-00.txt
diff options
context:
space:
mode:
Diffstat (limited to 'draft-gsenger-anycast-relay-00.txt')
-rw-r--r--draft-gsenger-anycast-relay-00.txt18
1 files changed, 9 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