IETF Last Call Review of draft-ietf-dnssd-multi-qtypes-11
review-ietf-dnssd-multi-qtypes-11-genart-lc-bryant-2026-01-14-00
| Request | Review of | draft-ietf-dnssd-multi-qtypes |
|---|---|---|
| Requested revision | No specific revision (document currently at 12) | |
| Type | IETF Last Call Review | |
| Team | General Area Review Team (Gen-ART) (genart) | |
| Deadline | 2026-01-02 | |
| Requested | 2025-12-12 | |
| Authors | Ray Bellis | |
| I-D last updated | 2026-02-02 (Latest revision 2026-01-30) | |
| Completed reviews |
Dnsdir Early review of -06
by Vladimír Čunát
(diff)
Secdir IETF Last Call review of -11 by Yoav Nir (diff) Dnsdir IETF Last Call review of -11 by Ralf Weber (diff) Genart IETF Last Call review of -11 by Stewart Bryant (diff) Artart IETF Last Call review of -11 by Barry Leiba (diff) Dnsdir IETF Last Call review of -12 by Vladimír Čunát |
|
| Assignment | Reviewer | Stewart Bryant |
| State | Completed | |
| Request | IETF Last Call review on draft-ietf-dnssd-multi-qtypes by General Area Review Team (Gen-ART) Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/gen-art/xs8W-NJ-M3A2F37s0GVbHMh8ZaA | |
| Reviewed revision | 11 (document currently at 12) | |
| Result | Ready | |
| Completed | 2026-01-14 |
review-ietf-dnssd-multi-qtypes-11-genart-lc-bryant-2026-01-14-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-dnssd-multi-qtypes-11 Reviewer: Stewart Bryant Review Date: 2026-01-14 IETF LC End Date: 2026-01-02 IESG Telechat date: Not scheduled for a telechat Summary: From a Genart perspective I believe that this is ready. Major issues:I would echo the amplification attack concerns expressed in other reviews and assume that they will be addressed in due course. I note that Nits catches the use of a an IPv4 example without a corresponding IPv6 example. I personally think that this OK in this example, but the IESG may have a policy concern over this. Minor issues:None Nits/editorial comments:None