RE: draft-ietf-ipv6-ula-central-02.txt

<michael.dillon@bt.com> Fri, 13 July 2007 19:27 UTC

Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9QnY-0008Ar-Ev; Fri, 13 Jul 2007 15:27:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9QnW-00081x-SN for ipv6@ietf.org; Fri, 13 Jul 2007 15:27:26 -0400
Received: from smtp3.smtp.bt.com ([217.32.164.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I9QnW-0006KQ-Hc for ipv6@ietf.org; Fri, 13 Jul 2007 15:27:26 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 13 Jul 2007 20:27:01 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 13 Jul 2007 20:28:32 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B0AF5F95@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <016101c7c56b$5b16ec70$373816ac@atlanta.polycom.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: AcfFa5SIVa8xOgSiRpSMTpgkDU1WJwAFVHGA
References: <200706221709.l5MH9uEN003458@mail.reprise.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com><467C1F53.9070600@spaghetti.zurich.ibm.com><20070622195429.GG31273@elvis.mu.org><467C2EE6.3070100@spaghetti.zurich.ibm.com><20070623005010.GI31273@elvis.mu.org><467D0806.7030100@spaghetti.zurich.ibm.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com><467FDEAA.1020503@spaghetti.zurich.ibm.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com><467FE693.5060103@spaghetti.zurich.ibm.com><D03E4899F2FB3D4C8464E8C76B3B68B09A3E29@E03MVC4-UKBR.domain1.systemhost.net><00b301c7c4ae$506469a0$3d3816ac@atlanta.polycom.com><Pine.LNX.4.64.0707131202560.9923@chandra.student.uit.no> <016101c7c56b$5b16ec70$373816ac@atlanta.polycom.com>
From: michael.dillon@bt.com
To: ipv6@ietf.org
X-OriginalArrivalTime: 13 Jul 2007 19:27:01.0307 (UTC) FILETIME=[C95D48B0:01C7C583]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> As far as why "site" has been abused to mean "administrative 
> domain", that comes from the IETF and RIRs being very 
> ISP-centric, as I said; a single downstream connection 
> denotes a single "site" regardless of how complex the 
> internal network behind it is or how many other locations it 
> serves.  Or maybe it doesn't, depending on who's talking; 
> that's the problem.

I have always believed that the definition of a site in IPv6 is tied in
with the idea that if every "site" has a /48 subnet assignment, then
migration to a different provider only requires changing the prefix
bits. The existing subnet topology hidden inside the /48 remains
unchanged.

By this definition an apartment or family home is a site. An office in
big buidling is a site. A company building is a site. A campus-like
collection of buildings is a site. Here is where definitions need to be
precise and relate back to original goals.

A single company may own several buildings and those buildings may be
next to each other. I believe that each separate building should be
considered to be a site. A campus is more than a collection of buildings
because it is difficult, or impossible to separate one building from the
group. On a campus there is centralization of utilities, even going so
far as to connect all buildings by tunnel systems and heat all buildings
via hot water from a central steam plant.

Why is the definition of a site so important? Because a "site" is
mobile. It can change providers and it can change ownership indpendent
of neighboring sites. By that definition, airplanes, trucks and train
carriages are also sites. They are just mobile more frequently than
sites in buildings.

I think it is important for the IETF to have clear documentation of the
interconnectedness of "sites", /48 prefixes, mobility, and freedom of
choice.

At least one RIR now allows ISPs to assign shorter /56 prefixes to
consumer sites, i.e. family homes and apartments. This is not
necessarily a bad thing since it is rare for a family home to turn into
an office without significant infrastructure change. But if there is to
be a special size for the family home, it too should be the same
worldwide. And it too should be documented by the IETF.

--Michael Dillon

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------