Updated registration procedure for the 256-9999 range (Addresses #28)

draft-ietf-core-cf-reg-update.md

@@ -35,7 +35,11 @@ author:
    email: [email protected]
 
 normative:
+  RFC7120: iana-early
   RFC7252: coap
+  BCP26:
+    -: iana-cons
+    =: RFC8126
 
 informative:
   Err4954: 7252
@@ -49,22 +53,24 @@ entity:
 
 --- abstract
 
-This document updates RFC7252 regarding the registration procedures for the "CoAP Content-Formats" registry, within the "CoRE Parameters" registry group,
-specifically, those regarding the First Come First Served (FCFS) portion of the registry.
+This document updates RFC7252 regarding the registration procedures for the "CoAP Content-Formats" registry, within the "CoRE Parameters" registry group. The affected registration procedures are
+specifically those regarding the IETF Review or IESG Approval portion of the registry as well as those regarding the First Come First Served (FCFS) portion of the registry.
 
 --- middle
 
 # Introduction
 
 {{Section 12.3 of -coap}} describes the registration procedures for the "CoAP Content-Formats" registry within the "CoRE Parameters" registry group {{IANA.core-parameters}}.
 (Note that the columns of this registry have been revised according to {{Err4954}}.)
-In particular, the text defines the rules for obtaining CoAP Content-Format identifiers from the First Come First Served (FCFS) portion of the registry (10000-64999).
-These rules do not involve the Designated Expert (DE) and are managed solely by IANA personnel to finalize the registration.
+
+In particular, the text defines the rules for obtaining CoAP Content-Format identifiers from the IETF Review or IESG Approval portion of the registry (256-9999) as well as from the First Come First Served (FCFS) portion of the registry (10000-64999).
+For the (FCFS) portion of the registry, these rules do not involve the Designated Expert (DE) and are managed solely by IANA personnel to finalize the registration.
+
 Unfortunately, the instructions do not explicitly require checking that the combination of content-type (i.e., media type with optional parameters) and content coding associated with the requested CoAP Content-Format is semantically valid.
 This task is generally non-trivial, requiring knowledge from multiple documents and technologies, which is not a task to demand solely from the registrar.
 This lack of guidance may engender confusion in both the registering party and the registrar, and has already led to erroneous registrations.
 
-In {{iana}}, this document updates {{-coap}} by modifying the registration procedures for the "CoAP Content-Formats" registry regarding its FCFS portion, to mitigate the risk of unintentional or malicious errors.
+In {{iana}}, this document updates {{-coap}} by modifying the registration procedures for the "CoAP Content-Formats" registry regarding its IETF Review or IESG Approval portion as well as its FCFS portion, to mitigate the risk of unintentional or malicious errors.
 
 # Conventions and Definitions
 
@@ -76,6 +82,8 @@ This document uses the terms "media type", "content coding", "content-type" and
 
 This section contains a few examples of registration requests for a CoAP Content-Format with identifier 64999 in the FCFS space that must not be allowed to succeed.
 
+The following considerations also apply to alternative examples where, for the same combination of content type and content coding, a registration was requested for a CoAP Content-Format with identifier in the IETF Review or IESG Approval space. That is, such registrations must not be allowed to succeed.
+
 ## The Media Type is Unknown {#ex-unknown-mt}
 
 The registrant requests an FCFS Content-Format ID for an unknown media type:
@@ -151,33 +159,38 @@ The CoAP Content-Formats registration procedures defined in {{Section 12.3 of -c
 
 | Range | Registration Procedures | Note |
 |--------|--------|
-| 0-255 | Expert Review | Full review described in {{&SELF}}, {{full-checks}} |
-| 256-9999 | IETF Review or IESG Approval | |
+| 0-255 | Expert Review | Review procedure described in {{&SELF}}, {{checks}} |
+| 256-9999 | IETF Review with Expert Review or IESG Approval with Expert Review | Review procedure described in {{&SELF}}, {{checks}} |
 | 10000-64999 (No parameters and empty Content Coding and media type not yet used in this registry) | First Come First Served | The corresponding media type must be registered (or approved for publication) in the "Media Types" registry {{IANA.media-types}} |
-| 10000-64999 (Includes parameters and/or Content Coding and/or media type appears in this registry) | Expert Review | Lightweight review described in {{&SELF}}, {{checks}} |
+| 10000-64999 (Includes parameters and/or Content Coding and/or media type appears in this registry) | Expert Review | Review procedure described in {{&SELF}}, {{checks}} |
 | 65000-65535 | Experimental use (no operational use) |
 {: #tbl-new-cf-proc title="Updated CoAP Content-Formats Registration Procedures"}
 
+The 256-9999 range now has registration procedures requiring IETF Review with Expert Review or IESG Approval with Expert Review. In particular:
+
+* All assignments according to "IETF Review with Expert Review" are made on an "IETF Review" basis per {{Section 4.8 of -iana-cons}} with "Expert Review" additionally required per {{Section 4.5 of -iana-cons}}.
+
+  The procedure for early IANA allocation of "standards track code points" defined in {{-iana-early}} also applies. When such a procedure is used, IANA will ask the Designated Expert(s) to approve the early allocation before registration. In addition, working group chairs are encouraged to consult the Expert(s) early during the process outlined in {{Section 3.1 of -iana-early}}.
+
+* All assignments according to "IESG Approval with Expert Review" are made on an "IESG Approval" basis per {{Section 4.10 of -iana-cons}} with "Expert Review" additionally required per {{Section 4.5 of -iana-cons}}.
+
 The 10000-64999 range now has two separate registration procedures.
 If the registration consists solely of a registered media type name in the "Content Type" field, without any parameter names or "Content Coding", and the media type has not yet been used in this registry, then the policy is FCFS, as before.
 In all other cases, the policy will be Expert Review, following the checklist described in {{checks}}.
 
-A new column with the title "Note" has been added to the registry, which contains information about expected checks.
-
-## "Full" Expert Review Checks {#full-checks}
+A new column with the title "Note" has been added to the registry, which contains information about the expected review procedure.
 
-For the 0-255 range, the DE is instructed to perform a "Full Review" described in this section, not only the "lightweight" Expert Review that may apply to the 10000-64999 range.
-For this range, in addition to the checks described in {{checks}}, the DE is instructed to also evaluate the requested codepoint concerning the limited availability of the 1-byte codepoint space.
-For the 10000-64999 range, this criterion does not apply.
+## Expert Review Procedure {#checks}
 
-## "Lightweight" Expert Review Checks {#checks}
-
-For the 10000-64999 range, the Designated Expert is instructed to perform the "lightweight" Expert review, as described by the following checklist:
+The Designated Expert is instructed to perform the Expert Review, as described by the following checklist:
 
 1. The combination of content-type and content coding for which the registration is requested must not be already present in the "CoAP Content-Formats" registry;
-1. The media type associated with the requested Content-Format must exist (or must have been approved for registration) in the "Media Types" registry {{IANA.media-types}};
-1. The optional parameter names must have been defined in association with the media type, and any parameter values associated with such parameter names must be as permitted;
-1. If a Content Coding is specified, it must exist (or must have been approved for registration) in the "HTTP Content Coding" registry of the "Hypertext Transfer Protocol (HTTP) Parameters" {{IANA.http-parameters}}.
+2. The media type associated with the requested Content-Format must exist (or must have been approved for registration) in the "Media Types" registry {{IANA.media-types}};
+3. The optional parameter names must have been defined in association with the media type, and any parameter values associated with such parameter names must be as permitted;
+4. If a Content Coding is specified, it must exist (or must have been approved for registration) in the "HTTP Content Coding" registry of the "Hypertext Transfer Protocol (HTTP) Parameters" {{IANA.http-parameters}}.
+
+For the 0-255 range, in addition to the checks described above, the DE is instructed to also evaluate the requested codepoint concerning the limited availability of the 1-byte codepoint space.
+For the 256-9999 range and the 10000-64999 range, a similar criterion may also apply where combinations of media type parameters and content coding choices consume considerable code point space.
 
 <!-- Should these actually use BCP14 MUSTs? -->