On Wed, Oct 01, 2014 at 10:53:48AM -0400, Joel M. Halpern wrote: > This actually does lead to a related question. > How does an I2RS client delte the state it has created. (Note that > said state might actually include a deletion from the underlying > data.)
This was briefly discussed at the netmod interim. With the idea that the "creator" is metadata that is part of the configuration, it becomes possible to craft new operations (rpc? extensions to netconf?) that effectively become "purge datastore (by createor-id)" The place this sort of "by creator-id" operation becomes messy is if two different clients of differing priorities have written to overlapping state - either from a schema perspective or from a dependency perspective. In such a case, deleting the higher-priority client state may lead to inconsistent configuration from what remains of the prior lower priority client state. The I2RS architecture basically says "send a notification this has happened and let the clients sort it out". -- Jeff _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
