Subject: Re: [TLS] Missing cipher: anon ephemeral ECDH w/ SHA-2 nor

From: "Lewis, Nick" <[email-masked]>
Date: Fri, 22 Mar 2013 09:24:51 +0000

>If nothing else we should have consistency, and we should define all modern cipher suites
>that make sense (e.g., we'd not define suites for stream ciphers w/ block cipher modes).
>We might leave some out (e.g., why bother with old non-AEAD modes for new block ciphers?),
>but we should not leave out modern suites providing important functionality that TLS has
>generally offered before (again, anon cipher suites with modern algorithms).

Nico

It is good to hear from someone with such high levels of motivation

I privately use cipher suites that I have never attempted to register or write an RFC for.
If you do write an RFC to add some cipher suites to the registry could you please consider
including these too:
 - TLS_ECDH_ECDSA_WITH_NULL_SHA256
 - TLS_ECDH_ECDSA_WITH_NULL_SHA384
 - TLS_ECDHE_ECDSA_WITH_NULL_SHA256
 - TLS_ECDHE_ECDSA_WITH_NULL_SHA384
 - TLS_ECDH_RSA_WITH_NULL_SHA256
 - TLS_ECDH_RSA_WITH_NULL_SHA384
 - TLS_ECDHE_RSA_WITH_NULL_SHA256
 - TLS_ECDHE_RSA_WITH_NULL_SHA384

--
Nick

The details of this company are as follows:
G4S Technology Limited, Registered Office: Challenge House, International Drive, Tewkesbury, Gloucestershire GL20 8UQ, Registered in England No. 2382338.

This communication may contain information which is confidential, personal and/or privileged.

It is for the exclusive use of the intended recipient(s).
If you are not the intended recipient(s), please note that any distribution, forwarding, copying or use of this communication or the information in it is strictly prohibited.

Any personal views expressed in this e-mail are those of the individual sender and the company does not endorse or accept responsibility for them.

Prior to taking any action based upon this e-mail message, you should seek appropriate confirmation of its authenticity.

This e-mail has been scanned for all viruses by MessageLabs.