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

[Balázs Lengyel <[e-mail]>]

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:	[e-mail]
To:	Benoit Claise <[e-mail]>, Balazs Lengyel <[e-mail]>

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" rel="nofollow">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/" rel="nofollow">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" rel="nofollow">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" rel="nofollow">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" rel="nofollow">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: [phone]              email: [e-mail]