FWD: Re: Last Call: Representing IPv6 addresses in DNS to Proposed Standard

Thomas Narten <narten@us.ibm.com> Thu, 14 March 2002 19:04 UTC

Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26334 for <dnsext-archive@lists.ietf.org>; Thu, 14 Mar 2002 14:04:28 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.35 #1) id 16laLq-0008ds-00 for namedroppers-data@psg.com; Thu, 14 Mar 2002 10:53:22 -0800
Received: from e22.nc.us.ibm.com ([32.97.136.228]) by psg.com with esmtp (Exim 3.35 #1) id 16laLp-0008dm-00 for namedroppers@ops.ietf.org; Thu, 14 Mar 2002 10:53:21 -0800
Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [9.37.3.209]) by e22.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id MAA24848 for <namedroppers@ops.ietf.org>; Thu, 14 Mar 2002 12:49:56 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.9.21]) by southrelay02.raleigh.ibm.com (8.11.1m3/NCO/VER6.00) with ESMTP id g2EIrEo55650 for <namedroppers@ops.ietf.org>; Thu, 14 Mar 2002 13:53:14 -0500
Received: from rotala.raleigh.ibm.com (narten@localhost) by rotala.raleigh.ibm.com (8.11.6/8.11.6) with ESMTP id g2EIopi26776 for <namedroppers@ops.ietf.org>; Thu, 14 Mar 2002 13:50:51 -0500
Message-Id: <200203141850.g2EIopi26776@rotala.raleigh.ibm.com>
To: namedroppers <namedroppers@ops.ietf.org>
Subject: FWD: Re: Last Call: Representing IPv6 addresses in DNS to Proposed Standard
Date: Thu, 14 Mar 2002 13:50:51 -0500
From: Thomas Narten <narten@us.ibm.com>
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk

FYI

------- Forwarded Message

From: Paul Vixie <paul@vix.com>
To: The IESG <iesg@ietf.org>
Date: Thu, 14 Mar 2002 10:24:13 -0800
Subject: Re: Last Call: Representing IPv6 addresses in DNS to Proposed Standard

Re: draft-ietf-dnsext-ipv6-addresses-01.txt

i object.  i consider this document, and the process which has led to it,
to be anticompetitive in the extreme.  it will also relegate IPv6 to mobile
data applications and will cement NAT as the main way for enterprises of all
sizes to connect to "the internet."  the process which led up to it involved
secret meetings and the decisions were never ratified by any working group.

consider that IPv6 allows far larger enterprise networks to use globally
_unique_ address space than IPv4.  now consider that no such enterprise will
have globally _routable_ address space except for a few large ISP's.  this
disconnect between eligibility for globally _unique_ vs globally _routable_
address space must inevitably lead to higher customer stiction by these few
large ISP's.  the "renumbering penality" for an enterprise with its own
globally unique (but not globally routable) /64 is much higher than for an
enterprise with its own globally unique /27 and its own internal RFC1918
cloud.

this document leads to a scenario where multihoming can only be practical
for a small number of "externally visible" hosts, but never for the whole
enterprise.  the artificially high "renumbering penalty" of a pure-AAAA
solution will either drive enterprises to continue using NAT and RFC1918,
or will drive them to remain customers of the ISP who owns their address
space regardless of market pressures to move elsewhere.

crawford's A6/DNAME proposal has some warts but it has none of THESE warts.

i am researching the appropriate federal agency to lodge a complaint about
anticompetitive activity, since the IETF's membership (including some of
the authors of this draft) are employees or agents of the large ISP's who
will benefit from a market stranglehold if this standard is approved.

meanwhile, i urge that this document be shredded and its authors chastised.

re:

> To: IETF-Announce: ;
> Cc: namedroppers@ops.ietf.org
> From: The IESG <iesg-secretary@ietf.org>
> SUBJECT: Last Call: Representing IPv6 addresses in DNS to Proposed
>          Standard
> Date: Thu, 14 Mar 2002 10:26:24 -0500
> 
> 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.
> 
> Files can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-dnsext-ipv6-addresses-01.txt


------- End of Forwarded Message

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