[multipathtcp] Future of the MPTCP Working group

<philip.eardley@bt.com> Thu, 22 August 2019 08:25 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 929C1120236 for <multipathtcp@ietfa.amsl.com>; Thu, 22 Aug 2019 01:25:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bt.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 MuyQcM1RBY_c for <multipathtcp@ietfa.amsl.com>; Thu, 22 Aug 2019 01:25:00 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [213.121.35.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD39812022E for <multipathtcp@ietf.org>; Thu, 22 Aug 2019 01:24:56 -0700 (PDT)
Received: from tpw09926dag05f.domain1.systemhost.net (10.9.202.24) by BWP09926077.bt.com (10.36.82.108) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Thu, 22 Aug 2019 09:23:48 +0100
Received: from tpw09926dag06e.domain1.systemhost.net (10.9.202.21) by tpw09926dag05f.domain1.systemhost.net (10.9.202.24) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 22 Aug 2019 09:22:55 +0100
Received: from bwp09926081.bt.com (10.36.82.112) by tpw09926dag06e.domain1.systemhost.net (10.9.202.21) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Thu, 22 Aug 2019 09:22:55 +0100
Received: from GBR01-CWL-obe.outbound.protection.outlook.com (104.47.20.50) by smtpe1.intersmtp.com (10.36.82.112) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Thu, 22 Aug 2019 09:22:34 +0100
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OF/hE0isxCbKyOQ9C4bVC+YALfGlViBJe89TyRyrNYdZNY2tL53GldYl4GKU2tgQSmqLUOgPYT51PzrMlEuGXEmZCK/vr+2E2TClL97toe9CrUOBbddmH1G76Fvr9dR5dxRx5od/AzJBblV/A13EUMxjI0g+JioVx4rkIn5G20UzVdXI3S/r0j9Ew22Fz5aYzAsRDxm4JBfQrk13sQ11tW2hbvWlnRy16i014DpPZhMxBV3XNgVxJJFbdrXVm1Yj0fMk26OgTCPY6VjP0foKX4Zcug07LxSJ8OhggkBIqbM+yjGrtSqU6GzW0wBld2yWZOwmrwA5x8jWAc53l3xF5A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=MBBVhsmsmDX6Y6CXsF3OThh2pz5FBLidtwtpSQ85P1c=; b=SKPRryrS5C9Qw1qKCOw7sINVMC1G8khK1juYOL37/TzhBhLotgT9G1ehQLSBj3Gx4ULqLgUzbwpa/EuA782MwuUhA5qnLMyimRGO9e0FnTEyWOIJ083913V8v+cYM1cW+bfKmAPIVbjrV1Vhb8BVSD+svZIjH6pEDFpxs5b1ThsO5ECPgjiel7Kgr2LZOWG861sw3DkhVlps7Hnb6HxYQ+k4/6uaUIBaYmYkIl4WrSCSGQLa2XngFG7a3RJ1ouIMsN80CmMfpjBCVIpbM8ijbDMhhx7Z3h+25jW3EKUVtXUpIjyRh9fv6CphvxzfJkFi+EYkBcTWdHcCwvVAq62P5Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=bt.com; dmarc=pass action=none header.from=bt.com; dkim=pass header.d=bt.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bt.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=MBBVhsmsmDX6Y6CXsF3OThh2pz5FBLidtwtpSQ85P1c=; b=YMPljZUdJWNxz0vYqYbPtXdyYWtTqAcG9KpZHx2b5vLagCYmpGwJ/orO9/41Ts9oky5L+bzj+gamJqGP426PF/eQ7GP0bg4eDS3WbrL+BmMDmHyNuFvJihgcAYpInxXK+t4b6zGKtaXtNodS22RE/Qy3O+4WCp27Q+O1O46iC/0=
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM (20.179.128.78) by LNXP123MB2265.GBRP123.PROD.OUTLOOK.COM (20.179.130.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2178.18; Thu, 22 Aug 2019 08:22:52 +0000
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM ([fe80::4fc:dcd0:dba3:89d3]) by LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM ([fe80::4fc:dcd0:dba3:89d3%5]) with mapi id 15.20.2178.020; Thu, 22 Aug 2019 08:22:52 +0000
From: <philip.eardley@bt.com>
To: <multipathtcp@ietf.org>
Thread-Topic: Future of the MPTCP Working group
Thread-Index: AdVYwMTUoaoE3I9qT8ua7nd7dbGaZQ==
Date: Thu, 22 Aug 2019 08:22:52 +0000
Message-ID: <LNXP123MB25873DB1982E6BCAF7E356CDEBA50@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=philip.eardley@bt.com;
x-originating-ip: [217.33.61.67]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1ce58f1d-0294-4775-5f6e-08d726d9ecf8
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600166)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:LNXP123MB2265;
x-ms-traffictypediagnostic: LNXP123MB2265:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <LNXP123MB2265140636D4720916642B1CEBA50@LNXP123MB2265.GBRP123.PROD.OUTLOOK.COM>
x-antispam-2: 1
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01371B902F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(39860400002)(346002)(376002)(136003)(366004)(199004)(189003)(256004)(606006)(7696005)(33656002)(66066001)(86362001)(8936002)(8676002)(81166006)(81156014)(14454004)(99286004)(66446008)(64756008)(66556008)(66476007)(966005)(66946007)(71190400001)(6916009)(476003)(486006)(53936002)(76116006)(3846002)(316002)(186003)(52536014)(7736002)(478600001)(14444005)(74316002)(236005)(5660300002)(25786009)(9686003)(790700001)(6116002)(55016002)(54896002)(6306002)(71200400001)(102836004)(6436002)(2906002)(26005)(6506007); DIR:OUT; SFP:1101; SCL:1; SRVR:LNXP123MB2265; H:LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: bt.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: H7tCBAyf0IEoLIKkI0eqJy4bNDNpF80+4m3u+oQCVTNSR9fxWdzaWHc8OAWqioS8NIHWqLNjPXvNyCme1qaA1IAKXU6QjNiIohjMySlrZnAwvoGcDZJnWpZdWDcvNGaWZwnMoc+Ni6EJxuJkhGhbPZN5N3m8MwOgnVa/frixB/tD3AsIohLSGtOWStgYKZcpn/iZC4pVD6hRdk1Rf5j6QSSwOHU3uACZqU2ES8cTkS94BfyDv4kiDfLGr8f07XQq/VGGYfYHS4nHKznAc37ixlv8pNAho2Q2I+ey79+34PnfiYH5R2qEJv4OoELNbJU5L5MxRp4lovSWf1XXsxqNeTXrwRqljwAIipKNokTbbhVPiw8NAq4La++5PoP2Fy2zmBl04ZsBbP2+Q54SIi7LsbcCnqWwikNpLMyR1Ly03YM=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_LNXP123MB25873DB1982E6BCAF7E356CDEBA50LNXP123MB2587GBRP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 1ce58f1d-0294-4775-5f6e-08d726d9ecf8
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Aug 2019 08:22:52.1103 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a7f35688-9c00-4d5e-ba41-29f146377ab0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 7YnIiO6bSXKF+HPOyR87BYSlsBhm9TqaLx4Bhy7Tzh8AoU9uHLfQFMPGKha/769LxyYVBHPTmlbKEwKDMABtmg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LNXP123MB2265
X-NAI-Spam-Flag: NO
X-NAI-Spam-Level: **
X-NAI-Spam-Threshold: 5
X-NAI-Spam-Score: 2.1
X-NAI-Spam-Report: 5 Rules triggered * 2 -- TS_MSG_REP_30 * 0.1 -- THREAD_INDX_INVALD_VAL * 0 -- EDT_SDHA_ADR_FRG * 0 -- EDT_SDHA_DMN_FRG * 0 -- RV6617
X-NAI-Spam-Version: 2.2.0.9309 : core <6617> : inlines <7138> : streams <1830808> : uri <2887853>
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/fEpwrLjVj5tv3-HZMQRR0-ndTAA>
Subject: [multipathtcp] Future of the MPTCP Working group
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 22 Aug 2019 08:25:03 -0000

For people not in the WG meeting in Montreal, and also after a couple of private comments, we wanted to summarise our perspective about the future of the working group.
With the completion of the protocol bis, our (revised) charter is essentially complete. We've already published RFC 8041 (Use Cases and Operational Experience with Multipath TCP), as well as RFC 7430 (Analysis of Residual Threats and Possible Fixes for Multipath TCP (MPTCP)). The middlebox item turned into the 0-RTT Converters work in tcpm (which is in WG last call). Excellent work!
Having completed the charter, the options are to re-charter or close. Note that closing the WG can be considered the default option. Re-chartering is possible (subject to the usual approvals procedure), but needs an increase on the current energy levels, in particular we would need a few topics - on each of which a group of people want to contribute, in terms of design, implementation and review (as well as the usual consensus to do work). Note even if the WG is closed, at least some MPTCP work could continue - for instance, work that is a 'minor extension' of MPTCP, or its maintenance, could be done in TCPM (under its current charter).
As a data point, there are currently the following active individual drafts:

1.       Multipath TCP extension for Robust Session Establishment

2.       Initial-Path Selection for Connection Establishment in Multipath TCP

3.       Privacy threats and possible countermeasures for Multipath-TCP (MPTCP)

4.       TFO support for Multipath TCP

5.       5G Session Continuity Support in MPTCP

6.       Multipath TCP Inactivity Time Option

7.       Multipath TCP Subflow Rate Limit Option

8.       Extended Socket APIs to control subflow priority in Multipath TCP

9.       One Way Latency Considerations for MPTCP

10.   A Stochastic Optimal Scheduler for Multipath Transmission Control Protocol (MPTCP)
Also - again just as a data point - #3 has authors from multiple institutions, as do #8 & #9, whilst #1 & #2 look to be addressing a similar problem (I know the authors now plan to collaborate). In addition, we believe there are several people interested in a more secure version of MPTCP (and expired individual drafts such as draft-bonaventure-mptcp-tls). So these might be topics on which a group of people want to contribute, in terms of design, implementation and review. For efforts to generate extra energy and collaboration, please make sure they're visible to us and on the mailing list, well before the Singapore IETF.
On a related point, there was a discussion in tsvarea about "Where to do multipath work in the IETF?" https://datatracker.ietf.org/meeting/105/materials/minutes-105-tsvarea-00 which finished with Mirja saying "I think the community needs to propose something here, please work on that if you're interested and think you can scope it in a reasonable way."
Best wishes,
Phil and Yoshi