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
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
Precedence: list

Hi Yoshi & Phil,

I still follow the mentioned feature extension 2a) robust initial setup. Ma=
ybe 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



> ----------------------------------------------------------------------
>=20
> 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=3DUtVyE39=3DYk+OSRWfcj1UyF=3D74VZwC8vw@mai
> l.gmail.com>
> Content-Type: text/plain; charset=3D"utf-8"
>=20
> Hello everyone,
>=20
> 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 an=
d
> so on at the meetings and on the ML.
>=20
> Below is the list of potential working items from the chairs' point of vi=
ew.
> 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 i=
tems,
> or this is not something we should work on, etc.
>=20
> Also, if you have some opinions on the status of the WG or suggestions to
> the chairs, please let us hear!
>=20
> We appreciate your feedback
>=20
> Thanks,
> --
> Yoshi & Phil
>=20
>=20
>=20
>=20
> 1: API extensions (This is already in our charter)
>     draft-hesmans-mptcp-socket
>     draft-samar-mptcp-socketapi
>=20
> 2: Feature extensions
>     a) robust initial setup
>         proposed by Markus, also Kien presented a similar idea
>=20
>     b) fast subflow setup
>         proposed by Quentin
>=20
>     c) security enhancement
>         1) TLS
>             draft-bonaventure-mptcp-tls-00
>             draft-paasch-mptcp-tls-authentication-00
>=20
>         2) Utilize proposals from tcpinc?
>=20
>         3) Elliptic Curve Cryptography
>             draft-kim-mptcp-semptcp-00
>=20
>     d) Solutions for operational issues
>          1) how to handle nat64 issue proposed by Quentin
>          2) how to handle load balancer proposed by Fabien, Christoph, Co=
stin
>=20
> 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
>=20
>      b) mptcp + BBR?