IETF Logo Mail Archive

Re: [netconf] YANG attributes in a datastore

Ladislav Lhotka <lhotka@nic.cz> Wed, 11 December 2019 07:59 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 58E8112088C for <netconf@ietfa.amsl.com>; Tue, 10 Dec 2019 23:59:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.998
X-Spam-Level:
X-Spam-Status: No, score=-6.998 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] 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 MbhK3pGrxqJX for <netconf@ietfa.amsl.com>; Tue, 10 Dec 2019 23:59:25 -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 CD078120891 for <netconf@ietf.org>; Tue, 10 Dec 2019 23:59:20 -0800 (PST)
Received: from birdie (unknown [IPv6:2a01:5e0:29:ffff:fc73:fa64:57e6:2115]) by mail.nic.cz (Postfix) with ESMTPSA id 2FDA0140CB3; Wed, 11 Dec 2019 08:59:18 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1576051158; bh=7Pg7mseUY47uXXMY16DtveTw3js16Ya2UQrayt0x3kc=; h=From:To:Date; b=NiSeW/MfL5I9NrzfqolV1RlbR/eX4yTc2pl5dcfQNytDR6MgFrbb5P6e4DuTxT7gJ 1ALID3fkUXRgthWqYs/haJw4A87YqRn1ijxjxflbLZ/QvCypm8XdirCGJ3V5NFegix Mo1xIXkuSdKqqhbdeNNi0sCIZMuzyGu72sJow0Wg=
Message-ID: <7027e13e49a631ee06a8fe63ba3e2abf102963dc.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Kent Watsen <kent@watsen.net>, Andy Bierman <andy@yumaworks.com>
Cc: "netconf@ietf.org" <netconf@ietf.org>
Date: Wed, 11 Dec 2019 08:59:17 +0100
In-Reply-To: <0100016ef0c6b0d8-cdbbe2ff-ac02-4692-b2c0-9f9b64ce4fc5-000000@email.amazonses.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> <411dd6ee5c435cee7042d042ec481acd111a7f92.camel@nic.cz> <CABCOCHQfXSD8fr70Hcn9Epu+Dcs9_wA+-+7Y+kQqB9k5fKDsOQ@mail.gmail.com> <0100016ef0c6b0d8-cdbbe2ff-ac02-4692-b2c0-9f9b64ce4fc5-000000@email.amazonses.com>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.34.2
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.100.3 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/S96nDwYhQCTFp1WLNw5s30JtPNU>
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 07:59:27 -0000

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.

Lada  

> 
> Kent // contributor
> 
> 
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67

v2.23.0 | Report a Bug | By Email