Re: [TLS] TLS 1.3 process

Douglas Stebila <stebila@qut.edu.au> Fri, 28 March 2014 12:28 UTC

From: Douglas Stebila <stebila@qut.edu.au>
To: "<tls@ietf.org>" <tls@ietf.org>
Thread-Topic: [TLS] TLS 1.3 process
Thread-Index: AQHPSgZiiOF3YEf/ZUKH5OC10VCCx5r04PEAgAAF2ICAAA4egIAAm+yAgAA1+4A=
Date: Fri, 28 Mar 2014 12:28:40 +0000
Message-ID: <0C41E872-6DDD-47DF-98F1-099D9B68D008@qut.edu.au>
References: <AF370E26-CA97-4CE3-9CC7-2F0939FE2B71@ieca.com> <CAGZ8ZG3dh23is9gj3XHzwaLkustznmYNECSGUL7zu_vJFfCNRA@mail.gmail.com> <CABkgnnWUvc2txkWQxhfEAT3N3Z+_pDn8ti2K6_-8MODLZrw0fw@mail.gmail.com> <CAGZ8ZG0X5c07+jUasfp5TRwSKNKtLoFDCQc7S+px6i0fCaRk2Q@mail.gmail.com> <1395998127.19721.61.camel@dhcp-2-127.brq.redhat.com>
In-Reply-To: <1395998127.19721.61.camel@dhcp-2-127.brq.redhat.com>
Accept-Language: en-CA, en-AU, en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B14277372D79AB4A8F8C02CBF8E5BD29@exchange.qut.edu.au>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/TByFwZ9FxpjiGEpxenet0ryS90M
Subject: Re: [TLS] TLS 1.3 process
Precedence: list

On Thu, 2014-03-27 at 16:57 -0700, Trevor Perrin wrote:

>> Sure, here's my proposal:
>> 
>> * The WG chairs continue to encourage discussion of goals and design
>> alternatives for TLS 1.3.  However, the WG holds off from making
>> binding decisions regarding TLS 1.3.
>> 
>> * The WG encourages interested parties to submit proposals for TLS 1.3.
>> 
>> * In X months time (4-6?), the WG chooses which proposal to adopt as
>> the base for TLS 1.3, and works to improve it for publication.

Please leave a healthy dose of time for academic cryptographers to analyze the protocols and try to develop attacks or proofs of security.  Complex message flows / state machines, like renegotiation and resumption, are hard to model and hard to prove.  Even if renegotiation is axed, we may have TLS candidates with complex flows and states, such as a zero round trip protocol with partial forward secrecy for parts of the handshake and initial application data and then the whole connection upgraded to forward secrecy on the server reply.

Douglas

[TLS] TLS 1.3 process Sean Turner
Re: [TLS] TLS 1.3 process Trevor Perrin
Re: [TLS] TLS 1.3 process Watson Ladd
Re: [TLS] TLS 1.3 process Martin Thomson
Re: [TLS] TLS 1.3 process Trevor Perrin
Re: [TLS] TLS 1.3 process Salz, Rich
Re: [TLS] TLS 1.3 process Peter Gutmann
Re: [TLS] TLS 1.3 process Nikos Mavrogiannopoulos
Re: [TLS] TLS 1.3 process t.petch
Re: [TLS] TLS 1.3 process Stephen Farrell
Re: [TLS] TLS 1.3 process Nikos Mavrogiannopoulos
Re: [TLS] TLS 1.3 process Douglas Stebila
Re: [TLS] TLS 1.3 process Salz, Rich
Re: [TLS] TLS 1.3 process Watson Ladd
Re: [TLS] TLS 1.3 process Dan Harkins
Re: [TLS] TLS 1.3 process Nikos Mavrogiannopoulos
Re: [TLS] TLS 1.3 process Adam Langley
Re: [TLS] TLS 1.3 process Eric Rescorla
Re: [TLS] TLS 1.3 process Watson Ladd
Re: [TLS] TLS 1.3 process Trevor Perrin
Re: [TLS] TLS 1.3 process Bill Frantz
Re: [TLS] TLS 1.3 process Eric Rescorla
Re: [TLS] TLS 1.3 process Dan Harkins
Re: [TLS] TLS 1.3 process Peter Gutmann
Re: [TLS] TLS 1.3 process Peter Gutmann
Re: [TLS] TLS 1.3 process Peter Gutmann
Re: [TLS] TLS 1.3 process Bill Frantz
Re: [TLS] TLS 1.3 process Dan Harkins
Re: [TLS] TLS 1.3 process Salz, Rich
Re: [TLS] TLS 1.3 process Peter Gutmann
Re: [TLS] TLS 1.3 process Bill Frantz
Re: [TLS] TLS 1.3 process Dan Harkins
Re: [TLS] TLS 1.3 process Watson Ladd
Re: [TLS] TLS 1.3 process Dan Harkins
Re: [TLS] TLS 1.3 process Peter Gutmann
Re: [TLS] TLS 1.3 process Andy Lutomirski
Re: [TLS] TLS 1.3 process henry.story@bblfish.net