Last Call Review of draft-ietf-6man-segment-routing-header-22
review-ietf-6man-segment-routing-header-22-opsdir-lc-liu-2019-08-14-00

Request Review of draft-ietf-6man-segment-routing-header
Requested rev. no specific revision (document currently at 23)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2019-08-20
Requested 2019-08-06
Draft last updated 2019-08-14
Completed reviews Secdir Last Call review of -22 by Liang Xia (diff)
Genart Last Call review of -22 by Roni Even (diff)
Tsvart Last Call review of -22 by Joseph Touch (diff)
Opsdir Last Call review of -22 by Will LIU (diff)
Assignment Reviewer Will LIU
State Completed
Review review-ietf-6man-segment-routing-header-22-opsdir-lc-liu-2019-08-14
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/HeW7QukuYKe1ivlW0DoXMaZdgms
Reviewed rev. 22 (document currently at 23)
Review result Ready
Review completed: 2019-08-14

Review
review-ietf-6man-segment-routing-header-22-opsdir-lc-liu-2019-08-14

Hi all,

I have reviewed draft-ietf-6man-segment-routing-header-22 as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are 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.

“Segment Routing can be applied to the IPv6 data plane using a new
   type of Routing Extension Header called the Segment Routing Header.
   This document describes the Segment Routing Header and how it is used
   by Segment Routing capable nodes.”

My overall view of the document is 'Ready' for publication.

** Technical **

No.

** Editorial **

As noted by author,   section 9 Implementation Status is to be moved removed prior to publishing as an RFC. However, it may be still valuable to simplify this part and put into appendix as a record.

Regards,
Will (Shucheng LIU)