Re: [TLS] SVCB codepoint for ECH

2023-09-21 Thread Stephen Farrell
On 21/09/2023 16:01, Salz, Rich wrote: https://github.com/tlswg/draft-ietf-tls-esni/pull/553 Looks good to me.

Re: [TLS] SVCB codepoint for ECH

2023-09-21 Thread Christopher Wood
Ugh, sorry everyone. I both forgot that this other draft (draft-sbn-tls-svcb-ech) existed and that we had already decided to put the code point in draft. Even better, as you say, that draft already has the codepoint request and was adopted. I closed this PR. Ben, Mike, Erik: can you please

Re: [TLS] SVCB codepoint for ECH

2023-09-21 Thread David Benjamin
How do we want to handle the rest of draft-sbn-tls-svcb-ech? It got WG adoption in May, but I don't think anything's happened with it since. (Unless we decided something and I forgot?) In particular, the section on switching to SVCB-reliant mode is important for a client:

Re: [TLS] SVCB codepoint for ECH

2023-09-21 Thread Salz, Rich
> > https://github.com/tlswg/draft-ietf-tls-esni/pull/553 Looks good to me.

[TLS] SVCB codepoint for ECH

2023-09-21 Thread Christopher Wood
Hi folks, Since the SVCB draft removed the “ech” parameter registration request (to expedite publication of that draft), we need to request registration elsewhere. It seems simplest to do this right in the ECH draft itself. To that end, I put up a PR to add the request (based on how this is