Re: IANA type code registration clean up

Mark Andrews <Mark_Andrews@isc.org> Thu, 14 June 2007 00:56 UTC

Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hyddl-0000Nc-4Y; Wed, 13 Jun 2007 20:56:45 -0400
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hyddj-0007Wp-OA; Wed, 13 Jun 2007 20:56:45 -0400
Received: from majordom by psg.com with local (Exim 4.67 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1HydOv-0006qZ-Lh for namedroppers-data@psg.com; Thu, 14 Jun 2007 00:41:25 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.8
Received: from [204.152.184.167] (helo=mx.isc.org) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67 (FreeBSD)) (envelope-from <Mark_Andrews@isc.org>) id 1HydOk-0006q9-6v for namedroppers@ops.ietf.org; Thu, 14 Jun 2007 00:41:20 +0000
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "farside.isc.org", Issuer "ISC CA" (verified OK)) by mx.isc.org (Postfix) with ESMTP id 5562C11407A for <namedroppers@ops.ietf.org>; Thu, 14 Jun 2007 00:41:13 +0000 (UTC) (envelope-from Mark_Andrews@isc.org)
Received: from drugs.dv.isc.org (localhost.isc.org [IPv6:::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "drugs.dv.isc.org", Issuer "ISC CA" (verified OK)) by farside.isc.org (Postfix) with ESMTP id BC9BFE6098 for <namedroppers@ops.ietf.org>; Thu, 14 Jun 2007 00:41:12 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.1/8.14.1) with ESMTP id l5E0difS021981; Thu, 14 Jun 2007 10:39:45 +1000 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <200706140039.l5E0difS021981@drugs.dv.isc.org>
To: Edward Lewis <Ed.Lewis@neustar.biz>
Cc: Andrew Sullivan <andrew@ca.afilias.info>, namedroppers@ops.ietf.org
From: Mark Andrews <Mark_Andrews@isc.org>
Subject: Re: IANA type code registration clean up
In-reply-to: Your message of "Wed, 13 Jun 2007 15:12:18 -0400." <a06240804c295ec020776@[10.31.32.65]>
Date: Thu, 14 Jun 2007 10:39:44 +1000
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1

> At 14:42 -0400 6/13/07, Andrew Sullivan wrote:
> >On Wed, Jun 13, 2007 at 12:57:17PM -0400, Edward Lewis wrote:
> >>
> >>  Answer A - document them.
> >>  Answer B - deprecate them.
> >
> >Answer AB: document _and_ deprecate.
> >
> >I'm serious.  I know this is work, but I think we should write these
> >down somewhere, and say they're deprecated and needn't be implemented.
> >At least then someone writing a compliant system that gets one of
> >these types in a query knows what it is supposed to be and that it can
> >be ignored.
> >
> >Yes, I am volunteering.  Do you have some pointers that I should go
> >read, so that I don't have to start all your forensic work from
> >scratch?
> 
> Yeah I do.  While thinking more about this, I realized that all we 
> would need to do is list the values and the mnemonics and then say 
> "just don't do it."  So I agree on an answer AB.
> 
> But there is one possible exception to outright deprecation of all 
> the un-RFC'd types, the ATMA record.  All but the ATMA died when 
> their draft expired.  The ATM one is defined in a document published 
> external to the IETF.  (But I get heartburn over that - the ATM Forum 
> is where the document was originally published.  The ATM Forum is no 
> longer amongst the living and even it's web site is gone.)
> 
> In talking to IANA on the side I noticed that they had cleaned up a 
> lot of the references (there were a few types in 2005 that were 
> RFC'd, like AAAA, that weren't documented as such and now are) but 
> these remain:
> 
> old NSAP-PTR        23
> new NSAP-PTR        23 for domain name pointer, NSAP style   [RFC1348]
> 
> old EID             31 Endpoint Identifier           [Patton]
> new EID             31 Endpoint Identifier
>      [http://ana-3.lcs.mit.edu/~jnc/nimrod/dns.txt]
> 
> old NIMLOC          32 Nimrod Locator                [Patton]
> new NIMLOC          32 Nimrod Locator
>      [http://ana-3.lcs.mit.edu/~jnc/nimrod/dns.txt]
> 
> old ATMA            34 ATM Address                   [Dobrowski]
> new ATMA            34 ATM Address
>      [http://www.mfaforum.org/ftp/pub/approved-specs/af-saa-0069.000.pdf]
> 
> old SINK            40 SINK                          [Eastlake]
> new SINK            40 SINK
>      [http://bgp.potaroo.net/ietf/all-ids/draft-eastlake-kitchen-sink-02.txt]
>
> The first may be just an editor's choice (see the page for what I 
> mean), the next two and last are types that were not quite formed. 
> The ATMA is the one defined elsewhere.  All URLs work as of today.

	Of the list above BIND 9 only implements NSAP-PTR.
	ATM looks like it is straight forward to implement.

> What I haven't considered are RFC'd types that are dead too - because 
> I am not looking at a bureaucratic cleansing, more at "what do we 
> need to leave for new implementors."
> 
> -- 
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Edward Lewis                                                +1-571-434-5468
> NeuStar
> 
> Sarcasm doesn't scale.
> 
> --
> 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/>
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

--
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/>