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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxx] 
Sent: Friday, February 2, 2024 10:43 PM
To: ops-dir@xxxxxxxx
Cc: draft-ietf-ippm-ioam-yang.all@xxxxxxxx; ippm@xxxxxxxx; last-call@xxxxxxxx
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.


-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call



[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux