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

Nick Hilliard <nick@foobar.org> Tue, 24 June 2014 20:43 UTC

Return-Path: <nick@foobar.org>
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 30B5B1B2884 for <v6ops@ietfa.amsl.com>; Tue, 24 Jun 2014 13:43:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 3ssujhqS5QXv for <v6ops@ietfa.amsl.com>; Tue, 24 Jun 2014 13:43:35 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D502E1B2813 for <v6ops@ietf.org>; Tue, 24 Jun 2014 13:43:34 -0700 (PDT)
X-Envelope-To: v6ops@ietf.org
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100::110]) (authenticated bits=0) by mail.netability.ie (8.14.9/8.14.5) with ESMTP id s5OKhVAZ092056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 24 Jun 2014 21:43:31 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.netability.ie: Host [IPv6:2001:4d68:2002:100::110] claimed to be cupcake.foobar.org
Message-ID: <53A9E2F3.6080206@foobar.org>
Date: Tue, 24 Jun 2014 21:43:31 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Gert Doering <gert@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> <20140624195720.GA46558@Space.Net>
In-Reply-To: <20140624195720.GA46558@Space.Net>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/veA8RMCDZ0-nVGFXL_mo8wTsFt0
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 20:43:39 -0000

On 24/06/2014 20:57, Gert Doering wrote:
> 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).

this kinda gets back to issue of what we mean when we talk about
multihoming, which is why I poked Ted multiple times to try to get him to
define what he meant when he used the term.  At the moment it seems like
we're all talking about different things, and this is leading to some of
the confusion.

So I ask again: can we please define what we mean by multihoming in the
context of this discussion?  Until we have clarified what we're talking
about, the discussion is not going to lead anywhere.

Nick