IETF Logo Mail Archive

RE: Multihoming Issues

"Michel Py" <michel@arneill-py.sacramento.ca.us> Sat, 31 August 2002 02:15 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12310; Fri, 30 Aug 2002 22:15:15 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id WAA10850 for ietf-outbound.09@loki.ietf.org; Fri, 30 Aug 2002 22:00: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 VAA10813 for <ietf-mainout@loki.ietf.org>; Fri, 30 Aug 2002 21:56:02 -0400 (EDT)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA11750 for ietf-mainout@loki.ietf.org; Fri, 30 Aug 2002 21:54:29 -0400 (EDT)
X-Authentication-Warning: ietf.org: majordom set sender to owner-ietf@ietf.org using -f
Received: from server2000.arneill-py.sacramento.ca.us (adsl-209-233-126-65.dsl.scrm01.pacbell.net [209.233.126.65]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11740; Fri, 30 Aug 2002 21:54:09 -0400 (EDT)
Subject: RE: Multihoming Issues
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Date: Fri, 30 Aug 2002 18:55:08 -0700
content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Message-ID: <2B81403386729140A3A899A8B39B046405E2BC@server2000>
Thread-Topic: Multihoming Issues
Thread-Index: AcJQQTrpkXFr4AkmR7KTAu9rQW9iqwATiVww
From: Michel Py <michel@arneill-py.sacramento.ca.us>
To: Sister Sibling <ccs522g9@yahoo.com>, ietf@ietf.org, iesg@ietf.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAB11741
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

> Sister Sibling wrote:
> The IETF is recommending that the DNS mechanisms to
> support IPv6 stay essentially the same as those already
> in use with IPv4 today. To our opinion, in the realm of
> multi-homed networks, the techniques used in IPv4 can't
> all be applied since they have scaling problems.
> Specifically, if the same prefix is advertised by multiple
> ISPs, the routing tables will grow as a function of the
> number of multihomed sites.

I fail to see the relation between DNS and the number of
prefixes being advertised.

As far as scalability is concerned, it is clear that the
mechanism currently being used with IPv4 is not very
scalable, but is reserved to multihomed ISPs/LIRs at this
time and it is generally admitted that one prefix per LIR
would remain a reasonably manageable number even in the
long run. End-sites will likely require a multihoming
solution that is aggregatable.

                       _   ____  __      __  ____   _    _   _    _
Michel Py             | | |  _ \ \ \    / / / ___| | \  / | | |  | |
Sr. Network Engineer  | | | |_| | \ \  / / | |__   |  \/  | | |__| |
CNE, MCSE, CNP        | | |  __/   \ \/ /  |  _ \  | \  / | |  __  |
CCIE #6673            | | | |       \  /   | |_| | | |\/| | | |  | |
mpy@ieee.org          |_| |_|        \/     \___/  |_|  |_| |_|  |_|

                        http://arneill-py.sacramento.ca.us/ipv6mh

v2.23.0 | Report a Bug | By Email