Opsdir last call review of draft-ietf-6man-spring-srv6-oam-10

Dan Romascanu via Datatracker <noreply@ietf.org> Fri, 09 April 2021 16:24 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dan Romascanu via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-6man-spring-srv6-oam.all@ietf.org, ipv6@ietf.org, last-call@ietf.org, dromasca@gmail.com
Subject: Opsdir last call review of draft-ietf-6man-spring-srv6-oam-10
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161798549210.10475.9095627778921105412@ietfa.amsl.com>
Reply-To: Dan Romascanu <dromasca@gmail.com>
Date: Fri, 09 Apr 2021 09:24:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/tFjiaFE0Le8Z_aWupYlddeG2W2A>

Reviewer: Dan Romascanu
Review result: Ready

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).

Opsdir last call review of draft-ietf-6man-spring… Dan Romascanu via Datatracker