Re: [netmod] augment YANG 1.0 with YANG 1.1 OK?

[Andy Bierman <[e-mail]>]

On Sun, Oct 15, 2017 at 12:52 AM, Martin Bjorklund <[e-mail]> wrote:

> Andy Bierman <[e-mail]> wrote:
> > Hi,
> >
> > RFC 7950 has no text at all that addresses this specific point:
> >
> > module if-aug {
> >   yang-version 1.1;
> >   namespace "http://netconfcentral.org/ns/if-aug";
> >   prefix ifa;
> >   import ietf-interfaces { prefix if; }
> >   revision "2017-10-14";
> >
> >   augment "/if:interfaces-state/if:interface" {
> >     action reset {
> >       description "Reset this interface";
> >     }
> >   }
> > }
> >
> > Both pyang and yangdump-pro accept this module with no warnings or
> errors.
> > Sec. 12 should address this issue.
>
> The intention was that this is legal, but as you note, for some reason
> there is no explicit text in 7950 about this.
>
>

that's what I thought.

Can you spot the NMDA problem above?
Actually, it exists for in-line definitions, not just augment.

Once you collapse the interfaces-state tree into /interfaces, there is no
way to
specify whether an action is intended for <operational> or a configuration
datastore,
or all datastores.

The parent container or list may be config=true just because the foo-state
tree
was taken away, and the moved action effectively changed from config=false
to config=true.

There is no way for the YANG action-stmt to specify a datastore (or
config-stmt)
There is no way for the <action> operation to specify a datastore.


This was issue Y60, see
> http://svn.tools.ietf.org/svn/wg/netmod/yang-1.1/issues.html#sec-61.
>
>
> /martin
>


Andy