[multipathtcp] Socket API for MPTCP

Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be> Fri, 08 July 2016 15:56 UTC

Return-Path: <olivier.bonaventure@uclouvain.be>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6034712D5CE for <multipathtcp@ietfa.amsl.com>; Fri, 8 Jul 2016 08:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id aFzeNJ5ZOWot for <multipathtcp@ietfa.amsl.com>; Fri, 8 Jul 2016 08:56:52 -0700 (PDT)
Received: from smtp3.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 649D812D1B9 for <multipathtcp@ietf.org>; Fri, 8 Jul 2016 08:56:52 -0700 (PDT)
Received: from mbpobo.local (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: obonaventure@smtp3.sgsi.ucl.ac.be) by smtp3.sgsi.ucl.ac.be (Postfix) with ESMTPSA id 6770567DC7E; Fri, 8 Jul 2016 17:56:45 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.9.2 smtp3.sgsi.ucl.ac.be 6770567DC7E
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1467993405; bh=ANrLfPYdp1pSFsLtpqOYUWtqvaAc6euEtYNHtsoLBHM=; h=Reply-To:To:From:Subject:Date; b=wRPE7CU3wwByvunWOgJL0M+mRTI2+sIizS+pzbo2IroFwvDrY298kk4QdGg68KeWP 18jPjtebHkOCPpRwQWKrjjQSJAo9ks8n6vR39PW6bNRnvpwD+Eo3acLQedbR6t3XhU aujz0oMGJWyjys4sm1K1aZ5UGvUKxc/dmXXxSbhg=
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.99 at smtp-3
To: multipathtcp <multipathtcp@ietf.org>, "<mptcp-dev@listes.uclouvain.be>" <mptcp-dev@listes.uclouvain.be>
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Message-ID: <13734f09-4c78-06eb-7201-8f125097a5e8@uclouvain.be>
Date: Fri, 8 Jul 2016 17:56:45 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Sgsi-Spamcheck: SASL authenticated,
X-SGSI-MailScanner-ID: 6770567DC7E.A3644
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: olivier.bonaventure@uclouvain.be
X-SGSI-Spam-Status: No
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/4_WwRCpINZwwoamwHj1t-RnaiqQ>
Subject: [multipathtcp] Socket API for MPTCP
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Olivier.Bonaventure@uclouvain.be
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: Fri, 08 Jul 2016 15:56:54 -0000


During the last years, we have received on a regular basis questions 
from users of Multipath TCP on how they could control the utilisation of 
the subflows. In the Linux implementation, the default solution was to 
tune the path manager, but this is kernel code and few users actually 
managed to change this path manager.

Benjamin Hesmans has spent some time to think about simple extensions to 
the socket API to allow applications to control the underlying Multipath 
TCP stack. He has implemented his ideas and has running code. A first 
draft describing his API has been submitted to the IETF :

Title:		A socket API to control Multipath TCP

    This document proposes an enhanced socket API to allow applications
    to control the operation of a Multipath TCP stack.

A related paper will also appear at the ANR workshop :


We have requested a slot to present in Berlin. We expect that agreeing 
on a common socket API exposed by Multipath TCP implementations would 
help its end-to-end deployment.

Olivier and Benjamin