Re: [netmod] Fwd: New Version Notification for draft-lengyel-netmod-yang-instance-data-01.txt

Ladislav Lhotka <lhotka@nic.cz> Tue, 26 June 2018 15:29 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C84A131038 for <netmod@ietfa.amsl.com>; Tue, 26 Jun 2018 08:29:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.999
X-Spam-Level:
X-Spam-Status: No, score=-6.999 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, 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 NFwbTDVFEucH for <netmod@ietfa.amsl.com>; Tue, 26 Jun 2018 08:29:41 -0700 (PDT)
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 58297130EAF for <netmod@ietf.org>; Tue, 26 Jun 2018 08:29:40 -0700 (PDT)
Received: from birdie (176.100.broadband6.iol.cz [88.101.100.176]) by mail.nic.cz (Postfix) with ESMTPSA id C3AA5604DF for <netmod@ietf.org>; Tue, 26 Jun 2018 17:29:37 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1530026977; bh=5d6PvM+Lj6PfTavZHvWTiy1//UL0wi8jRmsIUYrRDcY=; h=From:To:Date; b=kmK27/VuQhlaSb0z/HWz4K87L1X4xBOIb91syLbIyN0HUF9BmglE1Z9PqhEkji7jG zJTqHP7FkUltqHGsyBBZq0z46UV+SPuCyuiVlUM0JetUCqhFeV9JYhsdXzcXwVz8KE 15JzUoDyAYBdNJj17DUVzWzatg7IGNONBPIt4Wwg=
Message-ID: <c5b4efd70b166e902d1e855a1af0668308657e21.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: netmod@ietf.org
Date: Tue, 26 Jun 2018 17:30:15 +0200
In-Reply-To: <5d1ca9c3-75eb-9827-723b-9d9be67b7cff@ericsson.com>
References: <152889763632.15168.12247537431295038165.idtracker@ietfa.amsl.com> <75383a97-d08b-b202-70a6-eab064963af8@ericsson.com> <87y3fglcn6.fsf@nic.cz> <5d1ca9c3-75eb-9827-723b-9d9be67b7cff@ericsson.com>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.28.3
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/gxWypEp7WqF5vT0wzAOqV2DDNls>
Subject: Re: [netmod] Fwd: New Version Notification for draft-lengyel-netmod-yang-instance-data-01.txt
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jun 2018 15:29:45 -0000

On Tue, 2018-06-26 at 15:58 +0200, Balazs Lengyel wrote:
> Hello Lada,
> I don't insist on using yang-data-ext, but I like it.  Isn't this the exact
> use case for it: defining yang structured data that will never be loaded into
> a datastore. In this case the structure of the instance-data-set fits.

On the other hand, if it's never loaded into a datastore, there is no need to
encapsulate the data and break tools that don't support yang-data-ext.

The encapsulation is really needed only if such data is mixed with "real" YANG
data node definitions in the same module - for example, if error-message schemas
are defined along with datastore contents, operations etc. 

> If I would remove the yd:yang-data instance-data-format  statement it would
> not affect the actual file content. It just serves as  an indication that this
> is not  a datastore definition.

A comment in the module should perfecty suffice. Andy argued with machine
readability, but I don't see how it can be useful here.

And, after all, if a server implementor for whatever weird reason decides to
implement this module, what's wrong on doing so?

Lada

> regards Balazs
> 
> On 6/15/2018 9:41 AM, Ladislav Lhotka wrote:
> > Hi,
> > 
> > I support the adoption of this I-D as a workgroup item and my plan is to
> > implement it.
> > 
> > However, my suggestion is to avoid the use of yang-data-ext. It is
> > absolutely useless in this case and only complicates things that are
> > otherwise pretty trivial.
> > 
> > Lada
> > 
> > Balazs Lengyel <balazs.lengyel@ericsson.com>; writes:
> > 
> > > Hello, 
> > > 
> > > I submitted a new version of the yang-instance-data draft updated with
> > > comments from the last
> > > IETF and others. I would like to get this adopted as a workgroup item.
> > > Please review it and if you
> > > like it please indicate that you support it as a workgroup item.
> > > 
> > > Changes:
> > >    o  Redefined using yang-data-ext
> > >    o  Moved meta data into ordinary leafs/leaf-lists
> > >    o  Corrections, clarifications
> > > 
> > > regards Balazs 
> > > 
> > > -------- Forwarded Message -------- 
> > > 
> > >  Subject:   New Version Notification for draft-lengyel-netmod-yang-
> > > instance-data-01.txt  
> > >  Date:   Wed, 13 Jun 2018 06:47:16 -0700  
> > >  From:   internet-drafts@ietf.org  
> > >  To:   Benoit Claise <bclaise@cisco.com>;, Balazs Lengyel  
> > >    <balazs.lengyel@ericsson.com>;  
> > > 
> > > A new version of I-D, draft-lengyel-netmod-yang-instance-data-01.txt
> > > has been successfully submitted by Balazs Lengyel and posted to the
> > > IETF repository.
> > > 
> > > Name:		draft-lengyel-netmod-yang-instance-data
> > > Revision:	01
> > > Title:		YANG Instance Data Files and their use for
> > > Documenting Server Capabilities
> > > Document date:	2018-06-13
> > > Group:		Individual Submission
> > > Pages:		10
> > > URL:            https://www.ietf.org/internet-drafts/draft-lengyel-netmod-
> > > yang-instance-data-01.txt
> > > Status:         https://datatracker.ietf.org/doc/draft-lengyel-netmod-yang
> > > -instance-data/
> > > Htmlized:       https://tools.ietf.org/html/draft-lengyel-netmod-yang-inst
> > > ance-data-01
> > > Htmlized:       https://datatracker.ietf.org/doc/html/draft-lengyel-netmod
> > > -yang-instance-data
> > > Diff:           https://www.ietf.org/rfcdiff?url2=draft-lengyel-netmod-yan
> > > g-instance-data-01
> > > 
> > > Abstract:
> > >    This document specifies a standard file format for YANG instance
> > >    data, that is data that could be stored in a datastore and whose
> > >    syntax and semantics is defined by YANG models.  Instance data files
> > >    can be used to provide information that is defined in design time.
> > >    There is a need to document Server capabilities (which are often
> > >    specified in design time), which should be done using instance data
> > >    files.
> > > 
> > >                                                                           
> > >         
> > > 
> > > 
> > > Please note that it may take a couple of minutes from the time of
> > > submission
> > > until the htmlized version and diff are available at tools.ietf.org.
> > > 
> > > The IETF Secretariat
> > > 
> > > _______________________________________________
> > > netmod mailing list
> > > netmod@ietf.org
> > > https://www.ietf.org/mailman/listinfo/netmod
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67