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

<philip.eardley@bt.com> Mon, 14 November 2016 05:10 UTC

Return-Path: <philip.eardley@bt.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 B1E6B129694 for <multipathtcp@ietfa.amsl.com>; Sun, 13 Nov 2016 21:10:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.118
X-Spam-Level:
X-Spam-Status: No, score=-4.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 wURRAgSW7uQ2 for <multipathtcp@ietfa.amsl.com>; Sun, 13 Nov 2016 21:09:59 -0800 (PST)
Received: from smtpb1.bt.com (smtpb1.bt.com [62.7.242.138]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E88E91295C2 for <multipathtcp@ietf.org>; Sun, 13 Nov 2016 21:09:58 -0800 (PST)
Received: from EVHUB04-UKBR.domain1.systemhost.net (193.113.108.172) by EVMED04-UKBR.bt.com (10.216.161.34) with Microsoft SMTP Server (TLS) id 14.3.195.1; Mon, 14 Nov 2016 05:09:54 +0000
Received: from rew09926dag03d.domain1.systemhost.net (10.55.202.30) by EVHUB04-UKBR.domain1.systemhost.net (193.113.108.172) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 14 Nov 2016 05:09:56 +0000
Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by rew09926dag03d.domain1.systemhost.net (10.55.202.30) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 14 Nov 2016 05:09:55 +0000
Received: from rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e]) by rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e%12]) with mapi id 15.00.1210.000; Mon, 14 Nov 2016 05:09:55 +0000
From: <philip.eardley@bt.com>
To: <fabien.duchene@uclouvain.be>, <multipathtcp@ietf.org>
Thread-Topic: [multipathtcp] Adding a new work item on MPTCP API
Thread-Index: AdI6cw/RKIQBu3r4R/i6P9GRF0bXlgDDOcYAACbX2AAABn46rg==
Date: Mon, 14 Nov 2016 05:09:55 +0000
Message-ID: <1479100195639.46263@bt.com>
References: <0a0d2a248fac4616ac795c579d996be8@rew09926dag03b.domain1.systemhost.net> <20161113073136.GF4269@Chimay.local>, <495a3fd8-e83d-29f6-5612-bea5222a0d38@uclouvain.be>
In-Reply-To: <495a3fd8-e83d-29f6-5612-bea5222a0d38@uclouvain.be>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.187.101.36]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/QzFToxIOFzoibkM7GsEimJ4QNf0>
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 05:10:02 -0000

re socket operations.
this is the term used in https://tools.ietf.org/html/rfc6897#section-5.3
happy to use whatever term is clearest - operations, options or sometihing else!
phil
________________________________________
From: multipathtcp <multipathtcp-bounces@ietf.org> on behalf of Fabien Duchêne <fabien.duchene@uclouvain.be>
Sent: 14 November 2016 02:03
To: multipathtcp@ietf.org
Subject: Re: [multipathtcp] Adding a new work item on MPTCP API

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


_______________________________________________
multipathtcp mailing list
multipathtcp@ietf.org
https://www.ietf.org/mailman/listinfo/multipathtcp