IETF Last Call Review of draft-ietf-intarea-icmp-exten-hdr-len-05
review-ietf-intarea-icmp-exten-hdr-len-05-genart-lc-dunbar-2025-08-05-00
| Request | Review of | draft-ietf-intarea-icmp-exten-hdr-len |
|---|---|---|
| Requested revision | No specific revision (document currently at 08) | |
| Type | IETF Last Call Review | |
| Team | General Area Review Team (Gen-ART) (genart) | |
| Deadline | 2025-08-12 | |
| Requested | 2025-07-22 | |
| Authors | Ron Bonica , hexiaoming , Xiao Min , Tal Mizrahi | |
| I-D last updated | 2026-02-21 (Latest revision 2025-08-20) | |
| Completed reviews |
Genart IETF Last Call review of -05
by Linda Dunbar
(diff)
Opsdir IETF Last Call review of -04 by Jen Linkova (diff) Tsvart IETF Last Call review of -04 by Dr. Joseph D. Touch (diff) Secdir IETF Last Call review of -05 by Tim Hollebeek (diff) |
|
| Assignment | Reviewer | Linda Dunbar |
| State | Completed | |
| Request | IETF Last Call review on draft-ietf-intarea-icmp-exten-hdr-len by General Area Review Team (Gen-ART) Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/gen-art/VJ7BUc0BVUl3oY_kr27_Y6Mc2iU | |
| Reviewed revision | 05 (document currently at 08) | |
| Result | Ready w/nits | |
| Completed | 2025-08-05 |
review-ietf-intarea-icmp-exten-hdr-len-05-genart-lc-dunbar-2025-08-05-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-intarea-icmp-exten-hdr-len-5 Reviewer: Linda Dunbar Review Date: 2025-08-05 IETF LC End Date: 2025-08-12 IESG Telechat date: Not scheduled for a telechat Summary: The document is well written and very clear on adding a new Length field to the ICMP messages Major issues: None Minor issues: None Nits/editorial comments: Some legacy network devices may drop ICMP messages that contain non‑zero values in previously reserved bits, despite RFC 4884’s recommendation that receivers MUST ignore them. Recommendation: In Section 4 (Backwards Compatibility), explicitly note that some non‑compliant RFC 4884 implementations may drop messages when reserved bits are non-zero. Best Regards, Linda Dunbar