Xiaohu, > I guess the current "end-system L3VPN" proposal should belong to case > 1, rather than case 3 where NVE and TES are not in the same physical > device, unless the "end-system L3VPN" makes some changes as follows: > XMPP is only used as a signaling of VM attachment/detachment events > between hypervisors and ToRs, rather than as a replacement of BGP-based > L3VPN signaling. In this way, the NVE functionality (i.e., L3VPN PE) is > performed on the ToRs, rather than on the end-systems.
Actually, "end-system L3VPN" proposal covers both cases. In the case NVE functionality is on external switch, it operates as an XMPP server processing requests from end-systems and as a client of one or more controllers/signaling gateways. It relays to the signaling gateways(s) messages it receives from the end-system. In this scenario, the VPN routing information the NVE receives from a signaling gateway is not propagated to the end-system. Maria _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
