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

Greg Mirsky <gregimirsky@gmail.com> Wed, 05 July 2023 21:29 UTC

Return-Path: <gregimirsky@gmail.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 422ECC15153D for <ippm@ietfa.amsl.com>; Wed, 5 Jul 2023 14:29:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 JFXcA2h7xXYO for <ippm@ietfa.amsl.com>; Wed, 5 Jul 2023 14:29:58 -0700 (PDT)
Received: from mail-yw1-x1132.google.com (mail-yw1-x1132.google.com [IPv6:2607:f8b0:4864:20::1132]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C1D2C151525 for <ippm@ietf.org>; Wed, 5 Jul 2023 14:29:58 -0700 (PDT)
Received: by mail-yw1-x1132.google.com with SMTP id 00721157ae682-570114e1feaso735757b3.3 for <ippm@ietf.org>; Wed, 05 Jul 2023 14:29:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1688592597; x=1691184597; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=AE2UWr1XzHlvo4pvAjL/SNou/SFPyvoyoD/Y1kS1fOI=; b=Ixd8bgip+VSzFOfJgor+tM8BNhnA9hUNacpkZdOiND3f07/cfkYYLTnTyiat+2+Z08 K3M7qXhCIRKD53+CHThGL0pzXEBkfBCdkRNBtWrHK5D9s+u2H+JYpW9YBN4XyklvVeSx os95POXtyiEaouzHVJ6c/w3pHLdNOdpgYUFtxvn6LuqVOfDLJzo2xTVl4C34i14qcRK3 Vx8T2iPQaV2FECRYirzlwoxc1gZIaZ7qIhoq2a4tt/SK4myrFyDav70FEoi3NOMQT6rl +w4fyeiKK1SAKZRkDsTpOYsaWkevpsUpNQ+sWjMt2NSmyKh+TlER1TmWfdRLt41xP7E0 N4QA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688592597; x=1691184597; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=AE2UWr1XzHlvo4pvAjL/SNou/SFPyvoyoD/Y1kS1fOI=; b=TROFrr69hRuWCiHH2FKkuGyF+H9KtgK8Gtf22xv0OINLPd6o1IbV3Z8QL7WdfKVo6Y JkiIHKOMu+pD8c10XaVMZLJoXJpK7Wc+xiD0PjqkK+WoE+nI+Ehx5YoTdsc7cYYRVwH1 SDCTX75/CYdvLDI18q5QGAn1Jbfz+8oHbOVV01lgVLyo1wthpVaOE7Kwi3IwEI900vai tU8CkfyNSXLWxs5oFpUZJI37AyZMA8o0LL1W91BgNZNglDzcEVDbbffd7RsBtE831p0K OHlk4YVsFhVRxAjAzK7lwjLCVRL1BymANJXI0tLIv/Zc/j3kZ2c/yJKiIG9g7/smlVAV 8r/A==
X-Gm-Message-State: ABy/qLareUAMlsuvUkIhnxfS/gysZmIRsUAx9L05ruSW3chxfQPUSsb3 i/W0vBxvJ67he+06efRM3vT1eoE227yAimPeFlk=
X-Google-Smtp-Source: APBJJlECVOrP9kf8xKAaUV4Ryu09kIKZkaQrgJVK775vBIXkNznlz2M+hbW+gYGBwEWyEgtV7CCzJtx9EVhlMESYmjU=
X-Received: by 2002:a81:6dc9:0:b0:561:4bc2:1587 with SMTP id i192-20020a816dc9000000b005614bc21587mr183023ywc.39.1688592597532; Wed, 05 Jul 2023 14:29:57 -0700 (PDT)
MIME-Version: 1.0
References: <168786031538.46147.12638755689929338131@ietfa.amsl.com> <6df748de78dd4c4fbed32f665fa53e67@huawei.com> <4324418a2c7649909af22c72d173bb91@swisscom.com>
In-Reply-To: <4324418a2c7649909af22c72d173bb91@swisscom.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 05 Jul 2023 14:29:46 -0700
Message-ID: <CA+RyBmUqUjirEU3k_EB50mhuQ9Yqg3DLMr8NieK7kXE-WONF-Q@mail.gmail.com>
To: Thomas.Graf@swisscom.com
Cc: zhoutianran@huawei.com, ippm@ietf.org, alex.huang-feng@insa-lyon.fr
Content-Type: multipart/alternative; boundary="000000000000f243d005ffc41971"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/SjVcc0vcAHKLuhiSpg33oQHKjnE>
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: Wed, 05 Jul 2023 21:29:59 -0000

Hi Thomas,
I agree with the proposed change.

Regards,
Greg

On Tue, Jul 4, 2023 at 10:35 PM <Thomas.Graf@swisscom.com> wrote:

> Dear Tianran,
>
> Thanks a lot for add IOAM-DEX. That looks perfect to me.
>
> Greg and I made the following editorial remarks on the mailing list:
>
> Greg> The scope of the IOAM YANG data model - is limited to configuration
> or also includes the presentation of IOAM data types defined in RFC 9197?
> Thomas> I suggest to change the following sentence in the abstract from
>
> "This document defines a YANG module for the IOAM function."
>
> To
>
> "This document defines a YANG module for configuring IOAM functions."
>
>
> I think that would make it clear that the specified YANG module doesn't
> cover IOAM data types.
>
> Greg: Would the proposed sentence change in the abstract also address your
> concern?
>
> Best wishes
> Thomas
>
> -----Original Message-----
> From: Tianran Zhou <zhoutianran@huawei.com>
> Sent: Tuesday, June 27, 2023 12:08 PM
> To: IETF IPPM WG <ippm@ietf.org>
> Cc: Greg Mirsky <gregimirsky@gmail.com>; Graf Thomas, INI-NET-VNC-HCS <
> Thomas.Graf@swisscom.com>
> Subject: FW: New Version Notification for draft-ietf-ippm-ioam-yang-07.txt
>
> 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]
> 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
>
>
>
>