Re: site local addresses (was Re: Fw: Welcome to the InterNAT...)

Daniel Senie <dts@senie.com> Thu, 27 March 2003 03:06 UTC

Received: from ran.ietf.org (ran.ietf.org [10.27.6.60]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29787; Wed, 26 Mar 2003 22:06:38 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 18yNmn-0001ks-00 for ietf-list@ran.ietf.org; Wed, 26 Mar 2003 22:10:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 18yNf1-0001Gp-00 for ietf@ran.ietf.org; Wed, 26 Mar 2003 22:02:35 -0500
Received: from garlic.amaranth.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29480 for <ietf@ietf.org>; Wed, 26 Mar 2003 21:47:20 -0500 (EST)
Received: from Willow.senie.com (amaranth.ne.client2.attbi.com [24.34.18.226]) (authenticated (0 bits)) by garlic.amaranth.net (8.11.6/8.11.6) with ESMTP id h2R2ng907305 (using TLSv1/SSLv3 with cipher DES-CBC3-SHA (168 bits) verified NO) for <ietf@ietf.org>; Wed, 26 Mar 2003 21:49:42 -0500
Message-Id: <5.2.0.9.2.20030326214007.01b67320@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 26 Mar 2003 21:44:57 -0500
To: ietf@ietf.org
From: Daniel Senie <dts@senie.com>
Subject: Re: site local addresses (was Re: Fw: Welcome to the InterNAT...)
In-Reply-To: <139B47D4-5FF5-11D7-BCE2-000393DB42B2@nominum.com>
References: <DDC2EE76-5FEF-11D7-91E0-000393CB0816@qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 08:40 PM 3/26/2003, David Conrad wrote:
>Ted,
>
>On Wednesday, March 26, 2003, at 05:03  PM, Ted Hardie wrote:
>>         If you were using some of an allocated portion as routable addresses
>>and some as unrouted addresses, you might be forced to change the
>>unrouted addresses as a consequences of choosing someone new to carry
>>the traffic from the routed portions of your network.  That would carry
>>the same pain of renumbering it always does.
>
>Which, of course, implies NAT ("where's there's pain, there's NAT"? :-)).

No. It does not imply NAT. It implies traffic to hosts which are used for 
purposes which do not communicate to the public network.

Could we PLEASE leave NAT out of the equation? Not all hosts in the world 
want or need to be connected outside of the corporate network they belong 
to. Today such hosts are numbered in RFC 1918 space WITHOUT NAT and are 
connected to corporate networks. It's likely, given the line of argument 
you're proposing, that many corporations will just laugh at the IETF, and 
continue to use IPv4 for their private network space.