(BEGIN IANA COMMENTS)
IESG/Authors/ISE:
IANA will need the authors to take action before we can complete the registrations for draft-spinosa-urn-lex-21. It should also be noted that the public mailing lists meant to review those registrations may not have many active members.
We understand that this document will require three IANA actions: 1) updating the reference for the existing "lex" registration at
https://www.iana.org/assignments/urn-namespaces,
2) adding a NAPTR record to the urn.arpa domain, and 3) adding a NAPTR record to the urn.uri.arpa domain.
However, according to RFC 3405, in order to add records to urn.arpa and uri.arpa, the authors must submit their requests to these mailing lists for a two-week public review:
https://mm.icann.org/mailman/listinfo/register-urn
https://mm.icann.org/mailman/listinfo/register-uri
Because those lists (which haven't seen much activity post-2011) currently have ~20 members each, we've sent informal review requests to Leslie Daigle and Ted Hardie. We haven't heard from Leslie yet, but Ted had these notes:
> My quick scan of this sees a few potential issues with things listed
> as SHOULD which I believe would be better as MUST; I was also a little
> confused by this:
>
> "Such DNS routing chain does not work for all the URN components
> containing %-encoded characters. Therefore, when converting a lex:URN
> in UTF-8 code to a DNS query, clients MUST perform any necessary
> punycode conversion [RFC5891] before sending the query."
There are no designated experts for urn.arpa or uri.arpa, so unless the IESG instructs us otherwise, we'll mark this document "IANA OK" two weeks after the authors submit their review requests, provided that the lists don't raise any of the objections described
in Section 5 of RFC 3405.
Best regards,
Amanda Baber
IANA Operations Manager
(END IANA COMMENTS)