Subject: [nvo3] draft-ietf-nvo3-nve-nva-cp-req: VN Name to VN ID mapping

From: Zu Qiang <[email-masked]>
Date: Tue, 13 Aug 2013 13:45:49 +0000

Hi, Authors

In section 3.4, there is VN Name to VN ID mapping. "...it may be useful for the NVE-to-NVA protocol to support an operation that maps VN Names into VN IDs." This may or may not be an NVA-NVE function.
It is true that there are so many ways this might be done, including especially the potential for NVA functions being not so much distributed as addressed by a set of "servers" - some of which already exist - intended to support a subset of the required control functions. For instance, the VN Name to VN ID could be handled by a DNS like service, or by either Radius or Diameter.  And this is really a management/operational requirement since this information will be configured in NVA or each NVE.
In the NVA-to-NVE operation, either VN name or the VN ID is used, but it does not need both. Adding the mapping function into the NVA-NVE protocol is really not effective. As mentioned in the next section, a large scale data center may contain hundreds of thousands of these NVEs (which may be several independent implementations); Therefore, any savings in per-NVE resources can be multiplied hundreds of thousands of times.

Best Regards
Zu Qiang