Matt, thank you for your review. I have entered a Discuss ballot for this document based on my own review. Lars > On 2022-2-1, at 18:40, Matt Joras via Datatracker <noreply@xxxxxxxx> wrote: > > Reviewer: Matt Joras > Review result: Ready with Issues > > 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. > > > -- > last-call mailing list > last-call@xxxxxxxx > https://www.ietf.org/mailman/listinfo/last-call
Attachment:
signature.asc
Description: Message signed with OpenPGP
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
