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

Gert Doering <gert@space.net> Sat, 31 May 2014 10:41 UTC

Return-Path: <gert@Space.Net>
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 C93FA1A03C2 for <v6ops@ietfa.amsl.com>; Sat, 31 May 2014 03:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 wL5Kb-9Uj-L7 for <v6ops@ietfa.amsl.com>; Sat, 31 May 2014 03:41:51 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63CC01A01F2 for <v6ops@ietf.org>; Sat, 31 May 2014 03:41:51 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id B0E296042C for <v6ops@ietf.org>; Sat, 31 May 2014 12:41:45 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 81C0060183 for <v6ops@ietf.org>; Sat, 31 May 2014 12:41:45 +0200 (CEST)
Received: (qmail 1815 invoked by uid 1007); 31 May 2014 12:41:45 +0200
Date: Sat, 31 May 2014 12:41:45 +0200
From: Gert Doering <gert@space.net>
To: Owen DeLong <owen@delong.com>
Message-ID: <20140531104145.GQ46558@Space.Net>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <46D22F62-3528-4B9D-9FCF-C9C7466A9ABA@delong.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/ccniTAtfHhCrd3Oyy4YDZWas8lo
Cc: V6 Ops List <v6ops@ietf.org>, Tore Anderson <tore@fud.no>
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 10:41:52 -0000

Hi,

On Fri, May 30, 2014 at 05:15:14PM -0700, Owen DeLong wrote:
> It's more than that. It also creates an unpleasant kind of fate
> sharing between end-site and ISP as well as some vendor-lockin
> problems. Bottom line, for many end-sites, PA is an acceptable
> tradeoff, but it is desirable to none. PI is universally better for
> the end-site

I challenge that.  For a end site with no technical understanding (like,
*most* of them), PI is not useful.  Not at all.

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.

(*) for the case "there's a cable hanging from the wall with DHCPv6-PD 
and RA in it".  For cases where you need to configure access credentials,
homenet cannot automate this, of course.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279