Re: My thoughts on local-use addresses

Daniel Senie <dts@senie.com> Tue, 29 April 2003 16:45 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 MAA00594; Tue, 29 Apr 2003 12:45:54 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 19AXzt-0005MD-00 for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 12:30:25 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 19AXeQ-0004od-00 for ietf@ran.ietf.org; Tue, 29 Apr 2003 12:08:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29025 for <ietf@ietf.org>; Tue, 29 Apr 2003 12:05:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19AXdh-0005he-00 for ietf@ietf.org; Tue, 29 Apr 2003 12:07:29 -0400
Received: from garlic.amaranth.net ([208.254.46.17]) by ietf-mx with esmtp (Exim 4.12) id 19AXdg-0005hb-00 for ietf@ietf.org; Tue, 29 Apr 2003 12:07:28 -0400
Received: from Willow.senie.com (amaranth.ne.client2.attbi.com [24.34.18.226]) (authenticated (0 bits)) by garlic.amaranth.net (8.11.7/8.11.7) with ESMTP id h3TG62A10796 (using TLSv1/SSLv3 with cipher RC4-SHA (128 bits) verified NO); Tue, 29 Apr 2003 12:06:03 -0400
Message-Id: <5.2.1.1.2.20030429115950.01af3f30@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Tue, 29 Apr 2003 12:05:18 -0400
To: John Stracke <jstracke@centive.com>, ietf@ietf.org
From: Daniel Senie <dts@senie.com>
Subject: Re: My thoughts on local-use addresses
Cc: ipng <ipng@sunroof.eng.sun.com>
In-Reply-To: <3EAE8ABE.4010105@centive.com>
References: <BAD1757F.35D36%arien.vijn@ams-ix.net> <BAD1757F.35D36%arien.vijn@ams-ix.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 10:22 AM 4/29/2003, John Stracke wrote:
>Arien Vijn wrote:
>
>>On 26-04-2003 19:35PM, "Keith Moore" <moore@cs.utk.edu> wrote:
>>
>>
>>>>What is wrong with having addresses available for private use on
>>>>networks that do not intend on being connected to the Internet?
>>>>
>>>in principle, nothing.  but experience has shown that most of those networks
>>>do end up being connected to the Internet, while still keeping those 
>>>addreses,
>>>and that applications are expected to cope with that.
>>>
>>Ehm... What experience? You are referring to experiences with RFC1918
>>addresses in the IPv4-world, aren't you?
>I think Keith is most likely referring to the experience from before 
>RFC1597, when isolated networks would use random addresses, and then run 
>into trouble when they wanted to connect.  Even if the networks were 
>NATted, the users would suffer because they would never be able to 
>communicate with the legitimate holders of the addresses.

Indeed. Many folks used Sun's address block, since Sun used their own IP 
address space in their documenation for examples. Even worse than randomly 
selecting, this meant many people collided both in the ways we all know 
about when two RFC1918-numbered networks merge and in terms of conflicts if 
trying to connect to the public network.

Many NANOG folks are busy screaming that everyone who's got pre-RIR address 
space that's not publicly routed should be giving it up and using RFC 1918. 
Many IETF folks are similarly trying to eradicate the use of any non-public 
IP address space. Clearly we have a major disconnect between the IETF and 
the operations communities. And while the response to this posting will be 
"IPv6 space is limitless," I would argue that ignores the past, and the 
possibility of a repeat in the future.