Thomas, If NVA provides mapping entries for one VN, then the VNA should participate in this VN.
If NVA provides mapping entries for a set of VNs, then the VNA should participate in all those VNs. Other comments are inserted below: > -----Original Message----- > > 1) It would seem to raise recursion problems... An NVE that needs to > get address mappings attempts to contact the NVA, but it needs to > first get address mappings for the VN to which the NVA is connected, > oops... [Linda] The NVA's address has to be advertised to other NVEs. When a NVA is placed on a server rack and attached to a TOR (NVE) which is a pure L2 switch, you can let this NVE to be proxy for the attached NVA. This is one suggestion I give to Larry on NVE being acting for the NVA. Instead of advertise NVA's true IP address, use NVE's addresses. Otherwise, the ToR has to announce the NVA's address to other NVEs, i.e. ToR has to support L3 routing function. > All this is avoided by having the NVA connect to the underlay and be > accessible via underlay addresses. [Linda] My above comment should address this issue. Linda _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
