Re: Domain Centric Administration, RE: draft-ietf-v6ops-natpt-to-historic-00.txt
jnc@mercury.lcs.mit.edu (Noel Chiappa) Tue, 03 July 2007 16:23 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 1I5lAR-0003dO-Sy; Tue, 03 Jul 2007 12:23:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5lAR-0003Wb-1H for ietf@ietf.org; Tue, 03 Jul 2007 12:23:55 -0400
Received: from mercury.lcs.mit.edu ([18.26.0.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5l9e-0002F4-C7 for ietf@ietf.org; Tue, 03 Jul 2007 12:23:55 -0400
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 13269872D9; Tue, 3 Jul 2007 12:23:06 -0400 (EDT)
To: ietf@ietf.org
Message-Id: <20070703162306.13269872D9@mercury.lcs.mit.edu>
Date: Tue, 03 Jul 2007 12:23:06 -0400
From: jnc@mercury.lcs.mit.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: jnc@mercury.lcs.mit.edu
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
> From: Marshall Eubanks <tme@multicasttech.com> >> 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. This is rather close to a prediction I made some time ago: Subject: Re: Reality (was RE: Stupid NAT tricks and how to stop them.) Date: Mon, 10 Apr 2006 10:35:58 -0400 (EDT) Many years ago now, a funny thing happened on the way to "complete exhaustion of the IPv4 address space (Version 1)". Some clever people worked out this ugly hack, which the marketplace judged - despite its ugliness - to be a superior solution to the forklift upgrade to IPv6. It's been selling like hot-cakes ever since, while IPv6 languished. I've become rather disenchanted with my crystal ball, which seems quite cloudy of late .. so I have no specific prediction to make, but... Don't be surprised if the world, facing "complete exhaustion of the IPv4 address space (Version 2)" decides, yet again, that some sort of Plan B is a better choice than a conversion to IPv6. I have no idea exactly what it will be (maybe a free market in IPv4 addresses, plus layered NAT's, to name just one possibility), but there are a lot of clever people out there, and *once events force them to turn their attention to this particular alligator*, don't be surprised if they don't come up with yet another workaround. I still see no reason to change course on this particular prediction... Noel _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Re: Domain Centric Administration, RE: draft-ietf… Noel Chiappa
- Re: Domain Centric Administration, RE: draft-ietf… Noel Chiappa
- Re: Domain Centric Administration, RE: draft-ietf… Keith Moore
- RE: Domain Centric Administration, RE: draft-ietf… michael.dillon
- Re: Domain Centric Administration, RE: draft-ietf… Brian E Carpenter
- Re: Domain Centric Administration, RE: draft-ietf… Joe Baptista
- RE: Domain Centric Administration, RE: draft-ietf… John C Klensin
- Re: Domain Centric Administration, RE: draft-ietf… Joe Baptista
- RE: Domain Centric Administration, RE: draft-ietf… michael.dillon
- RE: Domain Centric Administration, RE: draft-ietf… John C Klensin
- Putting technology on the table [Re: Domain Centr… Brian E Carpenter
- RE: Putting technology on the table [Re: Domain C… Hallam-Baker, Phillip