enc

3 files changed, 24 insertions, 15 deletions

diff --git a/internet-draft-satp.html b/internet-draft-satp.html
index 49d0dd0..e9f756a 100644
--- a/internet-draft-satp.html
+++ b/internet-draft-satp.html
@@ -358,13 +358,13 @@ Header format</h3>
 <a name="rfc.section.3.2"></a><h3>3.2.&nbsp;
 sender ID</h3>
 
-<p>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
+<p>The sender ID is a 8bit unsigned integer. It HAS TO be unique for every sender sharing the same anycast address
 </p>
 <a name="anchor12"></a><br /><hr />
 <a name="rfc.section.3.3"></a><h3>3.3.&nbsp;
 sequence number</h3>
 
-<p>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.
+<p>The sequenze number is a 24 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.
 </p>
 <a name="anchor13"></a><br /><hr />
 <a name="rfc.section.3.4"></a><h3>3.4.&nbsp;
@@ -390,7 +390,7 @@ padding count</h3>
 <a name="rfc.section.3.7"></a><h3>3.7.&nbsp;
 payload type field</h3>
 
-<p>The payload type 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 MUST NOT be used. 
+<p>The payload type field defines the payload protocol. ETHER TYPE protocol numerbers are used. <a href='http://www.iana.org/assignments/ethernet-numbers'>See IANA assigned ethernet numbers</a> . The values 0000-05DC are reserverd and MUST NOT be used. 
             <br /><hr class="insert" />
 <a name="prot_type_table"></a>
 
@@ -408,6 +408,12 @@ HEX
 
 
 <a name="anchor17"></a><br /><hr />
+<a name="rfc.section.3.8"></a><h3>3.8.&nbsp;
+Encryption</h3>
+
+<p>Encryption is done in the same way as for <a class='info' href='#RFC3711'>SRTP<span> (</span><span class='info'>Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, &ldquo;The Secure Real-time Transport Protocol (SRTP),&rdquo; March&nbsp;2004.</span><span>)</span></a> [3]. This section will only discuss some small changes that HAVE TO be made.
+</p>
+<a name="anchor18"></a><br /><hr />
 <a name="rfc.section.A"></a><h3>Appendix A.&nbsp;
 The appan</h3>
 
diff --git a/internet-draft-satp.txt b/internet-draft-satp.txt
index 6c0b332..eda4f18 100644
--- a/internet-draft-satp.txt
+++ b/internet-draft-satp.txt
@@ -420,12 +420,12 @@ Internet-Draft  secure anycast tunneling protocol (satp)      March 2007
 
 3.2.  sender ID
 
-   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
+   The sender ID is a 8bit unsigned integer.  It HAS TO be unique for
+   every sender sharing the same anycast address
 
 3.3.  sequence number
 
-   The sequenze number is a 16bit unsigned integer in network byte
+   The sequenze number is a 24 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.
@@ -462,9 +462,8 @@ Internet-Draft  secure anycast tunneling protocol (satp)      March 2007
 3.7.  payload type field
 
    The payload type 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 MUST NOT be used.
+   protocol numerbers are used.  See IANA assigned ethernet numbers [5]
+   .  The values 0000-05DC are reserverd and MUST NOT be used.
 
    Some examples for protocol types
 
@@ -478,9 +477,10 @@ Internet-Draft  secure anycast tunneling protocol (satp)      March 2007
 
                                  Figure 6
 
+3.8.  Encryption
 
-
-
+   Encryption is done in the same way as for SRTP [3].  This section
+   will only discuss some small changes that HAVE TO be made.
 
 
 
@@ -576,7 +576,7 @@ Internet-Draft  secure anycast tunneling protocol (satp)      March 2007
    [4]  Partridge, C., Mendez, T., and W. Milliken, "Host Anycasting
         Service", RFC 1546, November 1993.
 
-
+   [5]  <http://www.iana.org/assignments/ethernet-numbers>
 
 
 
diff --git a/internet-draft-satp.xml b/internet-draft-satp.xml
index 7e36bc8..6ce96c7 100644
--- a/internet-draft-satp.xml
+++ b/internet-draft-satp.xml
@@ -189,10 +189,10 @@ Tunneling of IPv6 over IPv4 with RTP payload
 <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>
+       <t>The sender ID is a 8bit unsigned integer. 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 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>
+       <t>The sequenze number is a 24 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.</t>
        </section>
        <section title="payload">
        <t>A packet of the type payload type (e.g. an IP packet).</t>
@@ -206,7 +206,7 @@ None of the pre-defined encryption transforms uses any padding; for
        <t>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 protocol. If this field isn't present, the padding field MUST NOT be present as well.</t>
        </section>
        <section title="payload type field">
-         <t>The payload type 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 MUST NOT be used. 
+         <t>The payload type field defines the payload protocol. ETHER TYPE protocol numerbers are used. <eref target="http://www.iana.org/assignments/ethernet-numbers">See IANA assigned ethernet numbers</eref> . The values 0000-05DC are reserverd and MUST NOT be used. 
             <figure anchor="prot_type_table">
                <preamble>Some examples for protocol types</preamble>
                  <artwork>
@@ -221,6 +221,9 @@ HEX
 </figure>
 </t>
      </section>
+    <section title="Encryption">
+     <t>Encryption is done in the same way as for <xref target="RFC3711">SRTP</xref>. This section will only discuss some small changes that HAVE TO be made.</t>
+    </section>
     </section>
         <appendix title='The appan'></appendix>
     </middle>