Sue, As Alia says, in-line as always :)
> On Nov 23, 2015, at 9:57 PM, Susan Hares <[email protected]> wrote: > > Acee: > > Is your input individual input or input from the routing architecture for > yang models? > > <I2RS chair hat on> > The routing architecture for yang models is incomplete without the > consideration of the I2RS ephemeral state and I2RS architecture. Asking the > I2RS WG to change a document that is in WG LC based on an incomplete > architectural document is not reasonable. An alignment between > https://datatracker.ietf.org/doc/draft-ietf-netmod-routing-cfg/ > <https://datatracker.ietf.org/doc/draft-ietf-netmod-routing-cfg/> without the > consideration of the I2RS ephemeral state is an incomplete alignment and a > problematic approach for I2RS WG’s efforts. I’m still trying to figure out what is exactly I2RS ephemeral state. RIB and FIB by definition are ephemeral. Results of routing protocols are ephemeral. The only persistence in it are input parameters that will define the initial behavior of the protocol, but after that everything is ephemeral. IMO, I2RS agent should almost have no persistence configuration, except basic management and the I2RS client definitions. Dean
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
