Re: [multipathtcp] Possible future items for mptcp WG

Xavier de Foy <x.defoy.ietf@gmail.com> Tue, 19 June 2018 19:45 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 EFAA7130E6E for <multipathtcp@ietfa.amsl.com>; Tue, 19 Jun 2018 12:45:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=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 ZXutjWxvR85q for <multipathtcp@ietfa.amsl.com>; Tue, 19 Jun 2018 12:45:05 -0700 (PDT)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (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 760C2130EA6 for <multipathtcp@ietf.org>; Tue, 19 Jun 2018 12:45:03 -0700 (PDT)
Received: by mail-qt0-x235.google.com with SMTP id l33-v6so873489qta.11 for <multipathtcp@ietf.org>; Tue, 19 Jun 2018 12:45:03 -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=kBE6hWyJKfqNe8wzRjAN0xDsQedif8WFMXIFN2JQU1g=; b=MGZoQxlmR4JUDOZVQnA4k7dVMSbR9fDwhlv5Pdou74YUA2nrOLkR/xYexux3BIJL0N D2duTReKDs0PENP5FnKlajSUV26GksAH23EJaCFBIUhg8Ga1zM7TPXyrgX5A6i4+3R67 yxV0YlCTQaaMFx+FIl02fu6vee47X1K3d8lYpOCSKZ3cGDap6bt6COs4Mya/xdZqbZGw vs16OrQLkhOl/QM1f+5NObJdAL9HhFrYaqVhrceB2TQDRAVkt71z8cOTrsAU73L3+trG k/vcq2h7eTpTnlS/9iVYdUGtmBor/1dxkkcR654IJYENN89tvjhukTjWkgaIeI5lfJCZ a6rg==
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=kBE6hWyJKfqNe8wzRjAN0xDsQedif8WFMXIFN2JQU1g=; b=MXp68i7LeVcGuHUruOMTLL0zBKO//cwXQMRae9AQBCgYHaLw9p2728865VE8PVWf8s Xwl0wMC57beZ3eb4y8MGDrevKbRS3ZFBKsLP9OqW3/BwS0beaNDsXC8mYvwlEh9I1TTM qOP1QPLgv+lywe4WJJTSGKY4DJfQijo+GMwm7KQ+xLY+RkExsKUZbbG0bdhdqMxv/Bdw /SSUWcAyH5i3OHHlDAgLSaunxBvWCgxrmftkpIoOVoIVSN+2+CbZIuKSAvHfHZXiurwS ma8tVPnx4LEi6I4JN3mfCqggOQFdkdSysQAoEYybHUXllC+uZhmpM/02D2+Sk5E8OOG/ HpCg==
X-Gm-Message-State: APt69E0C6Ht2vD1+y7iRkNnQQpcLkIJape+gavO/VHPjPWpaIWlRpsFY cDwwWEHNhpV7uCj6o+g1d7GjVlQx6qWUHvj23jkpfQ==
X-Google-Smtp-Source: ADUXVKJK7pSrbNSRHMu5Wl68+mDH/6LeZkbPcQD7npNwsKS1obOuERWVVriLcnwLReYDQTgtx8TgVW6InjQvsHh5Qbk=
X-Received: by 2002:a0c:93ec:: with SMTP id g41-v6mr15954833qvg.243.1529437502603; Tue, 19 Jun 2018 12:45:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ac8:2f69:0:0:0:0:0 with HTTP; Tue, 19 Jun 2018 12:45:02 -0700 (PDT)
In-Reply-To: <CAO249yciU=5qS53__bZ9nJs6mT1Lq6_nbXNc=sadPfF6Q01yOQ@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>
From: Xavier de Foy <x.defoy.ietf@gmail.com>
Date: Tue, 19 Jun 2018 15:45:02 -0400
Message-ID: <CAHYjOTZ2j6Q_pcfcSOc13DzwGYKtDttppS-+oLghOBEtxXeRfg@mail.gmail.com>
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Cc: multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000c86b1056f03eb98"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/VgkMSSUb8g_aabb8B5NOVHZqMTg>
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: Tue, 19 Jun 2018 19:45:08 -0000

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