Re: [multipathtcp] Possible future items for mptcp WG
<Markus.Amend@telekom.de> Fri, 22 June 2018 14:01 UTC
Return-Path: <Markus.Amend@telekom.de>
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 CE66F130E64 for <multipathtcp@ietfa.amsl.com>; Fri, 22 Jun 2018 07:01:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level:
X-Spam-Status: No, score=-4.31 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, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 mUaLGYTcUxda for <multipathtcp@ietfa.amsl.com>; Fri, 22 Jun 2018 07:01:13 -0700 (PDT)
Received: from mailout34.telekom.de (MAILOUT34.telekom.de [194.25.225.146]) (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 5D9D7130E52 for <multipathtcp@ietf.org>; Fri, 22 Jun 2018 07:01:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1529676073; x=1561212073; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=mHdBcriRiLZensAEODtci92pQaSiRo0T+sfY+0z52Uc=; b=KjAscn0nD744W5ZigLqnimkyPwPCRJafDXRYUpgf5o87RzWp8074f2ub PlUICglJaL6AUarGbqL5H8O9wFJDTo84zLHNQUTzvMs4xrY77NEH+hv8Z ceWf0sam8ONYy+PttRFM/KtR//jrSUSjHsYNZTSYTrjP0WDw9PfvQLjWN oBIliWX2+dDqtbug1P3Abt58O9Fu0+17VrLAP2XVJiw+L5zyc/BC3FYsi oCAVO40VpPnOqBwpcx+TJxtMcy+c2HQKdKz4b/APk9TL3l2HYJtsRbmGS pVR7i9C4h3wzzyFQYROOGfDFVbuA9MvWPnx6PmLj9wGLZ8ENEdOhjnYM5 Q==;
Received: from qdezc2.de.t-internal.com ([10.171.255.37]) by MAILOUT31.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Jun 2018 16:01:11 +0200
X-IronPort-AV: E=Sophos;i="5.48,405,1517871600"; d="scan'208";a="832879286"
Received: from he105685.emea1.cds.t-internal.com ([10.169.119.47]) by qde0ps.de.t-internal.com with ESMTP/TLS/AES256-SHA; 22 Jun 2018 16:01:11 +0200
Received: from HE105686.EMEA1.cds.t-internal.com (10.169.119.48) by HE105685.emea1.cds.t-internal.com (10.169.119.47) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Fri, 22 Jun 2018 16:01:10 +0200
Received: from HE105686.EMEA1.cds.t-internal.com ([fe80::a951:f05b:3de5:32d9]) by HE105686.emea1.cds.t-internal.com ([fe80::a951:f05b:3de5:32d9%26]) with mapi id 15.00.1367.000; Fri, 22 Jun 2018 16:01:10 +0200
From: Markus.Amend@telekom.de
To: multipathtcp@ietf.org
Thread-Topic: Possible future items for mptcp WG
Thread-Index: AdQKMNmqpYIk5DurSQewXRqRqgFpDQ==
Date: Fri, 22 Jun 2018 14:01:10 +0000
Message-ID: <c086f8cdebba45588d8ecfa3f389bd08@HE105686.emea1.cds.t-internal.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.17.19]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/p5X2bcxCaZ4Lq9gLyFhCH7n_9vg>
Subject: Re: [multipathtcp] Possible future items for mptcp WG
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.26
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: Fri, 22 Jun 2018 14:01:18 -0000
Hi Yoshi & Phil, I still follow the mentioned feature extension 2a) robust initial setup. Maybe in late autumn, I want to publish an implementation inspired by https://www.ietf.org/mail-archive/web/multipathtcp/current/msg03474.html. As soon as this one is available, this might be a base for further discussions. Btw., I'm available @IETF 102 onsite. BR Markus > ---------------------------------------------------------------------- > > Date: Thu, 14 Jun 2018 00:16:40 -0700 > From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp> > To: multipathtcp <multipathtcp@ietf.org> > Subject: [multipathtcp] Possible future items for mptcp WG > Message-ID: > <CAO249ycbh_rL+i310=UtVyE39=Yk+OSRWfcj1UyF=74VZwC8vw@mai > l.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hello everyone, > > Phil and I have been discussing the next step for the WG. > After we finish 6824bis, we ?on't have active WG items as the proxy work will > be discussed at tcpm WG. > One suggestion might be to close the WG or to put it in dormant state, > however, we are thinking there still might be some more working items as > we've seen interesting presentations for new ideas, experiment results and > so on at the meetings and on the ML. > > Below is the list of potential working items from the chairs' point of view. > Please let us know if you think some of them are important items for the WG > (and your willingness to contribute if possible) or there are some more items, > or this is not something we should work on, etc. > > Also, if you have some opinions on the status of the WG or suggestions to > the chairs, please let us hear! > > We appreciate your feedback > > Thanks, > -- > Yoshi & Phil > > > > > 1: API extensions (This is already in our charter) > draft-hesmans-mptcp-socket > draft-samar-mptcp-socketapi > > 2: Feature extensions > a) robust initial setup > proposed by Markus, also Kien presented a similar idea > > b) fast subflow setup > proposed by Quentin > > c) security enhancement > 1) TLS > draft-bonaventure-mptcp-tls-00 > draft-paasch-mptcp-tls-authentication-00 > > 2) Utilize proposals from tcpinc? > > 3) Elliptic Curve Cryptography > draft-kim-mptcp-semptcp-00 > > d) Solutions for operational issues > 1) how to handle nat64 issue proposed by Quentin > 2) how to handle load balancer proposed by Fabien, Christoph, Costin > > 3: Congestion Control (This topic itself should probably be discussed at > ICCRG. But, it may trigger some updates of the protocol or APIs later) > a) OLIA > draft-khalili-mptcp-congestion-control-05 > > b) mptcp + BBR?
- Re: [multipathtcp] Possible future items for mptc… Markus.Amend
- Re: [multipathtcp] Possible future items for mptc… Xavier de Foy
- Re: [multipathtcp] Possible future items for mptc… Yoshifumi Nishida
- Re: [multipathtcp] Possible future items for mptc… Xavier de Foy
- Re: [multipathtcp] Possible future items for mptc… Yoshifumi Nishida
- Re: [multipathtcp] Possible future items for mptc… Yoshifumi Nishida
- Re: [multipathtcp] Possible future items for mptc… Xavier de Foy
- Re: [multipathtcp] Possible future items for mptc… Olivier Bonaventure
- [multipathtcp] Possible future items for mptcp WG Yoshifumi Nishida
- [multipathtcp] 答复: Possible future items for mptc… Kangjiao