IETF Logo Mail Archive

Re: [multipathtcp] MPTCP Schedulers

Olivier Bonaventure <olivier.bonaventure@uclouvain.be> Sun, 17 February 2019 10:20 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 BB752128CF3 for <multipathtcp@ietfa.amsl.com>; Sun, 17 Feb 2019 02:20:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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] 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 uVPZTt23GZso for <multipathtcp@ietfa.amsl.com>; Sun, 17 Feb 2019 02:20:54 -0800 (PST)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40117.outbound.protection.outlook.com [40.107.4.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D5F5127AC2 for <multipathtcp@ietf.org>; Sun, 17 Feb 2019 02:20:54 -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=728rTOyExctaOaopbwEM7y437xSR+rGFmZDAV8rJVUk=; b=Im8Gq5fVCEqyansx58N4ugAgvU6QvlqGd1mYwsncilctHIMIkY6gPL1FEFvbQlTnPYuHFd431nU9uKz2s/Gs+0bfd8wIWBDpIaKA6IJwRWJsYW9RaZVrGjcttV/vV1+WifV+6i5G461oSLSfae58G+bVVIBxBSppX3NBGuh5Kbg=
Received: from DB7PR03MB4170.eurprd03.prod.outlook.com (20.176.232.207) by DB7PR03MB3820.eurprd03.prod.outlook.com (52.135.135.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1622.19; Sun, 17 Feb 2019 10:20:52 +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.1601.023; Sun, 17 Feb 2019 10:20:52 +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: AQHUxTRoWIUwCTLGU0CsNE7Slx9UQKXjyn8A
Date: Sun, 17 Feb 2019 10:20:51 +0000
Message-ID: <c8daed86-e949-5edd-20c9-d7920d5ff9a6@uclouvain.be>
References: <a939bc37-16ed-9d8a-15d7-16dfec630290@cs.pub.ro>
In-Reply-To: <a939bc37-16ed-9d8a-15d7-16dfec630290@cs.pub.ro>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: AM6PR0202CA0027.eurprd02.prod.outlook.com (2603:10a6:209:15::40) 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: [2a02:2788:484:2c2:45df:e8a1:b2b3:af63]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 69eb6231-91ad-40ab-1743-08d694c197d8
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:DB7PR03MB3820;
x-ms-traffictypediagnostic: DB7PR03MB3820:
x-ms-exchange-purlcount: 1
x-microsoft-exchange-diagnostics: 1;DB7PR03MB3820;23:qNkPBQVNa/1uIiix/T4I8pKyPrM7cu8qj7J2E+3K3XxokUi8YTeT76Cf5vOICeBI9BhZglZwr3zIsjMdXBjytHGICT1WateBKcv3ye6XIJamYGhkB7V++Snd0o+oPx2tmd90nwtrPTNVbblrRqQfQqe4NuywEJIPTod2olzgBss/Wozyy3pWktMS0HEa18kY42qKLNiHLr2JYMtshp0uhoNFg8aSbMWHPWfkBx9+EdauPiBVJR5fc7eYKRscs33zMD8G3LIuELax2/fejl9fTs/+57Gyp5kpmL5b0B+ZXMVCe3QLa4Kllvwq48vPS2UmGgw/Ef0D6bNTzzzrfzymMzaeoTPDSGeL0s/E+JvpkFPdBWBqeweEcRr+LDpebiljQ1e/F0u2PRxp080OYIXwok9BveCoxqnuMiSKYoBfMRM7dVKXje6DKn7tgzoT9w23XCELr/x2BSzb53qHg/QH2QLpVdtbf2kIHLAtDNbWj+TuGDE+rg9XYBz+/q66fAX+N938WBw2G1rZFLDdfxFE2bGXwxmLu3okIszapb5UmDUSWLtL5RHQ1Jyea/Kl5RnZRWNRGv/W0vvhT+utABJELEs2+7XTMDifalAL2p84N9yiFUJuuAc+Hoox0sYxe6a8ymum2SOZPhIzoD0Wflo5XoMoXMeQtBb1DO225cv7ozvQ20BZ5EcGs9wEreuosOy4hJO2Gl++1PAbQt307t+O1iZll3CIRZcvBveq31d7/tPgA68lLjnrd9aokt/3LOnlENjqxXBI9Ne2ReDSXyHN4pDcHXggS32ZJSyoNkgY9XaEH5ZDP9AuH0/wCvlxVRwvFohzAqZlQNPQhyj1kjwFLccAlFjen8or8XpnxuIUDkgEsS61kXnazkTHCtxagGPTZfb342vxA2zZh1rTOuGzroDom9k7tRXlA0wVH6GWaCIvI/ivY6HjU3xWlAGgeAK+Pv4wQyzMcP+KaatI5LlakhrFBhtJyN68I2x4TWBG4Z9YKPmWT0N/D3Pmci9DWBKH31mqqjfhBg97tNS7le7HgogoEgrRUkPMIknw7UJouZTqZLu9HYNPj0sC1y2N8yDPPagwURUHY+add2NZWGIFM/iZ1kFgVCh6hAlIDmrqx6coZvkHdIlFIER89mUwubmWjyu17Omw1wd+MIdYszX+IcbbrX1TjpZ5izcQxNUuy/qgW6V2i2GRBZ2d2UC4+wIwvZXfIUCKmHGI6/MtPnhQFXaRUxdZ7inaDZnhO7r5ZYbjw6Gupj384sjWvasK/u7n
x-microsoft-antispam-prvs: <DB7PR03MB382041CBE663AC668BB3C94186620@DB7PR03MB3820.eurprd03.prod.outlook.com>
x-forefront-prvs: 0951AB0A30
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(366004)(136003)(376002)(39850400004)(396003)(189003)(199004)(51444003)(6436002)(6506007)(386003)(110136005)(229853002)(478600001)(8936002)(186003)(31686004)(2906002)(6486002)(105586002)(106356001)(25786009)(102836004)(53936002)(7736002)(68736007)(305945005)(6116002)(486006)(786003)(81166006)(81156014)(256004)(316002)(6512007)(476003)(36756003)(74482002)(6306002)(8676002)(2616005)(4744005)(11346002)(446003)(46003)(31696002)(99286004)(86362001)(52116002)(97736004)(6246003)(76176011)(5660300002)(71190400001)(71200400001)(14454004); DIR:OUT; SFP:1102; SCL:1; SRVR:DB7PR03MB3820; 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: +os/a6XcgAf6/kI1a0mFeVMM3i1sZmhE8CFH6rq6BKsqYOS6ITDsf9AKPb3GAeerIfvh+E3myiWxvJmOuwQVUd5z/dIKZkTivt7UgN0bet5zyUCMnKnqtm479/5DR/ScVrNd+uWGrAV6VcxRqvIofyS5Uon99oNzB5G7gF3mrnakTH0I8m9jxo1Qio0hT53T8wYGQJOdYXEJvj18HrwXsasRxL7XOCJU3HoEqXlJuP4PnHzdyNWVH4evqfPPDdHqKbA3xp7R9JbvxldDtvT6h2WAQStRVjroevHWFb/Jq2gvnHi5+7iUiKHiZFBZ0NivmzLM+ogcTmJAMHrvkOuvFkmguOoJjAewy8+PGUmY1ZjVMrBDC2TygSV+STuIU/Nd7/drJNZ0krAnFIVb9TNiJN8NJfSNoYZ8cFQxFWm6zM4=
Content-Type: text/plain; charset="utf-8"
Content-ID: <30E23D853E633E41A0E4136E9AA56F72@eurprd03.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: uclouvain.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 69eb6231-91ad-40ab-1743-08d694c197d8
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Feb 2019 10:20:51.5323 (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: DB7PR03MB3820
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/Ul537LXhVGTbMKkj31WF05Rw-2M>
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: Sun, 17 Feb 2019 10:20:57 -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

v2.23.0 | Report a Bug | By Email