Re: [multipathtcp] MPTCP Schedulers

<Markus.Amend@telekom.de> Sun, 17 February 2019 08:08 UTC

Return-Path: <Markus.Amend@telekom.de>
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 05F651293B1 for <multipathtcp@ietfa.amsl.com>; Sun, 17 Feb 2019 00:08:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 JfIb95u0oZhj for <multipathtcp@ietfa.amsl.com>; Sun, 17 Feb 2019 00:08:28 -0800 (PST)
Received: from mailout41.telekom.de (MAILOUT41.telekom.de [194.25.225.151]) (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 ED54F127AC2 for <multipathtcp@ietf.org>; Sun, 17 Feb 2019 00:08:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1550390907; x=1581926907; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=lzPEHppzUlfzPIrdaOITm56I+FOEyCVfepYoJd777Jo=; b=6X6iIfMVtS4J+dj2gU28BF2Yxm/J6gJJ2IGGRoGmT/PLQKkUEo1h8M4z 2J+r8FMak4MOhfIMFFlqM+2DonphD2QUulYT1frnHApqGDOBsvw7ARieF e59+u/kj84wBLWyjnv85WKA9dqx+ZD+4/qnyEMiC/c9Tgoto77FRheNwu L33grib+IOmecWwICn7HhjqxGGcMnAbV1m+jsCIbWNLLDMtDkPTgzaPKW LjDezkKFy0eU0ITuNP+fntzzAl6mdj/OaXsS6Mrqei59y4t9vVFWfK5Bo ZTUtJCvvVxWjC+Pnz9oRPKiB7E6pQLy4LP8CewPVVtZrLsqybnEUzaP05 w==;
Received: from qde9xy.de.t-internal.com ([10.171.254.32]) by MAILOUT41.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Feb 2019 09:08:24 +0100
Received: from he105717.emea1.cds.t-internal.com ([10.169.118.53]) by QDE9Y1.de.t-internal.com with ESMTP/TLS/AES256-SHA; 17 Feb 2019 09:08:24 +0100
Received: from HE101951.EMEA1.cds.t-internal.com (10.169.118.77) by HE105717.emea1.cds.t-internal.com (10.169.118.53) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sun, 17 Feb 2019 09:08:23 +0100
Received: from HE104160.emea1.cds.t-internal.com (10.171.40.36) by HE101951.EMEA1.cds.t-internal.com (10.169.118.77) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Sun, 17 Feb 2019 09:08:23 +0100
Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.21) by O365mail03.telekom.de (172.30.0.232) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sun, 17 Feb 2019 09:08:22 +0100
Received: from FRAPR01MB1170.DEUPRD01.PROD.OUTLOOK.DE (10.158.133.21) by FRAPR01MB1172.DEUPRD01.PROD.OUTLOOK.DE (10.158.133.23) 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 08:08:22 +0000
Received: from FRAPR01MB1170.DEUPRD01.PROD.OUTLOOK.DE ([fe80::9c7c:7db6:7338:e610]) by FRAPR01MB1170.DEUPRD01.PROD.OUTLOOK.DE ([fe80::9c7c:7db6:7338:e610%4]) with mapi id 15.20.1622.018; Sun, 17 Feb 2019 08:08:22 +0000
From: Markus.Amend@telekom.de
To: cpaasch=40apple.com@dmarc.ietf.org, vladimir.olteanu@cs.pub.ro
CC: multipathtcp@ietf.org
Thread-Topic: [multipathtcp] MPTCP Schedulers
Thread-Index: AQHUxTRtmNznkyUNKESV+wHhZbFmo6XhKC8AgAJ2lIA=
Date: Sun, 17 Feb 2019 08:08:22 +0000
Message-ID: <FRAPR01MB11706B85FE652E39F3F737B6FA620@FRAPR01MB1170.DEUPRD01.PROD.OUTLOOK.DE>
References: <a939bc37-16ed-9d8a-15d7-16dfec630290@cs.pub.ro> <20190215180722.GR1880@MacBook-Pro-19.local>
In-Reply-To: <20190215180722.GR1880@MacBook-Pro-19.local>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Markus.Amend@telekom.de;
x-originating-ip: [212.201.104.11]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e15faae0-3d74-40b5-7161-08d694af1602
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:FRAPR01MB1172;
x-ms-traffictypediagnostic: FRAPR01MB1172:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <FRAPR01MB11724CD2593D804DE858FDE2FA620@FRAPR01MB1172.DEUPRD01.PROD.OUTLOOK.DE>
x-forefront-prvs: 0951AB0A30
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(136003)(366004)(376002)(39860400002)(346002)(51444003)(199004)(189003)(478600001)(72206003)(4326008)(66066001)(305945005)(6246003)(71200400001)(8936002)(71190400001)(446003)(3846002)(7736002)(5660300002)(2906002)(105586002)(86362001)(476003)(6116002)(966005)(11346002)(106356001)(486006)(6306002)(81156014)(9686003)(186003)(7696005)(55016002)(229853002)(81166006)(14454004)(68736007)(75402003)(102836004)(316002)(76176011)(33656002)(53936002)(97736004)(52396003)(14444005)(8676002)(110136005)(26005)(256004)(74482002); DIR:OUT; SFP:1101; SCL:1; SRVR:FRAPR01MB1172; H:FRAPR01MB1170.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-microsoft-exchange-diagnostics: 1; FRAPR01MB1172; 23:FUQc3Q2Kzcmr4nZx2KYYqbicL4kJsITqUgGWwuZtr7tVhY8VnVUPvNqXJkZ3KZ5x60IHf6Hn3BXedrzOY+NrgdFH6cjuR5NQbOECBoWZs3zM1iO7LrwhACF5SMUUoRkHrmJrnaxtMLtN9ylniVNLAP5fy5GJUhQbIqyM1RwFkZffhLP9FTSmjC2hcWKsfOjBc984i1bMRuD/+UE/TheCFYYv4xj6pupkXJMqagHpYBsliGo1u6H+nrKmuMjOR2EcM1WfE59ovdM9yQ7XXcvkQcbcH826qeyKukEPG/bafxjH8w4FJmsdDIBUHKTTRtAZW1cEQecZnJ9FFt+LKzEKqcALU/HFANPVD/3wSEhx5mbYepxTEf5sne+94vY/5GgEcSNeJBm7xmYGE7x5s1RNbKflxDsNAIHYoaunYW0oWcp2hQEIgGUHCq2QiTWSPm621e8wRwwkCuy519CECmd2ReU2gj4EJ+60MeONPrWHQ0LfSufi42Tw6n7G6mcKLlq8CU5qeif29r2PYaHyqG1lzi6yJt/YytIaD/aPPc3kZVWBiICfcn9UJr/d4/gXhpxHLT86wRA8eywj/eYRvHP8u87I3xwqf06Q5HVL3pwPDuamqoftQy5Y/SPXP4RM/a7WTNPTy3OrvGB67iSw0FoXOHKbkEVKptJKUaYV2+pRxWgBvzuFHHZZAVQe78ubuTdx0tsnDoVDZw31szc1J/hRSdW9j9/lEKIsVOCgCDOF87rAOrky+bPiHTkkhZOFlxHmdDrT2craF8qr8CGNAQE7OdSQssHuv0XjoxADAHoO0knd8w9EqbO02sI9Dwu/x3WOJijU4TvPh+slyI/bJn7gFOCJEEdAdVntcX4XPGg+iWKgiwZcia4TX977vjJUJ4Jx9M9pD1ucPLAkWL8gwMHNVdMQqHFRMfgVglQ73PJu13Gh4FnEf7FkdYwS5QZuqdIZbPcMGGplWpbaMzr2tvDXXKZGAXduVZSYi132BwB0MWerSoK4a4gTweoCGQpAp1j9wB7thO+jNJfpjJf7tvfsDSZ1FbMq+W2wp8u/5fMplfL2tTfZbIu0isko+3UXpOtlhXsAhvNhP9KUmXpqxu9Y2cwegtxKEcQsweIGX4BKcDGXIl+cI06hdXPpuxJQYxOemf9CrcdophiBznAMndu4ObQX21GM+4yIuCuQi1O4mnrWVM1NoeWa1tj9pSl88NEy41BcvkIteRBZgQsOl5xwUg==
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: hjmF/bOMesxh/8mS4jAPqIST8NI0RGpFp+m6oym84i9R9uEBu+Ja5XYfHFnvWr1fzVDkA8GCSEGGxlbGQWwrDhYwIUa4zJJj0pw1uiqIPmixEZulYJrbmJ5VkFcf65lwtGzWBpbIfNVnHk3uwWAB/TEI/wrE/QWP6GViOatxbVsgYLb4j5XNlW0wz3F0BXeke/koHnduLoYd+QStNh4SX8htSTQ9KrJ3xKswT0UL9whj+s2ovg5s4pdgGD3r7rs2WSeYkUVbf7k9i0cip/GfwT8xHEvxDen7Eitr1E3wkU1RRH2/sNG0I2oq2YxU9Nw27ambHgqiAE0eK5qm1eoCmRoRPQolkHnKvcuKZyr4p29/0HITeE4BkAcl56LRC5MICxSQ9LYGepO4vWi7/j3b97sO8JtESlBwSmdAVx139n0=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: e15faae0-3d74-40b5-7161-08d694af1602
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Feb 2019 08:08:22.7919 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRAPR01MB1172
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/TcXhLJLEI73-EONmFKFpdOYWnAQ>
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 08:08:30 -0000

Hi Vladimir, hi Christoph,

> On 15/02/19 - 15:42:55, Vladimir Olteanu wrote:
> > Hi guys,
> >
> > 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.
> 
> In general, I think that would be good.

ACK

> The tricky part around MPTCP is that
> the client has no direct control on the server's scheduling behavior.
> The backup-bit provides some amount of control but it's not fine-grained
> enough.
> 

ACK, but that's also true for the other way round from server to client :-)

> Standardizing the schedulers or providing a more explicit "API/messaging"
> from the client to the server about the client's policies would be very useful.
> 

ACK, even other scheduling algorithms which are not part of the reference
implementation are worthwhile to consider. In particular it would also
support the current 5G ATSSS standardization, which most probably relies on
MPTCP. Standardized or at least documented scheduling algorithms would
make the traffic steering behavior more predictable across different vendor
implementations.

> That way, clients can connect to "any" MPTCP-server and make sure that the
> server's behavior is respecting the client's policies about data-usage on the
> different subflows.
> 

Half ACK :-), see comments above. From a 5G ATSSS view I would assume the UE
to be a client and the MPTCP Proxy in the 5G core to be a server, right? Than it
should be possible to exchange the preferred settings in both directions. But
independent from 5G I think we should not limit such an MPTCP API in one
direction. 

BR
Markus 
> 
> Christoph
> 
> >
> > Cheers,
> >
> > Vlad
> >
> > _______________________________________________
> > multipathtcp mailing list
> > multipathtcp@ietf.org
> > https://www.ietf.org/mailman/listinfo/multipathtcp
> 
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp