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

Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be> Wed, 04 June 2014 10:48 UTC

Return-Path: <olivier.bonaventure@uclouvain.be>
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 A28161A01B1 for <v6ops@ietfa.amsl.com>; Wed, 4 Jun 2014 03:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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 ypVpuUDmgZZ1 for <v6ops@ietfa.amsl.com>; Wed, 4 Jun 2014 03:48:25 -0700 (PDT)
Received: from smtp5.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be [130.104.5.67]) by ietfa.amsl.com (Postfix) with ESMTP id 7F25E1A0282 for <v6ops@ietf.org>; Wed, 4 Jun 2014 03:48:25 -0700 (PDT)
Received: from mbpobo.dhcp.info.ucl.ac.be (mbpobo.dhcp.info.ucl.ac.be [130.104.228.46]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: obonaventure@smtp5.sgsi.ucl.ac.be) by smtp5.sgsi.ucl.ac.be (Postfix) with ESMTPSA id F03DD19833D; Wed, 4 Jun 2014 12:48:12 +0200 (CEST)
X-DKIM: Sendmail DKIM Filter v2.8.3 smtp5.sgsi.ucl.ac.be F03DD19833D
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1401878893; bh=o4C6lmGjUTP+s7cxPc60mMiW4GRnfLxJ2TdSkWbLKbg=; h=Message-ID:Date:From:Reply-To:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=R3YzcUoiGZsHnKOF6tVPA5Q7rOrEQaIXurrkd7NEzRBdn73hG4vWpAMqKBrxDhwAR rZH83oaktDgyRhdPCCTC4DvxDCiBSarHHpKq4aEcxRYZD+18zPEh5vUefqp/y51baM DW+USVu0vWdbxnW0NO9phz0ytoZyTi/Jm3mW5OVM=
Message-ID: <538EF96E.8070300@uclouvain.be>
Date: Wed, 04 Jun 2014 12:48:14 +0200
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.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> <538D7A71.6070906@uclouvain.be> <538E2D2E.4020903@gmail.com> <CAPv4CP_S61spd-QWgrGiDo0i5cpeuz2WUAr8__s=AWPF-6-HDw@mail.gmail.com> <538E32D0.9050005@gmail.com> <CAPv4CP93=r-VRSgpbVjmy-gy6fuZ6GE_gFO5jwPxytX1htRpkw@mail.gmail.com>
In-Reply-To: <CAPv4CP93=r-VRSgpbVjmy-gy6fuZ6GE_gFO5jwPxytX1htRpkw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.97.7-exp at smtp-5.sipr-dc.ucl.ac.be
X-Virus-Status: Clean
X-Sgsi-Spamcheck: SASL authenticated,
X-SGSI-MailScanner-ID: F03DD19833D.A4C0C
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: olivier.bonaventure@uclouvain.be
X-SGSI-Spam-Status: No
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/YS3GGxyzT_LvCI7dmPJnkcbBMbA
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
Reply-To: Olivier.Bonaventure@uclouvain.be
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: Wed, 04 Jun 2014 10:48:27 -0000

Scott,

>> My point is that there are useful learnings in shim6 as well as in MPTCP
>> and SCTP. However, it will be very sad if we have to re-solve these
>> problems in every application suite rather than solving them once
>> in the stack.
>
> Got it. Agree completely. But looking at the momentum, I'm betting on
> higher layers. Content is driving the bus.

I'd prefer transport than application. The problem with solving 
multihoming or other issues at the application layer is that this is 
complex and requires a lot of networking expertise. Some app developpers
have this expertise, but they are the minority. We should not expect 
each app developper to have to deal with multihoming, the stack should 
solve the issue. This is the same problem as for reliability. We've 
placed reliability in the transport layer so that applications can built 
upon it. There are niche applications that want to reinvent reliable 
delivery, but this is not the best utilisation of scarce developper time...


Olivier

-- 
INL, ICTEAM, UCLouvain, Belgium, http://inl.info.ucl.ac.be