From: Nagesh shamnur <nagesh.shamnur@huawei.com>
To: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
CC: Ashutosh prakash <ashutosh.prakash@huawei.com>
Thread-Topic: Regarding rate control at a subflow level
Thread-Index: AdUMWULM15YYbMauQ2OybE7pkHW5IQ==
Date: Fri, 17 May 2019 02:37:01 +0000
Message-ID: <4AC96705FB868F42B2075BA50F806DEB56995EF6@dggema524-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative;
 boundary="_000_4AC96705FB868F42B2075BA50F806DEB56995EF6dggema524mbxchi_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/c2V_ceeM1RYAxNwbC-3WdgmgHxo>
Subject: [multipathtcp] Regarding rate control at a subflow level
Precedence: list

--_000_4AC96705FB868F42B2075BA50F806DEB56995EF6dggema524mbxchi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear MPTCP Group,
                Greetings. In case of Mobile deployments of MPTCP, though t=
he data rates are getting cheaper, still it would be wise not to run the ce=
llular path to full limit but to throttle to a certain extent considering c=
ost 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. So, while goi=
ng through the discussion archives, could only find that, the peer(server) =
can throttle the speed for the entire connection by publishing a smaller re=
ceiver window rather than for a particular subflow. I feel, it would be a g=
ood idea if the peers can exchange this information using the control packe=
ts.
                Any thoughts?

Regards,
Nagesh S

--_000_4AC96705FB868F42B2075BA50F806DEB56995EF6dggema524mbxchi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Dear MPTCP Group,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greetings. In case of Mobile deploym=
ents 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 certa=
in extent considering cost in mind
 or if server wants to limit the client at subflow level, then I couldn&#82=
17;t find the support for the same in the specification. So, while going th=
rough the discussion archives, could only find that, the peer(server) can t=
hrottle the speed for the entire connection
 by publishing a smaller receiver window rather than for a particular subfl=
ow. I feel, it would be a good idea if the peers can exchange this informat=
ion using the control packets.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Any thoughts?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:blue">Regards,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:blue">Nagesh S<o:p></o:p></span=
></p>
</div>
</body>
</html>

--_000_4AC96705FB868F42B2075BA50F806DEB56995EF6dggema524mbxchi_--