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

<michael.dillon@bt.com> Wed, 11 July 2007 11:50 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 1I8ai5-00061b-Ls; Wed, 11 Jul 2007 07:50:21 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8ai4-00061N-5h for ipv6@ietf.org; Wed, 11 Jul 2007 07:50:20 -0400
Received: from smtp2.smtp.bt.com ([217.32.164.150]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8aho-00060E-Ss for ipv6@ietf.org; Wed, 11 Jul 2007 07:50:20 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 11 Jul 2007 12:49:40 +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: Wed, 11 Jul 2007 12:51:13 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B0AA2DC9@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <4694BD3D.20708@spaghetti.zurich.ibm.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: AcfDracjZig411RsTGGRdw3ssFvo1wAA0b0w
References: <200706251556.l5PFu6Qa057410@mail.reprise.com><078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com><94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com><Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no><FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com><22851.1184090216@sa.vix.com><B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com> <Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no> <D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net> <4694BD3D.20708@spaghetti.zurich.ibm.com>
From: michael.dillon@bt.com
To: ipv6@ietf.org
X-OriginalArrivalTime: 11 Jul 2007 11:49:40.0340 (UTC) FILETIME=[90728340:01C7C3B1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
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

> The question here still remains though: how really different 
> is this from "PI". In effect it is non-DFZ-PI space that is 
> being defined here.

PI (Provider Independent) is not a relevant term to refer to addresses
that are allocated to end-user organizations for use in their own
networks. There is no provider in such a scenario, therefore the
addresses are neither provider-independent nor provider-dependent. In
fact, they are local to the end-user network which is why people have
been referring to them as Unique Local Addresses (ULA). It appears that
we are accumulating enough changes from the original ULA that it is not
correct to refer to them as ULA addresses that are centrally registered.
However, they are Unique, and they are Local. Perhaps ULRA (Unique Local
Registered Addresses) is sufficiently different from ULA that people
will not accidentally look to RFC 4193 for advice?

--Michael Dillon

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