Telechat Review of draft-ietf-bmwg-ngfw-performance-13
review-ietf-bmwg-ngfw-performance-13-genart-telechat-joras-2022-02-01-00
| Request | Review of | draft-ietf-bmwg-ngfw-performance |
|---|---|---|
| Requested revision | No specific revision (document currently at 15) | |
| Type | Telechat Review | |
| Team | General Area Review Team (Gen-ART) (genart) | |
| Deadline | 2022-02-01 | |
| Requested | 2022-01-14 | |
| Authors | Balamuhunthan Balarajah , Carsten Rossenhoevel , Brian Monkman | |
| I-D last updated | 2022-02-01 | |
| Completed reviews |
Secdir Early review of -00
by Kathleen Moriarty
(diff)
Tsvart Last Call review of -12 by Tommy Pauly (diff) Tsvart Telechat review of -13 by Tommy Pauly (diff) Iotdir Telechat review of -13 by Toerless Eckert (diff) Genart Telechat review of -13 by Matt Joras (diff) Tsvart Telechat review of -13 by Tommy Pauly (diff) |
|
| Assignment | Reviewer | Matt Joras |
| State | Completed | |
| Request | Telechat review on draft-ietf-bmwg-ngfw-performance by General Area Review Team (Gen-ART) Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/gen-art/NUycZt5uKAZejOvCr6tdi_7SvPA | |
| Reviewed revision | 13 (document currently at 15) | |
| Result | Ready w/issues | |
| Completed | 2022-02-01 |
review-ietf-bmwg-ngfw-performance-13-genart-telechat-joras-2022-02-01-00
I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please wait for direction from your document shepherd or AD before posting a new version of the draft. For more information, please see the FAQ at <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>. Document: draft-ietf-bmwg-ngfw-performance-13 Reviewer: Matt Joras Review Date: 2022-01-31 IETF LC End Date: 2021-12-29 IESG Telechat date: 2022-02-03 Nits/editorial comments: Section 4.3.1.1 This section details TCP stack attributes in great detail. However, subsequently HTTP/3 and QUIC are both mentioned in 4.3.1.3.. QUIC is in need of tuning just as much as TCP, if not more. " HTTP/3 emulated browser uses QUIC ([RFC9000]) as transport protocol." should be reworded, and I'm not exactly sure what it is trying to convey. "Depending on test scenarios and selected HTTP version, HTTP header compression MAY be set to enable or disable." should probably read " be enabled or disabled." Similarly in sections 7, there is a lot of specific mention of TCP connections, TCP RSTs, FINs, etc. and continued mentioning of HTTP. Since QUIC is a significant carrier of HTTP traffic it seems these sections should not be so specific to TCP. Especially since it seems as though for these kinds of devices their limits may very well be different for UDP or TCP flows.