Re: [kitten] TLS export for channel binding

[Sam Whited <[e-mail]>]

On Fri, May 8, 2020, at 11:41, tom petch wrote:
> which I think is the problem; whose is? The I-D baldly states that the
> current channel binding does not work with TLS 1.3, with no
> explanation.

I'll fix that, thanks!


> Whatever, this I-D needs to spell the problem out and IMHO update the
> current RFC on TLS Channel Binding so that others can see that there
> is a problem.

Is there a different process to update an existing RFC vs. creating a
new I-D and trying to get it adopted by a WG? I'm still unclear on the
process in general, and it seems like this might be different.

If we're updating that document anyways, I assume the TLS WG would be
the place and we might as well integrate this I-D into the document
update instead of keeping it a separate I-D.

> Which pushes me to thinking that this I-D

Looks like this got cut off?

Thanks for the feedback!

—Sam

-- 
Sam Whited