Re: [OPSAWG] Minutes of L3NM/L2NM module discussions (27th-May-2020)

Zhenghaomian <zhenghaomian@huawei.com> Thu, 04 June 2020 06:16 UTC

Return-Path: <zhenghaomian@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D07353A091B for <opsawg@ietfa.amsl.com>; Wed, 3 Jun 2020 23:16:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 qn1TuBjRivwi for <opsawg@ietfa.amsl.com>; Wed, 3 Jun 2020 23:16:35 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F5EF3A0917 for <OPSAWG@ietf.org>; Wed, 3 Jun 2020 23:16:35 -0700 (PDT)
Received: from lhreml737-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 2FBB9AEA21168FAD1122; Thu, 4 Jun 2020 07:16:32 +0100 (IST)
Received: from lhreml737-chm.china.huawei.com (10.201.108.187) by lhreml737-chm.china.huawei.com (10.201.108.187) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 4 Jun 2020 07:16:31 +0100
Received: from DGGEML422-HUB.china.huawei.com (10.1.199.39) by lhreml737-chm.china.huawei.com (10.201.108.187) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Thu, 4 Jun 2020 07:16:31 +0100
Received: from DGGEML511-MBX.china.huawei.com ([169.254.1.116]) by dggeml422-hub.china.huawei.com ([10.1.199.39]) with mapi id 14.03.0487.000; Thu, 4 Jun 2020 14:16:13 +0800
From: Zhenghaomian <zhenghaomian@huawei.com>
To: Qin Wu <bill.wu@huawei.com>, "Joe Clarke (jclarke)" <jclarke=40cisco.com@dmarc.ietf.org>, SAMIER BARGUIL GIRALDO <samier.barguilgiraldo.ext@telefonica.com>
CC: "OPSAWG@ietf.org" <OPSAWG@ietf.org>
Thread-Topic: [OPSAWG] Minutes of L3NM/L2NM module discussions (27th-May-2020)
Thread-Index: AdY6N6JpjUNZLGn8TEKjd2e5w5f7ew==
Date: Thu, 04 Jun 2020 06:16:13 +0000
Message-ID: <E0C26CAA2504C84093A49B2CAC3261A43F87D578@dggeml511-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.24.176.178]
Content-Type: multipart/alternative; boundary="_000_E0C26CAA2504C84093A49B2CAC3261A43F87D578dggeml511mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/07yoMY-cZcaCsT5fyMheH9l-7KA>
Subject: Re: [OPSAWG] Minutes of L3NM/L2NM module discussions (27th-May-2020)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2020 06:16:37 -0000

Hi, Joe, Qin,

The groupings in the types is understood to be used in multiple other modules. Considering about the potential ‘uses’ in other models, it may not be a matter for putting in a same type YANG or separate one.

A more challenging issue is to have a ‘right-fit’ types. If a types contain 100 typedef and identities, sometimes we will be in the dilemma whether we should import it as we may only use no more than 10 in it. In such case re-definition seems to be a waste but importation would be too much weight. It can be even worse if we start a new one, then redefine some of them and add more for extension.

Thoughts?

Best wishes,
Haomian

发件人: OPSAWG [mailto:opsawg-bounces@ietf.org] 代表 Qin Wu
发送时间: 2020年6月4日 12:09
收件人: Joe Clarke (jclarke) <jclarke=40cisco.com@dmarc.ietf.org>; SAMIER BARGUIL GIRALDO <samier.barguilgiraldo.ext@telefonica.com>
抄送: OPSAWG@ietf.org
主题: Re: [OPSAWG] Minutes of L3NM/L2NM module discussions (27th-May-2020)

发件人: OPSAWG [mailto:opsawg-bounces@ietf.org] 代表 Joe Clarke (jclarke)
发送时间: 2020年6月4日 0:16
收件人: SAMIER BARGUIL GIRALDO <samier.barguilgiraldo.ext@telefonica.com<mailto:samier.barguilgiraldo.ext@telefonica.com>>
抄送: OPSAWG@ietf.org<mailto:OPSAWG@ietf.org>
主题: Re: [OPSAWG] Minutes of L3NM/L2NM module discussions (27th-May-2020)


The module is available in the following PULL REQUEST: https://github.com/IETF-OPSAWG-WG/l3nm/pull/118

I know other *types module have included groupings, but to add groupings in a types module seems wrong to me.  I would just expect typedefs and identities.

[Qin]: We lack a good usage guidance on which kind of groupings should be included in types module,
section 4.3 of RFC8407 said:
“
4.13<https://tools.ietf.org/html/rfc8407#section-4.13>.  Reusable Groupings

   A reusable grouping is a YANG grouping that can be imported by
   another module and is intended for use by other modules.
”
But it didn’t tell us whether the reusable grouping should be in the separate module or in the same type modules as identity and typedef.
Following some published type module examples,e.g.,RFC8294 and draft-ietf-teas-yang-te-types-13 in the RFC queue, it did add some of reusable grouping in the type modules, my impression is grouping that contain newly defined typedef and identities can be added into type modules, grouping in grouping, we need to be very carefully,
There are some guidance on reusable grouping in section 4.3 of RFC8407