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

Fabien Duchêne <fabien.duchene@uclouvain.be> Wed, 10 August 2016 15:39 UTC

Return-Path: <fabien.duchene@uclouvain.be>
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 077BC12D5F7 for <multipathtcp@ietfa.amsl.com>; Wed, 10 Aug 2016 08:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level:
X-Spam-Status: No, score=-4.321 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=uclouvain.be
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 kKdUxKslb9Kp for <multipathtcp@ietfa.amsl.com>; Wed, 10 Aug 2016 08:39:24 -0700 (PDT)
Received: from smtp2.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be [130.104.5.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D94B512D5CC for <multipathtcp@ietf.org>; Wed, 10 Aug 2016 08:39:23 -0700 (PDT)
Received: from [130.104.228.52] (unknown [130.104.228.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: duchenef@smtp2.sgsi.ucl.ac.be) by smtp2.sgsi.ucl.ac.be (Postfix) with ESMTPSA id A97A667DA26 for <multipathtcp@ietf.org>; Wed, 10 Aug 2016 17:39:15 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.9.2 smtp2.sgsi.ucl.ac.be A97A667DA26
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1470843555; bh=mdETLHAVHBXBstFFA/uHNCM/fSB1VMPhHb9t5aKllLY=; h=To:From:Subject:Date; b=G7jELJOY01Y87kF5QjwJQXPoPD1Qs365csDHAMKw7WyOZdC/8ZPYYneo/1TQp8In7 mk1XWgw3pfGqcQ4DJIw7Qz5DGhpowyjLhwGxdQ7LKuGqfIG8GFxXC87XmlfswIuSJH 9Rfyhfm5ek7Pfo4XNXgAxhNO1EF14kQNW2sjfV4E=
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.99 at smtp-2
To: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
From: =?UTF-8?Q?Fabien_Duch=c3=aane?= <fabien.duchene@uclouvain.be>
Message-ID: <57AB4BF2.7080405@uclouvain.be>
Date: Wed, 10 Aug 2016 17:44:50 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Sgsi-Spamcheck: SASL authenticated,
X-SGSI-Information:
X-SGSI-MailScanner-ID: A97A667DA26.AF5F6
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: fabien.duchene@uclouvain.be
X-SGSI-Spam-Status: No
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/gbPwMfdlvlFIhi92uGyDX7mPSeI>
Subject: [multipathtcp] Multipath TCP Address advertisement 3/5 - Backup make after break
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 10 Aug 2016 15:39:26 -0000

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.

Cheers,

Fabien