Sri, See inline
On May 16, 2014, at 6:00 PM, Sriganesh Kini <[email protected]<mailto:[email protected]>> wrote: Dean, see inline Changes done by I2RS agent should have only device impact, not network impact. If there is desire to change across network, then each I2RS agent on each device should be updated. It is not simple to classify a change to a device as having an impact scoped to just that device. E.g a route that is added to a device with a different preference can have network-wide traffic impact. How can I explain this better. The static route on device will be routed to the next destination, but at the next destination the dynamic protocol will take effect, unless, another static route directs the traffic differently. Makes sense? Dynamic protocol routing tables should be read only. I2RS agent should create routing tables that can contain the same prefix as in the table belonging to dynamic protocol, so creating custom routing preference is possible. The RIB is the table where multiple clients (including multiple dynamic routing protocols) can create routes in order for it to be downloaded to the FIB. 'Preference' must be used to add multiple routes for the same prefix. The clients of the RIB can be dynamic routing protocols or clients that implement other use-cases. The RIB IM is designed to interface with all such clients. thank you for correcting me. If we really want to allow full manipulation of dynamic protocol routing tables, I think some extensions to routing protocols would be required. I am yet to see a use-case that requires direct manipulation of a single dynamic routing-protocol-instance specific route table by something other than that protocol. I don't believe there should be any such case. I completely agree with you. Sri Dean _______________________________________________ i2rs mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/i2rs _______________________________________________ i2rs mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/i2rs
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
