Re: [ippm] Call for adoption: draft-zhou-ippm-ioam-yang

Tianran Zhou <zhoutianran@huawei.com> Mon, 16 November 2020 02:55 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 9FC923A1023; Sun, 15 Nov 2020 18:55:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DjXM3f3ijjRl; Sun, 15 Nov 2020 18:55:44 -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 DD45D3A1053; Sun, 15 Nov 2020 18:55:41 -0800 (PST)
Received: from fraeml740-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4CZDCx04RFz67D2Z; Mon, 16 Nov 2020 10:53:33 +0800 (CST)
Received: from nkgeml705-chm.china.huawei.com (10.98.57.154) by fraeml740-chm.china.huawei.com (10.206.15.221) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 16 Nov 2020 03:55:39 +0100
Received: from nkgeml707-chm.china.huawei.com (10.98.57.157) by nkgeml705-chm.china.huawei.com (10.98.57.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 16 Nov 2020 10:55:37 +0800
Received: from nkgeml707-chm.china.huawei.com ([10.98.57.157]) by nkgeml707-chm.china.huawei.com ([10.98.57.157]) with mapi id 15.01.1913.007; Mon, 16 Nov 2020 10:55:37 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>
CC: IPPM Chairs <ippm-chairs@ietf.org>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>
Thread-Topic: [ippm] Call for adoption: draft-zhou-ippm-ioam-yang
Thread-Index: AQHWruxHXkttMybmSkWN4dSd7Dk7lanEEcWAgAYPvAA=
Date: Mon, 16 Nov 2020 02:55:37 +0000
Message-ID: <1ea39389889347bfb0e16fea668a9f59@huawei.com>
References: <43DADFB5-FE8A-49A1-BF39-1ECC10594211@apple.com> <CAB75xn4NP8T_P-icT1qz+Nvxra6f2of8zZew1Ymvgzr2Hjb1Kg@mail.gmail.com>
In-Reply-To: <CAB75xn4NP8T_P-icT1qz+Nvxra6f2of8zZew1Ymvgzr2Hjb1Kg@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.128]
Content-Type: multipart/alternative; boundary="_000_1ea39389889347bfb0e16fea668a9f59huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/urJLSfxBKCaXvNqnejmGSpLtEcQ>
Subject: Re: [ippm] Call for adoption: draft-zhou-ippm-ioam-yang
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
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, 16 Nov 2020 02:55:48 -0000

Hi Dhruv,

Thanks very much for your support and comments.
Please see in line for my reply.

Cheers,
Tianran

From: ippm [mailto:ippm-bounces@ietf.org] On Behalf Of Dhruv Dhody
Sent: Thursday, November 12, 2020 9:51 PM
To: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>
Cc: IPPM Chairs <ippm-chairs@ietf.org>; IETF IPPM WG (ippm@ietf.org) <ippm@ietf.org>
Subject: Re: [ippm] Call for adoption: draft-zhou-ippm-ioam-yang

Hi WG,

I support adoption of this YANG draft. A few high-level comments -

- Currently all 5 profiles can be configured at the same time in a single ioam-profile (as each of them have a separate container of their own). Is that intentional?
ZTR> Yes, we want to allow a packet to apply different IOAM at the same time.

- Can I configure an ioam-profile that is applicable to both IPv6 and NSH? The current yang model would force me to create two separate ioam-profile and give them different names!
ZTR> I can understand your question. But it seems right now the structure is not like a real profile or template. It do not allow the reuse. For example, apply to different protocols, apply to different flows(with acl).
Each profile is just one configuration.
If the working group would like to see more flexibility and reusability, we can try to revise in this direction.

- Currently ACL is the only way to identify the flow for which the IOAM profile needs to be applied. Think about how this could be used alongside SR policy YANG for instance. Maybe a generic grouping that can be used to augment SR Policy? Not sure how to make it work with the current filter-type.
ZTR> Interesting proposal. We need to think about it.

Hope these comments help to improve the YANG module!

Thanks!
Dhruv

On Sat, Oct 31, 2020 at 12:11 AM Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org<mailto:40apple.com@dmarc.ietf.org>> wrote:
Hello IPPM,

This email starts a Working Group call for adoption for draft-zhou-ippm-ioam-yang. Now that our IOAM documents are mature and progressing, the chairs believe it is time to consider the YANG work officially.

The document can be found here:

https://tools.ietf.org/html/draft-zhou-ippm-ioam-yang-08

Please provide your feedback on these document, and state whether or not you believe the IPPM WG should adopt this work by replying to this email. Please provide your feedback by the start of the IETF 109 meeting week, on Monday, November 16.

Best,
Tommy & Ian
_______________________________________________
ippm mailing list
ippm@ietf.org<mailto:ippm@ietf.org>
https://www.ietf.org/mailman/listinfo/ippm