To the draft authors: Here are some comments about the NVo3 framework draft, draft-lasserre-nvo3-framework-01.txt
1. Section 2.2 state: The NVE functionality could reside solely on the End Devices, on the ToRs or on both the End Devices and the ToRs. Section 4.2.5 state: In the case of ELAN service, it can be switched by a local VM switch or ToR switch and then by a DC gateway. The NVE function can be embedded within any of these elements. Question: Should NVE function reside on DC gateway or not? 2. It seems that some DC applications may also require VNI connecting external switch without overlay module. For example, One NVo3 instance connects many Tenant End Systems and also need to connect to Internet. Should the architecture reference model capture this as well? 3. Some DC applications also require a L2 Tenant instance and L3 Tenant instance interconnection on a NVE. Should the document describe this too? 4. Section 2.3 NVE Service Type. Comment: The service Type associates with Tenant Instance as described in the dp-reqs draft associates, not NVE. 5. Figure 5 should be Figure 4 and include multiple Tenant Instances. Figure 6 should be Figure 5. (no draw as Figure 4) 6. Section 3.2 Service Overlay Topologies. Suggest not use of "a tunnel mesh". IP tunnel provides one hop nature between NVEs but is an aggregated tunnel. 6. It would be nice to align the terms in the framework draft and data plane req. draft since authors are the same. Cheers, Lucy
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
