Re: [v6ops] ULA draft revision #2 Regarding isolated networks

Philip Homburg <pch-v6ops-3a@u-1.phicoh.com> Tue, 27 May 2014 13:56 UTC

Return-Path: <pch-bBB316E3E@u-1.phicoh.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDE8B1A038E for <v6ops@ietfa.amsl.com>; Tue, 27 May 2014 06:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.9
X-Spam-Level:
X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kP9OToI2-33J for <v6ops@ietfa.amsl.com>; Tue, 27 May 2014 06:56:41 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 024BA1A014E for <v6ops@ietf.org>; Tue, 27 May 2014 06:56:40 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #91) id m1WpHrp-0000BQC; Tue, 27 May 2014 15:56:37 +0200
Message-Id: <m1WpHrp-0000BQC@stereo.hq.phicoh.net>
To: v6ops WG <v6ops@ietf.org>
From: Philip Homburg <pch-v6ops-3a@u-1.phicoh.com>
Sender: pch-bBB316E3E@u-1.phicoh.com
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D8B6B9A@nkgeml506-mbx.china.huawei.com> <m261ks7xww.wl%randy@psg.com> <53840070.90801@gmail.com> <m2y4xn7wep.wl%randy@psg.com> <53840723.8010606@gmail.com> <CAKD1Yr1O_poMR200sjU=ttRvGaeQRkC1ZfXC0Ok4uQxdq3K=NQ@mail.gmail.com> <m2mwe37tbn.wl%randy@psg.com> <CAKD1Yr2t3-vxuG=iDi4biBNFpJwuzuHgfpB74i_uydWWRV7qZg@mail.gmail.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D8B6E02@nkgeml506-mbx.china.huawei.com> <m2fvjv7q4h.wl%randy@psg.com> <m1WpDcc-0000BMC@stereo.hq.phicoh.net> <43BB867C-7BCA-45F6-8ADC-A49B34D6C0DC@nominum.com>
In-reply-to: Your message of "Tue, 27 May 2014 08:52:02 -0400 ." <43BB867C-7BCA-45F6-8ADC-A49B34D6C0DC@nominum.com>
Date: Tue, 27 May 2014 15:56:36 +0200
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/qhvbh_AV6xagtHdkYNkL45cJTas
Subject: Re: [v6ops] ULA draft revision #2 Regarding isolated networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 13:56:48 -0000

In your letter dated Tue, 27 May 2014 08:52:02 -0400 you wrote:
>The operational situation that's problematic is the large enterprise 
>scenario, where you have two large enterprises with their own ULAs that 
>merge.   If those ULAs happen to clash, you have to renumber at least 
>one of them.   If they don't clash, you still have to deal with routing 
>them (although I think the split-horizon complexity objection Mikael 
>raised ought to be thought through carefully before being asserted as 
>factual, because I think it can be addressed through routing and not 
>naming).

If you are a large entrprise, just spend the 50 euro or so (RIPE service region) it
costs to get your own prefix.

I assume that any large enterprise is very likely to be multi-homed anyhow. Even
becoming an LIR should not even be noticable in the budget.

No real reason for a large enterprise to use ULA.