Re: [TLS] Remove deprecated fields in TLS 1.3

2017-04-02 Thread Benjamin Kaduk
On 04/02/2017 03:33 AM, Arnaud Venturi wrote: > I could not think of any security or interoperability issue with this > proposal, the only drawback I can see being the slight complexity added > in ClientHello parsing. The ClientHello message needs to be interpreted in the same way by TLS servers

Re: [TLS] Current TLS 1.3 state?

2017-04-02 Thread Eric Rescorla
On Sun, Apr 2, 2017 at 11:18 AM, Watson Ladd wrote: > Dear all, > > Sorry if I'm asking a question already answered elsewhere, but I am > wondering what the current state of the TLS 1.3 draft is. We have completed a second WGLC on -19 and I intend to put out -20 this

[TLS] Current TLS 1.3 state?

2017-04-02 Thread Watson Ladd
Dear all, Sorry if I'm asking a question already answered elsewhere, but I am wondering what the current state of the TLS 1.3 draft is. There seem to have been some major changes considered and put in after 27 March, and I don't know if the formal modeling ever got back about how much they could

Re: [TLS] draft-ietf-tls-tls13-19 section 1.2 cleanup

2017-04-02 Thread Yoav Nir
Hi. So I’ve just submitted PR #931 to resolve this. https://github.com/tlswg/tls13-spec/pull/931 Yoav > On 28 Mar 2017, at 23:31, Dave Garrett wrote: > > On Tuesday, March 28, 2017 11:31:56 am Short, Todd wrote: >> I

[TLS] Remove deprecated fields in TLS 1.3

2017-04-02 Thread Arnaud Venturi
Hello everybody, Here is a proposal for change aiming at removing the deprecated fields in ClientHello in a future TLS version. This proposal would consist in changing the ClientHello structure from : struct { ProtocolVersion legacy_version = 0x0303;/* TLS v1.2 */ Random