> I2RS facilitates real-time or event driven interaction with the > routing system through a collection of control or management > interfaces. These allow information, policies, and operational > parameters to be injected into and retrieved (as read or by > notification) from the routing system while retaining data > consistency and coherency across the routers and routing > infrastructure, and among multiple interactions with the routing > system. > > Nowhere that I can see does it give me any idea what the target of these > interfaces is: what is it that you want having interaction with the routing > system?
I want a protocol/user or multi protocols having that relation with RSs. Why not having interaction? IMO, we let the Use-Case for each document to answer, and others to answer why not. > What is it that will inject information, policies, and operational > parameters, that can't do so now? > Q) Does the RS not need external information?, and does the RS can do every thing for users without help? IF the Q answer is yes, THEN , we can *do so now* and lets close I2RS, ELSE, we need I2RS protocol(s). Abdussalam Baryun University of Glamorgan, UK _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
