RE: Multihoming Issues

"Christian Huitema" <huitema@windows.microsoft.com> Wed, 04 September 2002 01:01 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19104; Tue, 3 Sep 2002 21:01:12 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA06109 for ietf-outbound.09@loki.ietf.org; Tue, 3 Sep 2002 20:30: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 UAA06076 for <ietf-mainout@loki.ietf.org>; Tue, 3 Sep 2002 20:29:21 -0400 (EDT)
Received: by ietf.org (8.9.1a/8.9.1a) id UAA18258 for ietf-mainout@loki.ietf.org; Tue, 3 Sep 2002 20:27:44 -0400 (EDT)
X-Authentication-Warning: ietf.org: majordom set sender to owner-ietf@ietf.org using -f
Received: from mail4.microsoft.com (mail4.microsoft.com [131.107.3.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18254 for <ietf@ietf.org>; Tue, 3 Sep 2002 20:27:40 -0400 (EDT)
Received: from inet-vrs-04.redmond.corp.microsoft.com ([157.54.8.149]) by mail4.microsoft.com with Microsoft SMTPSVC(5.0.2195.4905); Tue, 3 Sep 2002 17:28:55 -0700
Received: from 157.54.6.150 by inet-vrs-04.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 03 Sep 2002 17:28:52 -0700
Received: from red-imc-01.redmond.corp.microsoft.com ([157.54.9.102]) by inet-hub-05.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966); Tue, 3 Sep 2002 17:28:44 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by red-imc-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.4905); Tue, 3 Sep 2002 17:28:44 -0700
Received: from win-msg-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.134]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3663.0); Tue, 3 Sep 2002 17:28:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6728.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: RE: Multihoming Issues
Date: Tue, 03 Sep 2002 17:28:05 -0700
Message-ID: <F66A04C29AD9034A8205949AD0C90104032709DE@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Multihoming Issues
Thread-Index: AcJThKC3cQZmkDPhQHCBP4bGCDzFbAAJFF4A
From: Christian Huitema <huitema@windows.microsoft.com>
To: Caitlin Bestler <caitlinb@rp.asomi.net>, Michel Py <michel@arneill-py.sacramento.ca.us>
Cc: ietf@ietf.org
X-OriginalArrivalTime: 04 Sep 2002 00:28:41.0717 (UTC) FILETIME=[053C2A50:01C253AA]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id UAA18255
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

> The relationship is that DNS is acting as an index service
> for IPv6 addresses. In doing so it treats them as simple
> hierarchical  addresses, i.e. like fat IPv4 addresses.
> 
> The question as to whether that is the correct handling of
> IPv6 addresses is a valid one. This thread started with
> exactly such a question being raised, but the rationale on
> how DNS *could* be optimized for IPV6 was not spelled out.

There is no IPv6 service that guarantees that the identifiers are
actually world-wide unique. In fact, there is ample evidence that they
often will not be. Poorly configured interface cards are known to have
phony IEEE-802 addresses; privacy addresses are random numbers that are
only statistically unique; configured addresses may use user assigned
values. In all these cases, local collisions can be detected, global
collisions cannot be. 

There is also no requirement that a given multi-homed hosts combines the
same identifier with different prefixes. Privacy advocates will no doubt
argue that a multi-homed host should associate different identifiers
with different provider prefixes, so it cannot be tracked by
big-brother.

-- Christian Huitema