Re: [netconf] YANG attributes in a datastore

Ladislav Lhotka <lhotka@nic.cz> Tue, 10 December 2019 14:24 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 A82F01200C1 for <netconf@ietfa.amsl.com>; Tue, 10 Dec 2019 06:24:38 -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 QvSuqQx46fi6 for <netconf@ietfa.amsl.com>; Tue, 10 Dec 2019 06:24:36 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (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 9AA96120088 for <netconf@ietf.org>; Tue, 10 Dec 2019 06:24:36 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:a88f:7eff:fed2:45f8]) by mail.nic.cz (Postfix) with ESMTPSA id 944DB140CE5 for <netconf@ietf.org>; Tue, 10 Dec 2019 15:24:34 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1575987874; bh=t1MqAphuoo7K7ojTB70gWfF3f/oAqE/GiX4qiLSdZfc=; h=From:To:Date; b=QpHCEnw770l6DaIo1bh+dkEY3+3rMxhb9rYCa/9DXNnSv53NAxIa+8GcL22ubns9S w6KhTbkAOx1ZtTTgIhQH+qIQssmbqs1GZB4BnXoj3hibwjDu7RMWo86qTExH3Cks4R 5l6k4HdjN64fKSlAtKvj0O+MqzZK+9DJiV2q1NOY=
Message-ID: <1eba9ea2d474ccc9cff0906e6f269fd9a532c03c.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: netconf@ietf.org
Date: Tue, 10 Dec 2019 15:24:34 +0100
In-Reply-To: <20191210.150333.2171238725445540389.mbj@tail-f.com>
References: <5cce-5def9a00-11-66c7ce00@101566344> <20191210.150333.2171238725445540389.mbj@tail-f.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/QTA1eqKLm6HBsbrALuGgkINHMgo>
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 14:24:39 -0000

On Tue, 2019-12-10 at 15:03 +0100, Martin Bjorklund wrote:
> 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.

Hmm, why don't you do simply

<foo/>

to delete the attribute?

Lada

> 
> 
> /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
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67