[tcpm] Éric Vyncke's No Objection on draft-ietf-tcpm-hystartplusplus-13: (with COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Tue, 14 February 2023 10:12 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-tcpm-hystartplusplus@ietf.org, tcpm-chairs@ietf.org, tcpm@ietf.org, tuexen@fh-muenster.de, tuexen@fh-muenster.de
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Éric Vyncke <evyncke@cisco.com>
Message-ID: <167636955372.44190.962883968913661659@ietfa.amsl.com>
Date: Tue, 14 Feb 2023 02:12:33 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/xUqsAq79ZdoPjM2Pxb26phZdVDc>
Subject: [tcpm] Éric Vyncke's No Objection on draft-ietf-tcpm-hystartplusplus-13: (with COMMENT)

Éric Vyncke has entered the following ballot position for
draft-ietf-tcpm-hystartplusplus-13: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-tcpm-hystartplusplus/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


# Éric Vyncke, INT AD, comments for draft-ietf-tcpm-hystartplusplus-13
CC @evyncke

Thank you for the work put into this document.

Please find below some non-blocking COMMENT points (but replies would be
appreciated even if only for my own education), and some nits.

Special thanks to Michael Tüxen for the shepherd's detailed write-up including
the WG consensus **and** the justification of the intended status (even if
"experimental" would have been possibly another good choice).

I hope that this review helps to improve the document,

Regards,

-éric

## COMMENTS

After writing my review, I have noticed that some of my comments were
previously also made by John Scudder.

### Section 1

Mostly a nit, but it took me a while to parse `uses delay increase` as some
terms are verb or word. Suggest "an increase of the delay is used by..." or use
"RTT" rather than "delay" ?

### Section 4.2

I second John's point about the function clamp(), the verb was unknown to me
(non-English speaker) before googling for the term.

### Section 4.3

s/A TCP implementation is REQUIRED/A TCP implementation of HyStart++ is
REQUIRED/

Please add a reference for `A paced TCP implementation`

Please expand or add a reference for `BDP`

### Section 5

Please be specific, i.e., say the year rather than `As of the time of writing`

### Section 9.1

RFC 8174 should be normative.

## NITS

### min (

Let's be consistent about "min (" vs. "min(" ;-)

## Notes

This review is in the ["IETF Comments" Markdown format][ICMF], You can use the
[`ietf-comments` tool][ICT] to automatically convert this review into
individual GitHub issues.

[ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md
[ICT]: https://github.com/mnot/ietf-comments

[tcpm] Éric Vyncke's No Objection on draft-ietf-t… Éric Vyncke via Datatracker