IETF Logo Mail Archive

Re: [multipathtcp] Multipath TCP Address advertisement 3/5 - Backup make after break

Alan Ford <alan.ford@gmail.com> Tue, 04 April 2017 22:10 UTC

Return-Path: <alan.ford@gmail.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33BAA129329 for <multipathtcp@ietfa.amsl.com>; Tue, 4 Apr 2017 15:10:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Nt9zDsZeh8lq for <multipathtcp@ietfa.amsl.com>; Tue, 4 Apr 2017 15:10:17 -0700 (PDT)
Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7B5A12778E for <multipathtcp@ietf.org>; Tue, 4 Apr 2017 15:10:16 -0700 (PDT)
Received: by mail-wr0-x235.google.com with SMTP id w11so222642646wrc.3 for <multipathtcp@ietf.org>; Tue, 04 Apr 2017 15:10:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=916koTbDNiTbdfpu8WNc1e4oA4BL+XDSuoS6gZcpSyA=; b=VOyeQgKx/IAetx9zeTr6mfdgu81NOOpoNndzIYgBBDfrsHh0CrI40dGtCpFYjxR6Q2 cSWjaehYz88fJlc1Dt+NxWGa0qplzDXd37hK7daVSZgr7ueJh6neKM73dRrm86QwTMK7 O8pQG0z2Yw6Y61AWXmQWXiVqMwUiwC6DNi1ddUDzkQTox4QxLQmmUKh0OR/ZxRC97FrS Kk6w2/pIaDga/M9gpyIweUJ1XnqC+0Eow2ekY0G+DbPEWcdAamvwI3Zf+9UBlDAHjJ7+ Nme9PDYmcOXMJjhMrqYS4CxD6qRITfDUkxPnsPTIHAOF9MU/vyKDEPPqo+4QaZ1MdYFi sgTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=916koTbDNiTbdfpu8WNc1e4oA4BL+XDSuoS6gZcpSyA=; b=H+ktL8pM6aOyZ6kjJb+q9Yzois1RRNbnSV1fAlc70FL34unQ1jGWVnNdWrf1PbrDgS FqnV/jHZ5rKJDv14W2Kyy/SiSWRWSbHb9py0+1i7RRHqdwUA1ytkr9d65EcGbMpu0upz ECUZlX4ZG03aWplD/DELm4A8B8vrwGAmuXqdkbNItB/MymyAoVlXmx5kMjdw0qf1yFb0 DcYiY4m6p6yrCdKzreOQ+ojOgTK6Le+BDpYtdQ3KNPQ36TaMHRoK4JBUyOlTp2LmKPXU N2EqQHdxJDUPkp7jYRchMocYvhHjoROdarFQxKarpQ7tqpaC1+pPOcN2dg3mqS+PCg+7 Hvgw==
X-Gm-Message-State: AFeK/H1o3nDaEScywSKLWBW2VRX8dL8o6exWExwyIwIzUqH3e5CqahW1sbV3n1mmK2XDSQ==
X-Received: by 10.223.138.200 with SMTP id z8mr23979528wrz.49.1491343815236; Tue, 04 Apr 2017 15:10:15 -0700 (PDT)
Received: from alans-mbp.lan ([83.216.156.174]) by smtp.gmail.com with ESMTPSA id 82sm23568263wmg.0.2017.04.04.15.10.14 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 04 Apr 2017 15:10:14 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_01EAB65A-F8FD-4C95-8CC6-1D9E127DD28F"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alan Ford <alan.ford@gmail.com>
In-Reply-To: <1412F543-0345-4C30-87DF-7E5F1DF54F5F@apple.com>
Date: Tue, 04 Apr 2017 23:10:14 +0100
Cc: Fabien Duchêne <fabien.duchene@uclouvain.be>, MultiPath TCP - IETF WG <multipathtcp@ietf.org>
Message-Id: <F106A5DF-2FD3-4E86-910E-5B2E9DBD08FB@gmail.com>
References: <57AB4BF2.7080405@uclouvain.be> <1412F543-0345-4C30-87DF-7E5F1DF54F5F@apple.com>
To: Christoph Paasch <cpaasch@apple.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/5-qvKyj7zCZG0lExAUfBW_AavOQ>
Subject: Re: [multipathtcp] Multipath TCP Address advertisement 3/5 - Backup make after break
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 22:10:19 -0000

Following up from discussion at IETF98… Does anyone else wish to voice support for this proposal?

> On 15 Aug 2016, at 22:03, Christoph Paasch <cpaasch@apple.com> wrote:
> 
>> 
>> On Aug 10, 2016, at 8:44 AM, Fabien Duchêne <fabien.duchene@uclouvain.be> wrote:
>> 
>> Hello,
>> 
>> As agreed in Berlin during IETF96, I'm sending a series of emails to
>> discuss the different contributions proposed in:
>> https://datatracker.ietf.org/doc/draft-duchene-mptcp-add-addr/
>> 
>> This is the part 3/5 : Backup make after break.
>> 
>> There are use cases where hosts would prefer to establish an additional
>> subflow only after the failure of the initial one.
>> This would correspond to a break-before-make scenario. Multipath TCP did
>> not select between break-before-make and make-before-break.
>> We propose to support this distinction by adding the "B" (for backup)
>> flag in the ADD_ADDR option.
>> When set, this flag would indicate that the announced address should
>> only be used to establish subflows if all the subflows established with
>> addresses without the B flag have failed.
> 
> +1 on this proposal!
> 
> 
> Christoph
> 
> 
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp <https://www.ietf.org/mailman/listinfo/multipathtcp>

v2.23.0 | Report a Bug | By Email