Re: [TLS] I-D ACTION:draft-ietf-tls-rfc2246-bis-09.txt

[ This announcement was cc'ed to ietf-tls@lists.certicom.com. 
  Someone should probably change this to tls@ietf.org ]

I looked at some of the changes in draft-ietf-tls-rfc2246-bis-09.txt, 
and my comments are below.

Section 6.2.1:
> Note: Data of different TLS Record layer content types MAY be
>       interleaved. Application data is generally of higher precedence
>       for transmission than other content types and therefore handshake

I thought application data had _lower_ precedencs than other
content types. SSL 3.0, TLS 1.0 and draft 8 says so.
Is this a change to TLS in draft 9?

Section 6.3:
>   Implementation note:
>       The currently defined which requires the most material is
>       AES_256_CBC_SHA, defined in [TLSAES]. It requires 2 x 32 byte

I think "cipher spec" is missing from this sentence.

Section A.5:
>    CipherSuite      TLS_KRB5_EXPORT_WITH_DES_CBC_40_SHA  = { 0x00,0x26
>   };
>    CipherSuite      TLS_KRB5_EXPORT_WITH_RC2_CBC_40_SHA  = { 0x00,0x27
>   };
>    CipherSuite      TLS_KRB5_EXPORT_WITH_RC4_40_SHA      = { 0x00,0x28
>   };
>    CipherSuite      TLS_KRB5_EXPORT_WITH_DES_CBC_40_MD5  = { 0x00,0x29
>   };
>    CipherSuite      TLS_KRB5_EXPORT_WITH_RC2_CBC_40_MD5  = { 0x00,0x2A
>   };
>    CipherSuite      TLS_KRB5_EXPORT_WITH_RC4_40_MD5      = { 0x00,0x2B
>   };

Strange formatting here.

-- 
Jostein Tveit <josteitv@pvv.ntnu.no>

_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls