Last Call Review of draft-ietf-6man-hbh-processing-15
review-ietf-6man-hbh-processing-15-genart-lc-sarikaya-2024-04-29-01

Request Review of draft-ietf-6man-hbh-processing
Requested revision No specific revision (document currently at 20)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2024-04-29
Requested 2024-04-15
Authors Bob Hinden , Gorry Fairhurst
I-D last updated 2024-04-30
Completed reviews Intdir Telechat review of -16 by Bernie Volz (diff)
Genart Last Call review of -15 by Behcet Sarikaya (diff)
Secdir Last Call review of -15 by Peter E. Yee (diff)
Secdir Telechat review of -17 by Peter E. Yee (diff)
Tsvart Last Call review of -15 by Brian Trammell (diff)
Assignment Reviewer Behcet Sarikaya
State Completed
Request Last Call review on draft-ietf-6man-hbh-processing by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/aEQ8p_yTMlf-S9E1W6wym29rIzA
Reviewed revision 15 (document currently at 20)
Result Ready w/nits
Completed 2024-04-29
review-ietf-6man-hbh-processing-15-genart-lc-sarikaya-2024-04-29-01
Reviewer: Behcet Sarikaya
Review result: 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-6man-hbh-processing-15
Reviewer: Behcet Sarikaya
Review Date: 2024-04-29
IETF LC End Date: 2024-04-29
IESG Telechat date: Not scheduled for a telechat

Summary:The document defines procedures for processing IPv6 Hop-by-Hop options,
as such, it updates IPv6 specification in RFC 8200. A comprehensive analysis of
the existing Hop-by-Hop options is offered and results are presented. One
Hop-by-Hop option, Router Alert Option (RFC 2711) is almost deprecated with a
compromise offered to avoid deprecation.  IPv6 Minimum Path MTU Hop-by-Hop
Option is presented as an example that do not rely upon all routers to
implement a specific Hop-by-Hop option. The main idea is to ensure that the
routers can process the options at the full forwarding rate.

Major issues:None.

Minor issues:None.

Nits/editorial comments:
Section 4. Router Alert Option is a Hop-by-Hop option
needs to be stated specifically with its reference (RFC 2711). 

Section 5.2 ..
values such if the packet is asked twice 
add "that" in between such and if

Section 9  Fernando is named twice.