Linda, according to draft-ietf-i2rs-architecture-09, an I2RS agent is part of a routing element. I am not sure your understanding "I2RS Agent is like the SDN controller" is consistent with the architecture document.
/js On Fri, Jun 26, 2015 at 05:03:25PM +0000, Linda Dunbar wrote: > Alex, et al, > > The I2RS architecture depicts two types of interfaces: > > - One is the interface between Agent and Client, and > > - another is the interface between Agent and Routing entities. > > > The network model and inventory are more for the interface between Agent and > the Clients, isn't it? One single routing engine doesn't need to know the > overall topology and inventory information of other nodes, even though some > may do. > > > And the /nd:network/nd:node and Termination points are more for the interface > between the Agent and the Forwarding Engine, isn't it? > > IMHO, the information models should be oriented around the I2RS architecture. > I.e. with description on where those information models are applicable, > making it easier to differentiate from other IETF WGs work (such as L2VPN, > L3VPN, or SFC). I recall there were some debates at the Dallas I2RS session. > > I2RS Agent is like the SDN controller, which can inform clients about the > topology information, instruct routes to routing engine of multiple nodes, > and retrieve link & termination points status from each of those nodes. > > The "Service Overlay" in Section 3.4.8 is definitely meant for clients not > towards individual nodes. Mixing them all together make it confusing. > > Cheers, > > Linda Dunbar > > > _______________________________________________ > i2rs mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/i2rs -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
