Jeff: Yes, this could be another way to look at it.
Sue -----Original Message----- From: Jeffrey Haas [mailto:[email protected]] Sent: Tuesday, May 31, 2016 5:58 PM To: Susan Hares Cc: 'Joel M. Halpern'; [email protected] Subject: Re: [i2rs] ephemeral RPC? Sue, Rather than saying "ephemeral RPC", I suspect you mean an RPC that has impact on ephemeral configuration or operational state. Arguably, if the RPC in question only manifests as operational state for that case the idea of ephemeral configuration in yang may become moot. -- Jeff On Tue, May 31, 2016 at 04:23:54PM -0400, Susan Hares wrote: > Joel: > > I2RS data model is a ephemeral-only data model, and uses an rpc to do > rib add/delete, route add/delete, nexthop add/delete. Therefore, we > need ephemeral rpc support. > > > Sue > > -----Original Message----- > From: i2rs [mailto:[email protected]] On Behalf Of Joel M. Halpern > Sent: Tuesday, May 31, 2016 12:34 PM > To: [email protected] > Subject: [i2rs] ephemeral RPC? > > We have agreed that non-ephemeral data must not reference ephemeral data. > > However, we have, up till now, not had the notion of ephemeral RPCs. > I see that the recent ephemeral requirements draft, as a side-effect > of improving clarity, creates the notion of an ephemeral RPC. > > What is an ephemeral RPC, and why do we have it? > We have been, up till now, assuming that we could use normal NetConf > RPCs to set and get the ephemeral information. > > Thank you, > Joel > > _______________________________________________ > i2rs mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/i2rs > > _______________________________________________ > i2rs mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/i2rs _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
