Skip to main content

Last Call Review of draft-ietf-opsawg-ipfix-fixes-09
review-ietf-opsawg-ipfix-fixes-09-secdir-lc-orman-2024-05-19-00

Request Review of draft-ietf-opsawg-ipfix-fixes
Requested revision No specific revision (document currently at 12)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2024-05-10
Requested 2024-04-26
Authors Mohamed Boucadair , Benoît Claise
I-D last updated 2024-05-19
Completed reviews Secdir Last Call review of -09 by Hilarie Orman (diff)
Tsvart Last Call review of -07 by Martin Duke (diff)
Intdir Last Call review of -08 by Donald E. Eastlake 3rd (diff)
Opsdir Early review of -03 by Qin Wu (diff)
Genart Early review of -03 by Behcet Sarikaya (diff)
Assignment Reviewer Hilarie Orman
State Completed
Request Last Call review on draft-ietf-opsawg-ipfix-fixes by Security Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/secdir/5rA93co6B63rGT9VkKK6Q4QAQa0
Reviewed revision 09 (document currently at 12)
Result Ready
Completed 2024-05-19
review-ietf-opsawg-ipfix-fixes-09-secdir-lc-orman-2024-05-19-00
	 Security review of 
 Simple Fixes to the IP Flow Information Export (IPFIX) IANA Registry
		   draft-ietf-opsawg-ipfix-fixes-09

Do not be alarmed.  I generated this review of this document as part
of the security directorate's ongoing effort to review all IETF
documents being processed by the IESG.  These comments were written
with the intent of improving security requirements and considerations
in IETF drafts.  Comments not addressed in last call may be included
in AD reviews during the IESG review.  Document editors and WG chairs
should treat these comments just like any other last call comments.


   "When OPSAWG was considering [RFC9565] which updates [RFC7125], the WG
   realized that some parts of the IANA IP Flow Information Export
   (IPFIX) registry [IANA-IPFIX] were not up-to-date.  This document
   intends to update the IANA registry and bring some consistency among
   the entries of the registry."

This is a straightforward document that updates each information
element, adding missing information or coreedting inconsistent
information, as necessary.  For example, to the list of protocols
having a source port identifier in the transport header.

No security issues are evident to me.

Hilarie