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

Gert Doering <gert@space.net> Tue, 24 June 2014 19:57 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 53EBA1A0387 for <v6ops@ietfa.amsl.com>; Tue, 24 Jun 2014 12:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.951
X-Spam-Level:
X-Spam-Status: No, score=-1.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_32=0.6, 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 p0womottqnOu for <v6ops@ietfa.amsl.com>; Tue, 24 Jun 2014 12:57:22 -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 85D351A03CB for <v6ops@ietf.org>; Tue, 24 Jun 2014 12:57:22 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id E68AC60AD3 for <v6ops@ietf.org>; Tue, 24 Jun 2014 21:57:20 +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 ABC5C6025B for <v6ops@ietf.org>; Tue, 24 Jun 2014 21:57:20 +0200 (CEST)
Received: (qmail 93545 invoked by uid 1007); 24 Jun 2014 21:57:20 +0200
Date: Tue, 24 Jun 2014 21:57:20 +0200
From: Gert Doering <gert@space.net>
To: Nick Hilliard <nick@foobar.org>
Message-ID: <20140624195720.GA46558@Space.Net>
References: <20140602013829.875B917236AC@rock.dv.isc.org> <53A843C9.1040002@gmail.com> <70F894D7-8701-420F-B16F-F8EAF3AE276F@nominum.com> <53A94E88.6070101@foobar.org> <8E5FC7CC-454E-437F-A85B-69366BC5D7B5@nominum.com> <53A989D8.2080704@foobar.org> <BA6D229B-0645-42CB-BC29-DB467EB697A7@nominum.com> <53A9C84A.8020304@foobar.org> <20140624194638.GZ46558@Space.Net> <53A9D643.6040100@foobar.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="ULYbezmuIpuQrBKU"
Content-Disposition: inline
In-Reply-To: <53A9D643.6040100@foobar.org>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/BgBU9_6sBFWEiyDWWDe9o3y5t14
Cc: v6ops@ietf.org
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: Tue, 24 Jun 2014 19:57:24 -0000

Hi,

On Tue, Jun 24, 2014 at 08:49:23PM +0100, Nick Hilliard wrote:
> On 24/06/2014 20:46, Gert Doering wrote:
> > Mainly because some people keep repeating that BGP+PI is the only available
> > option.  Like, religiously.  You're not *that* old yet.
> 
> ...then point me to another option which works reliably.

"reliably" in itself is already a red herring.  Protecting you against
*what*, and under which assumptions?

For "I want my facebook and youtube and e-mail to work, even if one of 
my ISPs goes belly-up!", homenet + dual-prefix works.  It will not give
you perfectness just yet, aka "source address selection will not 
pick the best source IP for whatever definition of 'best'", but MIF is
working on optimizing this.  Your sessions will die if you are actively 
using the ISP that just died on you, but mp-tcp is one *demonstrably
working* way to handle that, get much faster session failover that BGP 
would give you (seconds, not minutes).

For "I need to run a datacenter full of stuff that need to have stable
addresses, no matter what happens elsewhere", I give you that BGP+PI
(or whatever other source of "your addresses") is a much better and
more reliable approach.  But for a barber shop that just wants their
internet radio to be there all the time, it's completely wrong.

Short form.  Longer discussion of the options and missing bits upstream
in this very thread.

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