Re: EDNS0 numbers

[Samuel Weiler <weiler@tislabs.com>]

> > ... RFC 2671 says:
> >
> > >   OPTION-CODE    (Assigned by IANA.)
> >
> > However, when I look at <http://www.iana.org/numbers.html> I cannot find
> > any registry for EDNS0 OPTION-CODEs. Where do we have to go to apply for
> > an EDNS0 OPTION-CODE?

I can't find the registry either.  (IANA, where are you?)  But section
7 of RFC2671 says:

     IESG approval should be required to create new entries in the EDNS
     Extended Label Type or EDNS Version Number registries, while any
     published RFC (including Informational, Experimental, or BCP)
     should be grounds for allocation of an EDNS Option Code.

While very clear, this metric doesn't fall into any of the buckets in
RFC2434.  It sounds closest to "IETF Consensus" (or "IETF Review", as
used by draft-narten-iana-considerations-rfc2434bis-01.txt), but one
could argue that it was intended to be "Specification Required".

As Mark suggested, write an RFC and submit it for publication as
informational, experimental, or even standards track.  If you really
don't want to do an RFC for your option code assignments, then propose
a revision to RFC2929 that includes text on EDNS0 option codes and
makes the registry "specification required".  In either case, the
"where do we go" seems to be "the RFC Editor".

In the meantime, take a look at RFC3692.

-- Sam

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>