Skip to main content

Early Review of draft-ietf-opsawg-ipfix-tcpo-v6eh-05
review-ietf-opsawg-ipfix-tcpo-v6eh-05-intdir-early-von-hugo-2024-01-13-00

Request Review of draft-ietf-opsawg-ipfix-tcpo-v6eh
Requested revision No specific revision (document currently at 18)
Type Early Review
Team Internet Area Directorate (intdir)
Deadline 2024-01-08
Requested 2023-12-18
Requested by Joe Clarke
Authors Mohamed Boucadair , Benoît Claise
I-D last updated 2024-01-13
Completed reviews Genart Last Call review of -11 by Joel M. Halpern (diff)
Secdir Last Call review of -11 by Tero Kivinen (diff)
Tsvart Last Call review of -11 by Wesley Eddy (diff)
Intdir Last Call review of -11 by Dirk Von Hugo (diff)
Secdir Last Call review of -15 by Tero Kivinen (diff)
Tsvart Early review of -05 by Wesley Eddy (diff)
Opsdir Early review of -05 by Yingzhen Qu (diff)
Intdir Early review of -05 by Dirk Von Hugo (diff)
Assignment Reviewer Dirk Von Hugo
State Completed
Request Early review on draft-ietf-opsawg-ipfix-tcpo-v6eh by Internet Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/int-dir/v9S6YMArPoHmej0-M_p0U0_HkFM
Reviewed revision 05 (document currently at 18)
Result Ready w/nits
Completed 2024-01-13
review-ietf-opsawg-ipfix-tcpo-v6eh-05-intdir-early-von-hugo-2024-01-13-00
Hello,
I am an assigned INT directorate reviewer for
draft-ietf-opsawg-ipfix-tcpo-v6eh. These comments were written primarily for
the benefit of the Internet Area Directors. Document editors and shepherd(s)
should treat these comments just like they would treat comments from any other
IETF contributors and resolve them along with any other Last Call comments that
have been received. For more details on the INT Directorate, see
<https://datatracker.ietf.org/group/intdir/about/> Based on my review, if I was
on the IESG I would ballot this document as NO OBJECTION.

Although not being an expert on OPSAWG I agrre that the document is helpful
forhandling IPv6 extension headers and TCP options. I agree with prior
reviewers that IPFIX RFCs should be referenced already in sect. 1 as well as
maybe the corresponding draft draft-ietf-opsawg-ipfix-fixes on further details
on the described issues, if I understood it correctly. In addition the
following very minor nits should be corrected:

p.3:
Cover the full extension headers range => Cover the full extension headers'
range which do no correspond => which do not correspond

p.4:
these limitations can't be addressed  these limitations cannot be addressed

p.5:
packet of this Flow contained the respective => packet of this Flow contains
the respective

p.8:
these limitations can't be addressed =>  these limitations cannot be addressed

p.10:
that it does no support, => that it does not support,

p.12:
Let's consider a TCP Flow => Let us consider a TCP Flow

Thanks and best regards
Dirk