[multipathtcp] Consensus call on potential MPTCP proxy work
<philip.eardley@bt.com> Tue, 18 April 2017 08:17 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 80F93131803
for <multipathtcp@ietfa.amsl.com>; Tue, 18 Apr 2017 01:17:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01,
RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, 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 GrpR0wCWcFxM for <multipathtcp@ietfa.amsl.com>;
Tue, 18 Apr 2017 01:17:29 -0700 (PDT)
Received: from smtpb1.bt.com (smtpb1.bt.com [62.7.242.141])
(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 8430F126DEE
for <multipathtcp@ietf.org>; Tue, 18 Apr 2017 01:17:28 -0700 (PDT)
Received: from EVHUB05-UKBR.domain1.systemhost.net (193.113.108.173) by
EVMED05-UKBR.bt.com (10.216.161.37) with Microsoft SMTP Server (TLS) id
14.3.319.2; Tue, 18 Apr 2017 09:17:23 +0100
Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by
EVHUB05-UKBR.domain1.systemhost.net (193.113.108.173) with Microsoft SMTP
Server (TLS) id 14.3.158.1; Tue, 18 Apr 2017 09:17:25 +0100
Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by
rew09926dag03b.domain1.systemhost.net (10.55.202.22) with Microsoft SMTP
Server (TLS) id 15.0.1210.3; Tue, 18 Apr 2017 09:17:24 +0100
Received: from rew09926dag03b.domain1.systemhost.net
([fe80::d514:fe50:560c:401e]) by rew09926dag03b.domain1.systemhost.net
([fe80::d514:fe50:560c:401e%12]) with mapi id 15.00.1210.000; Tue, 18 Apr
2017 09:17:24 +0100
From: <philip.eardley@bt.com>
To: <multipathtcp@ietf.org>
Thread-Topic: Consensus call on potential MPTCP proxy work
Thread-Index: AdK4HBNY1jXzvDFKRxmRsHBM53Icbg==
Date: Tue, 18 Apr 2017 08:17:24 +0000
Message-ID: <8c5ffa879686472594bfd3db2fa06076@rew09926dag03b.domain1.systemhost.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.202.233]
Content-Type: multipart/alternative;
boundary="_000_8c5ffa879686472594bfd3db2fa06076rew09926dag03bdomain1sy_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/f1gWNze7nfVkpyX7jrKq4w1eVHQ>
Subject: [multipathtcp] Consensus call on potential MPTCP proxy work
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.22
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, 18 Apr 2017 08:17:31 -0000
Hi, During the MPTCP meeting in Chicago we did several hums about potential MPTCP proxy work. Our interpretation of these hums is that we should do a consensus call for the following work: -- MPTCP is now seeing widespread deployment in networks to bond together two accesses, such as fixed and mobile broadband, by using two MPTCP proxies, one in the home gateway or Customer Premises Equipment and one in the network. The WG develops a solution where the proxies are both under the control of the operator and where it is assumed that they are not on the default path. The solution is based on using the payload of an MPTCP packet to transfer a signalling message between the proxies. It is believed the solution will not require changes to RFC6824bis. The solution may require a means of configuring set-up information in the proxies, which would be done in coordination with other IETF WGs such as DHC. The WG does not develop a mechanism for the two proxies to discover each other. -- Please say whether you support, or don't support, such work - so we can see if there's consensus for it. Thanks Phil & Yoshi Hums during the meeting: * Should the MPTCP WG do any MPTCP proxy work, or do none - about 2:1 or 3:1 in favour of doing work * Should the MPTCP WG do proxy work based on option #1 in slide 12? Strongly more yes than no * Should the MPTCP WG do proxy work based on option #2 in slide 12? more no than yes * Should the MPTCP WG do proxy work based on option #3 in slide 12? Weak & roughly equal Ref: https://www.ietf.org/proceedings/98/slides/slides-98-mptcp-sessa-chairs-01.pdf We believe the work does not require an update to the MPTCP WG charter.
- [multipathtcp] Consensus call on potential MPTC... philip.eardley
- Re: [multipathtcp] Consensus call on potential ... christian.jacquenet
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Juliusz Chroboczek
- Re: [multipathtcp] Consensus call on potential ... Stefano Secci
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... Sargent, Matthew T. (GRC-LCA0)[Peerless Technologies]
- Re: [multipathtcp] Consensus call on potential ... Henderickx, Wim (Nokia - BE/Antwerp)
- Re: [multipathtcp] Consensus call on potential ... Henderickx, Wim (Nokia - BE/Antwerp)
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... Yoshifumi Nishida
- Re: [multipathtcp] Consensus call on potential ... David Allan I
- Re: [multipathtcp] Consensus call on potential ... Juliusz Chroboczek
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... Yoshifumi Nishida
- Re: [multipathtcp] Consensus call on potential ... Olivier Bonaventure
- Re: [multipathtcp] Consensus call on potential ... Costin Raiciu
- Re: [multipathtcp] Consensus call on potential ... Olivier Bonaventure
- Re: [multipathtcp] Consensus call on potential ... philip.eardley
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Markus.Brunner3
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Robert Skog
- Re: [multipathtcp] Consensus call on potential ... Sargent, Matthew T. (GRC-LCA0)[Peerless Technologies]
- Re: [multipathtcp] Consensus call on potential ... Jordan Melzer
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... Juliusz Chroboczek
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Juliusz Chroboczek
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Sargent, Matthew T. (GRC-LCA0)[Peerless Technologies]
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... Juliusz Chroboczek
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Eggert, Lars
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Eggert, Lars
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Yoshifumi Nishida
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Juliusz Chroboczek
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... philip.eardley
- Re: [multipathtcp] Consensus call on potential ... Sébastien Barré
- Re: [multipathtcp] Consensus call on potential ... Wouter Cloetens
- [multipathtcp] Increasing usage of MPTCP [was: ... Juliusz Chroboczek
- Re: [multipathtcp] Consensus call on potential ... SungHoon Seo
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Increasing usage of MPTCP [w... Olivier Bonaventure
- Re: [multipathtcp] Consensus call on potential ... Matt Sargent
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Increasing usage of MPTCP [w... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... Meyer, Ullrich, Vodafone DE
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... Juliusz Chroboczek
- Re: [multipathtcp] Consensus call on potential ... Juliusz Chroboczek
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair
- Re: [multipathtcp] Consensus call on potential ... Joe Touch
- Re: [multipathtcp] Consensus call on potential ... Yoshifumi Nishida
- Re: [multipathtcp] Consensus call on potential ... mohamed.boucadair