IETF Logo Mail Archive

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

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 03 July 2014 08:27 UTC

Return-Path: <swmike@swm.pp.se>
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 94FE91A0451 for <v6ops@ietfa.amsl.com>; Thu, 3 Jul 2014 01:27:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.602
X-Spam-Level:
X-Spam-Status: No, score=-4.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 WamiRidinqp7 for <v6ops@ietfa.amsl.com>; Thu, 3 Jul 2014 01:27:21 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A60241A03E9 for <v6ops@ietf.org>; Thu, 3 Jul 2014 01:27:21 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 6013FA1; Thu, 3 Jul 2014 10:27:19 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1404376039; bh=A5iYxuqqjQYIiB0TsW2V362jmWdV7nhlDA1teQVvTM4=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=gARHtt+3K63Le0E0Vt19OlDdyXARFLBNVp0xnE8oicOhr323l1TlJ6ZpZivmarT0R sCBMYTbpnUc2yl8wtIuWBs4SAToWc6Ys4AgGDVSxdXlQuTfmvBgTM9D1eX2JjZRtu9 jsrskbwdhmslcSmx8YmcDF9LocdsB3A0kSQlZ1TQ=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 523A89F; Thu, 3 Jul 2014 10:27:19 +0200 (CEST)
Date: Thu, 03 Jul 2014 10:27:19 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <A1865238-7A02-4E53-B191-5DD486FB3A7F@nominum.com>
Message-ID: <alpine.DEB.2.02.1407031010080.7929@uplift.swm.pp.se>
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> <A1865238-7A02-4E53-B191-5DD486FB3A7F@nominum.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/QtkMbqfxThdUOl8iRCUirqmd4kg
Cc: 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: Thu, 03 Jul 2014 08:27:23 -0000

On Mon, 2 Jun 2014, Ted Lemon wrote:

> 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

I'd say at least for some streaming service, the state of the art now is 
to download smaller chunks, for instance a few seconds, at a time. From my 
understanding, they do this so they can switch data rates/resolution 
fairly quickly to adapt to network conditions. So a host that has multiple 
interfaces could potentially pull video data from multiple paths, and it 
could switch fairly quickly if it had the logic needed. This is one reason 
why I find MIF very interesting going forward, it removes the need for 
"mobility" for some devices, because if they could switch over their 
application streams within a few seconds after being told to do so for 
instance by a mobile network, there would be a lot less need for tunneling 
in order to provide mobility.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

v2.23.0 | Report a Bug | By Email