"Joel M. Halpern" <[email protected]> wrote: > I had assumed that the YANG "datastore" was the repository in which the I2RS > agent stored all of the operations it had applied, who had applied them, etc.
Yes. > This actually does lead to a related question. > How does an I2RS client delte the state it has created. (Jeff replied to this) > (Note that said state > might actually include a deletion from the underlying data.) Right, we also discussed this at the interim. The idea we discussed was the ability to tag a subtree with an operation, which could be "merge", "replace" or "delete" (with "merge" being the default). > The client is not required to have the knowledge of what the config / I2RS > state was before it performed its operation. In this case it probably should use the "replace" operation - this ensures that the data in the "active" config is exactly what's in the ephemeral store, regardless of what was in the local config. /martin _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
