Re: [multipathtcp] MPTCP Schedulers

Vladimir Olteanu <vladimir.olteanu@cs.pub.ro> Mon, 18 February 2019 18:00 UTC

Return-Path: <vladimir.olteanu@cs.pub.ro>
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 D7467130F65 for <multipathtcp@ietfa.amsl.com>; Mon, 18 Feb 2019 10:00:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 aSbWkSurIKoI for <multipathtcp@ietfa.amsl.com>; Mon, 18 Feb 2019 10:00:34 -0800 (PST)
Received: from vesa.cs.pub.ro (vesa.cs.pub.ro [141.85.227.187]) by ietfa.amsl.com (Postfix) with ESMTP id DC204130F63 for <multipathtcp@ietf.org>; Mon, 18 Feb 2019 10:00:33 -0800 (PST)
IronPort-SDR: lXbDK2RY1LWjdBklSvhMi8DjzoOzIB4ffg+Svm8jRmsGHLLzvRG+TkY7Q4rB1/yXph7vJCYIDV fx55twCv1SQg==
IronPort-PHdr: 9a23:1AM9VxOXwRcYfODEqxol6mtUPXoX/o7sNwtQ0KIMzox0Kf7+rarrMEGX3/hxlliBBdydsK0UzbeO+4nbGkU+or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6aijSI4DUTAhTyMxZubqSwQ9aKzpf/6+fn0pnecwxOiDenVp1oshCzogjX/p0fhYZyI6A9xwHhrGFPduFTym5uY16eyVK0wcOx4p9u6Wx6vPQo6cNGTbjgcuxsSrhZEjUrKSY/48viqxTFURaV61MBWWERjwRBAg6D5hysGt/asjH7rfZ6wCnSBcT/Vrs0EWCp965iUxTo3XtfPiYh9GyRgct1pK5eqQiq4R1y34CSZ5uaYqlQZKTYKO0eTGZAW8dLHwtFHo61aZZHW/QFNOpZqojn4VwKsRa3AxSED/ip0iJCwGXxi/5pm989GB3LiVRzV+kFt27Z+ZCsbP8f
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2AOCwAs8mpcjAPjVY1jHAEBAQQBAQcEAQGBZYJugQCELYh5jGYtmhI4AYRAAoQSOBIBAwEBAgEBAgETAQEBJliCOgUBIwEGgmEBAgMjFUEQCxgCAiYCAlcGAQwIAQGDHIF3q3WBL4VEhGWBC40QP4E4gmuFAYMJglcCiXWZRQcCgjgEkBQfil2IHYpBinaITjcgKYEuMxqDYIInDgmOID0BAYE2AQGNUoFfAQE
X-IPAS-Result: A2AOCwAs8mpcjAPjVY1jHAEBAQQBAQcEAQGBZYJugQCELYh5jGYtmhI4AYRAAoQSOBIBAwEBAgEBAgETAQEBJliCOgUBIwEGgmEBAgMjFUEQCxgCAiYCAlcGAQwIAQGDHIF3q3WBL4VEhGWBC40QP4E4gmuFAYMJglcCiXWZRQcCgjgEkBQfil2IHYpBinaITjcgKYEuMxqDYIInDgmOID0BAYE2AQGNUoFfAQE
X-IronPort-AV: E=Sophos;i="5.58,385,1544479200"; d="scan'208";a="3195378"
Received: from mail.cs.pub.ro (HELO vmail.cs.pub.ro) ([141.85.227.3]) by vesa.cs.pub.ro with ESMTP; 18 Feb 2019 20:00:30 +0200
Received: from localhost (localhost [127.0.0.1]) by vmail.cs.pub.ro (Postfix) with ESMTP id 78D031A6014E; Mon, 18 Feb 2019 20:00:30 +0200 (EET)
Received: from vmail.cs.pub.ro ([127.0.0.1]) by localhost (vmail.cs.pub.ro [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id jDmBs2fD5DQK; Mon, 18 Feb 2019 20:00:30 +0200 (EET)
Received: from vmail.cs.pub.ro (localhost [127.0.0.1]) by vmail.cs.pub.ro (Postfix) with ESMTPS id 567331A60153; Mon, 18 Feb 2019 20:00:30 +0200 (EET)
Received: from [192.168.1.70] (unknown [84.117.93.208]) by vmail.cs.pub.ro (Postfix) with ESMTPSA id 447A41A6014E; Mon, 18 Feb 2019 20:00:30 +0200 (EET)
To: Alexander Frömmgen <alexander@froemmgen.de>, Olivier Bonaventure <olivier.bonaventure@uclouvain.be>, Christoph Paasch <cpaasch=40apple.com@dmarc.ietf.org>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
References: <a939bc37-16ed-9d8a-15d7-16dfec630290@cs.pub.ro> <20190215180722.GR1880@MacBook-Pro-19.local> <41d2eef4-67e8-62a5-5d05-b6248d2293e5@uclouvain.be> <1MKd92-1gcaMb0Y7I-00Kxa3@mrelayeu.kundenserver.de>
From: Vladimir Olteanu <vladimir.olteanu@cs.pub.ro>
Message-ID: <386d0bef-8eb0-b3ee-44bd-4ab17147be79@cs.pub.ro>
Date: Mon, 18 Feb 2019 20:00:30 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <1MKd92-1gcaMb0Y7I-00Kxa3@mrelayeu.kundenserver.de>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/ZArNuxtxiMj4coAgnSxHirjmxTk>
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 18:00:37 -0000

Hi,

On 2/17/2019 2:35 PM, Alexander Frömmgen wrote:
> What level of scheduler standardization do you consider? While an 
> informal description of the scheduler behavior should be feasible, I 
> have the feeling that a detailed specification of the scheduler 
> behavior is not possible, e.g., i) details of todays scheduler 
> behaviors emerged from the dependencies to the Linux Kernel (round 
> trip time is calculation, packet queues), and ii) intuitive 
> descriptions, such as "redundant“, are very imprecise (prefer old or 
> new packets for heterogenous subflow environments?). [0]

At the very least we should write a general description of the three 
algorithms that are available, what to expect from them and in which 
cases they are best suited.

In the absence of such a document, I'd have to include said descriptions 
in the SOCKS draft, which isn't the best place to go looking for such 
information.

Vlad