IETF Logo Mail Archive

Re: [netconf] YANG attributes in a datastore

Qin Wu <bill.wu@huawei.com> Wed, 11 December 2019 01:46 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B43E120059 for <netconf@ietfa.amsl.com>; Tue, 10 Dec 2019 17:46:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 fWysR0WD8GVg for <netconf@ietfa.amsl.com>; Tue, 10 Dec 2019 17:46:45 -0800 (PST)
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 A7DCF12025D for <netconf@ietf.org>; Tue, 10 Dec 2019 17:46:44 -0800 (PST)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 5415DB4E17B620C0F94F; Wed, 11 Dec 2019 01:46:43 +0000 (GMT)
Received: from lhreml705-chm.china.huawei.com (10.201.108.54) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 11 Dec 2019 01:46:43 +0000
Received: from lhreml705-chm.china.huawei.com (10.201.108.54) by lhreml705-chm.china.huawei.com (10.201.108.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Wed, 11 Dec 2019 01:46:42 +0000
Received: from DGGEML401-HUB.china.huawei.com (10.3.17.32) by lhreml705-chm.china.huawei.com (10.201.108.54) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Wed, 11 Dec 2019 01:46:42 +0000
Received: from DGGEML511-MBX.china.huawei.com ([169.254.1.39]) by DGGEML401-HUB.china.huawei.com ([fe80::89ed:853e:30a9:2a79%31]) with mapi id 14.03.0439.000; Wed, 11 Dec 2019 09:46:37 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Kent Watsen <kent+ietf@watsen.net>, Ladislav Lhotka <lhotka@nic.cz>
CC: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [netconf] YANG attributes in a datastore
Thread-Index: AdWvv1tiGaIJuapiQGa4ub0lAMbRUw==
Date: Wed, 11 Dec 2019 01:46:36 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAA94F0F2D@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.134.31.203]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAA94F0F2Ddggeml511mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/OliMhVZjHXeDtjUPw-b16yNTLEQ>
Subject: Re: [netconf] YANG attributes in a datastore
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Dec 2019 01:46:46 -0000

Kent:
How “enable” attribute is different from if-feature statement?

-Qin
发件人: netconf [mailto:netconf-bounces@ietf.org] 代表 Kent Watsen
发送时间: 2019年12月11日 0:20
收件人: Ladislav Lhotka <lhotka@nic.cz>
抄送: netconf@ietf.org
主题: Re: [netconf] YANG attributes in a datastore


A typical example is a "comment" annotation - you want to permit it basically
everywhere but don't want to clutter the schema with "comment" leaves.

These are what I refer to as "cross-cutting" metadata attributes.  Another example
is the "enabled" attribute defined in draft-kwatsen-conditional-enablement.

Kent // contributor

v2.23.0 | Report a Bug | By Email