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

Ted Hardie <hardie@qualcomm.com> Thu, 27 March 2003 00:18 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 TAA24152; Wed, 26 Mar 2003 19:18:34 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 18yL3R-0004f7-00 for ietf-list@ran.ietf.org; Wed, 26 Mar 2003 19:15:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 18yL20-0004Kw-00 for ietf@ran.ietf.org; Wed, 26 Mar 2003 19:14:08 -0500
Received: from ithilien.qualcomm.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23589 for <ietf@ietf.org>; Wed, 26 Mar 2003 18:58:55 -0500 (EST)
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by ithilien.qualcomm.com (8.12.8/8.12.5/1.0) with ESMTP id h2R01EX7001473; Wed, 26 Mar 2003 16:01:14 -0800 (PST)
Received: from qualcomm.com (carbuncle.qualcomm.com [129.46.227.161]) by magus.qualcomm.com (8.12.8/8.12.5/1.0) with ESMTP id h2R01CtN002646; Wed, 26 Mar 2003 16:01:12 -0800 (PST)
Date: Wed, 26 Mar 2003 16:01:11 -0800
Subject: Re: site local addresses (was Re: Fw: Welcome to the InterNAT...)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v551)
Cc: The IETF <ietf@ietf.org>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
From: Ted Hardie <hardie@qualcomm.com>
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F54D29@server2000.arneill-py.sacramento.ca.us>
Message-Id: <382B8D9A-5FE7-11D7-91E0-000393CB0816@qualcomm.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Michel,
	I don't think something needs to be provider independent
to fit this bill.  Getting a slice of the global address space from
some provider and choosing not route a portion of it (even
if that portion is 100%) seems to me to create "non-routed
globally unique space".  Are you concerned that doing so
has some impact on the routing system that needs to be
considered?
	Money and other annoyances are certainly concerns we
all face.  In that spirit please understand that keeping site local 
costs
different money and creates different annoyances.
				regards,
						Ted


On Wednesday, March 26, 2003, at 03:51 PM, Michel Py wrote:

>> Ted Hardie wrote:
>> I think we then to consider whether the current need
>> is for: "non-routed globally unique space" or for
>> something else.  If the answer is "non-routed globally
>> unique space", then the follow-on question is "Why not
>> get globally unique space and simply decide not to
>> route it?".
>
> Because such thing does not exist, it's called PI and is not available
> to IPv6 end-sites. And if it ever is, it will cost money or other
> annoyances to obtain.
>
> Michel.
>
>