Last Call Review of draft-ietf-6man-spring-srv6-oam-10
review-ietf-6man-spring-srv6-oam-10-opsdir-lc-romascanu-2021-04-09-00

Request Review of draft-ietf-6man-spring-srv6-oam
Requested revision No specific revision (document currently at 13)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2021-03-22
Requested 2021-03-08
Authors Zafar Ali , Clarence Filsfils , Satoru Matsushima , Daniel Voyer , Mach Chen
I-D last updated 2021-04-09
Completed reviews Rtgdir Last Call review of -09 by Stig Venaas (diff)
Tsvart Last Call review of -09 by Magnus Westerlund (diff)
Secdir Last Call review of -09 by Dan Harkins (diff)
Genart Last Call review of -09 by Matt Joras (diff)
Opsdir Last Call review of -10 by Dan Romascanu (diff)
Intdir Telechat review of -10 by Carlos J. Bernardos (diff)
Secdir Telechat review of -10 by Dan Harkins (diff)
Assignment Reviewer Dan Romascanu
State Completed
Request Last Call review on draft-ietf-6man-spring-srv6-oam by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/mjPkZcsAPZphXhT-AHZNPlNEde0
Reviewed revision 10 (document currently at 13)
Result Ready
Completed 2021-04-09
review-ietf-6man-spring-srv6-oam-10-opsdir-lc-romascanu-2021-04-09-00
I apologize for the late review.

This document describes OAM for SRv6 networks. For this purpose it describes an
OAM enhancement - the OAM flag in the Segment Routing Header (SRH) - for
performing controllable and predictable flow sampling from segment endpoints.
It also shows how the existing IPv6 mechanisms for ping and traceroute can be
used in an SRv6 network and how a centralized monitoring system performs a path
continuity check between any nodes within an SRv6 domain.

The document is useful, well written and Ready from an OPS perspective.

Operators should pay special attention to Section 2 which defines the OAM
extensions for SRv6 networks and Section 3 which shows how existing OAM
mechanisms can be used in SRv6 networks.

As a nit, I found the naming of Section 3 ('Illustrations') somehow
misleading.I suggest considering another name, more appropriate to the content
(usage of existing OAM mechanisms in SRv6 networks).