Subject: [nvo3] comments for the framework-03 draft

From: Lucy yong <[email-masked]>
Date: Tue, 14 Aug 2012 18:05:46 +0000

Hi Marc,

I think it is necessary to add server manger component in the section of functional components in the framework draft. As we know, one of main cases for nvo3 is to place NVE on a server. In which, there is no-wire between NVE and TESes. In DC today, a server manager is used to create vswitch/NVE and VMs, place VMs on a VN.  Current draft mixes this function in the control plane component, which causes a lot of confusion as seen in the mailing list. In addition, vm placement and mobility are very critical features that nvo3 need to support and these actions are initiated by the  server manger, separating control plane component and server manager component makes easy and clear for the solution development to target different parts.

Some text in section 3.5.1.1 can move server manager component section. I propose to add following subsections in server manager component:

-          NVE and a VN Creation

Note: state this applying to when NVE is on server.

-          Provisioning one or more TESes into an NVE/VNI
Note: state this applying to both NVE is on or not-on server.

Another comment: It is a bit confusion in figure 4 and 5 to show multiple VNIs with one VN context (single line).  What does mean?

Suggest to change section 2.3 title to "virtual network type". One NVE should be able to host both L2 VN and L3 VN. so 2.3.1 and 2.3.2 title misleading. Suggest
Replace "L2 NVE providing Ethernet LAN-like service" with "L2 virtual network providing Ethernet LAN-like service"
Replace "L3 NVE providing IP/VRF-like service" with "L3 virtual network providing IP VPN-like service"

In section 4.2.1, it only describes a concern on data plane driven, does not say anything on control plane driven. It should mention some traditional control plane dissemination protocol may bring big burden for each NVE to maintain the locations of all TESs.

Regards,
Lucy