Re: [TLS] a proposal for TLS 1.3

The story in IKEv2 was different. There were a few guys (already active 
in the IETF for a long time) proposing designs and there wasn't really 
an outreach to the research  outside the IETF, as far as I recall.

There was some work on documenting the design decisions (which also 
explains the problem being solved and captures the requirements) but 
that did not go anywhere. Here is the document: 
http://tools.ietf.org/html/draft-ietf-ipsec-ikev2-tutorial-01

Of course it takes longer than 2 IETF when it comes to such a complex task.

Am 12.11.13 11:51, schrieb Yaron Sheffer:
> What Nikos proposes is reminiscent of what happened with IKEv2. I wasn't
> following closely at the time (more than 10 years ago), but:
>
> - This did bring in people from the research community. See for example,
> http://tools.ietf.org/html/draft-ietf-ipsec-jfk-03.
> - It took WAY longer than 2 IETF cycles.
> - As far as I know there was never a problem statement document.
>
> So it's not a glowing example, but it proves this can be done.
>
> Thanks,
>      Yaron
>
> On 11/12/2013 12:05 PM, Yoav Nir wrote:
>> Hi Nikos. This is pretty much what httpbis did for HTTP/2. Only it did
>> not take a year or two - only two IETF cycles.
>>
>> So a competition could be announced now, with proposals presented in
>> London, and a decision reached before Toronto.
>>
>> While there are many research groups, they don't do protocol work so
>> much.
>>
>> The real tricky thing here is not designing a "new TLS", but
>> co-existence with SSLv3, TLS 1.0, 1.1, and 1.2 without resorting to
>> the kind of fallback mechanism where you try with TLS 1.3 (or 2.0, or
>> even better - 4.0) and if you get a reset, try again with TLS 1.2, and
>> if that doesn't work, go straight to SSLv3.
>>
>> -----Original Message-----
>> From: tls-bounces@ietf.org [mailto:tls-bounces@ietf.org] On Behalf Of
>> Nikos Mavrogiannopoulos
>> Sent: Tuesday, November 12, 2013 11:55 AM
>> To: tls@ietf.org
>> Subject: [TLS] a proposal for TLS 1.3
>>
>> Hello,
>>   Having seen the current discussion for TLS 1.3, I have some proposal.
>> Since the changes requested are large, I'd suggest not to design TLS
>> 1.3 in this working group. I'd suggest this working group to set the
>> specs for the next TLS version (and better name it 2.0), and then
>> announce a competition for the initial draft of the protocol. Then
>> have the WG review the submitted proposals in a year or two, accept a
>> winner, and the WG starts working on the winning draft.
>>
>> I'm pretty sure there are many research groups that will be honoured
>> to join such a competition and their results may outperform the
>> results of the limited number of participants in the working group.
>>
>> best regards,
>> Nikos
>>
>> _______________________________________________
>> TLS mailing list
>> TLS@ietf.org
>> https://www.ietf.org/mailman/listinfo/tls
>>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls