Re: [kitten] Call for adoption on draft-whited-tls-channel-bindings-for-tls13

[Sam Whited <[e-mail]>]

On Thu, Jun 4, 2020, at 14:37, Simo Sorce wrote:
> Over time I've heard comments that the current tls-unique bindings are
> not working out as initially expected. It would be nice to know if we
> also plan to address those issues in this draft (or whether this draft
> already avoid those).

To my knowledge there are two problems here: 1) it's not long enough,
and 2) without the master secret fix it's not actually unique enough.
This spec should fix both of those. If there are any other problems with
tls-unique that I'm not aware of, we should definitely fix them and this
is why the TLS WG would need to be involved most likely.

> Note that in practice, in the wild, I see that most implementations I
> am exposed to are opting for tls-server-end-point, so it would be
> important to know that this new bindings of type unique for TLS 1.3
> will be usable and there are consumers wanting to use them.

I wouldn't mind having an end-point binding mechanism too, and could see
us adding that to this document eventually; to start though I wanted to
get the most dead simple thing in the hands of the IETF.

> Not pushing back just asking to address these questions in due course.

Indeed; I've added them to my list of TODOs, issues, and open
questions. Thanks!

—Sam

-- 
Sam Whited