Re: [multipathtcp] MPTCP Schedulers

Olivier Bonaventure <olivier.bonaventure@uclouvain.be> Mon, 18 February 2019 09:42 UTC

Return-Path: <olivier.bonaventure@uclouvain.be>
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 A8907130EF1 for <multipathtcp@ietfa.amsl.com>; Mon, 18 Feb 2019 01:42:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 (1024-bit key) header.d=uclouvain.be
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 GdF6vEMlR8O2 for <multipathtcp@ietfa.amsl.com>; Mon, 18 Feb 2019 01:42:15 -0800 (PST)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-he1eur02on0727.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe05::727]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFBDB130EEF for <multipathtcp@ietf.org>; Mon, 18 Feb 2019 01:42:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uclouvain.be; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=smdGxscsI88jdETcYNkIskqUhLA1QZ6pkFUGIrJWgCo=; b=BkmKp9sBB1dk0b3xITyu/dw4WWOzqRPliTN+S6Zv1QDMZqAg621X0I4taMt4603NOoftf9ny6IUgOCI5e2HWqLpjhJp/5nBUz/rZxJHhL/NH4Z5+6fuNnrfeFVEd+lDIxvoCCxSAdaTX60gXlF/ImyQPnryh3j9xdwTDsi9tbuU=
Received: from DB7PR03MB4170.eurprd03.prod.outlook.com (20.176.232.207) by DB7PR03MB4267.eurprd03.prod.outlook.com (20.176.233.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1622.19; Mon, 18 Feb 2019 09:42:11 +0000
Received: from DB7PR03MB4170.eurprd03.prod.outlook.com ([fe80::3d22:a229:1259:ad1b]) by DB7PR03MB4170.eurprd03.prod.outlook.com ([fe80::3d22:a229:1259:ad1b%5]) with mapi id 15.20.1622.020; Mon, 18 Feb 2019 09:42:11 +0000
From: Olivier Bonaventure <olivier.bonaventure@uclouvain.be>
To: Vladimir Olteanu <vladimir.olteanu@cs.pub.ro>, multipathtcp <multipathtcp@ietf.org>
Thread-Topic: [multipathtcp] MPTCP Schedulers
Thread-Index: AQHUxTRoWIUwCTLGU0CsNE7Slx9UQKXj20MAgADhEwCAAJWxAA==
Date: Mon, 18 Feb 2019 09:42:11 +0000
Message-ID: <ecc9b731-c5c8-b479-1ec8-b7f9caa871ad@uclouvain.be>
References: <a939bc37-16ed-9d8a-15d7-16dfec630290@cs.pub.ro> <c8daed86-e949-5edd-20c9-d7920d5ff9a6@uclouvain.be> <83ef4bdc-f748-88f4-b7f8-21bc4bf381dc@cs.pub.ro>
In-Reply-To: <83ef4bdc-f748-88f4-b7f8-21bc4bf381dc@cs.pub.ro>
Reply-To: Olivier Bonaventure <olivier.bonaventure@uclouvain.be>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LO2P265CA0137.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9f::29) To DB7PR03MB4170.eurprd03.prod.outlook.com (2603:10a6:10:13::15)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=olivier.bonaventure@uclouvain.be;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:6a8:308f:2:358a:3d85:554a:48c6]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b54895cb-ca44-4d1f-826c-08d695855b33
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:DB7PR03MB4267;
x-ms-traffictypediagnostic: DB7PR03MB4267:
x-ms-exchange-purlcount: 1
x-microsoft-exchange-diagnostics: 1;DB7PR03MB4267;23:Rnd+aVfvhuDMOSiF/LulL6hfJJGihVoK+dJy6cCXSjAK+xBUZrMrTsFGCTuaG4EQfeHUKN1r6O6dKop67mu0pw5EjnfbxanaiE59txppUlMVTO4O/hrNjF4SGAfAx4Cne1ddVOds5VfI3NbZ9KdkVtyBZn1Lj10qk8Cn5ndnAUuTDSeN3R96WYQH7zvXPxobkIhi4IxlPWV5oSin7dOpkBJNymuYJbIgc+/YlpZr4tT41SzhxS4GUHaFK1KxI/DKRO/+kwqztiMk+HiS8wqy5c0m1FiW0vmMK3uAqv0cU9rAmNo5/vwZ1NSIdvWDq2Xg7mxIAR/rwietBaku5o6z+0uVeHx0p35SSIKWGy4L2ETai70J7Zs5SOMTq0Lcs1PgeNTnB4dHpmVyvi2S8iAP9oMHg6VKRjeWgQKALdj1TPOj6mDUWNkxyO2jRF0SFKmtdVuVp20Ian+cH3bYTw5ozi4navbROIjeVnbGN20bGORlY1PjFvxLprzAWEMK+fgavSD51f0gHGUIC+64CYfnp6oULxBmM8zoJGG6eWMrhomgEvJYIdHfxnszGqsAPNKWoNI2I7NWOCK/jNdDo+hJbElH4asfEeKpNUNyWUy4ITyZbZ5ucwY3O1sX2nnkodO/jWFDpglmEHXsD+l7f2BapogvmKV1gSGbzPT875O0CgsbSDg/EN8sJWLXrd28GC28LvNGFPUcIxMvRhrYKO8A0ra/9TUoA5ZxWrV6nBULgKCbgmMhj2cC8TIiBte/dqiwacr58q7shAOu9xfky9daDS9H36t56ntcERfZk1qBOPKBhOGLDP/pPSkoSCBbcpdpDDxA8Z2fpWTyBgTTgdRpgbw7edT2uDNCVIVUDXekucAhZbXsG/WS6qJvF+jIR/z/y0lewcotqOIPk5cYruY134HgssJv17nUnfX+1dZmOLvspSF/lbYJ5R1cVEMondlHbPIWoT/EPHzcuyTRdxTqVuSUkGiFh7Izzat8xNH81OOO0lz2aNYrPQF14eduIb4MrKrA3jVjjtLxnQM2XqiC9OuUTcs7eJTOV08etCzsoEvlAvE7yGWF0Vcvw9BKHd3ZQfOLGJjVPesxdvC5A/4cl4YArKZBc07lMXpv5qd0VjhIElgK/1+uG7Z+M2i43WLOR1SfhbDtBfgicFKOWEeq1EYpqwfTm+/Q9TVFEMBkYB+dlAf9yFH5vic7NB/MOg4Uq2jLeUAEz2P34nRwnDwDeyTi6E1ykzjCMm3J6OH6WQspW4dxipTn5jLumELkF3THYW0TmF9rZy81/Ag4osf9+J/PYyAvGbBZ3C2S3jp7V50=
x-microsoft-antispam-prvs: <DB7PR03MB426763FA7D0AD76935FAF83E86630@DB7PR03MB4267.eurprd03.prod.outlook.com>
x-forefront-prvs: 09525C61DB
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(39860400002)(376002)(366004)(136003)(396003)(189003)(199004)(51444003)(6116002)(76176011)(102836004)(6486002)(186003)(52116002)(71200400001)(8936002)(71190400001)(99286004)(6246003)(6436002)(43066004)(31686004)(36756003)(229853002)(316002)(97736004)(786003)(53936002)(68736007)(86362001)(14454004)(14444005)(256004)(46003)(386003)(6506007)(7736002)(25786009)(81166006)(81156014)(305945005)(8676002)(6512007)(106356001)(105586002)(486006)(5660300002)(478600001)(446003)(31696002)(110136005)(2616005)(6306002)(476003)(3450700001)(74482002)(11346002)(2906002); DIR:OUT; SFP:1102; SCL:1; SRVR:DB7PR03MB4267; H:DB7PR03MB4170.eurprd03.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: uclouvain.be does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 6M4YtoPfMpGW6gZXFJfg9XQB6xc72TKhry6nLPXi7qBJmmMv7Mx0qUG9Kgy/cZoIXcq8Gp8psirII1q/hpZequk2AXoAdOdU2gJFtWSq/m2VWuxdxiksam4ArqKZ8MyFUVaxSTIWKu3BVknVPzE4xkwA+8IHXePDOxq7Y3qi3fbFwAiTTA5MOtslGOfet8SrpAhZKKtlyxhEBEFd+WpJQQLvg31eduPx6iDPSKuogsDpNzKJHL1CwOz7sNIcPrsHXukksQFKbtPmoGzhHK7rjF5KjEhKsjuHbJc6pVNx0h6J06HxXSFF3oE3+uNFvMxspxJmGRQ/oprjItlAxviLh42vc9BXt8I6q0VWEkOYvL5QzeeBrjIE9vopEMHQk/hJyMdChPaB+jS/lPzFzR4L2b2dKz/Ou7aqaGqM6VwEQKU=
Content-Type: text/plain; charset="utf-8"
Content-ID: <B346BE80411F6A42A25636D1D9099D3C@eurprd03.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: uclouvain.be
X-MS-Exchange-CrossTenant-Network-Message-Id: b54895cb-ca44-4d1f-826c-08d695855b33
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Feb 2019 09:42:11.1654 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-id: 7ab090d4-fa2e-4ecf-bc7c-4127b4d582ec
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR03MB4267
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/dbOAfPKVAlV6HSjSrin38np8ND0>
Subject: Re: [multipathtcp] MPTCP Schedulers
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: Mon, 18 Feb 2019 09:42:18 -0000

Vlad,
>>> I'm trying to tie up any loose ends in the SOCKS 6 draft. There is some
>>> functionality which lets you change the MPTCP scheduler used by the
>>> proxy. The available schedulers are basically the ones available in the
>>> Linux kernel implementation.
>>> (https://tools.ietf.org/html/draft-olteanu-intarea-socks-6-05#page-20)
>>>
>>> Do you think it would be worthwhile to standardize the MPTCP schedulers?
>>> I think an informational or best practice RFC would be useful.
>> I think that this would make sense, but we could also encode the
>> requested MPTCP scheduler inside an MPTCP option instead of putting it
>> in an application level message as you propose in your draft. The
>> advantage of using MPTCP options is that the same solution would work
>> for any application.
>>
>>
>> Olivier
> 
> Hi,
> 
> I agree that it is worthwhile doing it at L4. As far as SOCKS is 
> concerned, this would also open the door for the client controlling the 
> scheduler used not only by the proxy, but also by the remote host.

Agreed

> I'd argue that being able to do it at the application layer is also 
> useful, even if your proposed option gets standardized. The scheduler 
> option will not fit inside a SYN + MP_CAPABLE + TFO (along with SACK, 
> TS, MSS and Wscale) and you'll have to send it 1 RTT later. (In fact, 
> not even the TFO option will fit if the cookie is large.) OTOH, there is 
> on such pressure oh the SOCKS option space; you've got 16K to play with.

The scheduler is not that important in the first rtt since you only have 
one subflow at that time anyway. I agree that SOCKS has a larger space 
to encode options, but after the SOCKS exchange you cannot send SOCKS 
data anymore. This means that with a SOCKS solution you can set the 
scheduler for the entire connection, but never change it during the 
connection. An MPTCP option could be used at the beginning of a 
connection but also at any time during the connection lifetime


Olivier