On Sat, Apr 19, 2014 at 4:11 PM, Dean Bogdanovic <[email protected]> wrote:
> It comes down how many transactions are required? Will you updated 1000 > routes in single transaction or in 1000 transactions. > Take your pick. The point is it boils down to how that is modelled and carried over the wire (and influences those decisions). > From my perspective there are two important metrics for i2rs > throughput > and > latency > Now we are talking. > > IMO, I2RS agent has to provide as high as possible throughput and add minimal > latency to the >process. What is the throughput required? Don't know at the > moment. I saw some request in high >single digit thousands per second, but > not sure about use cases. On the latency side, you want it as >close to 0 as > possible, but that will be highly platform dependent. > Agreed. > I have to start doing some PoCs to see what can and can not do with existing > tools. If those tools >work, then good. If those tools don't work, then back > to the drawing board. Until things work, keep on >moving with what works and > try to find break points. > But i do believe there are limitations which are not obvious without contrasting against requirements. > You can add your comments to the existing drafts. > I would gladly do - but i worry whether the discussion is about crowning some solution instead of meeting such objectives; if the WG decides to move in that direction i would be happy to contribute. There's material floating, the old protocol draft; Joel pointed to the architecture draft covering model requirements. Andy mentioned possible "stretch" requirements. I think what would be appropriate is one draft for the model and one for the protocol with gap analysis. >> >> Unfortunately - we are not having that kind of useful discussion and i >> feel like a broken >> record asking for requirements. > > I believe we have a set of requirements. It is in > draft-rfernando-i2rs-protocol-requirements. >You can always comment that draft and argue pro and con each requirement. Glad we are bringing that draft into play;-> How does restconf fair against it? Note: The draft is a good starting point but is missing as an example the issue of latency and throughput. cheers, jamal _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
