Re: [I2rs-proto-dt] couple YANG details

[Andy Bierman <[e-mail]>]

On Fri, Oct 23, 2015 at 1:36 PM, Susan Hares <[e-mail]> wrote:

> Andy:
>
>
>
> Sorry for the delay in responding.
>
>
>
> Declaring module-level “ephemeral” by declaring the top-node as ephemeral
> is fine.  However,   do you think people will want to query by the module
> library whether a module is ephemeral.
>

no - YANG does not need to make rules about what subset of statements
exist in a module. e.g., deviation-stmt is put in a regular YANG module.



>
>
> Sue
>
>
>


Andy


> *From:* I2rs-proto-dt [mailto:[e-mail]] *On Behalf
> Of *Andy Bierman
> *Sent:* Wednesday, October 21, 2015 5:46 PM
> *To:* Susan Hares; [e-mail]
> *Subject:* [I2rs-proto-dt] couple YANG details
>
>
>
> Hi,
>
>
>
> I would like to simplify the draft a bit further.
>
>
>
> 1) module-level "ephemeral" flag
>
> Since the data node flag applies to the entire subtree,
>
> it should be simple enough to just require each top-level
>
> data node to declare 'ephemeral true' if needed.
>
> There are usually 1 - 2 top-level data nodes per module so
>
> this is not a burden.  Checking 2 places is too complicated
>
> and they can conflict.
>
>
>
> 2) groupings wrt/ edit overlap
>
>
>
> YANG already has a way to say what sub-nodes must
>
> be present (mandatory=true, min-elements>0).
>
> Is this good enough for I2RS?  Can the requirements
>
> for the ephemeral version be different than the
>
> persistent version, wrt/ mandatory & min-elements?
>
>
>
>
>