RE: [Fwd: [Saad] Some initiating thoughts...]
"Michel Py" <michel@arneill-py.sacramento.ca.us> Fri, 17 October 2003 05:18 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07048 for <saad-archive@odin.ietf.org>; Fri, 17 Oct 2003 01:18:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAMzx-0006Kh-UR for saad-archive@odin.ietf.org; Fri, 17 Oct 2003 01:18:02 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9H5I1mt024337 for saad-archive@odin.ietf.org; Fri, 17 Oct 2003 01:18:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAMzx-0006KS-Or for saad-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 01:18:01 -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 BAA07045 for <saad-web-archive@ietf.org>; Fri, 17 Oct 2003 01:17:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAMzu-0006d3-00 for saad-web-archive@ietf.org; Fri, 17 Oct 2003 01:17:58 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AAMzu-0006d0-00 for saad-web-archive@ietf.org; Fri, 17 Oct 2003 01:17:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAMzw-0006K6-RH; Fri, 17 Oct 2003 01:18:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAMzH-0006JO-C0 for saad@optimus.ietf.org; Fri, 17 Oct 2003 01:17:19 -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 BAA07037 for <saad@ietf.org>; Fri, 17 Oct 2003 01:17:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAMzE-0006cm-00 for saad@ietf.org; Fri, 17 Oct 2003 01:17:16 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us) by ietf-mx with esmtp (Exim 4.12) id 1AAMzD-0006ch-00 for saad@ietf.org; Fri, 17 Oct 2003 01:17:15 -0400
Subject: RE: [Fwd: [Saad] Some initiating thoughts...]
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Date: Thu, 16 Oct 2003 22:16:46 -0700
Content-Transfer-Encoding: quoted-printable
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C663@server2003.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: [Fwd: [Saad] Some initiating thoughts...]
thread-index: AcOUWBrvqtIuv5R6R/qq+Xf8KhnzGgACv98g
From: Michel Py <michel@arneill-py.sacramento.ca.us>
To: Leslie Daigle <leslie@thinkingcat.com>, saad@ietf.org
Content-Transfer-Encoding: quoted-printable
Sender: saad-admin@ietf.org
Errors-To: saad-admin@ietf.org
X-BeenThere: saad@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/saad>, <mailto:saad-request@ietf.org?subject=unsubscribe>
List-Id: Scope Addressing Architecture Discussion <saad.ietf.org>
List-Post: <mailto:saad@ietf.org>
List-Help: <mailto:saad-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/saad>, <mailto:saad-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Leslie, > Leslie Daigle wrote: > I posted this a few days ago -- before, I think, people had > a chance to get subscribed IMHO, this text is a good short assessment of the situation. Needs some more work, but a good base. > [draft-iab-addressing-2003815.txt] > Although it is not strictly required, the IPv4 address > architecture largely assumed a unique binding of a device > interface to an IP address. Essentially this means a > device interface existed as a member of a single > addressing realm. With IPv6, a large number of issues with SLs and scoping are a direct consequence of the disappearance of this unique binding. Save for LLs which are a different kind of animal because they are not routable, the very assumption of multiple addresses per host has caused us a lot of trouble. IMHO the only way we could make any kind of scoping architecture work is to accept the following restriction: If scope is to be used, a host can have only two IPv6 addresses per interface: a link-local and another one, which would be routable but with possibly a have limited reachability depending on the scope. It would then be a design element to decide to use either multiaddressing or scoping. The idea behind scoping is that it should be a largely-automatic access control system, likely as a fail-safe for explicit filtering or firewalling. This means that hosts would not need to be aware of the scope except to make the distinction between LL and routable. Note that, for a many enterprise operators, the "restriction" of having only two addresses per host per interface which is very similar to the existing IPv4 situation is a feature, not a bug. Regardless of issues with scoping, multiple routable addresses per interface simply are too much complication. I am not saying that multiadressing is bad, what I am saying is that multiaddressing does not work in certain situations. This list is focused on scoping. I am aware that some identifier/locator solutions propose that the IPv6 address is used only as a locator, the identifier being a different type of animal. In the situations where scoping is desired, the way out IMHO is that the host's routable address is the identifier (the reason being it would be a lot simpler to scope than a flexible-shape identifier) and that there is a shim layer between Transport and Network that does the identifier / locator mapping. Michel. _______________________________________________ Saad mailing list Saad@ietf.org https://www1.ietf.org/mailman/listinfo/saad
- [Saad] Some initiating thoughts... Leslie Daigle
- [Fwd: [Saad] Some initiating thoughts...] Leslie Daigle
- RE: [Fwd: [Saad] Some initiating thoughts...] Michel Py
- Re: [Fwd: [Saad] Some initiating thoughts...] J. Noel Chiappa
- Re: [Fwd: [Saad] Some initiating thoughts...] Erik Nordmark
- Re: [Fwd: [Saad] Some initiating thoughts...] Melinda Shore
- Re: [Fwd: [Saad] Some initiating thoughts...] James Kempf
- Re: [Fwd: [Saad] Some initiating thoughts...] Erik Nordmark
- RE: [Fwd: [Saad] Some initiating thoughts...] Harrington, David
- Re: [Fwd: [Saad] Some initiating thoughts...] Melinda Shore
- RE: [Fwd: [Saad] Some initiating thoughts...] Erik Nordmark
- Re: [Fwd: [Saad] Some initiating thoughts...] Pekka Savola
- Re: [Fwd: [Saad] Some initiating thoughts...] Brian E Carpenter
- RE: [Fwd: [Saad] Some initiating thoughts...] Harrington, David
- Re: [Fwd: [Saad] Some initiating thoughts...] Brian E Carpenter