Re: Last Call: Representing IPv6 addresses in DNS to Proposed Standard
Nathan Jones <nathanj@optimo.com.au> Wed, 27 March 2002 10:47 UTC
Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22044 for <dnsext-archive@lists.ietf.org>; Wed, 27 Mar 2002 05:47:16 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.35 #1) id 16qAf1-0005yA-00 for namedroppers-data@psg.com; Wed, 27 Mar 2002 02:28:07 -0800
Received: from nara.off.connect.com.au ([192.94.41.40]) by psg.com with esmtp (Exim 3.35 #1) id 16qAez-0005y4-00 for namedroppers@ops.ietf.org; Wed, 27 Mar 2002 02:28:06 -0800
Received: (from njones@localhost) by nara.off.connect.com.au id VAA09911 (8.8.8/IDA-1.7); Wed, 27 Mar 2002 21:27:28 +1100 (EST)
Message-ID: <20020327212727.B23106@connect.com.au>
Date: Wed, 27 Mar 2002 21:27:27 +1100
From: Nathan Jones <nathanj@optimo.com.au>
To: iesg@ietf.org
Cc: namedroppers@ops.ietf.org
Subject: Re: Last Call: Representing IPv6 addresses in DNS to Proposed Standard
References: <200203141526.KAA19163@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Mailer: Mutt 0.93.2i
In-Reply-To: <200203141526.KAA19163@ietf.org>; from The IESG on Thu, Mar 14, 2002 at 10:26:24AM -0500
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
Having been away from the list for a while, the arguments against this draft have already been discussed. I'm sending this message to note that I also object to draft-ietf-dnsext-ipv6-addresses-01.txt. As I see it, the role of the IETF is to provide flexible standards that enable people to do things, not to tell people that they can't use certain functionality by deprecating the specification. It cannot be said that there is consensus to progress this draft. It can be said that is insufficient technical argument to deprecate A6 and DNAME. Most of the anti-A6 argument appears to say "we don't think you need easier renumbering, etc. so we'll take away the RR types and tell you to find a work around". In terms of administration, I believe A6 is only a little more complex than AAAA, and that administrators will cope just fine if there are guidelines available. Has anyone yet started work on a draft to document guidelines for the usage of DNS with IPv6? (eg. recommended limits on A6 chains, etc.) -- Nathan Jones nathanj@optimo.com.au On Thu, Mar 14, 2002 at 10:26:24AM -0500, The IESG wrote: >The IESG has received a request from the DNS Extensions Working Group >to consider Representing IPv6 addresses in DNS ><draft-ietf-dnsext-ipv6-addresses-01.txt> as a Proposed Standard. > >The IESG plans to make a decision in the next few weeks, and solicits >final comments on this action. Please send any comments to the >iesg@ietf.org or ietf@ietf.org mailing lists by April 2, 2002. -- 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/>
- Re: Last Call: Representing IPv6 addresses in DNS… Nathan Jones
- Re: Last Call: Representing IPv6 addresses in DNS… Paul Vixie
- Re: Last Call: Representing IPv6 addresses in DNS… Johan Ihren
- Re: Last Call: Representing IPv6 addresses in DNS… Nathan Jones
- Re: Last Call: Representing IPv6 addresses in DNS… Danny Mayer
- Re: Last Call: Representing IPv6 addresses in DNS… JINMEI Tatuya / 神明達哉
- Re: Last Call: Representing IPv6 addresses in DNS… Tim Chown
- Re: Last Call: Representing IPv6 addresses in DNS… JINMEI Tatuya / 神明達哉
- Re: Last Call: Representing IPv6 addresses in DNS… Robert Elz