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

Philip Homburg <pch-v6ops-3a@u-1.phicoh.com> Sat, 31 May 2014 21:11 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 2B2201A00BF for <v6ops@ietfa.amsl.com>; Sat, 31 May 2014 14:11:51 -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 XuceKuNoYLy7 for <v6ops@ietfa.amsl.com>; Sat, 31 May 2014 14:11:49 -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 D8A941A00BE for <v6ops@ietf.org>; Sat, 31 May 2014 14:11:48 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #91) id m1WqqZ4-0000DqC; Sat, 31 May 2014 23:11:42 +0200
Message-Id: <m1WqqZ4-0000DqC@stereo.hq.phicoh.net>
To: V6 Ops List <v6ops@ietf.org>
From: Philip Homburg <pch-v6ops-3a@u-1.phicoh.com>
Sender: pch-bBB316E3E@u-1.phicoh.com
References: <43BB867C-7BCA-45F6-8ADC-A49B34D6C0DC@nominum.com> <5384937A.90409@foobar.org> <m2iooq4oqi.wl%randy@psg.com> <5385762E.5020901@dougbarton.us> <5385AA97.1050207@fud.no> <53864DCB.5070202@gmail.com> <53865EA2.9000502@fud.no> <02dc01cf7c06$cc6a4bc0$4001a8c0@gateway.2wire.net> <97390E9C-460F-4D08-AFCE-E4A991E2B0E4@cisco.com> <46D22F62-3528-4B9D-9FCF-C9C7466A9ABA@delong.com> <20140531104145.GQ46558@Space.Net>
In-reply-to: Your message of "Sat, 31 May 2014 12:41:45 +0200 ." <20140531104145.GQ46558@Space.Net>
Date: Sat, 31 May 2014 23:11:42 +0200
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/RVzpnA9JbRk3-Jx9oW9VdkxjL1k
Subject: Re: [v6ops] PI [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: Sat, 31 May 2014 21:11:51 -0000

In your letter dated Sat, 31 May 2014 12:41:45 +0200 you wrote:
>PA with automatic network (re-)numbering and multihoming with multiple
>PA networks already works today, and will really work much more pleasantly
>than PI *for those networks* as soon as we've sorted out some of the 
>remaining kinks (like source-address selection with SA failover).
>
>Maybe you should step down from your "I have PI, I like it, everybody must
>have PI" soapbox and actually look at what, for example, homenet has 
>achieved in the last years.  This stuff looks complicated (and under the
>hood, it is), but the end user experience "take this box, plug in a number
>of ISPs, things work, no further configuration is needed(*)" is nothing you
>can match with a PI network.

I can see how you can do do multiple PA prefixes client side. Done that
for years now. Even with different routers providing the upstreams. No problem
there.

But I have nothing to update my DNS zones. How do I reflect which links 
are up or down? Is there even a draft for that? What's the BCP for TTL
values, DNSSEC, etc?