Re: [netmod] instance file parsing

Robert Wilton <rwilton@cisco.com> Fri, 30 November 2018 19:07 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 DBDFE130F33 for <netmod@ietfa.amsl.com>; Fri, 30 Nov 2018 11:07:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.958
X-Spam-Level:
X-Spam-Status: No, score=-15.958 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, 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 i7PRSqGOk431 for <netmod@ietfa.amsl.com>; Fri, 30 Nov 2018 11:07:07 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7749C130E5A for <netmod@ietf.org>; Fri, 30 Nov 2018 11:07:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3686; q=dns/txt; s=iport; t=1543604826; x=1544814426; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=M5obiQPTZVFCN8Tb2CooNPBP200qNYgM0lDJ1F2w0zc=; b=Biq8LJZApbchchCzl0/DRTWNYSyeQuhywgs8akY2x/obya+hBnBovD+/ fZ2Kwq8c6bUTs1BobjSliQqOLG3t9tFrSQoMeaEEBTGuSkdIOEBjP05Q9 kGmyS9u4sExtpSrTre0AB1W7uD2W0+EE6r6yV84oB1l4Uh6z+NZzBXvOr 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AGAABoiQFc/xbLJq1jGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUgMBAQEBAQsBgmmBAieDeYh3jQstkXKFVoF6DRgBCoQ?= =?us-ascii?q?DRgKDVjUIDQEDAQECAQECbRwMhT0BAQQBASFLGwsEFCoCAicwBgEMBgIBAYM?= =?us-ascii?q?dAYIBD6ZpgS8fhSGEZgWMMYFAP4E4gmuDHgEBhGWCNSICiVuWWgmRMQYYiWm?= =?us-ascii?q?HNoh7iHqGaIFHATYngS4zGggbFTuCbIschT8/AzCORwEB?=
X-IronPort-AV: E=Sophos;i="5.56,299,1539648000"; d="scan'208,217";a="8443296"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Nov 2018 19:07:03 +0000
Received: from [10.61.98.244] (dhcp-10-61-98-244.cisco.com [10.61.98.244]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTP id wAUJ73wX025631; Fri, 30 Nov 2018 19:07:03 GMT
To: Andy Bierman <andy@yumaworks.com>, NetMod WG <netmod@ietf.org>
References: <CABCOCHQYR_iY7Lp=0m8D-GQ8+Rzuijaa8_41bJw6ZvWPc+Cw_w@mail.gmail.com>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <b2ee0537-465a-fbc0-1b94-000da5993b05@cisco.com>
Date: Fri, 30 Nov 2018 19:07:03 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1
MIME-Version: 1.0
In-Reply-To: <CABCOCHQYR_iY7Lp=0m8D-GQ8+Rzuijaa8_41bJw6ZvWPc+Cw_w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------69A02B736D89796745E7B16C"
Content-Language: en-US
X-Outbound-SMTP-Client: 10.61.98.244, dhcp-10-61-98-244.cisco.com
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/CgCT9SNwJg8r2ucXA5ObXCsm6AM>
Subject: Re: [netmod] instance file parsing
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: Fri, 30 Nov 2018 19:07:09 -0000

I also think that the instance data header needs to have a way of 
indicating which modules (and versions/revisions) the instance data 
applies to.

It can be optional, so producers that know it is not required can leave 
it out.  But I think that it is required, at least for situations where 
being able to programmatically consume the instance data in a robust way 
is important.

Thanks,
Rob


On 30/11/2018 17:48, Andy Bierman wrote:
> Hi,
>
> I don't see much standards value in this draft so far.
> It seems the parser of the file needs to know the YANG library information
> for the instance file data in some out-of-scope non-standard manner.
> This is what we already have today just by naming the file in a 
> specific way.
>
> Is the intent that the instance-data-set leafs will be used to determine
> the module revisions, features, and deviations used in the children
> or the 'data' node?
>
> Andy
>
>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod