Re: [multipathtcp] Socket API for MPTCP

Olivier Bonaventure <> Thu, 14 July 2016 12:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B40F512D78C for <>; Thu, 14 Jul 2016 05:00:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ahBMesOflz5Z for <>; Thu, 14 Jul 2016 05:00:53 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9E82612D77B for <>; Thu, 14 Jul 2016 05:00:53 -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: by (Postfix) with ESMTPSA id D854867DE70; Thu, 14 Jul 2016 14:00:45 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.9.2 D854867DE70
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=selucl; t=1468497646; bh=iD7qaedWTrEdXlwDEyZ9IOj3WcOXtTSoUslMf1I0NdY=; h=Reply-To:Subject:References:To:Cc:From:Date:In-Reply-To; b=Q3Ct+3AX5NZpuSrV1/+PwSGDHASEE8osvyQN4x06+Vaud5nNlZqycmkW3ogOuIEPU wlFB4go6yHWvwGXwGwTOOvLa5/hYFCu201Fv91tAxucXC1xoMCASMFllpFrq5jhWco CZM2ISxsGtHEEYgvVX8YKk3j72XAJNHdujoDvb9c=
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.99 at smtp-1
References: <> <> <> <>
To: Rui Paulo <>
From: Olivier Bonaventure <>
Message-ID: <>
Date: Thu, 14 Jul 2016 14:00:46 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Sgsi-Spamcheck: SASL authenticated,
X-SGSI-MailScanner-ID: D854867DE70.A4934
X-SGSI-MailScanner: Found to be clean
X-SGSI-Spam-Status: No
Archived-At: <>
Cc: multipathtcp <>, "<>" <>
Subject: Re: [multipathtcp] Socket API for MPTCP
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-path extensions for TCP <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 14 Jul 2016 12:00:56 -0000


> On Jul 10, 2016, at 05:18, Olivier Bonaventure <> wrote:
>> We will then look at select. These notifications will be documented in the next version of the draft.
> Does it make sense to talk about kqueue-style notifications in the draft?  Some operating systems have notification mechanisms that can be extended to support MPTCP events in a way that’s cleaner than select().

My suggestion in Berlin will be to ask to include an API item in the 
charter and suggest the socket draft as a starting point. I hope that 
other implementors will participate to the draft so that we can have an 
API that it common to all MPTCP implementations. select is one option 
for the notifications, recvmsg/sendmsg, kqueues, etc. Ideally, we should 
document the available API and ask feedback from developpers to improve