IETF Logo Mail Archive

RE: Domain Centric Administration, RE: draft-ietf-v6ops-natpt-to-historic-00.txt

"Hallam-Baker, Phillip" <pbaker@verisign.com> Tue, 03 July 2007 16:54 UTC

Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5ldr-0000ib-NE; Tue, 03 Jul 2007 12:54:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5ldp-0000iJ-PT for ietf@ietf.org; Tue, 03 Jul 2007 12:54:17 -0400
Received: from colibri.verisign.com ([65.205.251.74]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5ld0-0006pW-Fa for ietf@ietf.org; Tue, 03 Jul 2007 12:54:17 -0400
Received: from MOU1WNEXCN03.vcorp.ad.vrsn.com (mailer6.verisign.com [65.205.251.33]) by colibri.verisign.com (8.13.6/8.13.4) with ESMTP id l63GrPcF029548; Tue, 3 Jul 2007 09:53:25 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 3 Jul 2007 09:53:25 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 03 Jul 2007 09:51:48 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012F693B@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <EC0A1E7E-7867-481F-BAB7-EF8C8337B170@multicasttech.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Domain Centric Administration, RE: draft-ietf-v6ops-natpt-to-historic-00.txt
Thread-Index: Ace9iTT4wogwZoqRSPu8m4aG4JsYhQACQ7qg
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: Marshall Eubanks <tme@multicasttech.com>
X-OriginalArrivalTime: 03 Jul 2007 16:53:25.0527 (UTC) FILETIME=[AC335A70:01C7BD92]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: Mark Andrews <Mark_Andrews@isc.org>, ietf@ietf.org
Subject: RE: Domain Centric Administration, RE: draft-ietf-v6ops-natpt-to-historic-00.txt
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

It might be a market.

It might well be something more Darwinian. 

> -----Original Message-----
> From: Marshall Eubanks [mailto:tme@multicasttech.com] 
> Sent: Tuesday, July 03, 2007 11:46 AM
> To: Hallam-Baker, Phillip
> Cc: David Conrad; Mark Andrews; ietf@ietf.org
> Subject: Re: Domain Centric Administration, RE: 
> draft-ietf-v6ops-natpt-to-historic-00.txt 
> 
> 
> On Jul 3, 2007, at 11:37 AM, Hallam-Baker, Phillip wrote:
> 
> >> From: David Conrad [mailto:drc@virtualized.org]
> >
> >> I am also a bit confused how a "dual stack" transition strategy to
> >> IPv6 is going to work when the IPv4 address free pool is 
> exhausted in 
> >> a few years without some form of NAT/ALG, but maybe that's just me.
> >
> > Perhaps the idea here is that when the IPv4 pool is 
> exhausted, people 
> > will be forced to use IPv6.
> >
> > If so it comes from the same school of politics that led 
> folk to say 
> > 'IF NXT means that DNSSEC can't be deployed in .com that's a good 
> > thing because it will force people to reduce the size of 
> .com'. That 
> > is an actual quote from a real DNSEXT meeting.
> >
> > Its not going to work that way. All we will end up with is 
> hyper-NAT.
> 
> And a Market in IPv4 addresses, which will certainly develop 
> as IPv4 exhaustion nears.
> 
> Regards
> Marshall
> 
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ietf
> 
> 

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email