On Sun, Jun 23, 2013 at 1:35 PM, Adrian Farrel <[email protected]> wrote:
> Andy, > > > my question is how many I2Rs agents does a client need to > > contact to perform a task that requires changes on multiple routers? > > You probably won't like my answer "that depends". > > If the effect of the action on router 1 is to cause router 1 to use a > routing/signaling protocol to make things happen in the network, then the > answer > may be 1. > > If the changes cannot be effected in that way, then the client may need to > talk > to multiple routers to make the different things happen on each router. > > I meant a high-level task performed by the client that requires routing state to be manually injected on multiple routers, not via routing protocols. I am happy to consider the I2RS agent to be running on a single router and the I2RS client to be the network-level broker. The API to specific network-wide services topology or routing can be standardized next. IMO it is better to start with the core functionality that is expected on one device (for some definition of "core" the WG will agree on later). Andy And in between there lies the case of needing to touch some, but not all > routers > because other routers in between are worked on by signaling/routing. > > So the answer is 1 <= #agents <= #routers > > And that answer is modulo there being only one agent on each router :-) > > For (crass) examples of the above I give you: > > Set up an LSP using RSVP-TE (just talk to head-end router) > Set up an end-to-end static route (talk to each router) > Set up a multi-segment pseudo-wire (talk to the T-PEs and the S-PEs) > > Adrian > >
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
