I was not alluding to malicious use but genuine use of I2rs interface in the absence of complete view of the latest network topology and/or view of what other I2RS client are doing or are about to do. There needs to be safeguards. I2RS needs to address consistency verification aspects.
If that is offloaded to some other entity, I2RS arch spec needs to explicitly mention that. /himanshu -----Original Message----- From: Joel M. Halpern [mailto:[email protected]] Sent: Wednesday, November 06, 2013 11:55 AM To: Shah, Himanshu; [email protected] Subject: Re: [i2rs] question on I2RS architecture If someone wants to create inconsistency using I2RS, we won't stop them. And although there was opne request for very precise timing on operations, that seems to me to be a step too far. Yours, Joel On 11/5/13 9:07 PM, Shah, Himanshu wrote: > /At the IETF I2RS interim meeting, I raised the concern about > conflicting set operations by I2RS clients to different I2RS agents,/ > > /Which may end up causing micro-loop or far-side loop. / > > // > > /Is this addressed in the architecture? / > > /May be this is responsibility of network orchestrator./ > > /If it is not mentioned in the doc, may be some text necessary to > explain??/ > > // > > /Thanks,/ > > /himanshu/ > > // > > /Himanshu Shah/ > > /Ciena Corp/ > > > > _______________________________________________ > i2rs mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/i2rs > _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
