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

Roger Jorgensen <rogerj@jorgensen.no> Wed, 11 July 2007 09:39 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 1I8Yf4-0000me-4k; Wed, 11 Jul 2007 05:39:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Yf3-0000mV-7V for ipv6@ietf.org; Wed, 11 Jul 2007 05:39:05 -0400
Received: from mux1.uit.no ([129.242.4.252]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8Yey-0002I3-MH for ipv6@ietf.org; Wed, 11 Jul 2007 05:39:05 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34]) by mux1.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l6B9cvjU087580 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jul 2007 11:38:57 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32]) by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id l6B9cui9032011; Wed, 11 Jul 2007 11:38:57 +0200
Date: Wed, 11 Jul 2007 11:38:56 +0200
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: james woodyatt <jhw@apple.com>
In-Reply-To: <B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>
Message-ID: <Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no>
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>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.4.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
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

On Tue, 10 Jul 2007, james woodyatt wrote:
<snip>
>
> Hmmm.  I guess the alternative is that the purpose of ULA-C/G is to mitigate 
> the risk of collision when merging on the order of hundreds of thousands of 
> ULA networks in one routing realm... sort of like creating a "local DFZ" of a 
> sort.
>
> Forgive me, but that sounds even more surreal.  It's tough for me to imagine 
> how a real organization doing that could fail to qualify for a PI allocation, 
> or why such an organization would find it unacceptable to have to use a PI 
> allocation without advertising it to the public DFZ.  Likewise, it's tough to 
> imagine how an organization that doesn't qualify for a PI allocation could be 
> merging enough ULA networks together that the risk of collision rises to a 
> level of any real significance.
>
> Okay.  Maybe the problem with PI allocations for this purpose is that 
> organizations doing all this network merging, i.e. extraordinarily paranoid 
> organizations, e.g. the Communist Party, want some kind of assurance from the 
> operators of the public Internet that their hundreds of thousands of local 
> networks aren't directly reachable from the public DFZ in the event a local 
> NOC configures a border router improperly.  Obviously, ULA-C can do that 
> better than PI.
>
> Is that the big driving factor here?

PI can be used for almost everything ULA-C/G can be used for, dont think 
anyone disagree on that. The whole ULA-C/G is about the purpose of the 
address space and what it can be used for both now and in the future. 
Strictly internal/private networking right now and ID/LOC or whatever in 
the future... or other thing we dont know about.

It is more about creating a address space that can be used for OTHER thing 
than the DFZ-way of thinking Internet we have now.

And yes you have a good point, internal infrastructure like the above 
operator but that is almost excacly what we (where I work) want to use it 
for! .. just that we will also place some of our customers there to.
(and please dont start the rant about NAT or whatever we need to get them 
onto internet because they are not suppose to be conneted directly to 
internet)



-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

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