keep alive

2 files changed, 133 insertions, 17 deletions

diff --git a/draft-gsenger-anycast-relay-00.txt b/draft-gsenger-anycast-relay-00.txt
index a04df99..17b560a 100644
--- a/draft-gsenger-anycast-relay-00.txt
+++ b/draft-gsenger-anycast-relay-00.txt
@@ -2,8 +2,8 @@
 
 
 Network Working Group                                         O. Gsenger
-Internet-Draft                                            March 10, 2007
-Expires: September 11, 2007
+Internet-Draft                                                March 2007
+Expires: September 2, 2007
 
 
                         Anycast stream relaying
@@ -32,7 +32,7 @@ Status of this Memo
    The list of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html.
 
-   This Internet-Draft will expire on September 11, 2007.
+   This Internet-Draft will expire on September 2, 2007.
 
 Copyright Notice
 
@@ -52,7 +52,7 @@ Copyright Notice
 
 
 
-Gsenger                Expires September 11, 2007               [Page 1]
+Gsenger                 Expires September 2, 2007               [Page 1]
 
 Internet-Draft           Anycast stream relaying              March 2007
 
@@ -61,9 +61,9 @@ Abstract
 
    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 or in relay mode to
-   transmit data form the client over the servers to a third party not
-   using the protocol and vice versa.
+   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.
 
 
 
@@ -108,7 +108,7 @@ Abstract
 
 
 
-Gsenger                Expires September 11, 2007               [Page 2]
+Gsenger                 Expires September 2, 2007               [Page 2]
 
 Internet-Draft           Anycast stream relaying              March 2007
 
@@ -127,7 +127,11 @@ Internet-Draft           Anycast stream relaying              March 2007
 
    RFC3068 [1] DTD.
 
-1.1.  Tunneling Mode
+1.1.  Operation modes
+
+1.1.1.  Tunnel modes
+
+1.1.1.1.  Tunneling Mode
 
    In tunneling mode the payload of the anytun packet is transmitted
    from one unicast host to the anycast server.  This server makes a
@@ -135,7 +139,115 @@ Internet-Draft           Anycast stream relaying              March 2007
    new anytun package to one or more clients depending on the routing
    descition.
 
-1.2.  Relay Mode
+1.1.1.2.  Open tunnel mode
+
+   In open tunnel mode only one of two clients talking to each other
+   over the server MUST use the anytun protocol. mode a client using the
+   anytun protocol, that wants to tunnel data, 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.  Therefor for the destination it
+   saems that it is talking to the client directly.
+
+1.1.1.3.  relay mode
+
+1.1.2.  Transport modes
+
+1.1.2.1.  anycast udp mode
+
+1.1.2.2.  unicast tcp with anycast initialisation
+
+1.1.2.3.  full anycast tcp
+
+
+
+
+
+
+Gsenger                 Expires September 2, 2007               [Page 3]
+
+Internet-Draft           Anycast stream relaying              March 2007
+
+
+1.1.2.3.1.  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
+   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.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gsenger                 Expires September 2, 2007               [Page 4]
+
+Internet-Draft           Anycast stream relaying              March 2007
+
+
+2.  Protocol specification
+
+2.1.  Header format
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
 
 
 
@@ -164,7 +276,7 @@ Internet-Draft           Anycast stream relaying              March 2007
 
 
 
-Gsenger                Expires September 11, 2007               [Page 3]
+Gsenger                 Expires September 2, 2007               [Page 5]
 
 Internet-Draft           Anycast stream relaying              March 2007
 
@@ -220,12 +332,12 @@ Appendix A.  The appan
 
 
 
-Gsenger                Expires September 11, 2007               [Page 4]
+Gsenger                 Expires September 2, 2007               [Page 6]
 
 Internet-Draft           Anycast stream relaying              March 2007
 
 
-2.  References
+3.  References
 
    [1]  Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",
         RFC 3068, June 2001.
@@ -276,7 +388,7 @@ Internet-Draft           Anycast stream relaying              March 2007
 
 
 
-Gsenger                Expires September 11, 2007               [Page 5]
+Gsenger                 Expires September 2, 2007               [Page 7]
 
 Internet-Draft           Anycast stream relaying              March 2007
 
@@ -332,7 +444,7 @@ Author's Address
 
 
 
-Gsenger                Expires September 11, 2007               [Page 6]
+Gsenger                 Expires September 2, 2007               [Page 8]
 
 Internet-Draft           Anycast stream relaying              March 2007
 
@@ -388,5 +500,5 @@ Acknowledgment
 
 
 
-Gsenger                Expires September 11, 2007               [Page 7]
+Gsenger                 Expires September 2, 2007               [Page 9]
 
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">