Re: [ippm] New Version Notification for draft-ietf-ippm-ioam-yang-07.txt

[Alex Huang Feng <[e-mail]>]

Hi Tianran,

Please see inline,

> On 20 Jul 2023, at 03:58, Tianran Zhou <[e-mail]> wrote:
> 
> Hi Alex,
>  
> Thanks very much for your suggestions.
> All are valid.
> Just one may discuss. Please see in line.
>  
> Best,
> Tianran
>  
> From: Alex Huang Feng [mailto:[e-mail] <mailto:[e-mail]>] 
> Sent: Thursday, July 20, 2023 7:04 AM
> To: Tianran Zhou <[e-mail] <mailto:[e-mail]>>
> Cc: IETF IPPM WG <[e-mail] <mailto:[e-mail]>>
> Subject: Re: [ippm] New Version Notification for draft-ietf-ippm-ioam-yang-07.txt
>  
> Hi Tianran,
>  
> Thanks for adding back IOAM DEX into the draft. 
> Some minor nits:
> - Section 3.1, at the last paragraph, the feature “direct export” needs a hyphen.
> - Apendix C, Prove —> Proof
>  
> I would suggest to add also a flag to enable the optional sequence-number in IOAM DEX. 
> Something like:
> +--rw direct-export-profile {direct-export}?
>    +--rw enabled?                boolean
>    +--rw node-action?            ioam-node-action
>    +--rw trace-types
>    |  +--rw use-namespace?   ioam-namespace
>    |  +--rw trace-type*      ioam-trace-type
>    +--rw flow-id?   
>    +--rw enable-sequence-number? boolean
>  
> ZTR> Yes, I find it useful. Should this be mandatory? For example, what if one ignore this configuration?

It can either be mandatory or using the “default” statement, setting by default to “false”. I find the “default” statement easier to operate but don’t have a strong opinion on this.

Cheers,

Alex

>  
> And at the end, I think adding an example for IOAM DEX configuration in the appendix as the authors did for the other types could complete the document.
>  
> Cheers,
> Alex
>  
> 
> 
> On 27 Jun 2023, at 12:07, Tianran Zhou <zhoutianran=[e-mail] <mailto:zhoutianran=[e-mail]>> wrote:
>  
> Hi Greg, Thomas, and WG,
> 
> As requested in the WGLC, I updated the draft with ioam-dex included.
> Please check if it works for you.
> 
> Cheers,
> Tianran
> 
> -----Original Message-----
> From: [e-mail] <mailto:[e-mail]> [mailto:[e-mail] <mailto:[e-mail]>] 
> Sent: Tuesday, June 27, 2023 6:05 PM
> To: Frank Brockners <[e-mail] <mailto:[e-mail]>>; Jim Guichard <[e-mail] <mailto:[e-mail]>>; Srihari Raghavan <[e-mail] <mailto:[e-mail]>>; Tianran Zhou <[e-mail] <mailto:[e-mail]>>
> Subject: New Version Notification for draft-ietf-ippm-ioam-yang-07.txt
> 
> 
> A new version of I-D, draft-ietf-ippm-ioam-yang-07.txt has been successfully submitted by Tianran Zhou and posted to the IETF repository.
> 
> Name:              draft-ietf-ippm-ioam-yang
> Revision:         07
> Title:                A YANG Data Model for In-Situ OAM
> Document date:          2023-06-27
> Group:             ippm
> Pages:              30
> URL:            https://www.ietf.org/archive/id/draft-ietf-ippm-ioam-yang-07.txt <https://www.ietf.org/archive/id/draft-ietf-ippm-ioam-yang-07.txt>
> Status:         https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-yang/ <https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-yang/>
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-ippm-ioam-yang <https://datatracker.ietf.org/doc/html/draft-ietf-ippm-ioam-yang>
> Diff:           https://author-tools.ietf.org/iddiff?url2=draft-ietf-ippm-ioam-yang-07 <https://author-tools.ietf.org/iddiff?url2=draft-ietf-ippm-ioam-yang-07>
> 
> Abstract:
>   In situ Operations, Administration, and Maintenance (IOAM) collects
>   operational and telemetry information in the packet while the packet
>   traverses a path between two points in the network.  RFC9197
>   discusses the data fields and associated data types for IOAM.  This
>   document defines a YANG module for the IOAM function.
> 
> 
> 
> 
> The IETF Secretariat
> 
> 
> 
> _______________________________________________
> ippm mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/ippm <https://www.ietf.org/mailman/listinfo/ippm>