Re: [multipathtcp] Possible future items for mptcp WG

Yoshifumi Nishida <nishida@sfc.wide.ad.jp> Wed, 20 June 2018 06:54 UTC

Return-Path: <nishida@sfc.wide.ad.jp>
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 1A9BB131028 for <multipathtcp@ietfa.amsl.com>; Tue, 19 Jun 2018 23:54:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 bZrBlAmqgpal for <multipathtcp@ietfa.amsl.com>; Tue, 19 Jun 2018 23:54:49 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [IPv6:2001:200:0:8803::53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 887C2131057 for <multipathtcp@ietf.org>; Tue, 19 Jun 2018 23:54:48 -0700 (PDT)
Received: from mail-it0-f42.google.com (mail-it0-f42.google.com [209.85.214.42]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 65FC72784A1 for <multipathtcp@ietf.org>; Wed, 20 Jun 2018 15:54:46 +0900 (JST)
Received: by mail-it0-f42.google.com with SMTP id p185-v6so4033723itp.4 for <multipathtcp@ietf.org>; Tue, 19 Jun 2018 23:54:46 -0700 (PDT)
X-Gm-Message-State: APt69E39d4KrBzUSTOXwpr6S/151cqmuMyWHuQ5v6o6BEbquWW1mS/tU UDnO37vbP2mc+qHcqus3HfnXytVC7fA23aEgi4U=
X-Google-Smtp-Source: ADUXVKK06dR7DCkc3UWMl7am+fVVW5zlZiUmQ//AJvO2v2zs2p2IbrM21yFtJ5qvXBZGTtRhMMCPnzUzvCM20MDrZvU=
X-Received: by 2002:a02:9914:: with SMTP id r20-v6mr15605716jaj.144.1529477685169; Tue, 19 Jun 2018 23:54:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:11c4:0:0:0:0:0 with HTTP; Tue, 19 Jun 2018 23:54:44 -0700 (PDT)
In-Reply-To: <CAHYjOTZ2j6Q_pcfcSOc13DzwGYKtDttppS-+oLghOBEtxXeRfg@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>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Tue, 19 Jun 2018 23:54:44 -0700
X-Gmail-Original-Message-ID: <CAO249yf9frAxyMDSphC54DWC1ggTndnf1bTuXagNC2zsOnSOcA@mail.gmail.com>
Message-ID: <CAO249yf9frAxyMDSphC54DWC1ggTndnf1bTuXagNC2zsOnSOcA@mail.gmail.com>
To: Xavier de Foy <x.defoy.ietf@gmail.com>
Cc: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>, multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001ddad6056f0d46dc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/unmhElb7nmKiE46byO8UBup1jEc>
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 06:54:53 -0000

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