Re: [TLS] SVCB codepoint for ECH

[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.


+1

Cheers,
S.


OpenPGP_0xE4D8E9F997A833DD.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature
___
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls

Re: [TLS] SVCB codepoint for ECH

[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 submit the WG version of this document? The I-D 
expired on September 12.

Thanks, and apologies again for any confusion.

Best,
Chris

> On Sep 21, 2023, at 12:11 PM, David Benjamin  wrote:
> 
> 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:
> https://www.ietf.org/archive/id/draft-sbn-tls-svcb-ech-00.html#section-4.1
> 
> Whether it's the same document or a separate one, I think the SVCB codepoint 
> should be allocated in the same document that discusses how to use the SVCB 
> codepoint. Since there's movement towards putting it in the ECH one and no 
> movement on draft-sbn, just folding it all in and making one document is 
> tempting...
> 
> On Thu, Sep 21, 2023 at 11:01 AM Salz, Rich 
> mailto:40akamai@dmarc.ietf.org>> 
> wrote:
>>  
>> 
>> >   https://github.com/tlswg/draft-ietf-tls-esni/pull/553 
>> > 
>>  
>> 
>>  
>> 
>> Looks good to me.
>> 
>> ___
>> 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

Re: [TLS] SVCB codepoint for ECH

[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:
https://www.ietf.org/archive/id/draft-sbn-tls-svcb-ech-00.html#section-4.1

Whether it's the same document or a separate one, I think the SVCB
codepoint should be allocated in the same document that discusses how to
use the SVCB codepoint. Since there's movement towards putting it in
the ECH one and no movement on draft-sbn, just folding it all in and making
one document is tempting...

On Thu, Sep 21, 2023 at 11:01 AM Salz, Rich  wrote:

>
>
> >   https://github.com/tlswg/draft-ietf-tls-esni/pull/553
> 
>
>
>
>
>
> Looks good to me.
> ___
> 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

Re: [TLS] SVCB codepoint for ECH

[Salz, Rich]

>   
> https://github.com/tlswg/draft-ietf-tls-esni/pull/553


Looks good to me.
___
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls

[TLS] SVCB codepoint for ECH

[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 deployed today):

   https://github.com/tlswg/draft-ietf-tls-esni/pull/553

Please have a look! We’d like to merge it soon.

Best,
Chris___
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls