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

Christoph Paasch <cpaasch@apple.com> Sun, 13 November 2016 07:31 UTC

Return-Path: <cpaasch@apple.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 A39831296C6 for <multipathtcp@ietfa.amsl.com>; Sat, 12 Nov 2016 23:31:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.799
X-Spam-Level:
X-Spam-Status: No, score=-5.799 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_H2=-0.001, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
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 6ULTZvx47rdj for <multipathtcp@ietfa.amsl.com>; Sat, 12 Nov 2016 23:31:37 -0800 (PST)
Received: from mail-in2.apple.com (mail-out2.apple.com [17.151.62.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16BB212962C for <multipathtcp@ietf.org>; Sat, 12 Nov 2016 23:31:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1479022296; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-transfer-encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=V/KjLd9nK2u/+vEFqsvWX9ro0eu6yootJns+XMgjtGI=; b=p9rjj8g03B7cz+cTwAkzrXHrGqUR85IFyjdEx88LchYdfzEeWRIFTFPgEymdBVzu lekwU4+61RSC3pbeG760Z5tq2+gOZSth7Rgn0/jHUNgwgLLdPqGeG/KAlqdUQRiB PVJINHJlaiiykWYrarrH7P9hqpgLg2x88UPR9Nn+5nWpCkxL9cXdaKkJ+gxIup6p Jc2rT9bnCx65YrMJzJOs3hY6u6pWIInEo8UoX3v/WB0wLp8HuV4wcYpNY08dSzw6 BKhQiEPRFzb3KgUFraAd7lgPPIXYfI/AA2puvvd7EC7JzEopCeff0i5gKoZf66JY RTqs0ARjyswC05ev7m8jRg==;
Received: from relay6.apple.com (relay6.apple.com [17.128.113.90]) by mail-in2.apple.com (Apple Secure Mail Relay) with SMTP id 64.DB.09085.8D618285; Sat, 12 Nov 2016 23:31:36 -0800 (PST)
X-AuditID: 11973e11-0d5e19a00000237d-50-582816d8c406
Received: from chive.apple.com (chive.apple.com [17.128.115.15]) by relay6.apple.com (Apple SCV relay) with SMTP id 5E.FC.23613.8D618285; Sat, 12 Nov 2016 23:31:36 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-disposition: inline
Content-type: text/plain; charset=utf-8
Received: from localhost ([17.150.210.10]) by chive.apple.com (Oracle Communications Messaging Server 8.0.1.1.0 64bit (built Jun 15 2016)) with ESMTPSA id <0OGK00IJXKWOV560@chive.apple.com>; Sat, 12 Nov 2016 23:31:36 -0800 (PST)
Sender: cpaasch@apple.com
Date: Sat, 12 Nov 2016 23:31:36 -0800
From: Christoph Paasch <cpaasch@apple.com>
To: philip.eardley@bt.com
Message-id: <20161113073136.GF4269@Chimay.local>
References: <0a0d2a248fac4616ac795c579d996be8@rew09926dag03b.domain1.systemhost.net>
In-reply-to: <0a0d2a248fac4616ac795c579d996be8@rew09926dag03b.domain1.systemhost.net>
User-Agent: Mutt/1.7.1 (2016-10-04)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrILMWRmVeSWpSXmKPExsUi2FAYpXtDTCPC4OpbS4vPq6+zWSxbu4LR gcmj7ctkJo8lS34yBTBFcdmkpOZklqUW6dslcGV8OrqEteCKakX3l3amBsZO+S5GTg4JAROJ txs+s3UxcnEICexllHi+ch8bTGL39AVMEImNjBJtB/4ygSR4BQQlfky+x9LFyMHBLCAvceRS NkiYWUBa4tHfGewQYXWJKVNyIVpfMUr839gGNlNYQFKi+84dZhCbRUBVYlXjAhYQm01AS+Lt 7XZWEFsEqGbF9lVsEDOB7L+fWCF67SWmbW5igTjBQOLHhGawc4QEwiSOXdzHDmJzCoRLPPq+ H6xXVEBZ4u9hkDO5gH45wibRePYwywRGkVlIXpiF8MIsJC/MQnhhASPLKkah3MTMHN3MPCO9 xIKCnFS95PzcTYygOJhuJ7iD8fgqq0OMAhyMSjy8HJnqEUKsiWXFlbmHGKU5WJTEecO91CKE BNITS1KzU1MLUovii0pzUosPMTJxcEo1ME42nZ51aKP+8dXLHqQcmmvq8SNC5n7/C+tbT2pb G4MXO85xm2H87fqFWFbt5dKub7eUG/r/+vTnhoHqRpsJYmJs5zzWcXR6tGnu7538nuerd8fK 5f4vV4aGsU19wBxgNW3PCWP3I+rtCtPfLJvgLacqd6C6b+OKY0q3zt73OW+YbVe795S/jqES S3FGoqEWc1FxIgC+rs3hZAIAAA==
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBIsWRmVeSWpSXmKPExsUi2FDMr3tDTCPC4OEZI4vPq6+zWSxbu4LR gcmj7ctkJo8lS34yBTBFcdmkpOZklqUW6dslcGV8OrqEteCKakX3l3amBsZO+S5GTg4JAROJ 3dMXMEHYYhIX7q1n62Lk4hAS2Mgo0XbgL1iCV0BQ4sfkeyxdjBwczALyEkcuZYOEmQWkJR79 ncEOEVaXmDIlF6L1FaPE/41tbCA1wgKSEt137jCD2CwCqhKrGhewgNhsAloSb2+3s4LYIkA1 K7avYoOYCWT//cQK0WsvMW1zEwvECQYSPyY0g50jJBAmceziPnYQm1MgXOLR9/1gvaICyhJ/ D99jmcAoNAvJ1bMQrp6F5OpZCFcvYGRZxShQlJqTWGmml1hQkJOql5yfu4kRHM6FUTsYG5Zb HWIU4GBU4uHdkKYeIcSaWFZcmXuIUYKDWUmEt1tYI0KINyWxsiq1KD++qDQntfgQYzLQuxOZ pUST84GxllcSb2hiYmBibGxmbGxuYk6asJI477UO+QghgfTEktTs1NSC1CKYLUwcnFINjElO O3b8+ClRcskiyeXSttXmEa6+T8Mr9tZdmv8p8p7pCxvFpwwZLbGvGo7O5kqZfPdnt6uuX9Or O432uXPmK+65G7170ykj5c3vvbfozNDPWv5KR7hNOk3zZO/tR+6sd+7sffLRYv/iyPKG35EN Wz0l9d6cX/NMNoeR+/+vfnnhws8/t39P26LEUpyRaKjFXFScCAA+/K7wqwIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/yKV_YvAlxii8nRs9_7ppoGHjS4I>
Cc: multipathtcp@ietf.org
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: Sun, 13 Nov 2016 07:31:38 -0000

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.


Christoph

> Thanks
> Phil & Yoshi
> 
> From: cpaasch@apple.com [mailto:cpaasch@apple.com]
> Sent: 31 July 2016 20:37
> To: Eardley,PL,Philip,TUB8 R <philip.eardley@bt.com>
> Cc: MultiPath TCP - IETF WG <multipathtcp@ietf.org>
> Subject: Re: [multipathtcp] potential new work item on MPTCP API
> 
> 
> On Jul 26, 2016, at 7:35 AM, philip.eardley@bt.com<mailto:philip.eardley@bt.com> wrote:
> 
> Christoph,
> https://tools.ietf.org/html/rfc6897#section-5.3 is “Sockets Interface Extensions by the Basic MPTCP API”
> (also https://tools.ietf.org/html/rfc6897#appendix-A “Appendix A. Requirements on a Future Advanced MPTCP API”)
> 
> Ok, I see. Fair enough. Extension to RFC6897 seems fine to me then.
> 
> 
> Cheers,
> Christoph
> 
> 
> phil
> 
> From: cpaasch@apple.com<mailto:cpaasch@apple.com> [mailto:cpaasch@apple.com]
> Sent: 22 July 2016 09:48
> To: Eardley,PL,Philip,TUB8 R <philip.eardley@bt.com<mailto:philip.eardley@bt.com>>
> Cc: MultiPath TCP - IETF WG <multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>>
> Subject: Re: [multipathtcp] potential new work item on MPTCP API
> 
> Hello,
> 
> On Jul 21, 2016, at 5:43 PM, philip.eardley@bt.com<mailto:philip.eardley@bt.com> wrote:
> Yesterday Olivier presented about his & Benjamin’s recent work on MPTCP socket api. We didn’t have much discussion whether to add this to the charter. One comment was that any work should build on /reference RFC6897.
> https://www.ietf.org/proceedings/96/slides/slides-96-mptcp-4.pdf
> Please can you comment whether you see this as a useful work item, or you think it shouldn’t be worked on, or how it should be adapted to something you think the WG should work on.
> 
> yes, I think it is a very useful work item and am willing to contribute to this work.
> 
> I'm not sure whether this can be seen as an update to 6897. I'm under the impression that 6897 takes a different approach, giving users a high-level overview of how using MPTCP might look like to an application that is talking to a TCP-socket (which happens to end up using MPTCP).
> 
> Olivier's work seems to rather make MPTCP entirely explicit to the application. So, I think both works take a different approach.
> 
> 
> 
> To help prompt the discussion, here’s a very first version of some possible charter text
> 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.
> 
> RFC6897 was Informational – would this new Milestone be Informational or Experimental?
> 
> I think it should be Informational.
> 
> 
> Christoph
> 
> 
> 
> 
> Thanks
> phil
> 
> Philip Eardley
> Research and Innovation
> This email contains BT information, which may be privileged or confidential. It's meant only for the individual(s) or entity named above. If you're not the intended recipient, note that disclosing, copying, distributing or using this information is prohibited. If you've received this email in error, please let me know immediately on the email address above. Thank you.
> We monitor our email system, and may record your emails.
> British Telecommunications plc
> Registered office: 81 Newgate Street London EC1A 7AJ
> Registered in England no: 1800000
> 
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp
> 

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