Russ: [i2rs-co-chair hat on] Ed Crabbe broke things up into In-charter and out-of charter (see the use case drafts). Our AD (Alia) has us focusing on the Protocol independent use cases (first), and the topology use cases which are in-charter. [i2rs-co-chair-hat off]
If this helps you to come up with a protocol specification for the Protocol Independent, and a later protocols specification - please do. For 12/16 interim, it is appropriate to bring a draft and a set of sides to discuss these protocols. Can you help with that protocol specification? The BGP I2RS Info-model and Yang draft - has the informational model for the BGP portion of the specification. We do suggest changing policy and community strings. This work is progressing in IDR, but needs the protocol specification for the larger issues. I'm happy to feedback those needs to you. Does this help? Sue -----Original Message----- From: i2rs [mailto:[email protected]] On Behalf Of Russ White Sent: Monday, December 08, 2014 12:09 PM To: 'Dean Bogdanovic' Cc: [email protected]; 'Martin Bjorklund'; [email protected]; [email protected]; [email protected]; [email protected]; [email protected] Subject: Re: [i2rs] Point about writable running > Then we really have to write up use cases, settle on requirements and > decide on the protocol. The original use case documents covered this specific situation. We decided to expand the use cases for future use, I think, which then led to trying to solve all the problems listed there in the first swack, and as one problem set. Part of this was merging all the different use cases into a single set of use case drafts that make the problem set appear (maybe) more unified than it really is. It's perhaps more logical to look at the use cases we have and break them back down into "now," and "later," and along clear lines of requirement sets. I don't think we've actually done that work yet. :-) Russ _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
