Re: [netmod] Fwd: New Version Notification for draft-ietf-netmod-yang-instance-file-format-01.txt

Robert Wilton <rwilton@cisco.com> Thu, 07 February 2019 12:10 UTC

Return-Path: <rwilton@cisco.com>
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 BD288131111 for <netmod@ietfa.amsl.com>; Thu, 7 Feb 2019 04:10:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.641
X-Spam-Level:
X-Spam-Status: No, score=-14.641 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 ZeqLYAKsKeEq for <netmod@ietfa.amsl.com>; Thu, 7 Feb 2019 04:10:24 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C738C12D4F2 for <netmod@ietf.org>; Thu, 7 Feb 2019 04:10:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16479; q=dns/txt; s=iport; t=1549541424; x=1550751024; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=F6zPw9ejPM+D6eaz4eXCAs2XbyTf44/Se8gKZyO9eoY=; b=DNRLhJofb+tFZlo1nVPBOqEYiHr4apJ/flR/Ow3Pro97zLgYSQrHXB63 MptZep0EioRZLbjtZ5I8J6vRTJ5K8Zaqjv0AHV3ePXB4XQOwr60Hr1XSj vIp1OjgwDV6EZXV7J4RA3JJdC0PRP9mMxKVF8Pfe/L57FrI0tuX1klCpx s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AFAAD/Hlxc/xbLJq0ZAUoZAQEBAQEBAQEBAQEBBwEBAQEBAYFRBAEBAQEBCwEBgmlQASASJ4QDiBpfjHAIJXyRJoVvFIFnDRgBDIQBRgKDQzQJDQEDAQECAQECbRwMhUoBAQEEAQEhSwkSCQIRAwECASoCAicoCAYBDAYCAQEXgwkBggEPjiiCe5thgS8fhBQCDkFAhGeMWoFAP4ERJwyCKjWDHgEBAgEBFoEUARIBCTaCaYI1IgKJWysCBYYoklsJhnNEiwgGGYFtUoR0gxcmh2WKLYEOhCqFHIcigUY4ZXEzGggbFRohgmwJgh8XE4hMhT8/AzABjDuCPgEB
X-IronPort-AV: E=Sophos;i="5.58,344,1544486400"; d="scan'208,217";a="9931662"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Feb 2019 12:10:21 +0000
Received: from [10.63.23.64] (dhcp-ensft1-uk-vla370-10-63-23-64.cisco.com [10.63.23.64]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTP id x17CAJQZ026261; Thu, 7 Feb 2019 12:10:20 GMT
To: Balázs Lengyel <balazs.lengyel@ericsson.com>, "netmod@ietf.org" <netmod@ietf.org>
References: <154409113299.3479.15867089668746650774.idtracker@ietfa.amsl.com> <35a31eae-9a4f-7d20-a9d3-6b0b60ac8a34@ericsson.com>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <c546ebd8-fa9c-2694-f9d1-a03ea4842543@cisco.com>
Date: Thu, 07 Feb 2019 12:10:19 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <35a31eae-9a4f-7d20-a9d3-6b0b60ac8a34@ericsson.com>
Content-Type: multipart/alternative; boundary="------------75B8BF7C7906B8957659A015"
Content-Language: en-US
X-Outbound-SMTP-Client: 10.63.23.64, dhcp-ensft1-uk-vla370-10-63-23-64.cisco.com
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/rMlU0fFB62GRGs9x0CYE_itjkPY>
Subject: Re: [netmod] Fwd: New Version Notification for draft-ietf-netmod-yang-instance-file-format-01.txt
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 07 Feb 2019 12:10:28 -0000

Hi Balazs,

Regarding identifying the instance data using a YANG package.

If the YANG packages work is liked by the WG and progresses, then it 
seems plausible that a YANG package could become a better way of 
identifying the set of modules rather than using YANG library for a 
couple of reasons:
  1) It will allow modules to be identified via semantic version rather 
than just revision date.  This will likely be more meaningful to readers.
  2) It allows for a much more concise definition.  Rather than having 
to try and infer what schema a particular set of YANG modules related to 
from the list of modules, it can instead refer to a single package 
definition and version number.
  3) YANG library (certainly RFC7895bis) defines the schema in terms of 
the datastore, so if this version of YANG library is being used then it 
is a bit more confusing as to which datastore is being referred to.  I 
appreciate that there is a datastore leaf in the instance data that can 
help mitigate this.

I also note that the draft currently binds that the only allowed inline 
schema is YANG library, but that seems somewhat overly restrictive, and 
perhaps this could be loosened to a leaf-list of inline module@revision 
definitions?

I also appreciate that you don't want to delay the instance data draft 
for YANG packages, bit I wonder whether the draft can easily facilitate 
using a YANG package definition in future if required.

Hence, rather than using a union for the "target pointer", I wonder 
whether it wouldn't be better to use a choice statement instead.

E.g. the choice statement could be something like this:

  choice "schema"
    leaf-list inline {
      type string {
        pattern '\w+@\d{4}-\d{2}-\d{2}\.yang';
      }
    }
    leaf yang-library-ref { type uri } // Points to a instance data 
document YANG library content.
  }

In future, the package draft could then augment (or update the revision) 
with something like this :

    container package-ref {
      leaf "name" { type string; }
      leaf "version" { type yang-semver; }
      leaf-list "url" { type uri; }// Points to a instance data document 
containing YANG package content.
    }

Thanks,
Rob

On 06/12/2018 10:15, Balázs Lengyel wrote:
>
> Hello,
>
> We uploaded a new version of the instance data draft. We tried to 
> address all comments and also to rework the format chapter to make it 
> easier to read. We omitted 2 comments:
>
> Rob commented that YANG packages could be used for defining the target 
> modules for instance data: I would like to avoid that because:
>
>   * Packages are not defined for YANG. Currently they are not part of
>     the versioning solution even though they were discussed and are
>     generally a good idea.
>   * IMHO as deviations/features are set on module level, just
>     specifying packages would not be enough. If we start using
>     package+module level deviations/features we may end up with a more
>     complicated hybrid solution.
>   * Module level YANG target definitions as described in the draft are
>     simple and need no new design
>
> Jürgen stated that it would be better to use the YANG XML/JSON 
> encoding as a format instead of referencing the get operation/request. 
> I might even agree with him, but for 2 reasons I did not follow his idea:
>
>   * Currently there is no RFC I could reference either for XML or
>     JSON. AFAIK even RFC7951 does not define how multiple modules
>     should be encoded side by side.
>   * It is not the job of the instance data draft to dictate how to
>     encode YANG data generally e.g. on the wire.
>   * The contents of the get operation/request are well defined
>
> regards Balazs
>
>
>
> -------- Forwarded Message --------
> Subject: 	New Version Notification for 
> draft-ietf-netmod-yang-instance-file-format-01.txt
> Date: 	Thu, 6 Dec 2018 02:12:12 -0800
> From: 	internet-drafts@ietf.org
> To: 	Benoit Claise <bclaise@cisco.com>, Balazs Lengyel 
> <balazs.lengyel@ericsson.com>
>
>
>
>
> A new version of I-D, draft-ietf-netmod-yang-instance-file-format-01.txt
> has been successfully submitted by Balazs Lengyel and posted to the
> IETF repository.
>
> Name: draft-ietf-netmod-yang-instance-file-format
> Revision: 01
> Title: YANG Instance Data File Format
> Document date: 2018-12-06
> Group: netmod
> Pages: 21
> URL: 
> https://www.ietf.org/internet-drafts/draft-ietf-netmod-yang-instance-file-format-01.txt
> Status: 
> https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-instance-file-format/
> Htmlized: 
> https://tools.ietf.org/html/draft-ietf-netmod-yang-instance-file-format-01
> Htmlized: 
> https://datatracker.ietf.org/doc/html/draft-ietf-netmod-yang-instance-file-format
> Diff: 
> https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-yang-instance-file-format-01
>
> Abstract:
> There is a need to document data defined in YANG models when a live
> YANG server is not available. Data is often needed already in design
> time or needed by groups that do not have a live running YANG server
> available. This document specifies a standard file format for YANG
> instance data, which follows the syntax and semantic from existing
> YANG models, re-using existing formats from <get> operation/request
> and decorates them with metadata.
>
>
>
> 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
>
> -- 
> Balazs Lengyel                       Ericsson Hungary Ltd.
> Senior Specialist
> Mobile: +36-70-330-7909              email:Balazs.Lengyel@ericsson.com  
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod