Re: [multipathtcp] Closing the MPTCP working group

Yoshifumi Nishida <> Wed, 18 March 2020 05:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 12EC33A0840 for <>; Tue, 17 Mar 2020 22:50:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id VtpxAgVNZSEN for <>; Tue, 17 Mar 2020 22:50:54 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::e2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 574F43A083D for <>; Tue, 17 Mar 2020 22:50:54 -0700 (PDT)
Received: by with SMTP id t10so15677286vsp.1 for <>; Tue, 17 Mar 2020 22:50:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=pMF3tsph/QFb6WlNYqucamW2FeJVblv/78Azk4fLGig=; b=tdGjlVT5BMC1IUqMEKkEcEwQB6WQClOsCPocWpdN8Bys2W/YDGuIU0dDFCK2F9IFdy spf1Y7IEIBM+zRavtwf1w9BuInTegwin2AfPIK71oEwQeVBQKA18IMUjI+WfvpreCqLx xg21hOPDQFK3pXTpUILSblCvN6BKPEBPFgeAmJKTPHp7axu1qDYZBsIPoO5TIFveO0E2 lUk2qXohahtUSUQVhCs/6OdyWZeNgmEeOhZubAWzl0s8rAnpTzzR6TUqWNUVHO05NbiZ PMyrxenBhuxi/SsHvroPTh6YqXhfqtvSsHQrsjOJqwAcM2DDqRxRGnOOK7qHH8XX7xw0 D+tg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=pMF3tsph/QFb6WlNYqucamW2FeJVblv/78Azk4fLGig=; b=sx0l1V3kYRwSw9XAT11dEKZMbEK79T67oFHdnvoOwPGIRtD6idEsCW78+0H5B0IZQQ CXY9dl3l1lg2AQl9aZPsUJqVgPidkBtXjHKsJnMheymHc8kQxlFNClgyQzOSQ7c02dom KX+7yETzTfdAZK82GH0jk1O2bfCIlRuEK0kOvZdsj+Esjz7RKVQGArBf5fu8qzAXhiPc A4fGGihQtSZyBakIUP8uVN1goH9NJGoYxXusaDz8Oz1fyWL/dl8vPPUghjZPEJQ8/8em 0KyH2H5juCxavvBOlP7yleuj6MkaoLIUltFDGNBVk8r/ALgi6Wqf1xxyCyqOkBh6Lhz9 HFnA==
X-Gm-Message-State: ANhLgQ3XTkiLqgNvK1jZm0xxtsRtm0WNCsOnOpNnw4X/MOdDbgOwoJmJ zL6mTZ+FeUFR9ISteDZbukTybvt/c+ZkbElUURNFqTT7
X-Google-Smtp-Source: ADFU+vu3O4O0GdidIS+iUmPvtcabU+b/2uaqfmSgEZh6mT4B3KrQhCD88ZstFSrc8cJCkKA9K+fUvGAKi7QIvbMTymA=
X-Received: by 2002:a67:ec88:: with SMTP id h8mr1835180vsp.65.1584510652964; Tue, 17 Mar 2020 22:50:52 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Yoshifumi Nishida <>
Date: Tue, 17 Mar 2020 22:50:42 -0700
Message-ID: <>
To: "" <>, Mirja Kuehlewind <>
Content-Type: multipart/alternative; boundary="0000000000009ce3d805a11aa2ef"
Archived-At: <>
Subject: Re: [multipathtcp] Closing the MPTCP working group
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 18 Mar 2020 05:50:58 -0000

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!!!

On Tue, Mar 17, 2020 at 11:40 AM Mirja Kuehlewind <>

> 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:
> 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