Re: [Tls-reg-review] [IANA #1287144] Re: Early IANA code allocations for draft-ietf-tls-esni

["Salz, Rich" <[e-mail]>]

Confirmed.

As for footnote vs references vs just-wait, I'm fine with whatever you decide.

On 12/12/23, 7:32 PM, "Amanda Baber via RT" <[e-mail] <mailto:[e-mail]>> wrote:


Hi Rich, Yoav,


Before we make the TLS ExtensionType registrations for this document, can you confirm that you're OK with listing "CH" as the TLS 1.3 entry for ech_outer_extensions (as opposed to leaving it blank)? The comment "Only appears in inner CH" will be added in the future. See below.


I should add that if you want us to, and Sean agrees, we could add that comment now as a temporary footnote, either in the TLS 1.3 field or the Reference field.


See Sean's message below.


thanks,
Amanda


=====


These changes are based on the following PRs:
https://urldefense.com/v3/__https://github.com/tlswg/draft-ietf-tls-esni/pull/584/files__;!!GjvTz_vk!SdkivvVzFz2cbYyEeEtkEeJo3UyFd02qHOzAYdL9oOAa6PGNfQvtSWThP6lSvV7hiyLFMsznEYB8I5R9KK19m-0$ <https://urldefense.com/v3/__https://github.com/tlswg/draft-ietf-tls-esni/pull/584/files__;!!GjvTz_vk!SdkivvVzFz2cbYyEeEtkEeJo3UyFd02qHOzAYdL9oOAa6PGNfQvtSWThP6lSvV7hiyLFMsznEYB8I5R9KK19m-0$> 
https://urldefense.com/v3/__https://github.com/tlswg/draft-ietf-tls-esni/pull/597/files__;!!GjvTz_vk!SdkivvVzFz2cbYyEeEtkEeJo3UyFd02qHOzAYdL9oOAa6PGNfQvtSWThP6lSvV7hiyLFMsznEYB8I5R9o8T7cI4$ <https://urldefense.com/v3/__https://github.com/tlswg/draft-ietf-tls-esni/pull/597/files__;!!GjvTz_vk!SdkivvVzFz2cbYyEeEtkEeJo3UyFd02qHOzAYdL9oOAa6PGNfQvtSWThP6lSvV7hiyLFMsznEYB8I5R9o8T7cI4$> 


*****
NOTE: The instructions from Section 11.1 #2 include a reference to a “Comment” column. That column does not yet exist. It is being created by draft-ietf-tls-rfc8447bis; you can see the IANA instructions in the following link:
https://urldefense.com/v3/__https://tlswg.org/rfc8447bis/draft-ietf-tls-rfc8447bis.html <https://urldefense.com/v3/__https://tlswg.org/rfc8447bis/draft-ietf-tls-rfc8447bis.html>*name-adding-comment-column__;Iw!!GjvTz_vk!SdkivvVzFz2cbYyEeEtkEeJo3UyFd02qHOzAYdL9oOAa6PGNfQvtSWThP6lSvV7hiyLFMsznEYB8I5R9EgdZzSo$ 


draft-ietf-tls-rfc8447bis has one remaining issue and will therefore track draft-ietf-tls-esni very closely. We would like to manage adding the value for the Comment column later based on these instructions later in the process. We prefer not to have a normative reference to draft-ietf-tls-rfc8447bis.
*****




The amended request is as follows:


11.1. Update of the TLS ExtensionType Registry


IANA is requested to create the following entries in the existing
registry for ExtensionType (defined in [RFC8446]):


1. encrypted_client_hello(0xfe0d), with "TLS 1.3" column values set to
"CH, HRR, EE", "DTLS-Only" column set to "N", and "Recommended" column set
to "Yes”.


2. ech_outer_extensions(0xfd00), with the "TLS 1.3" column values set to "CH",
"DTLS-Only" column set to "N", "Recommended" column set to "Yes", and the
"Comment" column set to "Only appears in inner CH."


11.2. Update of the TLS Alert Registry


IANA is requested to create an entry, ech_required(121) in the
existing registry for Alerts (defined in [RFC8446]), with the "DTLS-
OK" column set to "Y”.


spt