Re: [multipathtcp] MPTCP Schedulers

Alexander Frömmgen <Alexander@froemmgen.de> Fri, 15 February 2019 19:54 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 06144130FC4 for <multipathtcp@ietfa.amsl.com>; Fri, 15 Feb 2019 11:54:00 -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=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 N1B_lbY4uqB6 for <multipathtcp@ietfa.amsl.com>; Fri, 15 Feb 2019 11:53:57 -0800 (PST)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.130]) (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 BF6BD124D68 for <multipathtcp@ietf.org>; Fri, 15 Feb 2019 11:53:56 -0800 (PST)
Received: from Galaxy-S6-edge.local ([185.45.239.33]) by mrelayeu.kundenserver.de (mreue011 [212.227.15.167]) with ESMTPSA (Nemesis) id 1N8oOk-1h6Voi3OmE-015pwQ for <multipathtcp@ietf.org>; Fri, 15 Feb 2019 20:53:54 +0100
Date: Fri, 15 Feb 2019 20:53:52 +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="----DX8HX8N170E7JL9P5FIX2332LGZ045"
Content-Transfer-Encoding: 7bit
To: multipathtcp@ietf.org
From: Alexander Frömmgen <Alexander@froemmgen.de>
Message-ID: <635BA6CA-69D9-4552-849F-0906787BD4CF@froemmgen.de>
X-Provags-ID: V03:K1:LTID9l4qpMFLY4nbv4jP2ehuqxdOhsPbdvurUDkktZdXV1Y0I1f xS3Bt1/oUsjA47Bd8trB2M/ZERUwOhYS7QGOtZeDUeZPw3ItL+nbdrHdbBRCrltq0eJMBF/ 1A8xJxEGpcu4TdtLGRhaT6NNb94EhOc0m2dO4c2Q7vgDOQrxavNxIiL+HkehVikFAk/qvzm l43cJ8lwcxt0W+eH6idiQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:fZT7+tfsp2w=:HSLwzyAxQj3Ek29l5OXXru 5IJVampMn/XwpAMnx/ZSIwp7xaegmN1Jw+o+C0R+BlyUbikZruq2wfwLxwaSvpTgzG/ibVPat whPMmYzmNWDLqvXZ40Y5DU/3qQF4r4ZPcGO71BMaJtw+zUVKCulRHihBpFscp7/y0EE1BnYsN 7GhQb8K3p4h6gSj3BUnLbYtQVEtEDiT2ljsqxNJD6fWgQ4G7Mm+QmNmpwsC3qmZJD/l3UEwBS RBpuiCyO5PdYFWSc7I6B/9wqCK9aKoQMAbq/J6wyHzog1TI+PUxq9alnPLIWaf53IWU8G1JbL XtRh1s09dEiovwS3xwjIjpj+CqUYAhcRwXm4vEEFaPfbTWi/qwtwokopeP6V/7yEpO5AbXqQz 5Q6Lnm8gxmnxz9YybB5r9S6DBJShd7adbn49qYfjzZPeJmYb6Wqe6pdpWAoRWrOkkLGA9h0QP IJM851sfk+yb78WQddai6k1E4r/RUyh3Msr27bt1jSXu51D8MWMijdELMZyaCIKDkeUmscE0T 9wEB89ROY1HCe5k37yb1J8wSwwOEWo/6FrCuV16jTbZ9zr7r+W3PY2JRwyaY0O+rNSk0VFmxA VzBW7mMutDTaZjt7bgbgutrIkTJOUKAadzOL5PkemHr/R2GNgocZ6pBzKQjO1BIt0sP3fUzPO 8NkcoD7m/gB/8yHQLxn0DH7fHC74pxfAfPKZ7gKEIh4LG+BuPV37HDJowltQghkCP7GnSplM1 jy2pwUF8utz7U3tAVl8TDk7F/p89ZQ0cK+HTE0fzguKpSHaDsJtlGm4aAlE=
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/y1dkihFeT6xqspjBwNZkJY-F18M>
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:54:00 -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