Re: [core] [IANA #1232194] Ballot issued: <draft-ietf-core-problem-details-04.txt> to Proposed Standard

[Carsten Bormann <[e-mail]>]

To address the observation from IANA cited below, we changed the “first-come-first-served” policy for the Custom Problem Detail Key registry to “expert review” and added:

>> The expert is instructed to attempt making the registration experience
>> as close to first-come-first-served as reasonably achievable, but
>> checking that the reference document does provide a description as set
>> out below.
>> (This requirement is a relaxed version of "specification required" as
>> defined in {{Section 4.6 of -ianacons}}.)

While examining various IANA considerations sections in this process, it also occurred to me that we didn’t say much about key values and names.  
So I propose (https://github.com/core-wg/core-problem-details/pull/38) to add:

>> The expert is requested to assign the shortest key values (1+0 and
>> 1+1 encoding) to registrations that are likely to enjoy wide use and
>> can benefit from short encodings.
>> 
>> To be immediately useful in CDDL and programming language contexts, a
>> name consists of a lower-case ASCII letter (a-z) and zero or more
>> additional ASCII characters that are either lower-case letters,
>> digits, or a hyphen-minus, i.e., it matches [a-z][-a-z0-9]*.
>> As with the key values, names need to be unique.

See the whole thing in context in:
https://core-wg.github.io/core-problem-details/iana-expert-instructions/draft-ietf-core-problem-details.html#name-iana-considerations
(What was Section 5.1/5.2 when IANA reviewed this, now is 6.1/6.2.)

Quick reactions would be useful so we can bottle this up well before today’s (1400Z) IESG meeting.

Grüße, Carsten



> On 15. Jun 2022, at 05:35, Amanda Baber via RT <[e-mail]> wrote:
> 
> Correction to the correction: the First Come First Served registry is in Section 5.2!
> 
> On Wed Jun 15 03:33:04 2022, amanda.baber wrote:
>> Dear Authors/Chairs,
>> 
>> We missed a detail in our Last Call review:
>> 
>> Section 5.1 is creating a First Come First Served registry, but it
>> also requires "a reference document that provides a description of the
>> map, including a CDDL description, that describes all inside keys and
>> values."
>> 
>> https://datatracker.ietf.org/doc/html/draft-ietf-core-problem-details-
>> 05#section-5.1
>> 
>> IANA could check that a field called "Description" exists in the
>> document, but we can't confirm any details beyond that. If this
>> information is required, this needs to be an Expert Review registry
>> (or Specification Required, if the description in https://www.rfc-
>> editor.org/rfc/rfc8126.html#section-4.6 sounds appropriate).
>> 
>> Best regards,
>> 
>> Amanda Baber
>> IANA Operations Manager
>