[multipathtcp] MPTCP WG minutes - draft

<philip.eardley@bt.com> Tue, 16 April 2019 10:05 UTC

Return-Path: <philip.eardley@bt.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 22D9612047E for <multipathtcp@ietfa.amsl.com>; Tue, 16 Apr 2019 03:05:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bt.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 Lce_X2P3fgLI for <multipathtcp@ietfa.amsl.com>; Tue, 16 Apr 2019 03:05:11 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [62.239.224.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74A40120128 for <multipathtcp@ietf.org>; Tue, 16 Apr 2019 03:05:09 -0700 (PDT)
Received: from tpw09926dag15h.domain1.systemhost.net (10.9.212.39) by RDW083A009ED65.bt.com (10.187.98.35) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 16 Apr 2019 11:02:31 +0100
Received: from tpw09926dag18h.domain1.systemhost.net (10.9.212.42) by tpw09926dag15h.domain1.systemhost.net (10.9.212.39) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 16 Apr 2019 11:05:06 +0100
Received: from RDW083A009ED65.bt.com (10.187.98.35) by tpw09926dag18h.domain1.systemhost.net (10.9.212.42) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 16 Apr 2019 11:05:06 +0100
Received: from GBR01-CWL-obe.outbound.protection.outlook.com (104.47.20.54) by smtpe1.intersmtp.com (62.239.224.236) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 16 Apr 2019 11:02:29 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bt.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=LawxRTyAI46Ho3e3lmKPquNxrTNIcjiqJ/wMsRcQPmg=; b=mccT6kCecouptcdtK424pHB/mRh5XJdacCmXBoxLqKa2DrjNrPu27zN3lEr8b6dh7Lel2qjys+dKlJ/jOQZXqc+fWaCyPLTPviAOf5G/HJ7guAEg3NuI1MRhqSjkCW4TdvwcOydnyx0LrTsAO0AdMCzw0s+k6cI8cCshGC6QAeI=
Received: from LO2P123MB1965.GBRP123.PROD.OUTLOOK.COM (20.176.157.10) by LO2P123MB1887.GBRP123.PROD.OUTLOOK.COM (20.176.154.214) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.17; Tue, 16 Apr 2019 10:05:05 +0000
Received: from LO2P123MB1965.GBRP123.PROD.OUTLOOK.COM ([fe80::7940:b11d:fe0c:9f2f]) by LO2P123MB1965.GBRP123.PROD.OUTLOOK.COM ([fe80::7940:b11d:fe0c:9f2f%5]) with mapi id 15.20.1792.020; Tue, 16 Apr 2019 10:05:05 +0000
From: <philip.eardley@bt.com>
To: <multipathtcp@ietf.org>
Thread-Topic: MPTCP WG minutes - draft
Thread-Index: AdT0OcKjuZY10X+FSKSpns4gjqcfow==
Date: Tue, 16 Apr 2019 10:05:04 +0000
Message-ID: <LO2P123MB1965B4686737AFF0B42288BEEB240@LO2P123MB1965.GBRP123.PROD.OUTLOOK.COM>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=philip.eardley@bt.com;
x-originating-ip: [193.113.37.9]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 127af6f1-d85e-438b-d1ff-08d6c252ff90
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600140)(711020)(4605104)(2017052603328)(7193020); SRVR:LO2P123MB1887;
x-ms-traffictypediagnostic: LO2P123MB1887:
x-antispam-2: 1
x-microsoft-antispam-prvs: <LO2P123MB188754AD8575C9BA6AD034DFEB240@LO2P123MB1887.GBRP123.PROD.OUTLOOK.COM>
x-forefront-prvs: 000947967F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(396003)(39860400002)(366004)(346002)(376002)(189003)(199004)(486006)(71200400001)(97736004)(71190400001)(476003)(8936002)(8676002)(81166006)(106356001)(52536014)(25786009)(2351001)(105586002)(1730700003)(81156014)(478600001)(55016002)(561944003)(6506007)(53946003)(256004)(14444005)(6116002)(790700001)(3846002)(6306002)(102836004)(54896002)(9686003)(86362001)(186003)(5660300002)(4326008)(53936002)(66066001)(26005)(316002)(68736007)(99286004)(33656002)(2906002)(6916009)(7736002)(5640700003)(74316002)(14454004)(7696005)(6436002)(2501003)(559001)(579004); DIR:OUT; SFP:1101; SCL:1; SRVR:LO2P123MB1887; H:LO2P123MB1965.GBRP123.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: bt.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: Ek9fwhjgXIjJshoeqWdL85nsfJW+zZCafDzzNuiK32nA2WLXNkYpuXEudwZ/i6egGqAP+jLU0b20fjQo9dGGb6ajPTn9hbAA9QFGk4NtCBPsCnMOmYiVG3RWy0noNrc6auMl9hkL/WydW6SNoopaCKR3Ildnrep4Eas4pLkfU3qKfmJ85UnNC7O9waN04j3zx88rox4k83nuM1Ni/Khjz3egW1v045+D7DqOY8u/qxkO9Qr/ULZDev1TOcEQ70CuCPib42dvaRZOS+jnef7oMNGHyN3bHuZFi7Mk/udnX876IVPW0fcwD9vqpxx4bevejlI12ru9sKcpDRxOFwdkcuMDKk7Z+jv6+FlrnkO1XZDqmLlXqPbStTsjq0oKsKLUPcU88wmfz1r3UUvmO/rWEBF75t8qN9Hzs4qzGLpFic4=
Content-Type: multipart/alternative; boundary="_000_LO2P123MB1965B4686737AFF0B42288BEEB240LO2P123MB1965GBRP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 127af6f1-d85e-438b-d1ff-08d6c252ff90
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Apr 2019 10:05:04.9090 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a7f35688-9c00-4d5e-ba41-29f146377ab0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LO2P123MB1887
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/My0_i0LWeIybqs80xk0oZVhDTOc>
Subject: [multipathtcp] MPTCP WG minutes - draft
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
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, 16 Apr 2019 10:05:15 -0000

Here are the draft minutes for our WG meeting in Prague. Please let us know any corrections.
Thank-you to the minute takers - I think Anna & Xavier, please shout if I remember wrong!
Thanks
Phil & Yoshi
--

1. WG status (chair)

2. Implementation news (Christoph)
- Now have approval to open source the handshake
- Mainline Linux kernel: growing community (RedHat, Intel, Thesaurus), making progress, will get there eventually, have support from Linux maintainers
- Apache traffic server allows to enable MPTCP

3. Deployment updates
3.1. Results from the monitoring of MPTCP-based hybrid access networks - Olivier Bonaventure
See slides for overview of talk

Q & A

Q Use of transparent proxy, do you need converter (Rahul Jadhav)
A. CPE sees all the traffic, no need there. HAG may use a converter or be transparent. With transparent proxy on the HAG, all traffic must go through the HAG. Otherwise use a converter.

Q. Can converter be extended with policy support for scheduling (Rahul Jadhav)
A. Network operators control the policy

Q. Shown employment is not consistent with 3GPP Rel 16 (Florin Baboescu?)

Q. Specific scheduler used in deployment (Marcus Amend)
A. Scheduler and path manager prioritize DSL network

Q. In results, could you get 1G with single TCP flows. (Marcus Amend)
A. Was with multiple flows

Q. CPU overhead? (Marcus Amend)
A. Really depend on the CPE

Q. Need complement to TCP? It is hard to explain to customers if the benefit is for TCP only, this is why we propose a multipath UDP to complement MPTCP (Marcus Amend)
A. BBF does also GRE approach, will see how QUIC will be supported

Q. What is the issue with using MPTCP for tunneling IP traffic (Florin Baboescu?)
A. MPTCP will give you reliability and delay for applications that do not need it.

3.2. Multi-path Transport Deployment on Smartphone Apps - Zhen Cao
See slides for overview of talk

Q & A

Q. Can set ECN CE mark on the path you do not want the server to use (to implicitly tell server which path is preferred, eg toll-free) (Lars Eggert)
Does ECN work with MPTCP? (Zhen)
Yes (Stuart Cheshire)
Using ECN will reduce the cwnd for when you need it (Anna Brunstrom)
Need this functionality for other things (Marcus Amend)
Do not need more functionality in MPTCP (Lars)
Need to better understand the problem before we decide solution
More discussion on the mailing list would be helpful, there were already a thread discussing this;

Q. Why do you need MPTCP for mice flow.
A. For better latency

Q. Low latency path should naturally be the "best" path selected, so will not need anything special for path management to handle this (Lars)
A. Ok, got your point; At least we agree on the scenario and the problem exists.
Q  How often does this happen (Ben)
A. With full mesh all the time

Q. ATSSS slide not fully correct, only cover Rel. 15. (Florin)
A. Thanks, please send them to the list as the group is not fully aware of what's happening in 3GPP.


4. Individual drafts
4.1. Initial-Path Selection for Connection Establishment in Multipath TCP - Jianjian Zhu
See slides for overview of talk

Q & A
Q. This caching is already discussed in bis draft (Alan Ford)

Q. RSSI is not enough, suggest to look at MAMS draft (Florin)
Q CQI is what we use in mobile (Chris Seal)

Q Selection of initial interface important, but is independent of MPTCP. There is the same problem in QUIC. This should not be designed for MPTCP only. (Christoph)
This is happy eyeballs in narrow scope, please look at that if not familiar. WiFi assist to prefer one interface. (Stuart Cheshire)
Yes, this should be general solution. There will be PIPC side meeting (performance implications of path characteristics). (Zhen)
Agree, it is a general issue, but think we should not limit multipath protocols to single path at start-up (Marcus)
Keying attacks is a problem for happy eyeballs in MPTCP context (Alan Ford)


4.2. Generic Path-Manager Support with eBPF - Viet-Hoang Tran (remote)
See slides for overview of talk

Q & A

4.3. 5G Session Continuity Support in MPTCP - Xavier de Foy 5.
See slides for overview of talk

Q & A

Q Multi-access PDN is introduced in 3GPP Rel. 16, not well mapped to talk, also all terminals know their address (Florin)
A. Need to support continuity of addresses known at client but not at server

Q. Key proposal is communicating session continuity type to remote peer? (Sri)
A. Not really, it is one of the possible solutions but there are other options
Q. This information is not enough, need additional information, need to analyze
A. Actually in this particular solution the initial IP address index is also communicated to the remote peer, not only the session continuity type.

Q Any data quantifying when you do nothing (Lars Eggert)
A. No
Q. Suggest we discuss this when we have data and know if there is a problem
Q. Do you plan to get data (Phil)
A. Do not have access to 5G network yet
Any data even simulation may be useful, start with data (Lars)

Q. For 3GPP we have clear items that have priority, would like to have focus on this, this is not one of them (Florin)
Let's talk later to see how to best convey this to group (Phil)


5. Potential future topics for WG
5.1. Brief summary of Monday's side meeting
5.2. TAPS multipath support - Anna Brunstrom
5.3. Open discussion

Welcome input on API. Open issue on improving granularity of info (Apple use enum and 3 modes eg interactive, aggregation) (Tommy)
Path manager and scheduler is a challenge because you often have two competing goals, reduce cost and improve performance. Ok on the client you can make this trade-off, but needs to be communicated to the server. We currently know who we talk to and configure a policy for a particular service, This is not a general solution, so some signalling from client to server would be very useful. (Christoph)
Have you tried using ECN approach suggested by Lars? (Phil)
Can perhaps support throughput, but does not work for latency (Christoph)
Can we perhaps solve some of these issues in more general context, will apply to multipath QUIC as well at some time or any multipath protocol
Think it is important to collect path scheduling algorithms in informational document (Markus)
Issue is not only on handset, also on proxy that may implement load balancing scheme (Florin)
Would be useful to tease this problem apart (Lars)
Hear a lot of interesting issues, but they seem like research issues. Also some minor extensions, that could be done in tcpm. Also hear discussion on interfaces, this links to TAPS
Not only research issues, also experiences from operational experience. Also need connection to BBF and 3GPP
Can be handled in other groups (Mirja)
Much easier if we have a group collecting MPTCP experts (Zhen)
Concerned we are missing other experts here like congestion control. (Mirja)

Do have issue if a terminal or proxy need to implement a policy, we have very clear requirements here. (Florin)
For ATSSS we have a side channel for policies, right (Christoph)
Issue is how to use the policy as I understand (Florin)

Think we should have informational document on scheduling and path management for BBF and 3GPP to know. Do you think this is research? (Markus)
This topic is relevant for other protocols as well, we will find a home for this document (Mirja)
Closing a wg is not a threat to close the work, perhaps we should have a general wg on multipath (Tommy)
Agree a generic multipath group could be good. IEEE, 3GPP want to use IETF protocols, timeframe is ~ Dec 2019. (Florin)
Do not understand why we should close a group when we have issues to solve (Zhen)
Group has finished its charter, then we normally close. The mailing list can stay open. (Mirja)