Last Call Review of draft-ietf-pim-3376bis-10
review-ietf-pim-3376bis-10-genart-lc-bryant-2024-06-03-00
Request | Review of | draft-ietf-pim-3376bis-10 |
---|---|---|
Requested revision | 10 (document currently at 12) | |
Type | Last Call Review | |
Team | General Area Review Team (Gen-ART) (genart) | |
Deadline | 2024-06-05 | |
Requested | 2024-05-21 | |
Requested by | Gunter Van de Velde | |
Authors | Brian Haberman | |
I-D last updated | 2024-06-03 | |
Completed reviews |
Rtgdir Last Call review of -10
by Adrian Farrel
(diff)
Opsdir Last Call review of -10 by Jouni Korhonen (diff) Genart Last Call review of -10 by Stewart Bryant (diff) Secdir Last Call review of -10 by Loganaden Velvindron (diff) Intdir Telechat review of -11 by Bob Halley (diff) |
|
Assignment | Reviewer | Stewart Bryant |
State | Completed | |
Request | Last Call review on draft-ietf-pim-3376bis by General Area Review Team (Gen-ART) Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/gen-art/3ItF5blmNSrRxb7d72gT5hizpyc | |
Reviewed revision | 10 (document currently at 12) | |
Result | Ready w/issues | |
Completed | 2024-06-03 |
review-ietf-pim-3376bis-10-genart-lc-bryant-2024-06-03-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-pim-3376bis-10 Reviewer: Stewart Bryant Review Date: 2024-06-03 IETF LC End Date: 2024-06-06 IESG Telechat date: Not scheduled for a telechat Summary:This is a well written document with just a couple of small things to look at. Major issues:None Minor issues: This is a standards track document so I would expect the IANA Considerations to be standards track. In the IANA section the text says: All IGMP types described in this document are managed via [I-D.ietf-pim-3228bis]. However I-D.ietf-pim-3228bis is given as an informational reference. I would have expected it to be a normative reference. Nits/editorial comments: The keyword (RFC2119) boilerplate use is the old version and not the modern version. This should be changed.