IETF Logo Mail Archive

Re: [netconf] YANG attributes in a datastore

Ladislav Lhotka <lhotka@nic.cz> Tue, 10 December 2019 13:31 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 635A3120041 for <netconf@ietfa.amsl.com>; Tue, 10 Dec 2019 05:31:11 -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 mSjDgis9DLFp for <netconf@ietfa.amsl.com>; Tue, 10 Dec 2019 05:31:08 -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 82EBE120018 for <netconf@ietf.org>; Tue, 10 Dec 2019 05:31:08 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:a88f:7eff:fed2:45f8]) by mail.nic.cz (Postfix) with ESMTPSA id AFCB8140BA7 for <netconf@ietf.org>; Tue, 10 Dec 2019 14:31:06 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1575984666; bh=PedyzemViQBSVttBl75P0kEkfuLXoUeR2jdqaxxTWcQ=; h=From:To:Date; b=L/eC7XME0tsWibHQbmbI+guJdvId5EHptX/vJmkuJ04b2oVwdFtUMA4MF3kDZ0aZW CjtKupE+TJIAHMvKO9nDcrVFs1Bqp5MlxuBf4riNxczk6fQ/Y3HnNgFYhMUgacaKkr P6kMdn2g3KbgVItGhSSpTKkBNTxsk0tEYhJ7+9bM=
Message-ID: <f7e5a5f7bc9bb4e212dfc5a17188e28d9346cd68.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: netconf@ietf.org
Date: Tue, 10 Dec 2019 14:31:06 +0100
In-Reply-To: <5cce-5def9a00-11-66c7ce00@101566344>
References: <5cce-5def9a00-11-66c7ce00@101566344>
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/OVi-Q6BDvS67t6zVfoPsx0-EUZo>
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 13:31:11 -0000

On Tue, 2019-12-10 at 14:12 +0100, Michal Vaško 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 guess this should eventually be standardized in each protocol, so it makes
sense to figure out the current practices.

Lada

> 
> Regards,
> Michal
> 
> [1] https://tools.ietf.org/html/rfc7952
> 
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67

v2.23.0 | Report a Bug | By Email