<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi everyone,</p>
<p>I want to back up a little bit on this document because I think
there is confusion that needs to be addressed before we continue.
I would like to understand the difference between URN.ARPA and
URN.URI.ARPA, and why there needs to be two registrations.
Wouldn't that actually hurt interoperability?</p>
<p>I would also like to confirm that there is no URI registration
process needed for this document. This doesn't mean that I don't
take Ted's and Leslie's comments seriously. Indeed I will ask
them for all of their review comments, because they can further
improve this work.</p>
<p>Eliot<br>
</p>
<div class="moz-cite-prefix">On 16.01.2024 07:29, Murray S.
Kucherawy wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAL0qLwYq0AFK7YMhgV6+jwRDtt=yDnv9NHfMkmhaAn5r7QY=YA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Hi SM,<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, Jan 6, 2024 at
2:47 AM S Moonesamy <<a
href="mailto:sm%2Bietf@elandsys.com"
moz-do-not-send="true">sm+ietf@elandsys.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi
Francesca, Murray,<br>
<br>
[Cc to Document Shepherd]<br>
<br>
Please see the request quoted below.<br>
<br>
Barry is listed as RAD for <br>
<<a
href="https://datatracker.ietf.org/doc/draft-spinosa-urn-lex/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://datatracker.ietf.org/doc/draft-spinosa-urn-lex/</a>><a
href="https://datatracker.ietf.org/doc/draft-spinosa-urn-lex/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://datatracker.ietf.org/doc/draft-spinosa-urn-lex/</a>
<br>
I was a bit puzzled as I was unsure whether he was an AD or
<br>
not. Anyway, one of you may be able to figure out whether
there is <br>
any action required from the IESG's end as per RFC 8141.<br>
</blockquote>
<div><br>
</div>
<div>It looks like Barry is listed because at one point this
was being handled by the IESG, but it looks like that's no
longer the case and it's now being handled by the ISE.
Barry's name is on there for legacy reasons.</div>
<div><br>
</div>
<div>In any event, RFC 8141 doesn't seem to mention anything
about URN.ARPA, so it looks like RFC 3405 (BCP 65) is the
governing document. Section 3.2.1 of that document states:<br>
</div>
<div>
<pre class="gmail-newpage"> The registration of a NAPTR record for a URN NID MUST NOT precede
proper registration of that NID and publication of a stable
specification in accordance with [<a
href="https://www.rfc-editor.org/rfc/rfc3405.html#ref-9"
title=""URN Namespace Definition Mechanisms""
moz-do-not-send="true">9</a>]</pre>
However, draft-spinosa-urn-lex has not been published yet.
Is this request premature, in the sense that the referenced
draft is not stable (e.g., it could expire)? Should we wait
until it's an RFC?</div>
<div><br>
</div>
<div>It doesn't look to me like the IESG has to direct IANA to
do anything. The BCP suggests that such registration is
automatic once the NID is registered. Have you contacted
IANA to ask them to make the registration? They might also
be waiting for the RFC to be published.<br>
</div>
<div><br>
</div>
<div>-MSK<br>
</div>
</div>
</div>
</blockquote>
</body>
</html>