Re: [multipathtcp] Possible future items for mptcp WG
Xavier de Foy <x.defoy.ietf@gmail.com> Wed, 20 June 2018 18:25 UTC
Return-Path: <x.defoy.ietf@gmail.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 BD73A130E02 for <multipathtcp@ietfa.amsl.com>; Wed, 20 Jun 2018 11:25:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 VABkoL16jOvb for <multipathtcp@ietfa.amsl.com>; Wed, 20 Jun 2018 11:25:19 -0700 (PDT)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29780130DFA for <multipathtcp@ietf.org>; Wed, 20 Jun 2018 11:25:19 -0700 (PDT)
Received: by mail-qt0-x22d.google.com with SMTP id q6-v6so498328qtn.7 for <multipathtcp@ietf.org>; Wed, 20 Jun 2018 11:25:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=EsMHVk++S7T40Osl4rGSV27Zv4w7oR7mS7lB+BCLG/c=; b=AhcKgmF1IBrY6DQDJ6lXW/v37jFwuaGPqAKF5s4TIU0ECh7gMF9l4t0dIPOiX7c4rd z6HgsvVAm3LujRCertZy1uq/RkarFCXWKhXXGNoSGLv7qujj8mbhvGbOQ+7vhcKGpFXJ LHi9je9S9Ip0BLwtRwTpJO6j7217MFFaFMu5eOiNQqxLhGHdHZ6AxP011fTP4XKvCy13 8uMK4OYvZcjjFW2pp5YqW4v/b6B8fcsvCwh06qWewEd+r6POnYzzm1nMQZOdhY9yv7OZ WNCYl3BdP9dj0tYqh91759r26WTsy8duzeM4xxABeFCLnCxdGgtf2LtpOoJOQiNEJz8h DvoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=EsMHVk++S7T40Osl4rGSV27Zv4w7oR7mS7lB+BCLG/c=; b=KOoNEeKmyzkgECicb5jYned7OKFUVsPAvp9g0/fC1uxX5zfT2ylky0nULw4r3FmsRp oWCCfMEZaGhCnvsPP7BKtY4bCUwkPUbkPHEOkuDOxtCzMhSk/q4UdBIG0d+0GAOv85Dx P+bydR2EoDADluRoCkJoxn5VBPnV9NAC7YV3PBj6Wa1W3WxJ365x5GmUJw83eqBwWZXa C+du7dqtMeszH5BWnv+iiEkzTlMNh6mjA0u9GHaTyaIOCT9/5XeBJZ7VVFfTV2S22x0C vTzqnP6D1qG89ST5eKqwAyFR1mDxnF7jNeP6OPB5x/UAcoWUbvL0tZjqaL3gZXjQuE8R 4Naw==
X-Gm-Message-State: APt69E0eHYm5+o8vE4kRDBaMeETkZz5/YEOgEGgKduYQNoJspqe3w0/H DBZCjh7yWkHDz/E3T6HS792TsTxAMBnzjEoOQ+b+JQ==
X-Google-Smtp-Source: ADUXVKLSgmRr6/HDHAnCk116cw3Wqu7DQzApoPbHTdvC4H4mSWo/4U6R5T7B2mQs868aBnxIpKiIvr/EUdhG41lbe/Q=
X-Received: by 2002:a0c:870a:: with SMTP id 10-v6mr20005183qvh.169.1529519118064; Wed, 20 Jun 2018 11:25:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ac8:2f5b:0:0:0:0:0 with HTTP; Wed, 20 Jun 2018 11:25:17 -0700 (PDT)
In-Reply-To: <CAO249yf9frAxyMDSphC54DWC1ggTndnf1bTuXagNC2zsOnSOcA@mail.gmail.com>
References: <CAO249ycbh_rL+i310=UtVyE39=Yk+OSRWfcj1UyF=74VZwC8vw@mail.gmail.com> <CAHYjOTbVUZ-TofLPORYLL9dPEKifxqbLRW6MVrg76Ukxg3omTg@mail.gmail.com> <CAO249yciU=5qS53__bZ9nJs6mT1Lq6_nbXNc=sadPfF6Q01yOQ@mail.gmail.com> <CAHYjOTZ2j6Q_pcfcSOc13DzwGYKtDttppS-+oLghOBEtxXeRfg@mail.gmail.com> <CAO249yf9frAxyMDSphC54DWC1ggTndnf1bTuXagNC2zsOnSOcA@mail.gmail.com>
From: Xavier de Foy <x.defoy.ietf@gmail.com>
Date: Wed, 20 Jun 2018 14:25:17 -0400
Message-ID: <CAHYjOTbqfVzd4GLukPiodRuak78PXDo2VEzxho2dd5ZuF_Y7Mw@mail.gmail.com>
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Cc: multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b59e98056f16eb73"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/K6X4M9q4oSP06STq2JUyXA7CPFI>
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: Wed, 20 Jun 2018 18:25:22 -0000
Hi Yoshi, thanks for the explanation, it makes sense to me. We will update the 5G considerations draft shortly, hopefully it will help defining a more concrete proposal. Best Regards, Xavier. On Wed, Jun 20, 2018 at 2:54 AM, Yoshifumi Nishida <nishida@sfc.wide.ad.jp> wrote: > Hi Xavier, > > Thanks. I think the timing you mentioned won't be a critical issue by > itself. > However, one question is how soon we can have concrete proposals to MPTCP > for 5G networks. > If there are already some solid features in 5G and we have explicit ideas > to update or extend MPTCP for them, I think there will be possibilities. > -- > Yoshi > > > On Tue, Jun 19, 2018 at 12:45 PM, Xavier de Foy <x.defoy.ietf@gmail.com> > wrote: > >> Hi Yoshi, >> >> Thanks for the answer. In term of timing: 5G global deployment should >> occur in 2020 (with smaller/test deployments before this), so work related >> to 5G adaptation may be best completed within 12 to 18 months (just my >> understanding, maybe others on the list can share their views on the best >> timing for this type of work). Do you think it is too far ahead, or would >> it make sense to include 5G related investigations in the list? >> >> Best Regards, >> >> Xavier >> >> On Fri, Jun 15, 2018 at 4:04 AM, Yoshifumi Nishida < >> nishida@sfc.wide.ad.jp> wrote: >> >>> Hi Xavier, >>> >>> Thank you so much! >>> Yes, we have thought about 5G stuff as well. >>> The reason why we haven't included in the list below was it might not be >>> a short term topic while it can be important for mptcp in future. >>> New suggestions to mptcp with regard to this topic will always be very >>> welcome. >>> -- >>> Yoshi >>> >>> >>> On Thu, Jun 14, 2018 at 2:01 PM, Xavier de Foy <x.defoy.ietf@gmail.com> >>> wrote: >>> >>>> Yoshifumi & Phil, >>>> >>>> Another potential item under "Feature Extensions" could be dedicated >>>> to interoperability with 5G. We are preparing an update to the "5G >>>> considerations" draft presented in the last session, which can be used as >>>> input for the group to decide if it should be on this list. >>>> >>>> Best Regards, >>>> Xavier >>>> >>>> On Thu, Jun 14, 2018 at 3:16 AM, Yoshifumi Nishida < >>>> nishida@sfc.wide.ad.jp> wrote: >>>> >>>>> Hello everyone, >>>>> >>>>> Phil and I have been discussing the next step for the WG. >>>>> After we finish 6824bis, we won'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? >>>>> presented by Jing >>>>> >>>>> _______________________________________________ >>>>> multipathtcp mailing list >>>>> multipathtcp@ietf.org >>>>> https://www.ietf.org/mailman/listinfo/multipathtcp >>>>> >>>>> >>>> >>> >> >
- 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