Skip to main content

IETF Last Call Review of draft-ietf-bmwg-mlrsearch-11
review-ietf-bmwg-mlrsearch-11-genart-lc-eggert-2025-08-08-00

Request Review of draft-ietf-bmwg-mlrsearch
Requested revision No specific revision (document currently at 15)
Type IETF Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2025-08-06
Requested 2025-07-16
Authors Maciek Konstantynowicz , Vratko Polák
I-D last updated 2026-08-13 (Latest revision 2025-11-04)
Completed reviews Genart IETF Last Call review of -11 by Lars Eggert (diff)
Secdir IETF Last Call review of -11 by Shawn M Emery (diff)
Opsdir IETF Last Call review of -11 by Nabeel Cocker (diff)
Perfmetrdir IETF Last Call review of -14 by Xiao Min (diff)
Tsvart IETF Last Call review of -11 by Yoshifumi Nishida (diff)
Intdir Telechat review of -11 by Jen Linkova (diff)
Assignment Reviewer Lars Eggert
State Completed
Request IETF Last Call review on draft-ietf-bmwg-mlrsearch by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/Vxc5_XnvkwyBMvB6Y5N6Rv1Arcs
Reviewed revision 11 (document currently at 15)
Result Ready w/nits
Completed 2025-08-08
review-ietf-bmwg-mlrsearch-11-genart-lc-eggert-2025-08-08-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 treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-bmwg-mlrsearch-??
Reviewer: Lars Eggert
Review Date: 2025-08-08
IETF LC End Date: 2025-08-06
IESG Telechat date: Not scheduled for a telechat

Summary:

This is ready to go with no issues that I can see.

(A side note is that my re-reading of RFC 2544 doesn't leave me with the
definitive algorithm that this I-D ascribes to that RFC. The relevant parts of
RFC 2544 are extremely high-level, to the point of claiming it to specifying
anything like a search algorithm is IMO a stretch. It might be that the
benchmarking community has a shared set of assumptions around RFC 2544 that
come into play here. Are those written down anywhere? Would be good to cite.)

Major issues:

Minor issues:

Nits/editorial comments:

Has a bunch of misspellings and formatting nits that the RPC can fix.