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

Tianran Zhou <zhoutianran@huawei.com> Mon, 05 February 2024 09:44 UTC

Return-Path: <zhoutianran@huawei.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ECE0C14F6F0; Mon, 5 Feb 2024 01:44:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AvkR1kC2HrhJ; Mon, 5 Feb 2024 01:44:34 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F9BEC14F5E4; Mon, 5 Feb 2024 01:44:33 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4TT1bg1lcPz6GBQm; Mon, 5 Feb 2024 17:41:19 +0800 (CST)
Received: from lhrpeml500006.china.huawei.com (unknown [7.191.161.198]) by mail.maildlp.com (Postfix) with ESMTPS id E16F1141B1D; Mon, 5 Feb 2024 17:44:30 +0800 (CST)
Received: from dggpemm500003.china.huawei.com (7.185.36.56) by lhrpeml500006.china.huawei.com (7.191.161.198) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Mon, 5 Feb 2024 09:44:29 +0000
Received: from kwepemd100004.china.huawei.com (7.221.188.31) by dggpemm500003.china.huawei.com (7.185.36.56) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Mon, 5 Feb 2024 17:44:27 +0800
Received: from kwepemd100004.china.huawei.com ([7.221.188.31]) by kwepemd100004.china.huawei.com ([7.221.188.31]) with mapi id 15.02.1258.028; Mon, 5 Feb 2024 17:44:27 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: "Liushucheng (Will LIU, Strategy & Industry Development)" <liushucheng@huawei.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "draft-ietf-ippm-ioam-yang.all@ietf.org" <draft-ietf-ippm-ioam-yang.all@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>
Thread-Topic: Opsdir last call review of draft-ietf-ippm-ioam-yang-11
Thread-Index: AQHaVeYvn0FP4uUGF0WSmkIZLWTdq7D7fxZw
Date: Mon, 05 Feb 2024 09:44:27 +0000
Message-ID: <360213fd6a8442dcbf22e729f0b0a74e@huawei.com>
References: <170688500216.35262.4911495412038285151@ietfa.amsl.com>
In-Reply-To: <170688500216.35262.4911495412038285151@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.40.118]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/sfHTFXp472UQJQ2IkhdUnIxAB_Y>
Subject: Re: [ippm] Opsdir last call review of draft-ietf-ippm-ioam-yang-11
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
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: Mon, 05 Feb 2024 09:44:38 -0000

Hi Will,

Thanks very much for your review.
For the two clarification questions, please see below in line.

Cheers,
Tianran


-----Original Message-----
From: Will LIU via Datatracker [mailto:noreply@ietf.org] 
Sent: Friday, February 2, 2024 10:43 PM
To: ops-dir@ietf.org
Cc: draft-ietf-ippm-ioam-yang.all@ietf.org; ippm@ietf.org; last-call@ietf.org
Subject: Opsdir last call review of draft-ietf-ippm-ioam-yang-11

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? 
ZTR> IOAM, both RFC9197 and RFC9326, only specifies the data plane data format. 
It could just use the existing exporting protocols like IPFIX and YANG Push. 
The configurations of the exporting protocols have already been specified.  

2. I see only the ingress node need to configure the max-length check. May i ask what about the subsequent nodes?
ZTR> Yes, the ingress node need to configure the max-length. Then this information will be encapsulated into the IOAM header, and go through the consequent nodes. So that all the nodes along the path can check.