Re: [netconf] YANG attributes in a datastore
Ladislav Lhotka <lhotka@nic.cz> Tue, 10 December 2019 16:33 UTC
Return-Path: <lhotka@nic.cz>
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 5D51112013B for <netconf@ietfa.amsl.com>; Tue, 10 Dec 2019 08:33:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.997
X-Spam-Level:
X-Spam-Status: No, score=-6.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 3S2-P-K2y234 for <netconf@ietfa.amsl.com>; Tue, 10 Dec 2019 08:33:39 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (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 0D3BA120043 for <netconf@ietf.org>; Tue, 10 Dec 2019 08:33:38 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:a88f:7eff:fed2:45f8]) by mail.nic.cz (Postfix) with ESMTPSA id 0ED5F140D14; Tue, 10 Dec 2019 17:33:36 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1575995616; bh=1r7Va06LQtTPvLDN3fv3kiu6PjxyJePP/O9je4KZJQ8=; h=From:To:Date; b=uTJo+TBGw2BCOsFSEECb0oxN1AIXH7ibqwCz37unE/bTYt+5fbpAL90g24Tpw09pm 5igBnnEBBu9heFZkTAMqZzASFSb+gas7gl5Qb0kWNIedC/mQv3Pbtt+1+gfhJHfxLG 8U9/3B5ftCxMYa6SjLRxdoCBhDLJNsnElAXTcvUM=
Message-ID: <411dd6ee5c435cee7042d042ec481acd111a7f92.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Andy Bierman <andy@yumaworks.com>
Cc: Netconf <netconf@ietf.org>
Date: Tue, 10 Dec 2019 17:33:35 +0100
In-Reply-To: <CABCOCHQsxzX3raf8FmbXCcQp3mdfFRrcGhSP5c88cumhdNJDVw@mail.gmail.com>
References: <5cce-5def9a00-11-66c7ce00@101566344> <20191210.150333.2171238725445540389.mbj@tail-f.com> <AM0PR0702MB3665FD1B4EFB1797333EE77DF05B0@AM0PR0702MB3665.eurprd07.prod.outlook.com> <514fe834eaa528c42f6dc31009399a3392b05dfe.camel@nic.cz> <CABCOCHSgZYDOVC7cj=1jaf4_N4pWc0B5vXPDmtm93vw5srrRkQ@mail.gmail.com> <677480c1606c027b43afda383378a5a9320b15dd.camel@nic.cz> <CABCOCHQsxzX3raf8FmbXCcQp3mdfFRrcGhSP5c88cumhdNJDVw@mail.gmail.com>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.34.2
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.100.3 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/QWHx8080NT-_A5eSg_-YVxdnmok>
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: Tue, 10 Dec 2019 16:33:42 -0000
On Tue, 2019-12-10 at 08:25 -0800, Andy Bierman wrote: > > > On Tue, Dec 10, 2019 at 7:50 AM Ladislav Lhotka <lhotka@nic.cz> wrote: > > On Tue, 2019-12-10 at 07:42 -0800, Andy Bierman wrote: > > > Hi, > > > > > > YANG already has the "annotation" statement to define metadata. > > > YANG has data-def-stmt to define data. It would be very unwise > > > to use metadata inside a leaf as if it were a leaf inside a container. > > > > 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. > > > > I understand the difference between annotation-stmt and leaf-stmt. > If the semantics can apply to all data nodes then annotation is appropriate. > We should not change the protocols and YANG to reinvent a leaf-stmt. Then I don't understand the point of your previous message. I think we've been talking about annotations as per RFC 7952 from the beginning of this thread (Michal just called it somewhat confusingly "attribute"). Lada > > When we created YANG 1.0, we explicitly rejected the then-current style of XML > > <address street="123 Elm" city="Anytown" zipcode="100036" /> > > We rejected the use of attributes as leafs. We should not change that decision > now. > > > > Lada > > > > Andy > > > > > > > > > > Andy > > > > > > > > > On Tue, Dec 10, 2019 at 7:31 AM Ladislav Lhotka <lhotka@nic.cz> wrote: > > > > On Tue, 2019-12-10 at 14:58 +0000, Balázs Lengyel wrote: > > > > > Hello, > > > > > If we try to standardize editing metadata, we will face a number of > > issues > > > > > that need to be clarified: > > > > > > > > > > - Will you model whether the attribute (metadata) is writable? Config > > is > > > > > not an allowed substatement in > > > > https://tools.ietf.org/html/rfc7952#section-3 > > > > > > > > In my view annotations should never be configuration because they should > > not > > > > influence the device state. The read-only/read-write propertly might be > > > > useful. > > > > > > > > > - Can a metadata have other additional properties? (mandatory, > > > > cardinality, > > > > > uniqueness of some kind?) > > > > > > > > By design, annotations do not have a specific place in the schema, so > > they > > > > cannot be mandatory. > > > > > > > > Cardinality: if you mean annotations with a list of values, this was > > > > discussed > > > > but rejected due to difficulties with XML encoding. > > > > > > > > > - If it is modified, will it be subject to validation, error-messages? > > > > Will > > > > > a bad metadata result in a failed error-config? > > > > > > > > I would say yes because otherwise it makes no sense to define them and > > their > > > > properties. > > > > > > > > Lada > > > > > > > > > > > > > > Regards Balazs > > > > > > > > > > -----Original Message----- > > > > > From: netconf <netconf-bounces@ietf.org> On Behalf Of Martin Bjorklund > > > > > Sent: 2019. december 10., kedd 15:04 > > > > > To: mvasko@cesnet.cz > > > > > Cc: netconf@ietf.org > > > > > Subject: Re: [netconf] YANG attributes in a datastore > > > > > > > > > > Hi, > > > > > > > > > > Michal Vaško <mvasko@cesnet.cz> wrote: > > > > > > Hello, > > > > > > we are thinking about adding support for arbitrary attributes [1] > > in > > > > > > our YANG/NETCONF datastore. To my knowledge, only the > > representation > > > > > > in XML or JSON is defined and standardized but there are no > > guidelines > > > > > > for editing (CRUD) these attributes. > > > > > > > > > > > > So, my question is a rather general one, regarding implementations > > > > > > that support editing these attributes, would you mind sharing some > > > > > > basic ideas or principles used? Or is this outside any consensus > > and > > > > > > each implementation is free to handle this completely in its own > > > > > > fashion? Thanks for any input. > > > > > > > > > > I think this depends on the attribute defintion. Some attributes are > > > > > read-only from the northbound's protocol point of view. Internally in > > the > > > > > server you may need some API to set/change them of course. Some other > > > > > attributes are read-write. > > > > > > > > > > In our implementation we support a few read-write attributes (and some > > > > > read-only). Here's a simple example (in an edit-config): > > > > > > > > > > <foo annotation="hello"/> > > > > > > > > > > This would set/change the "annotation" attribute's value to "hello", > > > > > regardless of its previous value. > > > > > > > > > > To delete an annotation, you would do: > > > > > > > > > > <foo annotation=""/> > > > > > > > > > > Each of our attributes has a special value that means "delete" (in > > most > > > > > cases it is the empty string. > > > > > > > > > > > > > > > /martin > > > > > > > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > Michal > > > > > > > > > > > > [1] https://tools.ietf.org/html/rfc7952 > > > > > > > > > > > > _______________________________________________ > > > > > > netconf mailing list > > > > > > netconf@ietf.org > > > > > > https://www.ietf.org/mailman/listinfo/netconf > > > > > > > > > > > _______________________________________________ > > > > > netconf mailing list > > > > > netconf@ietf.org > > > > > https://www.ietf.org/mailman/listinfo/netconf > > > > > _______________________________________________ > > > > > netconf mailing list > > > > > netconf@ietf.org > > > > > https://www.ietf.org/mailman/listinfo/netconf -- Ladislav Lhotka Head, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67
- [netconf] YANG attributes in a datastore Michal Vaško
- Re: [netconf] YANG attributes in a datastore Ladislav Lhotka
- Re: [netconf] YANG attributes in a datastore Martin Bjorklund
- Re: [netconf] YANG attributes in a datastore Ladislav Lhotka
- Re: [netconf] YANG attributes in a datastore Martin Bjorklund
- Re: [netconf] YANG attributes in a datastore Balázs Lengyel
- Re: [netconf] YANG attributes in a datastore Ladislav Lhotka
- Re: [netconf] YANG attributes in a datastore Andy Bierman
- Re: [netconf] YANG attributes in a datastore Ladislav Lhotka
- Re: [netconf] YANG attributes in a datastore Kent Watsen
- Re: [netconf] YANG attributes in a datastore Andy Bierman
- Re: [netconf] YANG attributes in a datastore Ladislav Lhotka
- Re: [netconf] YANG attributes in a datastore Andy Bierman
- Re: [netconf] YANG attributes in a datastore Kent Watsen
- Re: [netconf] YANG attributes in a datastore Qin Wu
- Re: [netconf] YANG attributes in a datastore Qin Wu
- Re: [netconf] YANG attributes in a datastore Ladislav Lhotka
- Re: [netconf] YANG attributes in a datastore Martin Bjorklund
- Re: [netconf] YANG attributes in a datastore Kent Watsen
- Re: [netconf] YANG attributes in a datastore Kent Watsen
- Re: [netconf] YANG attributes in a datastore Andy Bierman
- Re: [netconf] YANG attributes in a datastore Andy Bierman