Re: [multipathtcp] potential MPTCP proxy charter item

Robert Skog <robert.skog@ericsson.com> Fri, 07 October 2016 08:52 UTC

Return-Path: <robert.skog@ericsson.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 95E6112953C for <multipathtcp@ietfa.amsl.com>; Fri, 7 Oct 2016 01:52:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.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 XATOgIHvdC9J for <multipathtcp@ietfa.amsl.com>; Fri, 7 Oct 2016 01:52:07 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7F9712944D for <multipathtcp@ietf.org>; Fri, 7 Oct 2016 01:52:06 -0700 (PDT)
X-AuditID: c1b4fb30-f60a598000000cb2-b5-57f7623439dd
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by (Symantec Mail Security) with SMTP id B3.C7.03250.43267F75; Fri, 7 Oct 2016 10:52:05 +0200 (CEST)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.66) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 7 Oct 2016 10:52:04 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=DBLb2CbTkMgsPoY14wKf9rNrAS2l1rcgZkD5l8TDKvc=; b=lUGdKDkSN6RGH5gT2sa7R7LYJz5zDTq+75Dz9sExgDWKmQqXewpHTVY42QhXUxdQRHA/CoWqbW7D1Zz7c3eNub3xKZxL1XZt77jn/eAy0Om8RFKjr3m1DFnvTLQHQiviTDeZ+WIQ37T4R7OOY3c/RCbT7aI1c4f0cRTLqok6weY=
Received: from HE1PR07MB1258.eurprd07.prod.outlook.com (10.164.51.144) by HE1PR07MB1257.eurprd07.prod.outlook.com (10.164.51.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.5; Fri, 7 Oct 2016 08:51:59 +0000
Received: from HE1PR07MB1258.eurprd07.prod.outlook.com ([10.164.51.144]) by HE1PR07MB1258.eurprd07.prod.outlook.com ([10.164.51.144]) with mapi id 15.01.0639.017; Fri, 7 Oct 2016 08:51:59 +0000
From: Robert Skog <robert.skog@ericsson.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "philip.eardley@bt.com" <philip.eardley@bt.com>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: potential MPTCP proxy charter item
Thread-Index: AdHxWbUCMvV2F7dASMGmgM35ml/5/QvDnYJgAANoGMA=
Date: Fri, 7 Oct 2016 08:51:59 +0000
Message-ID: <HE1PR07MB1258C6846E497208C7E6935B8BC60@HE1PR07MB1258.eurprd07.prod.outlook.com>
References: <c96a67008ee045dda304a983cfb3de73@rew09926dag03b.domain1.systemhost.net> <787AE7BB302AE849A7480A190F8B933008E3DDE0@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933008E3DDE0@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=robert.skog@ericsson.com;
x-originating-ip: [192.176.1.84]
x-ms-office365-filtering-correlation-id: 2093ecc4-c416-4a46-808f-08d3ee8f3322
x-microsoft-exchange-diagnostics: 1; HE1PR07MB1257; 6:25Y8MZpKikVerqUDjy1j9Ghiax/JbwwHID6DwRTfsMh42UnWpo4h7nTiwn7QoX4QKom9PCTqCZYe47kF8chHtugDUoczUP0G2s1gMrzotzWWWIph6Ydj4YIGE0RTXgFa+hYuAz14kDU8VpPyyS/c3p42VXtxn7v2fexVmnwbK0nyQQjS1Vz6K2Kiyn11cDgqVWMC7HnnxIJ67hasn2KE2RnWa/0sbpi5xu8mntF+4/Wa/Zb39ce52Jsx9+C0wneCfN3mv2otJV8hVdPcFR6Zm1fmGCeYLhJnaLAatICup8ZX/OZpXiFwitXC865tPepl; 5:RfKdGi37et7iXOi9T92/MOokla+9N/zdMOLBcKq6Z0NGaGIyh9izxZrsqP540FADin3rTdowAZIFkN6514EJDg2mdb3dXoJKpi2f+CgDuIXu2M3xP5GGHXIHfrKc6otRam03Tjm+OYcfekbrlqvP5g==; 24:mldLDoJlo3tmwGfcwNyh4D6mD2LZGG6xfZGuBMtTCKMdQW0bzD2vrTwdjX+Oj/YWUOD5E0P6oeTCIieR3f4i0R0jSmAC7hHrX7fcge6XNGY=; 7:MSeDfNtkT309La5q25wQGi1Md1dODhYki0MsRPTzPP5dqbcxyXdf2Xhhuf/QvDV9q36jt4jWLdU5CxWmEtUmETXil083K460S+WsnMxpdtd1Fzu++NorsC/42ePl1TSuNRuFTWYEB45rFxNvPbltJtxZHSdBf1Ieb+aphQoOeNQDS1elHHJvHAUWOcKxsQS7pCfZl6tbxfFr2AUgcSTdOiiNebWGfWSSIb1Qjgb9AyR2EKSvRyKMnNxXenfJa4ZqUGQDJCNPa4zP03PEiM/oXq9Vo85aiK9WRvDcEDGXOQrNFuTOtLXmjLRCzfGp7zyB
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:HE1PR07MB1257;
x-microsoft-antispam-prvs: <HE1PR07MB125715DD1FD72BEFEFD773298BC60@HE1PR07MB1257.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(146908506813832)(18271650672692)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046); SRVR:HE1PR07MB1257; BCL:0; PCL:0; RULEID:; SRVR:HE1PR07MB1257;
x-forefront-prvs: 0088C92887
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(189002)(199003)(790700001)(6116002)(74316002)(87936001)(189998001)(97736004)(19625215002)(5001770100001)(107886002)(11100500001)(7736002)(7846002)(3280700002)(105586002)(106356001)(92566002)(3660700001)(2950100002)(19580395003)(19580405001)(122556002)(50986999)(76176999)(54356999)(9686002)(19300405004)(66066001)(101416001)(16236675004)(2201001)(68736007)(102836003)(3846002)(86362001)(33656002)(5002640100001)(5660300001)(2900100001)(15975445007)(77096005)(8936002)(586003)(7696004)(76576001)(81166006)(10400500002)(8676002)(81156014)(2906002)(2501003); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB1257; H:HE1PR07MB1258.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HE1PR07MB1258C6846E497208C7E6935B8BC60HE1PR07MB1258eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Oct 2016 08:51:59.2903 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB1257
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SfSyVcRTH+93nee59qLv93Lyc5I+6tTJySZRZS8lMf/RirV2jVhfPMFx6 LpZa665hIaOSMIkl99I1L5mXRctVC63JCJnXebuYGOZlmuXenzb/fc75fs85v3P2YylJLWPL RijjOF6piJIKzem8gHpvJ/fgNblLp6tH6/ykyGP5fZ/Qo7RCi85TfikrLwR+JSUbAr+kqXbh NSrQ/GwoFxWRwPHO5+6Yh89+8o9tDLuXXlkkUqOtwDRkxgJ2A32hAaUhc1aCKxGM5/ZSJPiG oEX/WWQMaJxBQd2UhiFKtgDerg7RJPiKoL76CWNsJsQnoLq40uSyxBoEr7K6aaOwHztDQ9VP oZEtsQvUZDbtsCcYCipNTOOj0LjabGokxjfhR1+rkEzQIehantl+Fcua4WAYznM3ehC2hrUO ncDIFLaBgYk3ArIRhpKmToqwFcyMbzHEHwQfF8eFJH8IZtPVO3wZJtI3THsC1otgOClDRARf 6NCN04QjQVs4wBAOgv6UHEQKGhAU/KraMdlB69wSTYQ/DGxkpJgqJJgDTUUyIqewhaGe1B22 A8NgM5OF7PN3bUE4BrpXSul80zUsoD1vgiZ5GfS/zBYSdoTS4jmKsBPkbunp3fkiJCpHVipO FRwd5uoq4/iIEJUqRilTcnE1aPsvtdRuujSgmekLeoRZJN0nHg1YlUsYRYIqMVqPgKWkluLk W2tyiThUkXif42Nu8/FRnEqPDrK01EZ8umxELsFhijgukuNiOf6/KmDNbNUo//d8guMXGDkW UrCoPn439bF0ocvCwcf3xuipCYPuSBv9PXVp3e1M/IKt64Ox5HJ2U11m5ixLzTx8fezSRXvt 4jtF0cPelCyDp4+Gfy320vb8jWzfnCp/+rzuirfPM+Uez8EQm6szB/bS5X25q4PgT0/mTHut L2y2PfKw/iAZrZHSqnDFSQeKVyn+Ad0ZKE1HAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/QUBTGjKtkIENztUZWNZwJC0biK0>
Subject: Re: [multipathtcp] potential MPTCP proxy charter item
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 07 Oct 2016 08:52:11 -0000

Hi!
I agree with Med. Hope we can resolve the charter discussion.

Cheers,
/Robert

From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of mohamed.boucadair@orange.com
Sent: den 7 oktober 2016 09:08
To: philip.eardley@bt.com; multipathtcp@ietf.org
Subject: Re: [multipathtcp] potential MPTCP proxy charter item

Hi Phil,

Please see inline.

Cheers,
Med

De : multipathtcp [mailto:multipathtcp-bounces@ietf.org] De la part de philip.eardley@bt.com<mailto:philip.eardley@bt.com>
Envoyé : lundi 8 août 2016 11:50
À : multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
Objet : [multipathtcp] potential MPTCP proxy charter item

I had thought a potential charter item could be something on the lines of:

<Experimental Extensions to the MPTCP protocol to enable an MPTCP-aware middlebox to act as an MPTCP proxy for an end host, which runs TCP. One or both end hosts may be MPTCP-unaware, and the MPTCP proxy(s) is (are) not necessarily on the default routing path(s). The working group will also detail, in an Informational document, the use cases /deployment scenarios and the operational considerations.>



[Med] I would like to see the charter includes the following; "The working group will also edit Network-Assisted Multipath provisioning documents. In particular, the WG will specify DHCP options and RADIUS attributes for MPTCP."


However, if I get the discussion right, this is not quite right.
* assume a controlled environment (to avoid a problem where the message reaches the 'wrong' proxy) (IETF usually prefers generally applicable protocols)
* assume some (?additional) 'header swapping' protocol and a new signalling protocol (not an mptcp extension - so probably in INTAREA WG's remit)
[Med] IMHO, it is not odd to document in the mptcp wg how a Network-Assisted MPTCP solution can also be applicable to other protocols (UDP in particular). This work can be done jointly/closely with other WGs. The important point is whether there is enough interest from the mptpcp WG members to work on this.
If the above is roughly right, then I think some extra work is needed before we can get a clear charter item. Can some of the work that isn't mptcp extensions be cleanly separated out? Can you be clear what deployment assumptions are being made (and preferably reduce them, so there is wider applicability). Personally I'd also find it very helpful if the plain/transparent 'merged' draft could try and follow the guidance about protocol models in RFC4101 (personally I found the plain mode doc difficult to understand).

Thanks
phil