Re: [multipathtcp] Adding a new work item on MPTCP API

Fabien Duchêne <fabien.duchene@uclouvain.be> Mon, 14 November 2016 02:04 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 C9CC81295F0 for <multipathtcp@ietfa.amsl.com>; Sun, 13 Nov 2016 18:04:00 -0800 (PST)
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 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 V9Zt-OwTSUf9 for <multipathtcp@ietfa.amsl.com>; Sun, 13 Nov 2016 18:03:59 -0800 (PST)
Received: from smtp3.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 0CEE3127058 for <multipathtcp@ietf.org>; Sun, 13 Nov 2016 18:03:59 -0800 (PST)
Received: from [31.133.134.81] (dhcp-8651.meeting.ietf.org [31.133.134.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: duchenef@smtp3.sgsi.ucl.ac.be) by smtp3.sgsi.ucl.ac.be (Postfix) with ESMTPSA id 58BA267DA44 for <multipathtcp@ietf.org>; Mon, 14 Nov 2016 03:03:51 +0100 (CET)
DKIM-Filter: OpenDKIM Filter v2.9.2 smtp3.sgsi.ucl.ac.be 58BA267DA44
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1479089031; bh=E9XQr1KjjH+4z34NKx8ORYrynx4aeH8WFSkHe/Ode0M=; h=Subject:To:References:From:Date:In-Reply-To; b=m053D0ApuLRc+SHG0eox7ZcuU5litvmzA7EsYetsLXfBZ1sNb6KEFVNQTbsKByFTj HOlrjC+pBD1Mg+UHQ5mDteY2izgEUaWMB94dGM4ewP21Bt6M3HyDOIfUS7Xjrvgg2n Yo8Eboxlp4tZwdFpdona5NZb2EVrKA8/CrgYGAO4=
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.99.2 at smtp-3
To: multipathtcp@ietf.org
References: <0a0d2a248fac4616ac795c579d996be8@rew09926dag03b.domain1.systemhost.net> <20161113073136.GF4269@Chimay.local>
From: =?UTF-8?Q?Fabien_Duch=c3=aane?= <fabien.duchene@uclouvain.be>
Message-ID: <495a3fd8-e83d-29f6-5612-bea5222a0d38@uclouvain.be>
Date: Mon, 14 Nov 2016 03:03:48 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.2.0
MIME-Version: 1.0
In-Reply-To: <20161113073136.GF4269@Chimay.local>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Sgsi-Spamcheck: SASL authenticated,
X-SGSI-Information:
X-SGSI-MailScanner-ID: 58BA267DA44.A1421
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/quu5Fd1IqO7JbdWk4NI0WO9qHt4>
Subject: Re: [multipathtcp] Adding a new work item on MPTCP API
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: Mon, 14 Nov 2016 02:04:01 -0000

Hello,


On 11/13/2016 08:31 AM, Christoph Paasch wrote:
> Hello,
>
> On 09/11/16 - 10:21:42, philip.eardley@bt.com wrote:
>> Following the earlier discussion, there is support to add a charter item as follows:
>> <<RFC6897 defined an optional, basic application interface for MPTCP-aware applications, including a set of socket operations. Now there is more experience of how MPTCP is being used, the WG will re-visit this work, and consider adding more advanced socket operations. The document will be Informational.>>
>> If you disagree with this being added, or suggest some mod to this item, please say.
> I support this work as well.
>
> But, I also agree with Mirja's comment that "socket operations" is not a
> well-defined term. I guess, what has been meant was "socket options" - the
> ones that are available in many operating systems.
>
> I think the API should not limit itself to a specific way on how to
> configure the stack (e.g., through socket-options, ioctl, netlink,...).
> But rather be agnostic as to the technical details on how the higher
> layer configures/controls the MPTCP-stack.
>

I support this work and I agree with Christoph and Mirja.
> Christoph
>

Cheers,

Fabien