Re: [TLS] Proposed text for removing renegotiation

[Martin Thomson <[e-mail]>]

On 9 June 2014 11:49, Andrei Popov <[e-mail]> wrote:
>> The former we have decided to solve in HTTP.
>
> Are you referring to these I-Ds:
> http://tools.ietf.org/html/draft-thomson-httpbis-cant-00
> http://tools.ietf.org/html/draft-thomson-tls-care-00
>
> Httpbis-cant talks (rather vaguely) about using "realm" or "other challenge parameters" to select an appropriate client cert. I think client cert selection should be clearly specified before we can say that the mid-session client auth problem has been solved, and remove renegotiation from TLS 1.3.

The selection problem is, as we discussed in Denver, worth addressing.
The short term fix in HTTP/2 will actually be to force these users
down to HTTP/1.1.  That's suboptimal, certainly, but it does fix the
immediate problem.

As far as the -cant draft goes, I simply haven't uploaded an updated
version after our discussion in Denver.  There's a work in progress
version on github:
http://martinthomson.github.io/drafts/draft-thomson-httpbis-cant.html

> It would be even better to solve this problem at the TLS layer, so that each application protocol does not need to come up with a separate solution. And avoiding the round-trips involved in establishing a TCP connection would be awesome, too. The current solution using renegotiation has both of these desirable properties.

I'm sympathetic to this, but if HTTP is the only one that wants this
particular feature, then we are better off leaving them to work around
this.  At least in my opinion.