[multipathtcp] Comments on "draft-hoang-mptcp-sub-rate-limit-00.txt" draft

Nagesh shamnur <nagesh.shamnur@huawei.com> Thu, 11 July 2019 13:08 UTC

From: Nagesh shamnur <nagesh.shamnur@huawei.com>
To: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
CC: Ashutosh prakash <ashutosh.prakash@huawei.com>
Thread-Topic: Comments on "draft-hoang-mptcp-sub-rate-limit-00.txt" draft
Thread-Index: AdU36Tk1Exv/Kj4cScaaUFj4/65w5A==
Date: Thu, 11 Jul 2019 13:07:58 +0000
Message-ID: <a2c4d5b8b5a741debc36a1e1551c8de2@huawei.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/Ho_tylKnGmHDgfR0XIoV_M2oYwM>
Subject: [multipathtcp] Comments on "draft-hoang-mptcp-sub-rate-limit-00.txt" draft
Precedence: list

Dear Hoang & Olivier,
	Thanks for taking up the topic and realizing the same as a draft. 

1) section 3 mentions that, " Hosts SHOULD resend is several times, but not more frequently than once per second.". Instead more clarity can be provided on the strategy that needs to be adapted, or can explicitly mention that it is implementation dependent or to be decided later.

2) Section 3 has editorial issue, " Hosts SHOULD resend is several times, but not more frequently than once per second." needs to be changed to " Hosts SHOULD resend it several times, but not more frequently than once per second."

3) As per "draft-ietf-mptcp-rfc6824bis-18" section 3, then length field is specified in bytes and includes 2 bytes of kind of length. But in this draft 3.1, says that the length of the option is 5, it needs to be changed to 7.

4) This draft doesn't address how this option needs to be handled on receiving side which is running older version of MPTCP stacks and doesn't implement this draft.

Regards,
Nagesh S

Date: Tue, 9 Jul 2019 09:04:48 +0000
From: Viet Hoang Tran <hoang.tran@uclouvain.be>
To: multipathtcp <multipathtcp@ietf.org>
Subject: [multipathtcp] Fw: New Version Notification for
	draft-hoang-mptcp-sub-rate-limit-00.txt
Message-ID:
	<DB7PR03MB42663A746B38EB94C2E26298EBF10@DB7PR03MB4266.eurprd03.prod.outlook.com>
	
Content-Type: text/plain; charset="us-ascii"

We submitted two drafts on  Subflow Rate Limit Option and  Inactivity Time Option (https://tools.ietf.org/html/draft-hoang-mptcp-inactivity-time-00)

Feedbacks and suggestions are more than welcomed.
Thanks,

Hoang & Olivier

________________________________________
From: internet-drafts@ietf.org <internet-drafts@ietf.org>
Sent: Monday, 8 July 2019 16:28
To: Viet Hoang Tran; Olivier Bonaventure; Olivier Bonaventure
Subject: New Version Notification for draft-hoang-mptcp-sub-rate-limit-00.txt

A new version of I-D, draft-hoang-mptcp-sub-rate-limit-00.txt
has been successfully submitted by Viet-Hoang Tran and posted to the IETF repository.

Name:           draft-hoang-mptcp-sub-rate-limit
Revision:       00
Title:          Multipath TCP Subflow Rate Limit Option
Document date:  2019-07-08
Group:          Individual Submission
Pages:          6
URL:            https://www.ietf.org/internet-drafts/draft-hoang-mptcp-sub-rate-limit-00.txt
Status:         https://datatracker.ietf.org/doc/draft-hoang-mptcp-sub-rate-limit/
Htmlized:       https://tools.ietf.org/html/draft-hoang-mptcp-sub-rate-limit-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-hoang-mptcp-sub-rate-limit


Abstract:
   This document defines a new MPTCP Option that enables hosts to
   request their peers to limit the maximum transfer rate on a per-
   subflow basis.

[multipathtcp] Comments on "draft-hoang-mptcp-sub… Nagesh shamnur
Re: [multipathtcp] Comments on "draft-hoang-mptcp… Nagesh shamnur
Re: [multipathtcp] Comments on "draft-hoang-mptcp… Viet Hoang Tran