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 0E43F130F15 for ; Thu, 14 Jun 2018 14:01:25 -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 pOYp5KzzMi7p for ; Thu, 14 Jun 2018 14:01:23 -0700 (PDT) Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::231]) (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 1B238130E2F for ; Thu, 14 Jun 2018 14:01:23 -0700 (PDT) Received: by mail-qt0-x231.google.com with SMTP id y31-v6so7197960qty.9 for ; Thu, 14 Jun 2018 14:01:23 -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=G98yp7DP88LOs2IAR38GONATJtdGA5i+tBVTakdE6RI=; b=A3bbmqvX7Dts0YFWS34Zw5BaFWurEjyGPFmJyagU/uZ77Hv3RwdODyv6Hud8jUa9w/ aUvHGklnxgQzE44sA3sipSYNnSjorZD9OjXeMdUU+ix1KU09d00KaDTsGMvIxSFvfT8v K32Hl/sIJjwcgo49W7zVREBXxTC4G1sR2AZGP13oLN4iHun0ob7Fxx0VCD2YdfizV+sx VSybCKXQlEzaeboWNNULzk66Ahsaigolmvip6aSzRYir+IGqHEpJBe3ID6p9+vlrDf5z Q5hSsbFfw9yyLJgTNXnmIU4EL7tlVqdisxz9SIIjwI//FyBzLae1hX7OgQ1w+YGWOmEr 00PA== 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=G98yp7DP88LOs2IAR38GONATJtdGA5i+tBVTakdE6RI=; b=ODwjZQWK1GdZ54EeKv6O9TvVFf7jvu63Khpix0K/kmawHHuTJLB34GI+sSOW2SsM7i +5AoGRQnnx4+i1VeVkG/2hMqNqbIp1RJ/kbEuC34e4Q21FS+1zndH1zLW9CvRnOykqVa bkCCtRnYuA1nCzbpNVebdJkTNPgjsgsAE4U6YB91oKubqyoQGknYZx/E5uHt+DP8tBES HsRKuXccZH5N/GzX/CjzJLo59CJvdxEU0xp+cXKe+qz9Eb5BTdINBl5PdDR6h3c6gIhc WgZUSHowhkA40iCeCExZx3muZNiJDbVaxqTCmkhm541qxyFIGtIpMqa0jZjKMOz+OFm2 niBg== X-Gm-Message-State: APt69E3E1rSOJHytgpQyEQFw4R1ScGqjgEIL0F75tc5Oe43ZyVgs2bPk gzhX6f27O1Jkquw4/NOICdvx7ZCkftTryxlBnw1STQ== X-Google-Smtp-Source: ADUXVKKF0I85LC487QgJs47Qq6IvYfG2ymbvAcE4bBt85KfgdLdFyi/G1pHoSsQHel6tWOuv0QJu7FdQZswRHETSjsA= X-Received: by 2002:a0c:89dd:: with SMTP id 29-v6mr3761597qvs.233.1529010081293; Thu, 14 Jun 2018 14:01:21 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac8:353a:0:0:0:0:0 with HTTP; Thu, 14 Jun 2018 14:01:20 -0700 (PDT) In-Reply-To: References: From: Xavier de Foy Date: Thu, 14 Jun 2018 17:01:20 -0400 Message-ID: To: Yoshifumi Nishida Cc: multipathtcp Content-Type: multipart/alternative; boundary="000000000000c0eaf3056ea066c4" 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: Thu, 14 Jun 2018 21:01:25 -0000 --000000000000c0eaf3056ea066c4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 pro= xy 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 > > --000000000000c0eaf3056ea066c4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 <ni= shida@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 items as the proxy=C2=A0work will be discussed at tcpm WG.<= div>One suggestion might be to close the WG = or to put it in dormant state, however,=C2=A0we are thinking there still might be some more working items as we&= #39;ve seen=C2=A0interesting presenta= tions 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.<= /span>
Please le= t us know if you think some of them are important items for=C2=A0the WG (and your willingness to contribute if p= ossible) or there are=C2=A0some 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=C2= =A0to the chairs, please let us hear!=

We appreciate your feedback

Thanks= ,
--
Yoshi & P= hil



1: API extensi= ons (This is already in our charter)
=C2=A0 =C2=A0 draft-hesmans-mptcp-socket=
=C2=A0 =C2=A0 d= raft-samar-mptcp-socketapi

2: Feature extensions=
=C2=A0 =C2=A0 a= ) robust initial setup
=C2=A0 =C2=A0 =C2=A0 =C2=A0 proposed by Markus,=C2=A0<= span style=3D"font-size:16px">also Kien presented a similar idea

=C2=A0 =C2=A0 b) fast subflow setup
=C2=A0 =C2=A0 =C2=A0 =C2=A0 proposed b= y 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 proposals from tcpinc?

=C2=A0 =C2=A0 =C2=A0 =C2=A0 3) Elliptic Curve Cryptography=C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 draft-kim-mptcp-semptcp-00

=C2= =A0 =C2=A0 d) Solutions for operational issues
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01) = how to handle nat64 issue proposed by Quentin
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A02) h= ow to handle load balancer proposed by Fabien, Christoph, Costin

3: Congestion Control (This topic itself should probably be discu= ssed at ICCRG. But, it may trigger some updates of the protocol or APIs lat= er) =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) mptcp + BBR?
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 pr= esented by Jing

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


--000000000000c0eaf3056ea066c4--