From e335fdee27dd9756478f174a2edabdda61e61fb7 Mon Sep 17 00:00:00 2001 From: Christian Pointner Date: Mon, 31 Mar 2008 00:45:28 +0000 Subject: fixed some typos @ internet draft --- draft-gsenger-secure-anycast-tunneling-protocol-02.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'draft-gsenger-secure-anycast-tunneling-protocol-02.html') diff --git a/draft-gsenger-secure-anycast-tunneling-protocol-02.html b/draft-gsenger-secure-anycast-tunneling-protocol-02.html index 8b5e98d..80ab6c9 100644 --- a/draft-gsenger-secure-anycast-tunneling-protocol-02.html +++ b/draft-gsenger-secure-anycast-tunneling-protocol-02.html @@ -299,7 +299,7 @@ Tunneling from unicast hosts over anycast routers to other unicast hosts endpoint | using SATP | endpoint | using SATP | endpoint
 Figure 1 
-

In this scenario the payload gets encapsuleted into a SATP packet by a unicast host and gets transmitted to one of the anycast routers. It than gets decapsulated by the router. 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. +

In this scenario the payload gets encapsuleted into a SATP packet by a unicast host and gets transmitted to one of the anycast routers. It than gets decapsulated by the router. 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 decision.


 TOC 
@@ -516,7 +516,7 @@ padding (OPTIONAL)

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 the padding count field is present, than the padding count field MUST be set to the padding lenght. + 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 the padding count field is present, than the padding count field MUST be set to the padding length.


 TOC 
@@ -546,7 +546,7 @@ Encryption

Encryption is done in the same way as for SRTP (Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, “The Secure Real-time Transport Protocol (SRTP),” March 2004.) [1]. This section will only discuss some small changes that HAVE TO be made. Please read SRTP RFC3711 section 3-9 (Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, “The Secure Real-time Transport Protocol (SRTP),” March 2004.) [1] for details.

-

The least significant bits of SSRC are replaced by the sender ID and the rest is filled with zeros. For the SRTP SEQ the 16 least significant bits of the SATP sequence number are used and the 16 most significant bits of the sequence number replace the 16 least significant bits of the SRTP ROC. +

The least significant bits of SSRC are replaced by the sender ID and the most significant bits are replaced by the mux. For the SRTP SEQ the 16 least significant bits of the SATP sequence number are used and the 16 most significant bits of the sequence number replace the 16 least significant bits of the SRTP ROC.


@@ -579,7 +579,7 @@ Encryption

5.  Security Considerations

-

As SATP uses the same encrytion technics as SRTP (Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, “The Secure Real-time Transport Protocol (SRTP),” March 2004.) [1], it shares the same security issues. This section will only discuss some small changes. Please read SRTP RFC3711 section 9 (Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, “The Secure Real-time Transport Protocol (SRTP),” March 2004.) [1] for details. +

As SATP uses the same encryption techniques as SRTP (Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, “The Secure Real-time Transport Protocol (SRTP),” March 2004.) [1], it shares the same security issues. This section will only discuss some small changes. Please read SRTP RFC3711 section 9 (Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, “The Secure Real-time Transport Protocol (SRTP),” March 2004.) [1] for details.


 TOC 
-- cgit v1.2.3