Last Call Review of draft-ietf-core-hop-limit-05

Request Review of draft-ietf-core-hop-limit
Requested rev. no specific revision (document currently at 07)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2019-09-27
Requested 2019-09-13
Authors Mohamed Boucadair, Tirumaleswar Reddy.K, Jon Shallow
Draft last updated 2019-09-22
Completed reviews Opsdir Last Call review of -05 by Scott Bradner (diff)
Genart Last Call review of -05 by Roni Even (diff)
Secdir Last Call review of -05 by Radia Perlman (diff)
Assignment Reviewer Roni Even
State Completed
Review review-ietf-core-hop-limit-05-genart-lc-even-2019-09-22
Posted at
Reviewed rev. 05 (document currently at 07)
Review result Ready with Nits
Review completed: 2019-09-22


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


Document: draft-ietf-core-hop-limit-??
Reviewer: Roni Even
Review Date: 2019-09-22
IETF LC End Date: 2019-09-27
IESG Telechat date: Not scheduled for a telechat

The document is ready for publication as a standard track RFC with nits

Major issues:

Minor issues:

Nits/editorial comments:

In section 6.2 I am not sure why you have CUNR , I did not see these values in RFC7252 section 12.2  or in the registry

         | Number | C | U | N | R | Name             | Reference |
         |  TBA2  |   |   |   |   | Hop-Limit        | [RFCXXXX] |
             C=Critical, U=Unsafe, N=NoCacheKey, R=Repeatable