The diagram is a high-level conceptual picture mostly showing connections from i2rs to other aspects of the box. The RIB Manager is, I think, the exception.
Alia On Fri, Mar 1, 2013 at 1:11 PM, Russ White <[email protected]> wrote: > >> I'd find it helpful if we could agree to use Alia's terminology from >> draft-atlas-i2rs-problem-statement-01, specifically "Policy Database" >> and "RIB Manager", or clarify what's wrong with that terminology. > > IMHO, this terminology isn't specific enough to drive the discussion... > The policy manager, as shown in problem-statement, controls what kind of > policy for which elements which is inserted where? What's the difference > between the connection to the "routing and signaling protocols," box, > and the "RIB Manager?" > > Further, the drawing in problem-statement appears to assume a local > process called the "I2RS agent," which intercedes between the policy and > database injection points and the I2RS client/applications. I don't > think we're going to build a solid data model if we're building a model > around a local process, with it's own internal database, processes, and > policy, rather than targeting the ultimate end users of the information > (the policy and database in each of the independent processes). > > :-) > > 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
