operation modes

1 files changed, 51 insertions, 30 deletions

diff --git a/internet-draft-satp.xml b/internet-draft-satp.xml
index 5011b75..f56afd7 100644
--- a/internet-draft-satp.xml
+++ b/internet-draft-satp.xml
@@ -39,67 +39,85 @@
         <keyword>secure</keyword>
         <keyword>protocol</keyword>
         <abstract>
-            <t>The secure anycast tunneling protocol (satp) defines a protocol used for communication between any combination of unicast and anycast tunnel endpoints. It has less protocol overhead than IPSec in Tunnel mode and allows tunneling of every ETHER TYPE protocol (e.g. ethernet, ip, arp ...). satp directly includes cryptography and message authentication based on the methodes used by SRTP. It is intended to deliver a generic, scaleable, secure and reliability solution for tunneling and relaying of packets of any protocol.
+            <t>The secure anycast tunneling protocol (satp) defines a protocol used for communication between any combination of unicast and anycast tunnel endpoints. It has less protocol overhead than IPSec in Tunnel mode and allows tunneling of every ETHER TYPE protocol (e.g. ethernet, ip, arp ...). satp directly includes cryptography and message authentication based on the methodes used by SRTP. It is intended to deliver a generic, scaleable and secure solution for tunneling and relaying of packets of any protocol.
             </t>
         </abstract>
     </front>
     <middle>
     <section title='Introduction'>
-        <t>anytun defines a Host Anycast Service as defined in rfc1546. It uses a peer-to-peer achitecture, with anycast servers and unicast clients. It can be used to build high scalable and redundant tunnel services. 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>anytun defines a Host Anycast Service as defined in rfc1546. </t>
          <t><xref target="RFC3068">RFC3068</xref> DTD.</t>
     </section> 
-    <section title="Operation modes">
-       <t>This section gives an overview of possible operation modes und usage scenarios. Please note, that the protocols used in the figures are only examples and that anytun itself does not care about either transport protocols or encapsulated protocols. Routing and network address translation is not done by anytun. Each implemetation MAY choose it's own way of doing this task (e.g. using functions provided by the operating system). Anytun is used to establish and controll tunnnels, to encapsulate and encrypt data.</t>
+    <section title="Features and usage scenarios">
+       <t>This section gives an overview of possible operation modes und usage scenarios. Please note, that the protocols used in the figures are only examples and that SATP itself does not care about either transport protocols or encapsulated protocols. Routing is not done by SATP and each implemetation MAY choose it's own way of doing this task (e.g. using functions provided by the operating system). SATP is used only to encapsulate and encrypt data.</t>
        <section title="Usage scenarions">
     
-            <section title='tunneling from unicast client over anycast servers to unicast client'>
+            <section title='tunneling from unicast hosts over anycast routers to other unicast hosts'>
               <figure anchor="tunnel_mode">
-                 <preamble>An example of anytun used in tunnel mode</preamble>
+                 <preamble>An example of SATP used to tunnel in a unicast client - anycast server model</preamble>
                  <artwork>
           -----------                      ----------- 
           |   RTP   |      ----------      |   RTP   |
-          -----------  ->  |server 1|  ->  -----------
+          -----------  ->  |router 1|  ->  -----------
           |   UDP   |      ----------      |   UDP   |
           -----------                      -----------
 -----     |   IPv6  |      ----------      |   IPv6  |     -----
-|   |  -> -----------  ->  |server 2|  ->  -----------  -> |   |
------     |  anytun |      ----------      |  anytun |     -----
+|   |  -> -----------  ->  |router 2|  ->  -----------  -> |   |
+-----     |   SATP  |      ----------      |   SATP  |     -----
 #####     -----------                      -----------     #####
           |   UDP   |      ----------      |   UDP   |
-client 1  -----------  ->  |server 3|  ->  -----------     client 2
-          |   IPv4  |      ----------      |   IPv4  |
-          -----------                      -----------
-          |   ...   |       anycast        |   ...   |
+unicast   -----------  ->  |router 3|  ->  -----------    unicast
+host 1    |   IPv4  |      ----------      |   IPv4  |    host 2
+          -----------       anycast        -----------
+          |   ...   |       hosts          |   ...   |
                  </artwork>
        </figure>
-	      <t>In tunneling mode the payload of the anytun packet is transmitted from one unicast host to the anycast server. This server makes a routing descision based on the underlying protocol and transmits a new anytun package to one or more clients depending on the routing descition. The server MAY also route the packet to a directly connected network or a service running on the server, but please note, that this is only usefull for anycast host services like DNS and that the services HAVE TO be running on all servers in order to work.</t> 
+	      <t>In this scenario the payload of a SATP packet is transmitted from one unicast host to one of the anycast routers. This router makes a routing descision based on the underlying protocol and transmits a new SATP package to one or more unicast hosts depending on the routing descition.</t> 
 	    </section>
 
-	    <section title='tunneling from client to a server connected network'>
+	    <section title='tunneling from unicast hosts to anycast networks'>
               <figure anchor="open_tunnel_mode">
                  <preamble>An example of anytun used in open tunnel mode</preamble>
                  <artwork>
           -----------                                 
-          |   RTP   |      ----------                 
-          -----------  ->  |server 1|  ->             
+          |   DNS   |      ----------                  
+          -----------  ->  |router 1|  ->               -> DNS server
           |   UDP   |      ----------      -----------
-          -----------                      |   RTP   |
------     |   IPv6  |      ----------      -----------     -----
-|   |  -> -----------  ->  |server 2|  ->  |   UDP*  |  -> |   |
------     |  anytun |      ----------      -----------     -----
-#####     -----------                      |   IPv6* |     #####
+          -----------                      |   DNS   |
+-----     |   IPv6  |      ----------      -----------     
+|   |  -> -----------  ->  |router 2|  ->  |   UDP   |  -> DNS server
+-----     |   SATP  |      ----------      -----------      
+#####     -----------                      |   IPv6  |     
           |   UDP   |      ----------      -----------
-client 1  -----------  ->  |server 3|  ->  |   ...   |    host
-          |   IPv4  |      ----------                     not using
-          -----------                                     anytun
+unicast   -----------  ->  |router 3|  ->  |   ...   |  -> DNS server
+host      |   IPv4  |      ----------                     
+          -----------                                     
           |   ...   |       anycast        
-                                           *changed source address
-                                            or port   
                  </artwork>
        </figure>
 
-               <t>In open tunnel mode only one of two clients talking to each other over the servers MUST use the anytun protocol. When a client using the anytun protocol wants to tunnel data, it 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. The source address of the datagramm HAS TO be changed to the anycast address of the server. The anytun servers act like a source NAT router, therefor for the destination it saems that it is talking to the client directly.</t>
+               <t>When a client using the anytun protocol wants to tunnel data, it 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. The source address of the datagramm HAS TO be changed to the anycast address of the server. The anytun servers act like a source NAT router, therefor for the destination it saems that it is talking to the client directly.</t>
 	    </section>
+      <section title='redundant tunnel connection of 2 networks'>
+              <figure anchor="connect_networks">
+                 <preamble>An example of anytun used in open tunnel mode</preamble>
+                 <artwork>
+              Router -----------   ---------------Router
+            /                   \ /                     \
+    Network - Router ------------x                       Network
+       A    \                   / \                     /   B
+              Router -----------   ---------------Router
+
+            | packets       |  packets  |  packets      |
+ plaintext  | get           |  take a   |  get          | plaintext
+ packets    | de/encrypted  |  random   |  de/encrypted | packets
+            |de/encapsulated|   path    |de/encapsulated|              
+
+                 </artwork>
+       </figure>
+
+               <t>Network A has multible routers, that act as gateway/tunnel endpoint to another network B. This is done to build e redundant encrpted tunnel connection between the to networks. All tunnel endpoints of network A share the same anycast address and all tunnel endpoints of network B share another anycast address.</t>
+      </section>
 	</section>
 	<section title="Transport modes">
       <t>Anytun does not define wich lower layer protocols HAVE TO be used, but it's most likely used on top of udp. This section should only discuss some issues on udp in combination with anycasting and tunnels.
@@ -163,7 +181,7 @@ client 1  -----------  ->  |server 3|  ->  -----------     client 2
         0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
-     |                         sequence number                       | |
+     |           sender ID           |         sequence number       | |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
    | |              ....        payload        ...                   | |
@@ -180,8 +198,11 @@ client 1  -----------  ->  |server 3|  ->  -----------     client 2
 </figure>
 <t></t>
        </section>
+       <section title="sender ID">
+       <t>The sender ID is a 16bit unsigned integer in network byte order. It HAS TO be unique for every sender sharing the same anycast address</t>
+       </section>
        <section title="sequence number">
-       <t>The sequenze number is a 32bit unsigned integer in network byte order. It starts with a random value and is increased by 1 for every sent packet. After the maximum value, it starts over from 0. This overrun causes the ROC to be increased.</t>
+       <t>The sequenze number is a 16bit unsigned integer in network byte order. It starts with a random value and is increased by 1 for every sent packet. After the maximum value, it starts over from 0. This overrun causes the ROC to be increased.</t>
        </section>
        <section title="payload">
        <t>A packet of the type payload type (e.g. an IP packet).</t>