Alia, et al,

Here are my comments and questions to the draft-ietf-i2rs-architecture-02.txt:


-          Last paragraph of Section 1, Typo "tivial example". Do you mean 
"trivial example"?

-          Section 3.2 (Extensibility): This section is more on justifying the 
scope of I2RS than the architecture.

-          Section 3.3 (Model - Driven ...): what is "model-driven architecture 
and protocol(s)"? is Yang model a valid one? Or Netconf?

-          Section 6.2.1 (I2RS Agent Failure)

o   Unexpected failure: it is very likely under the "unexpected failure" that 
the I2RS agent loses its records of clients. A more reasonable way is for I2RS 
agent to broadcast its status (e.g. restart), to let the Clients to 
re-subscribe if they need to.

-          6.4.2 (IGP, BGP, ..):

o   The first bullet says "Directly writing to these protocol-specific RIBs or 
databases is out of scope for I2RS."

o   The information model defined by draft-ietf-i2rs-rib-info-model-02 has 
"route", nexthop", modifying them can impact the result of those 
protocol-specific RIBs.

o   The last paragraph seems to say that local route attributes can be changed, 
e.g. link metrics, local attachment, however, information received from other 
nodes (LSA) can't be modified, is it correct?

o   Then, all those local attributes can also be modified by CLI, correct?

-          6.4.5: this section is more like the requirement for Informational 
model. I don't see how  they impact the architecture.

-          Which entity does the cross check if policies to one Routing Element 
from different Clients are contradicting with each other?

o    Page 8 states that two clients can't attempt to write (modify) the same 
piece of information.  Does it mean two clients can't write (modify) "Tunnel 
nexthops" or "weighted lists" (defined by draft-ietf-i2rs-rib-info-model-02)? 
What if two clients need to modify "Tunnel nexthops" for some prefixes (e.g. 
two different applications for one virtual network)?



o   How to guarantee it?


-          Who checks policies to multiple routing elements are contradicting 
to each other?

-          Today's router can be configured/ changed by CLI, or NETCONF, 
monitored by SNMP, how is "I2RS" agent different from those entities?



-          What if clients need to re-direct traffic on attributes that are not 
in the RIB?



Linda Dunbar
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs

Reply via email to