Re: [I2rs-proto-dt] [i2rs] inteirm 10/7/20

[Andy Bierman <[e-mail]>]

On Sun, Oct 11, 2015 at 10:51 AM, Juergen Schoenwaelder <
[e-mail]> wrote:

> On Sun, Oct 11, 2015 at 09:55:31AM -0700, Andy Bierman wrote:
> > On Sun, Oct 11, 2015 at 9:11 AM, Juergen Schoenwaelder <
> > [e-mail]> wrote:
> >
> > > On Fri, Oct 09, 2015 at 04:13:03PM -0400, Susan Hares wrote:
> > > > The 10/7/2015 interim discussed the ephemeral portion of the protocol
> > > >
> > > >
> > > >
> > > > 1)      Ephemeral state is not unique to zI2RS
> > > >
> > > > 2)      The ephemeral datastore is a datastore holds
> > > >
> > > > configuration that is intended to not survive a reboot.
> > > >
> > >
> > > Configuration as YANG config true or a subset thereof?
> > >
> >
> >
> > config=true nodes only.
>
> good
>
> > Some way is needed to specify I2RS conformance for
> > a given YANG module, unless every persistent config leaf
> > is expected to also be supported as ephemeral data.
> >
> > If not, a YANG "ephemeral-stmt" is probably needed, since
> > config=true is insufficient to support I2RS conformance.
>
> One question is whether this needs to be inline in the data model or
> not. If conformance is the goal, then you know what having things
> defined inline has limits. If we would address conformance in more
> general terms, perhaps I2RS conformance falls out as a special case.
>
> > One ephemeral datastore.
> > No client panes.  That was to support caching, but
> > the architecture forbids caching, so that was taken out.
> >
> > One ephemeral pane that overrides the running datastore
>
> good
>
> > > Identities? I assume you mean schema nodes, do you?  Adding by
> > > defining an YANG extension such as i2rs:ephemeral true? How does such
> > > an i2rs:ephemeral true interplay with config true/false? What about
> > > contexts for must/when expressions? Or is the idea to settle on
> > > RESTCONF and to work with YANG patch?
> > >
> >
> > I think a real keyword is needed not an extension.
> > Otherwise YANG groupings cannot be utilized w/ statements
> > that are refined in the uses-stmt to set the ephemeral flag.
>
> I fail to understand the groupings argument.
>


The refine-stmt is defined to work on YANG statements, not external
statements.

A YANG extension is (by definition) something external to the YANG language.
The WG needs to decide if the ephemeral property should be specific to
an I2RS YANG module or should be basic property of the YANG data modeling
language.  YANG keywords must be supported and they do not need
to be imported from a YANG module to be used.



> > NETCONF has no edit ordering or ability to return a partial
> > error. IMO only RESTCONF is needed.  Proposals to
> > improve NETCONF editing to support YANG Patch have
> > already been made, and the WG had higher priorities.
> > I don't see why 2 protocols are needed instead of 1.
>
> Perhaps the WG should discuss and decide. If all the WG wants is
> RESTCONF, then we can simplify the discussion.



>
>
/js
>
>

Andy



> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   [phone]         <http://www.jacobs-university.de/>
>