Re: [TLS] Request to register value in TLS extension registry

Actually, I submitted a request to IANA while this RFC was in process which got sent to the tls-reg-review alias for approval.  There was apparently a hiccup, where the alias members did not receive the request from IANA, but did receive my follow-up e-mail asking if anyone had looked at it.  IANA's understanding of the new process at the time was:

    >> Thank you for contacting us. We've sent this on to the new team of
    >> IESG-designated experts. The Application-Layer Protocol Negotiation
    >> (ALPN) Protocol IDs registry will be updated soon to include a link to
    >> recently-approved document draft-ietf-tls-iana-registry-updates, which
    >> provides new instructions for submitting registration requests for
    >> some of the TLS registries. Specifically, in the future, new requests
    >> should be sent to a mailing list (rather than IANA) for a three-week
    >> review period. The experts will then contact us if they approve a
    >> registration.

-----Original Message-----
From: TLS <tls-bounces@ietf.org> On Behalf Of Sean Turner
Sent: Wednesday, October 3, 2018 8:29 AM
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
Cc: tls@ietf.org
Subject: Re: [TLS] Request to register value in TLS extension registry

> On Oct 3, 2018, at 02:17, Peter Gutmann <pgut001@cs.auckland.ac.nz> wrote:
> 
> [CC'd back to the TLS list because this affects other TLS work as 
> well]
> 
> Benjamin Kaduk <bkaduk@akamai.com> writes:
> 
>> Having looked a bit harder, it seems that perhaps I need to point out 
>> that, if you want IANA to allocate a value, you need to *ask IANA for 
>> it*.  The tls-reg-review@ietf.org list is not a supported IANA 
>> entrypoint;
> 
> That's not what the RFC appears to say:
> 
>   Specification Required [RFC8126] registry requests are registered
>   after a three-week review period on the <tls-reg-review@ietf.org>
>   mailing list, on the advice of one or more designated experts.
> 
>   [...]
> 
>   Registration requests sent to the mailing list for review SHOULD use
>   an appropriate subject (e.g., "Request to register value in TLS bar
>   registry").
> 
> This is exactly what I did, I sent a registration request to the list 
> for review.
> 
>   Within the review period, the designated experts will either approve
>   or deny the registration request, communicating this decision to the
>   review list and IANA.
> 
> This never happened.
> 
> Did anyone actually test RFC 8447 before it was published?

You are the first.

> You send a request
> to a mailing list that doesn't seem to work, to be reviewed by a 
> secret panel (well, we know that Rich Salz is one member :-), with no 
> public discussion or list archives you can examine to see what 
> happened, and in my case no response to the registration request submitted as per the RFC.

The “panel” is not secret.  The experts were identified when draft-ietf-tls-tls13 and draft-ietf-tls-iana-registry-updates were approved [0][1] and are/were enshrined in the IANA registry [2][3].

We are in the process of changing the archives to be public accessible.

Since you have been squatting on a code point for a bit [4], I am hoping that you can bear with us while we work the kinks out.

spt

[0] https://www.ietf.org/mail-archive/web/tls/current/msg25837.html
[1] https://www.ietf.org/mail-archive/web/tls/current/msg26316.html
[2] https://www.iana.org/assignments/tls-extensiontype-values/tls-extensiontype-values.xhtml
[3] https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml
[4] https://mailarchive.ietf.org/arch/msg/tls/rxIiS3pn63yp9YaZMODWXCk8mTg
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls