Re: [CCAMP] [inventory-yang] poll for network inventory base model

"maqiufang (A)" <maqiufang1@huawei.com> Tue, 29 August 2023 02:58 UTC

Return-Path: <maqiufang1@huawei.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E125C15171B; Mon, 28 Aug 2023 19:58:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham 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 7U9yJnNV0lCS; Mon, 28 Aug 2023 19:58:10 -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 F0493C1516F8; Mon, 28 Aug 2023 19:58:09 -0700 (PDT)
Received: from lhrpeml100003.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4RZX7J75j0z6J6CY; Tue, 29 Aug 2023 10:53:48 +0800 (CST)
Received: from kwepemm000020.china.huawei.com (7.193.23.93) by lhrpeml100003.china.huawei.com (7.191.160.210) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Tue, 29 Aug 2023 03:58:05 +0100
Received: from kwepemm600017.china.huawei.com (7.193.23.234) by kwepemm000020.china.huawei.com (7.193.23.93) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Tue, 29 Aug 2023 10:58:04 +0800
Received: from kwepemm600017.china.huawei.com ([7.193.23.234]) by kwepemm600017.china.huawei.com ([7.193.23.234]) with mapi id 15.01.2507.031; Tue, 29 Aug 2023 10:58:04 +0800
From: "maqiufang (A)" <maqiufang1@huawei.com>
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>, "inventory-yang@ietf.org" <inventory-yang@ietf.org>
CC: "ivy-chairs@ietf.org" <ivy-chairs@ietf.org>, opsawg <opsawg@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>
Thread-Topic: [inventory-yang] poll for network inventory base model
Thread-Index: AdnZd2aurH+3TSP/QE69JhEVg4aB+QAQ0AEgABnPDEA=
Date: Tue, 29 Aug 2023 02:58:03 +0000
Message-ID: <7c39303a3412449f830f2d33304d0c0e@huawei.com>
References: <7c4effcc6c5d43a6a7ddc4735d370272@huawei.com> <BN9PR11MB5371A16B1FE771AF778F3ECAB8E0A@BN9PR11MB5371.namprd11.prod.outlook.com>
In-Reply-To: <BN9PR11MB5371A16B1FE771AF778F3ECAB8E0A@BN9PR11MB5371.namprd11.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.118.147]
Content-Type: multipart/alternative; boundary="_000_7c39303a3412449f830f2d33304d0c0ehuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/r9Kl8lyjyEeI2yXXhT59UCZ0PTI>
Subject: Re: [CCAMP] [inventory-yang] poll for network inventory base model
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Aug 2023 02:58:12 -0000

Hi, Joe, WG,

As a clarification:

For this polling, we're trying to figure out if there is a consensus to use one of the existing documents as a starting point.

If there is, the chairs' assumption is to ask the authors to move the work to IVY, instead of just referencing it progressed in other places. It may still take some time for the WG (e.g., via design team discussion, interim meeting(s)) to tailor the work to fully fit the IVY charter, that's why we say "evolve it to become the network inventory base model".

Best Regards,
Qiufang
From: Joe Clarke (jclarke) [mailto:jclarke@cisco.com]
Sent: Monday, August 28, 2023 10:26 PM
To: maqiufang (A) <maqiufang1=40huawei.com@dmarc.ietf.org>; inventory-yang@ietf.org
Cc: ivy-chairs@ietf.org; opsawg <opsawg@ietf.org>; ccamp@ietf.org
Subject: Re: [inventory-yang] poll for network inventory base model

Since you copied opsawg, I'll make it clear my reply is as a contributor.  As I said at the first IVY meeting, I like the CCAMP work a bit more as a base inventory draft.  It feels more data-centric and less use-case centric if that makes sense.

That said, it's adopted work in CCAMP.  What would happen to it?  Would it move to IVY?  Would IVY work just reference it as it progresses through CCAMP?

While I like option 1, I think perhaps option 3 might be more viable, but using the model of the CCAMP work where it leverages previous ENTITY-MIB concepts while staying true to common inventory.

Joe

From: Inventory-yang <inventory-yang-bounces@ietf.org<mailto:inventory-yang-bounces@ietf.org>> on behalf of maqiufang (A) <maqiufang1=40huawei.com@dmarc.ietf.org<mailto:maqiufang1=40huawei.com@dmarc.ietf.org>>
Date: Monday, August 28, 2023 at 02:22
To: inventory-yang@ietf.org<mailto:inventory-yang@ietf.org> <inventory-yang@ietf.org<mailto:inventory-yang@ietf.org>>
Cc: ivy-chairs@ietf.org<mailto:ivy-chairs@ietf.org> <ivy-chairs@ietf.org<mailto:ivy-chairs@ietf.org>>, opsawg <opsawg@ietf.org<mailto:opsawg@ietf.org>>, ccamp@ietf.org<mailto:ccamp@ietf.org> <ccamp@ietf.org<mailto:ccamp@ietf.org>>
Subject: [Inventory-yang] [inventory-yang] poll for network inventory base model
Hi Working Group,

It's now time to start considering how to move forward with the inventory base model. We have two different documents that could be used as a starting point for our work or, in case the working group believes none of them is "good enough", we can start a brand new ID.
In case the latter option is chosen, Daniele and I will write a -00 version including just the table of content and what we'd like to be covered in each section. The document will then be handed over to a pool of authors which will bring it till the WG adoption.

Hence, we will have a 3 weeks polling starting today. We decided to make it a bit longer than usual because this time the working group is requested to review two drafts instead of one.

This mail starts a 3 weeks polling, terminating on September 15th,  where we would like the working group to express your preference among:

1.      Adopt  draft-ietf-ccamp-network-inventory-yang-02 in IVY and evolve it to become the network inventory base model
2.      Adopt draft-wzwb-opsawg-network-inventory-management-03 in IVY and evolve it to become the network inventory base model
3.      Start a brand new document from scratch as described above

In the week after the closure of the polling (between September 18 and 25) we will have an IVY interim meeting to discuss the issues/concerns raised during the polling ( A separate mail will be sent).

Thank you,

Qiufang and Daniele