Last Call Review of draft-ietf-opsawg-tsvwg-udp-ipfix-08
review-ietf-opsawg-tsvwg-udp-ipfix-08-genart-lc-sparks-2024-05-03-00
review-ietf-opsawg-tsvwg-udp-ipfix-08-genart-lc-sparks-2024-05-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-opsawg-tsvwg-udp-ipfix-08 Reviewer: Robert Sparks Review Date: 2024-05-03 IETF LC End Date: 2024-05-10 IESG Telechat date: Not scheduled for a telechat Summary: Ready with nits 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-opsawg-tsvwg-udp-ipfix-18 Reviewer: Robert Sparks Review Date: 2024-05-03 IETF LC End Date: 2024-05-10 IESG Telechat date: Not scheduled for a telechat Summary: Ready with nits Consider discussing, or point to existing considerations about, what should happen when you are exporting very large udp options (perhaps constructed maliciously to be as large as possible) and you are carrying the exported values over UDP (Section 10.3 of RFC7011) and run out of room. There are several references by section number into I-D.ietf-tsvwg-udp-options that have become stale. For instance the pointer to section 22 in the security considerations should be pointing to section 24.