IETF Logo Mail Archive

Re: [multipathtcp] Regarding rate control at a subflow level

Nagesh shamnur <nagesh.shamnur@huawei.com> Mon, 20 May 2019 09:09 UTC

Return-Path: <nagesh.shamnur@huawei.com>
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 1A8FB120151 for <multipathtcp@ietfa.amsl.com>; Mon, 20 May 2019 02:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 Tmzb6fRYd61w for <multipathtcp@ietfa.amsl.com>; Mon, 20 May 2019 02:09:34 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 95B4F120106 for <multipathtcp@ietf.org>; Mon, 20 May 2019 02:09:34 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 6053D7C0F1A5A9878637 for <multipathtcp@ietf.org>; Mon, 20 May 2019 10:09:32 +0100 (IST)
Received: from lhreml711-chm.china.huawei.com (10.201.108.62) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 20 May 2019 10:09:31 +0100
Received: from lhreml711-chm.china.huawei.com (10.201.108.62) by lhreml711-chm.china.huawei.com (10.201.108.62) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Mon, 20 May 2019 10:09:31 +0100
Received: from DGGEMA405-HUB.china.huawei.com (10.3.20.46) by lhreml711-chm.china.huawei.com (10.201.108.62) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Mon, 20 May 2019 10:09:31 +0100
Received: from DGGEMA524-MBX.china.huawei.com ([169.254.7.203]) by DGGEMA405-HUB.china.huawei.com ([10.3.20.46]) with mapi id 14.03.0415.000; Mon, 20 May 2019 17:09:24 +0800
From: Nagesh shamnur <nagesh.shamnur@huawei.com>
To: Olivier Bonaventure <olivier.bonaventure@uclouvain.be>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>
CC: Ashutosh prakash <ashutosh.prakash@huawei.com>
Thread-Topic: [multipathtcp] Regarding rate control at a subflow level
Thread-Index: AdUMWULM15YYbMauQ2OybE7pkHW5IQAPgMiAAJULV/A=
Date: Mon, 20 May 2019 09:09:24 +0000
Message-ID: <4AC96705FB868F42B2075BA50F806DEB569AC350@dggema524-mbx.china.huawei.com>
References: <4AC96705FB868F42B2075BA50F806DEB56995EF6@dggema524-mbx.china.huawei.com> <4f40e635-2a80-20ec-c991-8a7a61ef327a@uclouvain.be>
In-Reply-To: <4f40e635-2a80-20ec-c991-8a7a61ef327a@uclouvain.be>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.156.80]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/Hggp3dD_87XEpXjYJCdFBjOah_k>
Subject: Re: [multipathtcp] Regarding rate control at a subflow level
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, 20 May 2019 09:09:36 -0000

Reply inline.

Regards,
Nagesh.

-----Original Message-----
From: Olivier Bonaventure [mailto:olivier.bonaventure@uclouvain.be] 
Sent: 17 May 2019 15:30
To: Nagesh shamnur <nagesh.shamnur@huawei.com>; multipathtcp@ietf.org
Cc: Ashutosh prakash <ashutosh.prakash@huawei.com>
Subject: Re: [multipathtcp] Regarding rate control at a subflow level

Dear Nagesh,
> 
>                  Greetings. In case of Mobile deployments of MPTCP, 
> though the data rates are getting cheaper, still it would be wise not 
> to run the cellular path to full limit but to throttle to a certain 
> extent considering cost in mind or if server wants to limit the client 
> at subflow level, then I couldn't find the support for the same in the 
> specification.

We have developed several prototypes that include this capability in the Linux kernel.

> So, while going through the discussion archives, could only find that, 
> the peer(server) can throttle the speed for the entire connection by 
> publishing a smaller receiver window rather than for a particular 
> subflow. I feel, it would be a good idea if the peers can exchange 
> this information using the control packets.

We could imagine an MPTCP option that provides the maximum rate on a per-subflow level, but I was wondering whether the use case is not to limit the bandwidth on the smartphone at the link level (i.e. multiple tcp connections or udp flows) and not at the subflow level. Could you precise your use case for the subflow level ?
[Nagesh]: This is to ensure similar bandwidth availability to the server for all the clients.

Thanks


Olivier

v2.23.0 | Report a Bug | By Email