IETF Logo Mail Archive

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

Ted Lemon <ted.lemon@nominum.com> Mon, 02 June 2014 20:57 UTC

Return-Path: <Ted.Lemon@nominum.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 B56FD1A043E for <v6ops@ietfa.amsl.com>; Mon, 2 Jun 2014 13:57:13 -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 GR8mHGLgdLbH for <v6ops@ietfa.amsl.com>; Mon, 2 Jun 2014 13:57:11 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D098A1A0425 for <v6ops@ietf.org>; Mon, 2 Jun 2014 13:57:11 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 8C9631B8204 for <v6ops@ietf.org>; Mon, 2 Jun 2014 13:57:06 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 812D219005C; Mon, 2 Jun 2014 13:57:06 -0700 (PDT)
Received: from [10.1.10.98] (173.162.205.174) by CAS-01.WIN.NOMINUM.COM (64.89.228.131) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 2 Jun 2014 13:57:06 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <20140602204730.GH46558@Space.Net>
Date: Mon, 02 Jun 2014 16:57:03 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <A1865238-7A02-4E53-B191-5DD486FB3A7F@nominum.com>
References: <2A4B72CD-EDF3-4D11-AC39-B65892F9173F@nominum.com> <CAKD1Yr2NH4Kca4EvhjN2XnDbt8F2eS56ipxu3npH9yOh1bmQaA@mail.gmail.com> <F12F173B-9FF2-4EF8-B11E-33AEDA24961F@nominum.com> <CAKD1Yr1cGx7UfxZaEhm7oHA5PLvghVc52oPVkEQF90_7Vm__vw@mail.gmail.com> <1FDC3A7F-15EC-4397-AF3E-10F86EA04228@nominum.com> <538BDA84.6030800@bogus.com> <37D09BEE-FEDF-4514-8CEB-62959A89C3FF@nominum.com> <538BE13C.7050900@bogus.com> <20140602081743.GP46558@Space.Net> <538CE1CF.9030002@gmail.com> <20140602204730.GH46558@Space.Net>
To: Gert Doering <gert@space.net>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [173.162.205.174]
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/YpxYnxFw99TR99-jrrcTnz_neI4
Cc: Philip Homburg <pch-v6ops-3a@u-1.phicoh.com>, V6 Ops List <v6ops@ietf.org>
Subject: Re: [v6ops] source address failover [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: Mon, 02 Jun 2014 20:57:13 -0000

On Jun 2, 2014, at 4:47 PM, Gert Doering <gert@space.net> wrote:
> I'm not convinced we particularily *need* it, though, as - as far as I 
> understood - shim6 will primarily serve to ensure session survivability, 
> while in most scenarios, sessions are so shortlived that "oh, ISP broken,
> use other one" will be a matter of clicking reload in the browser...

The long-lived connection I'd be most interested in would be a download or a video stream.   TBH, I don't know the state of the art on streaming and multiply homed devices, though.   I know that there are techniques that spread streams across flows, but I don't know if they spread flows across links without operator intervention on a dual-homed home network.

v2.23.0 | Report a Bug | By Email