diff options
| author | Othmar Gsenger <otti@anytun.org> | 2007-04-20 09:38:14 +0000 |
|---|---|---|
| committer | Othmar Gsenger <otti@anytun.org> | 2007-04-20 09:38:14 +0000 |
| commit | 25898a1c8702897ec9a4a2c3fb08485480efc65d (patch) | |
| tree | 34427f3cf667c5717d948e0c4ef1db2a12c6f684 /internet-draft-satp.xml | |
| parent | fixed srtp ref (diff) | |
enc
Diffstat (limited to 'internet-draft-satp.xml')
| -rw-r--r-- | internet-draft-satp.xml | 9 |
1 files changed, 6 insertions, 3 deletions
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> |