Re: [TLS] Re: I-D ACTION:draft-ietf-tls-srp-13.txt

[Eric Rescorla <ekr@xxxxxxxxxxxxxxxxxxxx>]

Peter Sylvester <Peter.Sylvester@xxxxxxxxxx> writes:

> Hello,
>
> it took me a while to discover that the new srp-tls draft contains:
>
>
>
>       CipherSuite TLS_SRP_SHA_WITH_3DES_EDE_CBC_SHA = { 0xC0,0xTBD2 };
>
>       CipherSuite TLS_SRP_SHA_RSA_WITH_3DES_EDE_CBC_SHA = { 0xC0,0xTBD3
>       };
>
>       CipherSuite TLS_SRP_SHA_DSS_WITH_3DES_EDE_CBC_SHA = { 0xC0,0xTBD4
>       };
>
>       CipherSuite TLS_SRP_SHA_WITH_AES_128_CBC_SHA = { 0xC0,0xTBD5 };
>
>       CipherSuite TLS_SRP_SHA_RSA_WITH_AES_128_CBC_SHA = { 0xC0,0xTBD6
>       };
>
>       CipherSuite TLS_SRP_SHA_DSS_WITH_AES_128_CBC_SHA = { 0xC0,0xTBD7
>       };
>
>       CipherSuite TLS_SRP_SHA_WITH_AES_256_CBC_SHA = { 0xC0,0xTBD8 };
>
>       CipherSuite TLS_SRP_SHA_RSA_WITH_AES_256_CBC_SHA = { 0xC0,0xTBD9
>       };
>
>       CipherSuite TLS_SRP_SHA_DSS_WITH_AES_256_CBC_SHA = { 0xC0,0xTBD10
>       };
>
>
> Does this mean that that the document is not supposed to proceed in
> standards track
> according to TLS 1.1?
>
>      2. Cipher suite values with first byte decimal 192 (0xC0) through
>          decimal 254 (0xFE) inclusive are reserved for assignment for
>          non-Standards Track methods.

Yes. This document is expected to proceed as Experimental.

-Ekr

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