[ippm] Opsdir last call review of draft-ietf-ippm-ioam-yang-11

Will LIU via Datatracker <noreply@ietf.org> Fri, 02 February 2024 14:43 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ippm@ietf.org
Delivered-To: ippm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BBE8C14CE42; Fri, 2 Feb 2024 06:43:22 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Will LIU via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-ippm-ioam-yang.all@ietf.org, ippm@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.4.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <170688500216.35262.4911495412038285151@ietfa.amsl.com>
Reply-To: Will LIU <liushucheng@huawei.com>
Date: Fri, 02 Feb 2024 06:43:22 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/2pamwS9tEXCe8S8_sv5dMZpWRoQ>
Subject: [ippm] Opsdir last call review of draft-ietf-ippm-ioam-yang-11
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Feb 2024 14:43:22 -0000

Reviewer: Will LIU
Review result: Ready

I have reviewed draft-ietf-ippm-ioam-yang-11 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.

   "In-situ Operations, Administration, and Maintenance (IOAM) is an
   example of an on-path hybrid measurement method.  IOAM defines a
   method to produce operational and telemetry information that may be
   exported using the in-band or out-of-band method.  RFC9197 and
   RFC9326 discuss the data fields and associated data types for IOAM.
   This document defines a YANG module for the configuration of IOAM
   functions."

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

** Technical **

No.

** Editorial **

No.

I do not see any special operational or network management related issue. I
just have some clarification questions: 1. I do not see any configuration on
data export, especially for the direct export type. May I ask your
consideration? 2. I see only the ingress node need to configure the max-length
check. May i ask what about the subsequent nodes?