Hi Eric el al,
The following should be pointed out in the section of data plane requirements.
* Requirement: L3 VNIs MUST provide virtualized IP routing and
forwarding.
Both NVGRE and VXLAN are designed for L2 Overlay only, i.e. carrying Ethernet
frame. Therefore they do not meet this requirement. Since NVGRE uses gre header
that has a prototype field, it can be easily extend to support other overlay
payload type.
* Requirement: For performance reasons, multipath over LAG and ECMP
paths SHOULD be supported.
VXLAN supports common five tuple based LB. NVGRE requests LB to use GRE header,
which is not commonly supported by underlying IP network.
Suggest adding a new section of a Data Center Network Virtualization Generic
Requirements. Here are the requirements belongs to the section.
Multi-Tenancy networks over an IP underlying network
Tenant Networks isolation with independent address space
Tenant Network separation from underlying network
Tenant System Mobility
Tenant Network interworking with external and/or physical networks
Network Virtual Edge (NVE) and Tenant System co-located
Network Virtual Edge (NVE) and Tenant System not co-located (NVGRE/VXLAN
does not support this)
Scalability to support millions VNs and many tenant systems in a VN
Suggest removing the management requirement section and merge it with operation
requirement, adding sub section of OAM requirements in section of operation
requirement.
Suggest adding SDN based controller as a solution in section of control plane
requirements and remove NVGRE and VXLAN. State that SDN based controller can
apply to any data plane solution that are not tied into the control plane
solution. NVGRE and VXLAN are good example.
Suggest adding a sub section of NVE-to-NVA control plane protocol requirements
in section of control plane requirements.
Suggest adding a section for security requirements.
Cheers,
Lucy
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
