IETF Logo Mail Archive

Re: [multipathtcp] MPTCP Schedulers

Alexander Frömmgen <Alexander@froemmgen.de> Fri, 15 February 2019 19:45 UTC

Return-Path: <Alexander@froemmgen.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 60531130FFC for <multipathtcp@ietfa.amsl.com>; Fri, 15 Feb 2019 11:45:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 EjEzXTOIOAoN for <multipathtcp@ietfa.amsl.com>; Fri, 15 Feb 2019 11:45:56 -0800 (PST)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E9BC130FED for <multipathtcp@ietf.org>; Fri, 15 Feb 2019 11:45:55 -0800 (PST)
Received: from Galaxy-S6-edge.local ([185.45.239.33]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.167]) with ESMTPSA (Nemesis) id 1M2xjg-1gvptL3gtg-003QSQ; Fri, 15 Feb 2019 20:45:44 +0100
Date: Fri, 15 Feb 2019 20:45:39 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <20190215180722.GR1880@MacBook-Pro-19.local>
References: <a939bc37-16ed-9d8a-15d7-16dfec630290@cs.pub.ro> <20190215180722.GR1880@MacBook-Pro-19.local>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----V95ARYOV1P9FHNBATRC2SNNB1UUFHZ"
Content-Transfer-Encoding: 7bit
To: multipathtcp@ietf.org, Christoph Paasch <cpaasch=40apple.com@dmarc.ietf.org>, Vladimir Olteanu <vladimir.olteanu@cs.pub.ro>
CC: multipathtcp <multipathtcp@ietf.org>
From: Alexander Frömmgen <Alexander@froemmgen.de>
Message-ID: <13538FA7-7289-487F-8283-57F68D9258D7@froemmgen.de>
X-Provags-ID: V03:K1:Ksu3XJKd6WmM5tVOD6HLtvTIXwx6q0ED6hZCLFwfevVNusGwxtm 4dnAYQNM4QwNxMebSlGZdzTvT6a8MioCn2nyfmMm9layPlyyUtfJXGdhNNWNR3IdBLEWS+K /1zxMdnoD6y38oVKc2YNuwmSv77WjkNDufP53gHqSIu3cgFtevYTlQDMWOMa4vsDGOMCCaw CtwhZhIpCSvae0Q86G08A==
X-UI-Out-Filterresults: notjunk:1;V03:K0:6gIH9hs6sBw=:O/aRMUellDy7SEM4uf6x86 Ov5ajPnXKv8PrESyH7uDLD05dhww9qgnsjypF7UQFdrEmW/0HAZaEUJdzh5+4kZp9QE5rbNoj tGHYpfhAa6fLwMI4CO53tNkcXE6T90mNedB1miO91tFnPeMg70D6nVCjRAFd3VkVPUZVRlJVg 14V3LI49R0UJFH9CQa/ATJ5tnKw2QtQMkVwjxgkTNtd8INhXIV+/cYUbqKMpI4BLKwkZb1/Iq gRT6jshG8reLQmcyV58UQR7+o08deZZsfiTTLftqzSUOOG6UFqI4yhXKJw8bXiMz03j6OzD28 SRYIH7igplVu482J55JgZjMHgOepjGhHBqKjKfWmcMfdQEUBie7NxMyF8epdAcd+N2qh6Eqju rOo/dq9zVWQiVw16ERyI6X8IoNj3P3OHA0LuPz0U25rCFavYEAIjkRaS51JUjTvtttqKcAuZG BCXKNT50UTFZ3+Ir6GhLu21RQIIigqSgyDjoW2lE1hPUfHdbb2uJaE/MYgc+igpdpsk7HBLbd Zo4VoxucEVYmX+gsYNzRy86g/5sFDKmZas2K66Pau8xCglrIFAMstt4CxEIHXrHCKNvgpo7kt NU90LGbdwaJaQ3MhpcmNB3Fe82DpnES8atJpSOL5I4Hp3WSiFztLjhM/u4hLX//LJQ4SYH/Hu Ck2PNkATwdD0XDLGcLKpZPu7WctBCem9jvTKx2eB+vo4UItemfcwSy+ArQ4xm5zhayG5Cv24L 4ft6a/psbU+nn7s5uonZhIx1yX7SryikPUJ8ynFkqmN0LDOFWsiSwHstAEg=
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/TeBxDW268u6PcNs_7e7QnQRynFQ>
X-Mailman-Approved-At: Sat, 16 Feb 2019 11:37:00 -0800
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: Fri, 15 Feb 2019 19:49:44 -0000

This reminds me that I once took some notes about a scheduling API https://github.com/AlexanderFroemmgen/draft-ietf-mptcp-api-for-preference-awareness

Best,

Alexander 

Am 15. Februar 2019 19:07:22 MEZ schrieb Christoph Paasch <cpaasch=40apple.com@dmarc.ietf.org>:
>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. 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.
>
>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.
>
>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.
>
>
>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

v2.23.0 | Report a Bug | By Email