--On Thursday, June 20, 2013 12:36 -0400 Andrew Sullivan
<ajs@xxxxxxxxxxxxxxxxxx> wrote:
> On Thu, Jun 20, 2013 at 11:17:16AM -0400, John C Klensin wrote:
>
>> So some review of the DNSEXT-specified procedures and
>> expectations may be in order.
>...
> But more generally, as a practical matter it is better that
> people register their stuff with us than that they don't. We
> have, in the wild, a used EDNS0 option code that is all over
> the Internet. It is undocumented, and the code point isn't
> actually registered. That state of affairs is surely worse
> than that the IETF didn't get to provide good advice to
> authors. DNSEXT already tried to be the DNS cops, and has
> failed miserably, partly because of the usual get-off-my-lawn
> crowd and partly because people unfamiliar with the IETF find
> its procedures a little arcane.
>
> My view is that we need to be more pragmatic.
Andrew,
Just to be clear, I completely agree. I thought that should
have been clear from the context of my note (context that you
omitted above). I think that what I have referred to as the
lightweight registration procedure is just fine. What I have
objected to since the first time a Last Call on the present
document was initiated is any assertion that, because something
is registered, it is entitled to be documented in the RFC
Series. I object even more strongly to any implication that
such a registered RRTYPE should be accepted as a Standards Track
document without any further review because it is registered
already.
I thought that issue had been settled for this document by
reclassifying its intended status to Informational and
clarifying the relationship of the RRTYPEs to other
consideration, particularly privacy ones. IMO, that
clarification along makes it worth publishing as an RFC, but the
notion of entitlement was, I thought, put to rest.
Consequently, I was mildly astonished when Olafur's comment
(which included the information that he is co-chair of DNSEXT)
included "...we (DNS community) want to encore [sic] that any
such allocations be published as RFC's for future references".
So, once again and in short sentences:
(1) The present registration procedure does nothing to ensure
any such thing.
(2) There is nothing else in either IETF or RFC Editor
procedures that ensures RFC publication. If a document
describing an already-registered RRTYPE is submitted and some AD
wants to sponsor it for publication as an individual submission
and puts it into a Last Call on that basis, the community may
pick at it, insist on changes, or even reach consensus that it
should not be published.
(3) I think the above is fine. If someone (else) thinks that
RFC publication should be "ensured" for any RRTYPE allocation,
then they need to persuade whomever needs to be persuaded to
modify the registration procedure. I would, personally, oppose
that change if it eliminated the possibility of quick,
lightweight, registrations but my opinion probably doesn't count
for much relative to the "DNS community" for which Olafur and/or
you are speaking.
best,
john