On Oct 1, 2014, at 11:08 AM, Joel Halpern Direct <[email protected]> wrote:
> In line: > > On 10/1/14, 11:03 AM, Dean Bogdanovic wrote: >> >> On Oct 1, 2014, at 10:53 AM, Joel M. Halpern <[email protected]> >> 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.) >> >> How, if the client writes only into ephemeral store? > > There is nothing in the I2RS work that says that the only requests that the > I2RS client can make are creation or modify operations. It seems perfectly > legitimate for an I2RS client to decide that the what needs to be done is to > remove some static route or policy statement, because circumstances have > temporarily changed. That is opening a can of worms. You can not allow deletion of data that is not owned by the client. That can create instability of the system and the network. Using your example, I2RS client should enter a new static route or policy statement that would nullify the existing one. > > Yours, > Joel > > PS: THe same question still applied even if it can not delte, since having > the I2RS client write new values is not the same as removing the data. And > having an I2RS client issue a delete operation for something it has created > does not seem to mean the same thing as "return this to its previous value" > which is the required I2RS semantics. _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
