IETF Logo Mail Archive

[netconf] YANG attributes in a datastore

Michal Vaško <mvasko@cesnet.cz> Tue, 10 December 2019 13:12 UTC

Return-Path: <mvasko@cesnet.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 919B51200A1 for <netconf@ietfa.amsl.com>; Tue, 10 Dec 2019 05:12:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=cesnet.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 vbhUMmavNV80 for <netconf@ietfa.amsl.com>; Tue, 10 Dec 2019 05:12:51 -0800 (PST)
Received: from kalendar.cesnet.cz (kalendar.cesnet.cz [IPv6:2001:718:1:1f:50:56ff:feee:34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F27512009E for <netconf@ietf.org>; Tue, 10 Dec 2019 05:12:51 -0800 (PST)
Received: by kalendar.cesnet.cz (Postfix, from userid 999) id 6D65460182; Tue, 10 Dec 2019 14:12:49 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cesnet.cz; s=kalendar; t=1575983569; bh=Jqka26GdTxMWyq8c9SSsK/JaMkRRW2fTKUKOWe3M9C0=; h=To:Date:Subject:From; b=GbP1h7GmmDQ90z0RbyUbWATvJUMBzBJ0dRoWM3g2SpdvcUoCWMypaD9ebCvPVv3rq MZ7Mr6BJrb/jILK5HMzDIFhBhGRz6oQgLdNDXu4C7SCnss0r7n8IO7FRnGC06/R4nh wylPrWfjdPpX7TzVHAJcqAZKL5QedVaSPeEYYoIc=
Content-Type: text/plain; charset="utf-8"
To: netconf <netconf@ietf.org>
User-Agent: SOGoMail 2.3.23
MIME-Version: 1.0
Date: Tue, 10 Dec 2019 14:12:49 +0100
Message-ID: <5cce-5def9a00-11-66c7ce00@101566344>
X-Forward: 2001:67c:1220:80c:b5:55d3:81d5:8636
From: Michal Vaško <mvasko@cesnet.cz>
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/XiqarW5cpq6XB6v0TieLBWWMzGM>
Subject: [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:12:53 -0000

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.

Regards,
Michal

[1] https://tools.ietf.org/html/rfc7952

v2.23.0 | Report a Bug | By Email