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

Benoit Claise <benoit.claise@huawei.com> Thu, 20 July 2023 23:23 UTC

Return-Path: <benoit.claise@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 ED3EFC14E513 for <ippm@ietfa.amsl.com>; Thu, 20 Jul 2023 16:23:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 jPfwm0xnZfob for <ippm@ietfa.amsl.com>; Thu, 20 Jul 2023 16:23:23 -0700 (PDT)
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 931EEC15109C for <ippm@ietf.org>; Thu, 20 Jul 2023 16:23:22 -0700 (PDT)
Received: from frapeml500001.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4R6TDb5PYlz6J7fg; Fri, 21 Jul 2023 07:19:59 +0800 (CST)
Received: from [10.45.154.211] (10.45.154.211) by frapeml500001.china.huawei.com (7.182.85.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Fri, 21 Jul 2023 01:23:16 +0200
Content-Type: multipart/alternative; boundary="------------9NRJhpyEXgdjYbs0ajr04208"
Message-ID: <6719b64f-0d8b-1244-9d91-01de7d7c29c0@huawei.com>
Date: Thu, 20 Jul 2023 16:23:10 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0
Content-Language: en-GB
To: Tianran Zhou <zhoutianran=40huawei.com@dmarc.ietf.org>, Alex Huang Feng <alex.huang-feng@insa-lyon.fr>
CC: IETF IPPM WG <ippm@ietf.org>
References: <168786031538.46147.12638755689929338131@ietfa.amsl.com> <6df748de78dd4c4fbed32f665fa53e67@huawei.com> <EA4497AB-D0F3-4C14-A0A8-091DD0E8D1B0@insa-lyon.fr> <7ffb9342d1ba4f0aa655c527d1c4679e@huawei.com> <b7484cd352db40c09bb07d2334d1a842@huawei.com>
From: Benoit Claise <benoit.claise@huawei.com>
In-Reply-To: <b7484cd352db40c09bb07d2334d1a842@huawei.com>
X-Originating-IP: [10.45.154.211]
X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To frapeml500001.china.huawei.com (7.182.85.94)
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/Lei5rZ0cjCVYR6Z8gCg99ajk9t0>
Subject: Re: [ippm] New Version Notification for draft-ietf-ippm-ioam-yang-07.txt
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: Thu, 20 Jul 2023 23:23:27 -0000


On 7/20/2023 3:42 PM, Tianran Zhou wrote:
> Hi Alex,
> You’re right.
> I have used default in my local file.
Yes, default to false is the right way IMO.

Regards, Benoit
> I will upload once the system is open.
>
> Thank you,
> Tianran
>
>
>
>
> ------------------------------------------------------------------------
>
> Sent from WeLink
> *发件人: *Alex Huang Feng<alex.huang-feng@insa-lyon.fr>
> *收件人: *Tianran Zhou<zhoutianran@huawei.com>
> *抄送: *IETF IPPM WG<ippm@ietf.org>
> *主题: *Re: [ippm] New Version Notification for 
> draft-ietf-ippm-ioam-yang-07.txt
> *时间: *2023-07-21 04:57:04
>
> Hi Tianran,
>
> Please see inline,
>
>> On 20 Jul 2023, at 03:58, Tianran Zhou <zhoutianran@huawei.com> 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:alex.huang-feng@insa-lyon.fr 
>> <mailto:alex.huang-feng@insa-lyon.fr>]
>> *Sent:*Thursday, July 20, 2023 7:04 AM
>> *To:*Tianran Zhou <zhoutianran@huawei.com>
>> *Cc:*IETF IPPM WG <ippm@ietf.org>
>> *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=40huawei.com@dmarc.ietf.org> 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:internet-drafts@ietf.org[mailto:internet-drafts@ietf.org
>>     <mailto:internet-drafts@ietf.org>]
>>     Sent: Tuesday, June 27, 2023 6:05 PM
>>     To: Frank Brockners <fbrockne@cisco.com>; Jim Guichard
>>     <james.n.guichard@futurewei.com>; Srihari Raghavan
>>     <srihari@cisco.com>; Tianran Zhou <zhoutianran@huawei.com>
>>     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
>>     Status: https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-yang/
>>     Htmlized:
>>     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
>>
>>     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
>>     ippm@ietf.org
>>     https://www.ietf.org/mailman/listinfo/ippm
>>
>
>
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm