Hello,
Some questions and comments on this draft:
* The word "802.1Q trunk" and "VLAN trunk" is used in a few places. Is it
just a proprietary concept? If not, do we need a definition somewhere?
* 3.1.2: "When the VN is providing L3 forwarding, the NVE must have the
knowledge of the TS IP addresses." This is true if the L3VNI is embedded in the
NVE function which is facing the TS. However, some implementations may have the
L3VNI centralized in the DC. In this case, the NVE function is split, where the
L2VNI and the L3VNI function are located in different boxes. It may be better
to have clear description allows more generic network architecture.
* 4.2: The two ways of TS address discovery is for MAC address discovery?
IP address discovery or both? Do we allow the VM to inform the NVE directly at
VN address association? Can we cover it in the text as well?
* 4.3: In the VNIC address disassociation procedure, it only cover the case
when the VM is removed from a VNIC. Do we need to cover the case where the VM
disassociates one of the addresses from the VNIC and informs the NVE?
* 4.3: For the case that VM mobility between different hypervisors under
the same NVE, it's right that notifying the NVA may be inefficient. But it
doesn't have to be disallowed, right? It shall be allowed to let the NVA to
keep the track of the VM mobility.
* 4.4: is the timer solution good enough for the case of address
misconfiguration? How the NVE knows there is an address misconfiguration or it
is VM mobility?
Have a nice day
Zu Qiang
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
