Re: [multipathtcp] Closing the MPTCP working group

philip.eardley@bt.com Thu, 19 March 2020 15:09 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 9FD053A0363 for <multipathtcp@ietfa.amsl.com>; Thu, 19 Mar 2020 08:09:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, 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 0MQECfogep6A for <multipathtcp@ietfa.amsl.com>; Thu, 19 Mar 2020 08:09:30 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [213.121.35.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC4653A0366 for <multipathtcp@ietf.org>; Thu, 19 Mar 2020 08:09:29 -0700 (PDT)
Received: from tpw09926dag06h.domain1.systemhost.net (10.9.202.33) by BWP09926079.bt.com (10.36.82.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Thu, 19 Mar 2020 15:09:26 +0000
Received: from tpw09926dag09h.domain1.systemhost.net (10.9.202.48) by tpw09926dag06h.domain1.systemhost.net (10.9.202.33) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 19 Mar 2020 15:09:27 +0000
Received: from RDW083A009ED65.bt.com (10.187.98.35) by tpw09926dag09h.domain1.systemhost.net (10.9.202.48) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Thu, 19 Mar 2020 15:09:27 +0000
Received: from GBR01-CWL-obe.outbound.protection.outlook.com (104.47.20.53) by smtpe1.intersmtp.com (62.239.224.236) with Microsoft SMTP Server (TLS) id 14.3.439.0; Thu, 19 Mar 2020 15:03:03 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=mJ7TxVWVgA7BLMoKrLiTZ7xAQjXMdjKncQDTg8FfhSZOSwVnTuzlTNpLQCId00AMuk7mHjXgQ1BAXeXW0UtvLsjixSc8RIzhiILMJXdstSbb7g/FZQPdrGAFhflH6IqjFMDMU0V2yw5s7QIDV++0C5oBRf3Nkt8LpoBpVME1IX8VfKQZHujp3kz982bsjBnIAB/kV4X4apSFvbKe8MbIm6za2NMpyNJl2r9Qkno7IfIpaQr+pvh9lT5ofsQO5CwStiDFsdFLe0lsGiA4Ffbl2WkjvgXS00ZDKFW+sIsjuUx7IsJagdYEaazfu+btAUDv5u4DwfMCPkxnS8q5Wne7yw==
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=V4Jes3fRilJksdNxH2qp2vd9OKqaJ38FHlvlwhxJN9I=; b=JTjPkp/D5XPhxJBUDLhpQz6bIgf5Z3XVz9Sk9FKgTEr0nVS+ahZiixhZejWIlmrDiKQ/0WPbaguPqJvQnWIocQ4hetx4lh8FsOPMa/XQ/iyIfsOonICjr7NIi3dfZzOrKEVzEb/1QfLyyBRn6l6uyoILK4kf2krj40ascwD+saVx3gBWXDuSKR1P1ZDYSTBXUbnnPpklqd2D0Hjmtf5fsNIlbeG/+FdJiZFkJaWnb8doKm+5U/VIbkCdpG0P1hQPklDArWKRU5i6/YeFme42UntY8oSl0sG4cujxX+8CkL6yxoBah1tBeUYiRZSDkycjGfaySIpK9sUZr0o8wTebOQ==
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=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=V4Jes3fRilJksdNxH2qp2vd9OKqaJ38FHlvlwhxJN9I=; b=CKKx5+F0Q/PHtD0LGnePpOoc1SwWm/pzJBuTFS9i0udxh5uaPuKCiWZA/X5t2Qzyv3+A/vRIAr1ZUhPS9hvKMdUYxXBTuWq/PMQY4ptlOWZvBESsIHWsdiQefkRNBTHCAq5JRFaRYOgcgXSryPR2ezg05iET2FeR7Xqcet+wUUg=
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM (20.179.128.78) by LNXP123MB2057.GBRP123.PROD.OUTLOOK.COM (20.179.131.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2835.18; Thu, 19 Mar 2020 15:09:25 +0000
Received: from LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM ([fe80::75a8:9aa3:70e2:3a1c]) by LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM ([fe80::75a8:9aa3:70e2:3a1c%7]) with mapi id 15.20.2814.025; Thu, 19 Mar 2020 15:09:25 +0000
From: <philip.eardley@bt.com>
To: <nsd.ietf@gmail.com>, <multipathtcp@ietf.org>, <ietf@kuehlewind.net>
Thread-Topic: [multipathtcp] Closing the MPTCP working group
Thread-Index: AQHV/IuNzTo2xzBugEWHk5EbjmbqhKhN2ToAgAH664A=
Date: Thu, 19 Mar 2020 15:09:25 +0000
Message-ID: <LNXP123MB258714EDB1B86AF0E629EAECEBF40@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
References: <36EF244C-7490-481E-8D7F-E5D9E5075E41@kuehlewind.net> <CAAK044QtZ__A43MFiN=6Z4N+uyb=HSgcSQJe3caV=NPCpDL=9Q@mail.gmail.com>
In-Reply-To: <CAAK044QtZ__A43MFiN=6Z4N+uyb=HSgcSQJe3caV=NPCpDL=9Q@mail.gmail.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: [193.113.37.9]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 30187fa4-72fc-448e-5991-08d7cc178343
x-ms-traffictypediagnostic: LNXP123MB2057:
x-microsoft-antispam-prvs: <LNXP123MB205741ACA20C42AFAEBD0076EBF40@LNXP123MB2057.GBRP123.PROD.OUTLOOK.COM>
x-antispam-2: 1
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0347410860
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(346002)(376002)(396003)(366004)(136003)(199004)(76116006)(2906002)(33656002)(55016002)(8676002)(81156014)(66556008)(316002)(64756008)(52536014)(5660300002)(66446008)(110136005)(81166006)(8936002)(66946007)(478600001)(66476007)(86362001)(966005)(6506007)(7696005)(186003)(26005)(9686003)(53546011)(71200400001); DIR:OUT; SFP:1101; SCL:1; SRVR:LNXP123MB2057; H:LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1;
received-spf: None (protection.outlook.com: bt.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: R+nLzgYrb+1Co1ahxIRVsyzADhi1nJm0RqiOFrLmZz0baBr88VNGizcY02QA73T2qmjT/yq77G5RVd0lIqltoDbV1OMjODlQP1TW9geqY9OoBzmpwj1zpfSGiW56gYDUyScvLxI4Rulc4wYLd1WNFuWMKGiSPzj17/7RigaTTVcWmj1wiVc4547IwQrgomxnAkVtVjvXgbfGpax5fUL3rpvNv1Z2RQ9hs8YZNBLinsvyLsaymnm3reWATqZgyAOatxWori+xm81lGx1oYvErz7sd6zNAFKjrnUKjMqFRpx+Ul76EIz+tG0CZhVcFBH8+bz//5I7Ed4NNktcQLJ7rl67UmtjxdTQgmGMVZyS9I3EyZ+GAhz++dM0zRBcnuklBAqlSZclrpeHa6AtnhOpmSmM9avu7cr42DU0JChMpdBc7+GXz7iFX9Aerp5bpAPun4o6FrYToRta9dLU+HPETYfAa/6QOrZ3u5qYrv2zDDPtuUaEe+EZALGQ7eHmo6ZM4oWN9kczImnc7NBWska6qwA==
x-ms-exchange-antispam-messagedata: Qj8zowoHjY8sdLpLBXBONgU7hR7abNos4GwLGxiyER30lUgS7qigGbFzkj76BkRRPwzt9ckFeTD58mDzuBOnbb+g5ObwgRArgsWIWc1rIzTE6B6QiATbN6OLcHATCJgNdS8mun5MZIN021Nb1DxNzQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_LNXP123MB258714EDB1B86AF0E629EAECEBF40LNXP123MB2587GBRP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 30187fa4-72fc-448e-5991-08d7cc178343
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Mar 2020 15:09:25.3718 (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: TikKSLo8tHojZn2er8CzlicY3fn5n0TYqKsVxQeMpfh8UEXEfoayLuDbRztIoPMT2KpAdCuAxDvMX+2qZql7JQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LNXP123MB2057
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/KTKCFVQU9Yx2kXcQRIDecpqe6k8>
Subject: Re: [multipathtcp] Closing 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, 19 Mar 2020 15:09:33 -0000

All,

Just to echo what Mirja and Yoshi say – thank-you to everyone for all the hard work – the numerous people who’ve written the RFCs, commented on them, written the code, tested, bug fixed and maintained implementations, launched products, been part of the commercial roll-outs etc etc.

From a personal point of view, it has been a pleasure to be one of the chairs of the WG and play a very small part of something that’s been successful. I hope all the efforts continue to make it even more useful and re-apply the ideas to make multipath protocols even more widely applicable and successful.

Best wishes,

phil



From: multipathtcp <multipathtcp-bounces@ietf.org> On Behalf Of Yoshifumi Nishida
Sent: 18 March 2020 05:51
To: multipathtcp@ietf.org; Mirja Kuehlewind <ietf@kuehlewind.net>
Subject: Re: [multipathtcp] Closing the MPTCP working group

Hi Mirja, thanks for the announcement.

I really appreciate 11 years hard work of the people in the WG.
MPTCP now became a successful technology which has been adopted and used in various places.
Although the WG is closed, we can and should continue this work in a new venue as I believe MPTCP still has lots of room to extend so that it can be more efficient and sophisticated.

Thank you so much!!!
--
Yoshi

On Tue, Mar 17, 2020 at 11:40 AM Mirja Kuehlewind <ietf@kuehlewind.net<mailto:ietf@kuehlewind.net>> wrote:
Hello everybody,

Now that we have resolved the last remaining issue on draft-ietf-mptcp-rfc6824bis, it time to declare the work on this group as accomplished.

A huge thanks to everybody involved in this work, of course especially to the document editors and chairs but also everybody else who contributed to the outcome of this group but commenting and in discussions!

Given MPTCP is actually a quite successful protocol with usage cases that have driven large-scale deployment, I do understand that people, including me, are also maybe a bit sad to see this group closing, but I think it rather a sign of success and completion.

However, this is not meant to say that no future work on MPTCP can be done anymore, and tcpm was officially re-chartered yesterday to explicitly account that future work on MPTCP or extensions to MPTCP can be done in that group similar as other TCP maintenance work. See here for the new tcpm charter:

https://datatracker.ietf.org/group/tcpm/about/

Further the mailing list of this group will remain open, as a way to reach experts for advise or specific questions and MPTCP-specifc discussions.

Again, huge thanks and congrats for the good work!

Mirja