> On Oct 31, 2023, at 15:53, Sean Turner <s...@sn3rd.com> wrote:
>
>
>
>> On Oct 30, 2023, at 11:58, Sean Turner <s...@sn3rd.com> wrote:
>>
>>
>>> On Sep 18, 2023, at 20:45, Sean Turner <s...@sn3rd.com> wrote:
>>>
>>> Hi! After discussions with the authors of draft-ietf-tls-esni, Joe and I
>>> would like to determine whether there is consensus to request two early
>>> code point assignments; see RFC 7120. One is for the encrypted_client_hello
>>> extension and one is for the ech_required alert; see s11 of the I-D. Please
>>> let the list know by 03 October 2023 if you support these early allocations.
>>>
>>> Cheers,
>>> Joe & Sean
>>
>> We have consensus to go ahead and ask for an early allocation for both the
>> extension and the alert. The SVCB allocation has already been reserved so
>> there is no action necessary from IANA on that point. One final
>> confirmation: I am sending the request to Paul for the code point numbers
>> listed in the I-D:
>>
>> TLS ExtensionType Registry: encrypted_client_hello(0xfe0d)
>> TLS Alert Registry: ech_required(121)
>>
>> Cheers (and Thanks),
>> spt
>
> Stephen has corrected pointed out that there are actually two TLS extensions
> in s11.1. The other is ech_outer_extensions(0xfd00). I will let this linger
> until we meet next week, but I am currently under the assumption that I will
> forward the early allocation request to Paul with the values in the I-D.
We confirmed at the session today that we should keep the code points that are
in the I-D. Sending the request to our AD now.
spt
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
