Re: Multihoming Issues

David Conrad <david.conrad@nominum.com> Wed, 04 September 2002 03:07 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21894; Tue, 3 Sep 2002 23:07:47 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id WAA06915 for ietf-outbound.09@loki.ietf.org; Tue, 3 Sep 2002 22:54:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id WAA06890 for <ietf-mainout@loki.ietf.org>; Tue, 3 Sep 2002 22:51:16 -0400 (EDT)
Received: by ietf.org (8.9.1a/8.9.1a) id WAA21594 for ietf-mainout@loki.ietf.org; Tue, 3 Sep 2002 22:49:38 -0400 (EDT)
X-Authentication-Warning: ietf.org: majordom set sender to owner-ietf@ietf.org using -f
Received: from shell.nominum.com (shell.nominum.com [128.177.192.160]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21590; Tue, 3 Sep 2002 22:49:34 -0400 (EDT)
Received: from [202.11.26.88] (shell.nominum.com [128.177.192.160]) by shell.nominum.com (Postfix) with ESMTP id 45551137F02; Tue, 3 Sep 2002 19:50:39 -0700 (PDT)
User-Agent: Microsoft-Entourage/10.1.0.2006
Date: Tue, 03 Sep 2002 19:51:23 -0700
Subject: Re: Multihoming Issues
From: David Conrad <david.conrad@nominum.com>
To: Simon Leinen <simon@limmat.switch.ch>
Cc: Fred Baker <fred@cisco.com>, Sister Sibling <ccs522g9@yahoo.com>, ietf <ietf@ietf.org>, iesg@ietf.org
Message-ID: <B99AC33B.11924%david.conrad@nominum.com>
In-Reply-To: <aaptvxaik9.fsf@limmat.switch.ch>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Simon,

On 9/1/02 7:30 AM, "Simon Leinen" <simon@limmat.switch.ch> wrote:
>>> - one prefix for each ISP in the world
>>> - one prefix for each POP or campus in your network
>>> - one prefix for each LAN in your POP or Campus
>>> - additional prefixes that you decide to carry for your own reasons (eg,
>>> policy)
>> My, that's a lot of prefixes.  I'm sure I'm missing something here.
> Probably - note how the scope gets narrower as you go down to smaller
> parts of the Internet.

Well, yeah, but if you want to gain full benefit of multi-homing, each of
these prefixes would need global visibility, no?

> In the IPv4 Internet, you have all of the above, plus
> - many prefixes assigned to most ISPs in the world after they used up
> their first assignment
> - many "campus" prefixes around the world that haven't been assigned
> according to ISP topology (such as legacy Class B/Cs)
> - many prefixes for "campuses" around the world that changed or added
> ISPs but kept addresses from their original provider's range.
> 
> Looks like IPv6 won't have the first two of these.  We'll see what
> will happen to the third category.

I would agree with the first of these.  I am skeptical regarding the second
-- having seen what sort of organizations became "ISPs" when CIDR
restrictions were imposed make me a bit cynical.  As for the third, I
suspect enforcement of renumbering implied by your statement guarantees
NATv6.

Rgds,
-drc