Return-Path: 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 8C294130DE0 for ; Fri, 15 Jun 2018 01:04:12 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 EKCIBP4GzRLd for ; Fri, 15 Jun 2018 01:04:10 -0700 (PDT) Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DDD6130DDC for ; Fri, 15 Jun 2018 01:04:10 -0700 (PDT) Received: from mail-io0-f174.google.com (mail-io0-f174.google.com [209.85.223.174]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id BE8BE278538 for ; Fri, 15 Jun 2018 17:04:08 +0900 (JST) Received: by mail-io0-f174.google.com with SMTP id t5-v6so9951444ioa.8 for ; Fri, 15 Jun 2018 01:04:08 -0700 (PDT) X-Gm-Message-State: APt69E1OLPD6/eXJfAl3GjqQQHmhK+IOdh0aquZmGws1oE7tBWdQIjlK Ds8R/Df5VGPdb6/AFGp4A9M06k8nm3wJnxtcs8M= X-Google-Smtp-Source: ADUXVKJSwml62V6i7pNCMn2kzXPQUpwd6daLsRLfXpE80b31LHd7EyeLWwtp0GGlInj0CR0GX/P/wHl0mfPD9rVaBNY= X-Received: by 2002:a6b:dd14:: with SMTP id f20-v6mr597331ioc.7.1529049847597; Fri, 15 Jun 2018 01:04:07 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:11c4:0:0:0:0:0 with HTTP; Fri, 15 Jun 2018 01:04:06 -0700 (PDT) In-Reply-To: References: From: Yoshifumi Nishida Date: Fri, 15 Jun 2018 01:04:06 -0700 X-Gmail-Original-Message-ID: Message-ID: To: Xavier de Foy Cc: Yoshifumi Nishida , multipathtcp Content-Type: multipart/alternative; boundary="000000000000028fb9056ea9a929" Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 08:04:13 -0000 --000000000000028fb9056ea9a929 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 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 > wrote: > >> Hello everyone, >> >> Phil and I have been discussing the next step for the WG. >> After we finish 6824bis, we =EF=BD=97on't have active WG items as the pr= oxy 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 t= o >> 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 >> >> > --000000000000028fb9056ea9a929 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Xavier,

Thank you so much!
Yes, we have thought about 5G stuff as well.=C2=A0
The reason wh= y we haven't included in the list below was it might not be a short ter= m topic while it can be important for mptcp in future.
New sugges= tions 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 &=20 Phil,

=C2=A0 Another potential item under "Fe= ature Extensions" could be dedicated to interoperability with 5G. We a= re 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.

=C2=A0 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 =EF=BD=97on't have active WG i= tems as the proxy=C2=A0work will be d= iscussed at tcpm WG.
One suggesti= on might be to close the WG or to put it in dormant state, however,=C2=A0we are thinking there still might be so= me more working items as we've seen=C2=A0interesting presentations for new ideas, experiment results and so = on at the=C2=A0meetings 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 import= ant items for=C2=A0the WG (and your w= illingness to contribute if possible) or there are=C2=A0some more items, or this is not something we should wor= k on, etc.

= Also, if you have some opinions on the statu= s of the WG or suggestions=C2=A0to th= e chairs, please let us hear!

We appreciate your feedb= ack

Thanks,
--
Yoshi & Phil



1: API extensions (This is already in our charter)=C2=A0 =C2=A0 dra= ft-hesmans-mptcp-socket
=C2=A0 =C2=A0 draft-samar-mptcp-socketapi

2: Feature extensions
=C2=A0 =C2=A0 a) robust initial setup
=C2=A0 =C2=A0 =C2=A0 =C2=A0 pro= posed by Markus,=C2=A0also Kien prese= nted a similar idea

=C2=A0 =C2=A0 b) fast subflow setup=
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 proposed by Quentin=C2=A0

=C2=A0 = =C2=A0 c) security enhancement
=C2=A0 =C2=A0 =C2=A0 =C2=A0 1) TLS
=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 draft-bonaventure-mptcp-tls-00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 draft-paasch-mptcp-tls-authentication-00

=C2=A0 =C2=A0 =C2=A0 =C2=A0 2) Utilize pro= posals from tcpinc?

=C2=A0 =C2=A0 =C2=A0 =C2=A0 3) Elli= ptic Curve Cryptography
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 draft-kim-mptcp-se= mptcp-00

=C2=A0 =C2=A0 d) Solutions for operational iss= ues
=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01) how to handle nat64 issue proposed by Que= ntin
=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A02) how to handle load balancer proposed by F= abien, Christoph, Costin

3: Congestion Control (This to= pic itself should probably be discussed at ICCRG. But, it may trigger some = updates of the protocol or APIs later) =C2=A0
=C2=A0 =C2=A0 =C2=A0a) OLIA
=C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 draft-khalili-mptcp-congestion-control-05

=C2=A0 =C2=A0 =C2=A0b) mptc= p + BBR?
= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 presented by Jing

_______________________________________________
multipathtcp mailing list
multipathtcp@iet= f.org
https://www.ietf.org/mailman/listinfo/multipa= thtcp



--000000000000028fb9056ea9a929--