IETF Logo Mail Archive

Re: [netconf] YANG attributes in a datastore

Martin Bjorklund <mbj@tail-f.com> Wed, 11 December 2019 08:30 UTC

Return-Path: <mbj@tail-f.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 BFD4A12081E for <netconf@ietfa.amsl.com>; Wed, 11 Dec 2019 00:30:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 3GGETxTk5Oic for <netconf@ietfa.amsl.com>; Wed, 11 Dec 2019 00:30:50 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id D186812022A for <netconf@ietf.org>; Wed, 11 Dec 2019 00:30:49 -0800 (PST)
Received: from localhost (unknown [173.38.220.41]) by mail.tail-f.com (Postfix) with ESMTPSA id 823C01AE0388; Wed, 11 Dec 2019 09:30:47 +0100 (CET)
Date: Wed, 11 Dec 2019 09:30:12 +0100
Message-Id: <20191211.093012.945147782345213985.mbj@tail-f.com>
To: lhotka@nic.cz
Cc: kent@watsen.net, andy@yumaworks.com, netconf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <7027e13e49a631ee06a8fe63ba3e2abf102963dc.camel@nic.cz>
References: <CABCOCHQfXSD8fr70Hcn9Epu+Dcs9_wA+-+7Y+kQqB9k5fKDsOQ@mail.gmail.com> <0100016ef0c6b0d8-cdbbe2ff-ac02-4692-b2c0-9f9b64ce4fc5-000000@email.amazonses.com> <7027e13e49a631ee06a8fe63ba3e2abf102963dc.camel@nic.cz>
X-Mailer: Mew version 6.8 on Emacs 25.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/-3w1fmw7c9EU5rczimofyikHVAU>
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 08:30:52 -0000

Ladislav Lhotka <lhotka@nic.cz> wrote:
> On Tue, 2019-12-10 at 17:06 +0000, Kent Watsen wrote:
> > > OK, but there is no way to prevent "annotation zipcode", etc.
> > > The use of foo="value" to set and foo="" to delete seems fine, but not sure
> > > any new
> > > standards are needed for that.
> > 
> > 
> > Metadata is not data.  Whilst syntacally possible, and some may attempt to
> > [mis-]use
> > it as such, we must hold the line that any IETF-defined metadata/annotations
> > do not
> > encode data.
> 
> While I agree with this, the original question remains: how to edit
> such metadata in an interoperable way. Deleting the annotation with
> foo="" may not always work, and indicating deletion with a special
> magic value is also brittle because such a value is not specified in
> the annotation's definition.

So far, noone is proposing to standardize anything.  The question was
if any implementation is doing this today, and if so, how.


/martin

v2.23.0 | Report a Bug | By Email