Hi Martin,

One comment below.


> -----Original Message-----
> From: netmod <[email protected]> On Behalf Of Martin Bjorklund
> Sent: 18 November 2019 19:54
> To: [email protected]
> Cc: [email protected]
> Subject: Re: [netmod] comments on draft-ietf-netmod-yang-instance-file-
> format-04
> 
> Balázs Lengyel <[email protected]> wrote:
> >
> >

[RW] <snipped>
> >
> > BALAZS3: People explicitly asked for a short, simple solution, so
> > reusing the well-known module-file-naming format seemed logical, and
> > nobody misunderstood it till now.
> > I would really like to avoid creating a list with 2 separate leaf's:
> > longer, more complex. It goes against the express wishes of other
> > group members.
> > If you prefer we can drop the file extension.
> 
> Yes I think this is better.
> 
> > IMHO it will look strange.
> 
> Perhaps this document will set the standard for future references to
> modules, so that this short-hand notation is used in more places, rather
> than separate name / revision leafs...
> 
[RW] 
The module versioning draft (draft-verdt-netmod-yang-module-versioning) allows 
modules to be identified by their name and revision-label, e.g. from section 
3.3:

   If a revision has an associated revision label, then it may be used
   instead of the revision date in two places:

      In an "rev:revision-or-derived" extension statement argument.

      In the filename of a YANG module, where it takes the form: module-
      or-submodule-name ['@' revision-label] ( '.yang' / '.yin' )

Obviously the revision label could be a YANG semver, e.g. it would be nice if 
we were allowed strings like:
  "[email protected]" rather than forcing it to use the revision date.

The module versioning draft hasn't been adopted as a WG item yet, but I'm 
hoping that this can be considered, along with the other drafts soon.

Thanks,
Rob


> BTW, you mentioned in your presentation of draft-ietf-netconf-
> notification-capabilities that this doc will be impacted by changes in
> draft-ietf-netmod-yang-instance-file-format.  I think that this is ok and
> we continue the process for this document.
> The RFC editor won't publish it until instance-file-format is done, so
> there is time to fix the examples.
> 
> 
> /martin
> _______________________________________________
> netmod mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/netmod
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to