typos speedy complete

1 files changed, 36 insertions, 92 deletions

diff --git a/internet-draft-satp.txt b/internet-draft-satp.txt
index 36f08ca..2cd33d1 100644
--- a/internet-draft-satp.txt
+++ b/internet-draft-satp.txt
@@ -184,7 +184,7 @@ Internet-Draft  secure anycast tunneling protocol (satp)      March 2007
 2.1.1.  tunneling from unicast hosts over anycast routers to other
         unicast hosts
 
-   An example of SATP used to tunnel in an unicast client - anycast
+   An example of SATP used to tunnel in a unicast client - anycast
    server model
 
                        --------- router -----------
@@ -267,12 +267,12 @@ Internet-Draft  secure anycast tunneling protocol (satp)      March 2007
 
                                  Figure 3
 
-   Network A has multible routers, that act as gateway/tunnel endpoint
-   to another network B. This is done to build a redundant encrpted
+   Network A has multiple routers, that act as gateway/tunnel endpoints
+   to another network B. This is done to build a redundant encrypted
    tunnel connection between the two networks.  All tunnel endpoints of
    network A share the same anycast address and all tunnel endpoints of
    network B share another anycast address.  When a packet from network
-   a gets transmitted to network B, it first arrives on one of networks
+   A gets transmitted to network B, it first arrives on one of network
 
 
 
@@ -281,17 +281,17 @@ Gsenger                 Expires September 2, 2007               [Page 5]
 Internet-Draft  secure anycast tunneling protocol (satp)      March 2007
 
 
-   A border routers.  Which router is used is determined by network A's
-   internal routing.  This router encapsulates the package and sends it
-   to the anycast address of the network B routers.  The SATP packet
+   A's border routers.  Which router is used is determined by network
+   A's internal routing.  This router encapsulates the package and sends
+   it to the anycast address of the network B routers.  The SATP packet
    arrives at one of network B's routers and gets decapsulated and
    routed to it's destination within network B.
 
 2.2.  Encapsulation
 
-   SATP does not depend an which lower layer protocols is used, but it's
-   most likely used on top of ip or udp.  This section should only
-   discuss some issues on ip and udp in combination with anycasting and
+   SATP does not depend on which lower layer protocols is used, but it's
+   most likely used on top of IP or UDP.  This section should only
+   discuss some issues on IP and UDP in combination with anycasting and
    tunnels.
 
    Examples of SATP used with different lower layer and payload
@@ -339,22 +339,22 @@ Internet-Draft  secure anycast tunneling protocol (satp)      March 2007
 
                                  Figure 4
 
-   When using UDP no flow controll or retransmission is done, neigther
-   by UDP nor anytun.  The encapsulated protocol HAS TO take care of
-   this tasks if needed.  UDP however has a checksum of the complete udp
+   When using UDP no flow control or retransmission is done, neither by
+   UDP nor anytun.  The encapsulated protocol HAS TO take care of this
+   tasks if needed.  UDP however has a checksum of the complete UDP
    datagram, so a packet gets discarded if there is a biterror in the
    payload
 
 2.3.  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 encapsulated protocol can do a retransmission and all
-   fragments will arrive at the new server.
+   The only way of fully supporting fragmentation would be to
+   synchronise fragments between all anycast servers.  This is
+   considered to be too much overhead, so there are two non perfect
+   solutions for these 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 encapsulated protocol can do a
+   retransmission and all fragments will arrive at the new server.
 
 
 
@@ -402,13 +402,14 @@ Internet-Draft  secure anycast tunneling protocol (satp)      March 2007
         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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
-     |           sender ID           |         sequence number       | |
-     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
-   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
+     |                         sequence number                       | |
+     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ |
+     |           sender ID           #                               | |
+   +#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+                               + |
    | |              ....        payload        ...                   | |
    | |-------------------------------+-------------------------------+ |
    | | padding (OPT) | pad count(OPT)|         payload type          | |
-   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+   +#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+-+
    | ~                          MKI (OPTIONAL)                       ~ |
    | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
    | :                 authentication tag (RECOMMENDED)              : |
@@ -420,12 +421,12 @@ Internet-Draft  secure anycast tunneling protocol (satp)      March 2007
 
 3.2.  sender ID
 
-   The sender ID is a 8bit unsigned integer.  It HAS TO be unique for
+   The sender ID is a 16bit unsigned integer.  It HAS TO be unique for
    every sender sharing the same anycast address
 
 3.3.  sequence number
 
-   The sequenze number is a 24 bit unsigned integer in network byte
+   The sequence number is a 32 bit 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.
@@ -436,11 +437,10 @@ Internet-Draft  secure anycast tunneling protocol (satp)      March 2007
 
 3.5.  padding (OPTIONAL)
 
-   Padding of max 255 ocitets.  None of the pre-defined encryption
+   Padding of max 255 octets.  None of the pre-defined encryption
    transforms uses any padding; for these, the plaintext and encrypted
    payload sizes match exactly.  Transforms are based on transforms of
    the SRTP protocol and these transforms might use the RTP padding
-   format, so a RTP like padding is supported.  If padding field is
 
 
 
@@ -449,21 +449,22 @@ Gsenger                 Expires September 2, 2007               [Page 8]
 Internet-Draft  secure anycast tunneling protocol (satp)      March 2007
 
 
+   format, so a RTP like padding is supported.  If padding field is
    present, than the padding count field MUST be set to the padding
    lenght.
 
 3.6.  padding count
 
    The number of octets of the padding field.  This field is optional.
-   It's presents is signaled by the key management and not by this
+   It's presence is signaled by the key management and not by this
    protocol.  If this field isn't present, the padding field MUST NOT be
    present as well.
 
 3.7.  payload type field
 
    The payload type field defines the payload protocol.  ETHER TYPE
-   protocol numerbers are used.  See IANA assigned ethernet numbers [5]
-   .  The values 0000-05DC are reserverd and MUST NOT be used.
+   protocol numbers are used.  See IANA assigned ethernet numbers [5] .
+   The values 0000-05DC are reserverd and MUST NOT be used.
 
    Some examples for protocol types
 
@@ -499,68 +500,11 @@ Internet-Draft  secure anycast tunneling protocol (satp)      March 2007
 
 
 
-
 Gsenger                 Expires September 2, 2007               [Page 9]
 
 Internet-Draft  secure anycast tunneling protocol (satp)      March 2007
 
 
-Appendix A.  The appan
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Gsenger                 Expires September 2, 2007              [Page 10]
-
-Internet-Draft  secure anycast tunneling protocol (satp)      March 2007
-
-
 4.  References
 
    [1]  Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. Traina,
@@ -612,7 +556,7 @@ Internet-Draft  secure anycast tunneling protocol (satp)      March 2007
 
 
 
-Gsenger                 Expires September 2, 2007              [Page 11]
+Gsenger                 Expires September 2, 2007              [Page 10]
 
 Internet-Draft  secure anycast tunneling protocol (satp)      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  secure anycast tunneling protocol (satp)      March 2007
 
@@ -724,5 +668,5 @@ Acknowledgment
 
 
 
-Gsenger                 Expires September 2, 2007              [Page 13]
+Gsenger                 Expires September 2, 2007              [Page 12]