rfc split

4 files changed, 480 insertions, 96 deletions

diff --git a/draft-gsenger-anycast-relay-00.txt b/draft-gsenger-anycast-relay-00.txt
index 2f97cb5..588d4d6 100644
--- a/draft-gsenger-anycast-relay-00.txt
+++ b/draft-gsenger-anycast-relay-00.txt
@@ -400,84 +400,25 @@ Internet-Draft           Anycast stream relaying              March 2007
    realtime data is beeing transimittet or the tunneled protocol does
    error correction/detection by itself.
 
-2.2.3.  unicast tcp with anycast initialisation
+2.2.3.  Protocol specification
 
-2.2.4.  full anycast tcp
+2.2.3.1.  Header format
 
-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
-   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 8]
-
-Internet-Draft           Anycast stream relaying              March 2007
-
-
-3.  Protocol specification
-
-3.1.  Header format
-
-3.2.  Protocol field
+2.2.3.2.  Protocol field
 
    The protocol field defines the payload protocol.  ETHER TYPE protocol
    numerbers are used. http://www.iana.org/assignments/ethernet-numbers
-   .  The values 0000-05DC are not used for DIX ethernet lenght, but are
-   reservered for special purposes.  As the definition of transparent
-   ethernet bridging is very unclear 2 special types are added for
-   ethernet frames
+   .  The values 0000-05DC are reserverd and not used at the moment.
 
-   Protocol Types
+   Some exmples for protocol types
 
    HEX
    0000 Reserved
-   0001 Raw Ethernet - both IEEE 802.3 and DIX ethernet
-                       without preamble,SFD, PAD and FCS
-   0002 Raw ethernet with FCS
-   0003 Reserved
    .... Reserved
    05DC Reserved
-   05DD as in http://www.iana.org/assignments/ethernet-numbers
-   .... as in http://www.iana.org/assignments/ethernet-numbers
    0800 Internet IP (IPv4)
-   .... as in http://www.iana.org/assignments/ethernet-numbers
+   6558 transparent ethernet bridging
    86DD IPv6
-   .... as in http://www.iana.org/assignments/ethernet-numbers
 
                                  Figure 6
 
@@ -500,7 +441,10 @@ Internet-Draft           Anycast stream relaying              March 2007
 
 
 
-Gsenger                 Expires September 2, 2007               [Page 9]
+
+
+
+Gsenger                 Expires September 2, 2007               [Page 8]
 
 Internet-Draft           Anycast stream relaying              March 2007
 
@@ -556,12 +500,12 @@ Appendix A.  The appan
 
 
 
-Gsenger                 Expires September 2, 2007              [Page 10]
+Gsenger                 Expires September 2, 2007               [Page 9]
 
 Internet-Draft           Anycast stream relaying              March 2007
 
 
-4.  References
+3.  References
 
    [1]  Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",
         RFC 3068, June 2001.
@@ -612,7 +556,7 @@ Internet-Draft           Anycast stream relaying              March 2007
 
 
 
-Gsenger                 Expires September 2, 2007              [Page 11]
+Gsenger                 Expires September 2, 2007              [Page 10]
 
 Internet-Draft           Anycast stream relaying              March 2007
 
@@ -668,7 +612,7 @@ Author's Address
 
 
 
-Gsenger                 Expires September 2, 2007              [Page 12]
+Gsenger                 Expires September 2, 2007              [Page 11]
 
 Internet-Draft           Anycast stream relaying              March 2007
 
@@ -724,5 +668,5 @@ Acknowledgment
 
 
 
-Gsenger                 Expires September 2, 2007              [Page 13]
+Gsenger                 Expires September 2, 2007              [Page 12]
 
diff --git a/internet-draft-anycast-tcp-stream-relay.txt b/internet-draft-anycast-tcp-stream-relay.txt
new file mode 100644
index 0000000..ad91815
--- /dev/null
+++ b/internet-draft-anycast-tcp-stream-relay.txt
@@ -0,0 +1,392 @@
+
+
+
+Network Working Group                                         O. Gsenger
+Internet-Draft                                                March 2007
+Expires: September 2, 2007
+
+
+                      Anycast TCP stream relaying
+               draft-gsenger-anycast-tcp-stream-relay-00
+
+Status of this Memo
+
+   By submitting this Internet-Draft, each author represents that any
+   applicable patent or other IPR claims of which he or she is aware
+   have been or will be disclosed, and any of which he or she becomes
+   aware will be disclosed, in accordance with Section 6 of BCP 79.
+
+   Internet-Drafts are working documents of the Internet Engineering
+   Task Force (IETF), its areas, and its working groups.  Note that
+   other groups may also distribute working documents as Internet-
+   Drafts.
+
+   Internet-Drafts are draft documents valid for a maximum of six months
+   and may be updated, replaced, or obsoleted by other documents at any
+   time.  It is inappropriate to use Internet-Drafts as reference
+   material or to cite them other than as "work in progress."
+
+   The list of current Internet-Drafts can be accessed at
+   http://www.ietf.org/ietf/1id-abstracts.txt.
+
+   The list of Internet-Draft Shadow Directories can be accessed at
+   http://www.ietf.org/shadow.html.
+
+   This Internet-Draft will expire on September 2, 2007.
+
+Copyright Notice
+
+   Copyright (C) The IETF Trust (2007).
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gsenger                 Expires September 2, 2007               [Page 1]
+
+Internet-Draft         Anycast TCP stream relaying            March 2007
+
+
+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 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.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gsenger                 Expires September 2, 2007               [Page 2]
+
+Internet-Draft         Anycast TCP stream relaying            March 2007
+
+
+1.  full anycast tcp
+
+1.1.  Introduction
+
+   TCP is statefull, this is a big problem, because every anycast server
+   has 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 MUST
+   be used.  This is considered to be a real hack, so it is not
+   recommendid to use this mode unless it is really necessary.  It might
+   for instance be necessary to build connection trough special kind of
+   NAT routers or firewalls.
+
+1.2.  Reducing syncronisaton overhead
+
+1.2.1.  Fragmentation
+
+   The only way of fully supporting fragmentation would be to syncronise
+   fragments between all anycast servers.  This is considered to be to
+   much overhead, so there are two non perfect solutions for this
+   problems.  Either fragmentation HAS TO be disabled or if not all
+   fragments arrive at the same server the ip datagramm HAS TO be
+   discarded.  As routing changes are not expected to occure very
+   frequently, the ip datagram will get retransmitted by TCP and all
+   fragments will arrive at the new server.
+
+1.2.2.  sequence number
+
+   It is nessarary to send tcp segments with a correct sequence number,
+   that appear to come from the same host, in order to get a valid
+   connecton to the client.  Syncronisation of sequence numbers would
+   mean to much overhead, so it hast to be provided by the relayed data.
+   The relayed data from the anycast serveres point of view, consits of
+   multible datastream, each directed from one client to anotherIn
+   tunneling mode all anytun packets from the client
+
+1.3.  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 3]
+
+Internet-Draft         Anycast TCP stream relaying            March 2007
+
+
+Appendix A.  The appan
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gsenger                 Expires September 2, 2007               [Page 4]
+
+Internet-Draft         Anycast TCP stream relaying            March 2007
+
+
+2.  References
+
+   [1]  Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",
+        RFC 3068, June 2001.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gsenger                 Expires September 2, 2007               [Page 5]
+
+Internet-Draft         Anycast TCP stream relaying            March 2007
+
+
+Author's Address
+
+   Othmar Gsenger
+   Sporgasse 6
+   Graz  8010
+   AT
+
+   Phone:
+   Email: otti@wirdorange.org
+   URI:   http://anytun.org/
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gsenger                 Expires September 2, 2007               [Page 6]
+
+Internet-Draft         Anycast TCP stream relaying            March 2007
+
+
+Full Copyright Statement
+
+   Copyright (C) The IETF Trust (2007).
+
+   This document is subject to the rights, licenses and restrictions
+   contained in BCP 78, and except as set forth therein, the authors
+   retain all their rights.
+
+   This document and the information contained herein are provided on an
+   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
+   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
+   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
+   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
+   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
+   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
+
+
+Intellectual Property
+
+   The IETF takes no position regarding the validity or scope of any
+   Intellectual Property Rights or other rights that might be claimed to
+   pertain to the implementation or use of the technology described in
+   this document or the extent to which any license under such rights
+   might or might not be available; nor does it represent that it has
+   made any independent effort to identify any such rights.  Information
+   on the procedures with respect to rights in RFC documents can be
+   found in BCP 78 and BCP 79.
+
+   Copies of IPR disclosures made to the IETF Secretariat and any
+   assurances of licenses to be made available, or the result of an
+   attempt made to obtain a general license or permission for the use of
+   such proprietary rights by implementers or users of this
+   specification can be obtained from the IETF on-line IPR repository at
+   http://www.ietf.org/ipr.
+
+   The IETF invites any interested party to bring to its attention any
+   copyrights, patents or patent applications, or other proprietary
+   rights that may cover technology that may be required to implement
+   this standard.  Please address the information to the IETF at
+   ietf-ipr@ietf.org.
+
+
+Acknowledgment
+
+   Funding for the RFC Editor function is provided by the IETF
+   Administrative Support Activity (IASA).
+
+
+
+
+
+Gsenger                 Expires September 2, 2007               [Page 7]
+
diff --git a/internet-draft-anycast-tcp-stream-relay.xml b/internet-draft-anycast-tcp-stream-relay.xml
new file mode 100644
index 0000000..a1a7a4b
--- /dev/null
+++ b/internet-draft-anycast-tcp-stream-relay.xml
@@ -0,0 +1,66 @@
+<?xml version='1.0'?>
+    <!DOCTYPE rfc SYSTEM 'rfcXXXX.dtd' [
+
+    <!ENTITY rfc3068 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3068.xml'>
+]>
+    <rfc ipr='full3978' docName='draft-gsenger-anycast-tcp-stream-relay-00'>
+    <front>
+        <title>Anycast TCP stream relaying</title>
+
+        <author initials='O.G.' surname='Gsenger'
+                fullname='Othmar Gsenger'>
+            <organization></organization>
+
+            <address>
+                <postal>
+                    <street>Sporgasse 6</street>
+                    <city>Graz</city>
+                    <code>8010</code>
+                    <country>AT</country>
+                </postal>
+
+                <phone></phone>
+                <email>otti@wirdorange.org</email>
+                <uri>http://anytun.org/</uri>
+            </address>
+        </author>
+
+        <date month='March' year='2007' />
+
+        <area>General</area>
+        <workgroup></workgroup>
+        <keyword>anytun</keyword>         <keyword>Internet-Draft</keyword>
+        <keyword>Anycast TCP relaying</keyword>
+        <abstract>
+            <t>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 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.
+            </t>
+        </abstract>     </front>     <middle>
+    <section title="full anycast tcp">
+       <section title="Introduction">
+       <t>TCP is statefull, this is a big problem, because every anycast server has 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 MUST be used. This is considered to be a real hack, so it is not recommendid to use this mode unless it is really necessary. It might for instance be necessary to build connection trough special kind of NAT routers or firewalls.
+       </t>
+       </section>
+       <section title="Reducing syncronisaton overhead">
+         <section title="Fragmentation">
+         <t>
+           The only way of fully supporting fragmentation would be to syncronise fragments between all anycast servers. This is considered to be to much overhead, so there are two non perfect solutions for this problems. Either fragmentation HAS TO be disabled or if not all fragments arrive at the same server the ip datagramm HAS TO be discarded. As routing changes are not expected to occure very frequently, the ip datagram will get retransmitted by TCP and all fragments will arrive at the new server.
+         </t>
+         </section>
+         <section title="sequence number">
+           <t>It is nessarary to send tcp segments with a correct sequence number, that appear to come from the same host, in order to get a valid connecton to the client. Syncronisation of sequence numbers would mean to much overhead, so it hast to be provided by the relayed data. The relayed data from the anycast serveres point of view, consits of multible datastream, each directed from one client to anotherIn tunneling mode all anytun packets from the client
+           </t>
+         </section>
+       </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>
+    </section>
+        <appendix title='The appan'></appendix>
+    </middle>
+    <back>
+    <references>
+        &rfc3068; An Anycast Prefix for 6to4 Relay Routers
+    </references>
+    </back>
+    </rfc>
+
diff --git a/internet-draft-anytun.xml b/internet-draft-anytun.xml
index ea9ce44..6efd823 100644
--- a/internet-draft-anytun.xml
+++ b/internet-draft-anytun.xml
@@ -169,47 +169,29 @@ client 1  -----------  ->  |server 3|  ->  -----------     client 2
        </figure>
 
       <t>The light UDP mode is neerly the same as the normal UDP mode, the only difference is, that the udp size is set to the udp header lenght and not to the length of the full packet and therefor the checksum is only calculated for the udp header itself. So there is no error correction or detection done on the payload. This can be usefull if realtime data is beeing transimittet or the tunneled protocol does error correction/detection by itself.</t>
-	  </section>
-	  <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>
-	  </section>
-	</section>
-     </section>
+    </section>
      <section title="Protocol specification">
        <section title="Header format">
        </section>
        <section title="Protocol field">
-         <t>The protocol field defines the payload protocol. ETHER TYPE protocol numerbers are used. http://www.iana.org/assignments/ethernet-numbers . The values 0000-05DC are not used for DIX ethernet lenght, but are reservered for special purposes. As the definition of transparent ethernet bridging is very unclear 2 special types are added for ethernet frames<br/>
+         <t>The protocol field defines the payload protocol. ETHER TYPE protocol numerbers are used. http://www.iana.org/assignments/ethernet-numbers . The values 0000-05DC are reserverd and not used at the moment. 
             <figure anchor="prot_type_table">
-               <preamble>Protocol Types</preamble>
+               <preamble>Some exmples for protocol types</preamble>
                  <artwork>
 HEX
 0000 Reserved
-0001 Raw Ethernet - both IEEE 802.3 and DIX ethernet 
-                    without preamble,SFD, PAD and FCS
-0002 Raw ethernet with FCS
-0003 Reserved
 .... Reserved
 05DC Reserved
-05DD as in http://www.iana.org/assignments/ethernet-numbers
-.... as in http://www.iana.org/assignments/ethernet-numbers
 0800 Internet IP (IPv4)
-.... as in http://www.iana.org/assignments/ethernet-numbers
+6558 transparent ethernet bridging
 86DD IPv6
-.... as in http://www.iana.org/assignments/ethernet-numbers
 </artwork>
 </figure>
 </t>
-       </section>
      </section>
+    </section>
+    </section>
+    </section>
         <appendix title='The appan'></appendix>
     </middle>
     <back>