Skip to main content

Last Call Review of draft-ietf-ccwg-rfc5033bis-06
review-ietf-ccwg-rfc5033bis-06-opsdir-lc-schoenwaelder-2024-07-06-00

Request Review of draft-ietf-ccwg-rfc5033bis
Requested revision No specific revision (document currently at 08)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2024-07-08
Requested 2024-06-24
Authors Martin Duke , Gorry Fairhurst
I-D last updated 2024-07-06
Completed reviews Genart Last Call review of -06 by Joel M. Halpern (diff)
Secdir Last Call review of -06 by Derrell Piper (diff)
Artart Last Call review of -06 by Sean Turner (diff)
Opsdir Last Call review of -06 by Jürgen Schönwälder (diff)
Assignment Reviewer Jürgen Schönwälder
State Completed
Request Last Call review on draft-ietf-ccwg-rfc5033bis by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/Ei8s19Hj_2_CKBng-S2IODssSo0
Reviewed revision 06 (document currently at 08)
Result Ready
Completed 2024-07-06
review-ietf-ccwg-rfc5033bis-06-opsdir-lc-schoenwaelder-2024-07-06-00
The document provides guidelines for the IETF when evaluating new
proposed congestion control algorithms. While important, this document
is not directly influencing network operations.

This update grows the document from 10 pages (RFC 5033) to 25 pages. I
found the draft well structured and easy to read and all content
appears to be well justified. The draft provides helpful advice to
everybody involved in the development and evaluation of congestion
control algorithms.

- I am wondering whether section 7.1.1 really should be a sub-section
  of 7.1, which implies that a network circuit breaker are viewed as a
  special kind of an active queue management technique. Keeping the
  sub-sections a flat list of special cases may simplify things. I
  also found the title of section 7.1.1 a bit longish compared to the
  other section titles. Perhaps turning 7.1.1 into "7.2 Interaction
  with Network Transport Circuit Breakers" or just "7.2 Network
  Transport Circuit Breakers" leads to a simpler structure.

- Similarly, I wonder whether sub-section 7.7.1 should be lifted up as
  well. Path changes are not necessarily a transient event. Perhaps
  7.7.1 should become "7.X Changes in the Path" (dropping sudden as
  well). The point made in the text is that paths are not static, they
  may change.

Perhaps	the above two comments make no sense, then just	ignore them.
I just thought I share them since they came up during my first time
read of the document.