Jeff:

Could you give me an example of the interim's thoughts on commit versus
Alexander's message: 

http://www.ietf.org/mail-archive/web/i2rs/current/msg01974.html

Sue 

-----Original Message-----
From: i2rs [mailto:[email protected]] On Behalf Of Jeffrey Haas
Sent: Wednesday, September 24, 2014 11:44 AM
To: Susan Hares
Cc: 'Jeffrey Haas'; [email protected]; [email protected]
Subject: Re: [i2rs] Summary of discussion from netmod interim on i2rs
requirements on netmod/netconf

Sue,

On Tue, Sep 23, 2014 at 06:14:16PM -0400, Susan Hares wrote:
> The fourth option is interesting and creative. A few 
> questions/requests: 1) How would the fourth model be expressed in the 
> yang model  - config (empheral)?

I believe Juergen has answered this point.

> 2)  Please define your definition of local config with an example.,

This corresponds to "config true" state, probably in the running datastore.
The semantics on the impact for the commit model when writable-running is
not in use haven't been fully explored.

> and 3) please give an example of the (must, when) use cases 
> envisioned?

In the original proposal in my draft, when we had completely disjoint
datastores, consider the BGP I2RS ephemeral peer case.  The I2RS model would
have a container of ephemeral peers.  That container might not specify the
local Autonomous System number.  In that case, there would be a MUST
requirement for that neighbor that there exist a system-wide configured
Autonomous System number, probably in the local Config.

Currently, there is no syntax that says how to examine nodes that are in a
different datastore.  From an XPath context, the current datastore is the
document context.

In the new proposal, since the ephemeral datastore gets a shadow of the
local config, there is no need to have extensions to XPath to refer between
data stores.

However, if we end up with more than one ephemeral datastore (not
recommended for this reason), such an issue returns.

-- Jeff

_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs

_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs

Reply via email to