On May 1, 2014, at 5:17 AM, t.petch <ie...@btconnect.com> wrote: > > Jeff > > If I2RS updates the routing table, do we expect it to persist for any > length of time? That is, the routing table is stable, the result of the > convergence of the routing protocols (and configuration) across the > relevant routers in the routing system and is reflected in the > operational state of a router. > > A stable system in engineering is one that when perturbs, returns to its > original state. So make a change in one router and I would expect the > rest of the system to gang up on that router and reinstate the status > quo. For example, what I have in Adj-RIB-Out comes from someone else > via Adj-RIB-In and if I change Adj-RIB-Out, then sooner or later I will > refresh it from Adj-RIB-In and be back where I started, while if I > change Adj-RIB-In, then the other router will repeat its advertisement - > and I will be back where I started. > > If I think of the changes I might want to make, it seems to me that they > have to be changes to what NETCONF/YANG refer to as config and not to > the operational state. Ephemeral or persistent, which I take to refer > to what happens after a reboot, is then a question of which NETCONF > datastore I update, running or startup or both. > > Tom Petch
Tom, Good question, but IMO, I2RS agent should not change tables belonging to dynamic routing protocols. 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. 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. If we really want to allow full manipulation of dynamic protocol routing tables, I think some extensions to routing protocols would be required. Dean _______________________________________________ i2rs mailing list i2rs@ietf.org https://www.ietf.org/mailman/listinfo/i2rs
