[Dance] Re: AD review of draft-ietf-dance-tls-clientid-06

[Paul Wouters <[e-mail]>]

On Sun, 14 Sep 2025, Shumon Huque wrote:

>       This is not a complete IANA registration request. It needs to specify:
>
>       Value   Extension Name          TLS 1.3                 DTLS-Only       Recommended     Reference
>       <tbd>   dane_clientid                EE,CR (I think?)        N                       N                       [this doc]
> 
> 
> Thanks Paul,
> 
> Here's my proposed rewrite of that section:
> 
> IANA is requested to create the following entry in the "TLS ExtensionTypes Values" registry:
> 
> Extension Name "dane_clientid" with value TBD, "TLS 1.3" column values set to "CR, CT", "DTLS-Only" column set to "N", and "Recommended" column set to "N".
> The "TLS1.3" columns indicate the 2 protocol structures in TLS 1.3 that this extension can appear in (Certificate Request and Certificate messages).

Ok. The DE's will confirm these anyway.

> Regarding the "Recommended" column, is your reasoning for "No" that this extension has limited applicability, or is only intended for specific cases (which are
> valid reasons for 'N')? Otherwise, extensions going through the IETF standards action seem to be eligible for 'Y'.
> (per https://www.rfc-editor.org/rfc/rfc8447#section-5)
> 
> I'm fine with 'N', but I just want to confirm the reason.

You cannot really use recommended is Yes when requiring DNSSEC of some
kind. That would surely cause an invasion of the TLS WG during IETF LC
and/or IESG Telechat :)

I think also because it is not a generic extension but a very specific
feature thing.

> I prefer not using the term "apriori" for those not speaking Latin or English natively.
> 
> 
> Ok. I propose to change this to "beforehand".
> 
> I will queue up these updates shortly.

Thanks!

Paul