[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: IANA type code registration clean up
We're not short of RR codes so there is no reason to recycle them for
the foreseeable future. It seems to me that what is called for is a
simple RFC. For each of the handful of RR codes in question, the RFC
should presumably say that the code is reserved, say whether or not the
use is deprecated, say a few words about this history of the RR, and
possibly point to or even incorporate documentation for the RR.
As the proud author of the Kitchen SINK RR, I'd be happy to help.
Donald
-----Original Message-----
From: owner-namedroppers@ops.ietf.org
[mailto:owner-namedroppers@ops.ietf.org] On Behalf Of Danny Mayer
Sent: Thursday, June 14, 2007 1:07 PM
To: bmanning@karoshi.com
Cc: Edward Lewis; namedroppers@ops.ietf.org
Subject: Re: IANA type code registration clean up
bmanning@karoshi.com wrote:
>> Weren't other types like MAILA, MD, MF and WKS deprecated somewhere?
I
>> can't find a document on it. If so then it's been done before and the
>> same path can be followed.
>
>
> wrt deprication, sure, it can be done. but that step is a
different
> activity than the concerns listed above. Even if a DNS
attribute is
> depricated, the source document that caused its creation may be
> in doubt. ... witness UID and GID.
>
> There may be a handful of people who -KNOW- why these RR codes
were
> created. The documentation for their creation is, to my
knowledge,
> nonexistant. Now the IANA has flagged the codes as
[IANA-reserved],
> but there is no data on how they got there, other than hearsay.
Yes but if you have deprecation documents you can at least say that they
don't need to be implemented and if you can find the documents you can
reference them and if not you can say that they could not be found. You
don't need to implement something that's been deprecated as long as
there's a document saying so.
You can drag a dead horse to water, but how do you get it to drink?
Danny
--
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/>
--
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/>