We are talking about an entity that has information on inner-outer address mapping, and potentially other host (VMs or Servers) location information. This entity is orthogonal to "virtualization".
Therefore, I think "Network Mapping Authority" or "Host Location Information Service" is more accurate. Linda From: [email protected] [mailto:[email protected]] On Behalf Of Truman Boyes Sent: Tuesday, April 09, 2013 11:48 PM To: Lou Berger Cc: [email protected]; Larry Kreeger (kreeger) Subject: Re: [nvo3] NVO3 Terminology changes Hi, I think the below two suggestions provide the clearest terminology and description for the function: NVA - Network Virtualization Authority (may be vague) NVMA - Network Virtualization Mapping Authority (less vague) BGP might not be a mapping service; but with a stretch of the imagination the mapping of NLRI to prefix/communities/etc could fulfil the litmus test. The below words of 'server', 'controller', and 'orchestrator' carry a lot of baggage/meaning at the moment and might convey other meanings. I like the NVMA as a functional element. NVMA +1 Truman On 9 Apr, 2013, at 9:04 PM, Lou Berger <[email protected]<mailto:[email protected]>> wrote: Also... NVS - Network Virtualization Server NVC - Network Virtualization Controller NVO - Network Virtualization Orchestrator On 4/9/2013 8:27 PM, Larry Kreeger (kreeger) wrote: Lou, Given your criteria for starting with NV, we could potentially have one of the following: NVS - Network Virtualization Service (service seems vague and perhaps an overloaded term) NVA - Network Virtualization Authority (may be vague) NVMA - Network Virtualization Mapping Authority (less vague) NVO - Network Virtualization Oracle (assuming oracle is OK when it has the NV prefix) - Larry On 4/9/13 4:51 PM, "Lou Berger" <[email protected]<mailto:[email protected]>> wrote: Larry, I think the NVC and NVO terms are fairly solution neutral, i.e., I don't see why not. I guess your question does lead to yet another option NVS: Network Virtualization Service I personally like NVC, but given that we have NVEs, I'd be happy with anything of the form "Network Virtualization <foo>" as long as <foo> doesn't start with an "E". Lou On 4/9/2013 7:25 PM, Larry Kreeger (kreeger) wrote: Lou, Do you see the terms "Controller" or "Orchestrator" standing up to David Black's "BGP" litmus test? - Larry On 4/9/13 3:18 PM, "Lou Berger" <[email protected]<mailto:[email protected]>> wrote: On 4/8/2013 9:12 PM, Larry Kreeger (kreeger) wrote: At the NVO3 WG meeting in Orlando, I brought up some suggestions for terminology changes/additions and had an AI to bring this to the listŠso here goes. I would prefer to see constructive suggestions in responses. In other words, please suggest something better if you object to these. 1) Oracle -> Information Mapping Authority Stewart mentioned that he has copyright concerns with using the term "oracle", and others have expressed distaste as well. In draft-kreeger-nvo3-hypervisor-nve-cp-01 we replaced the term with "Information Mapping Authority" (IMA). We would like to get consensus on using this new term in all WG documents going forward. In the meeting Linda expressed a concern that IMA might get confused with IMA being confused with the acronym for Inverse Multiplexing for ATM, and suggested something like "Directory Service" to which David Black replied that she might have trouble convincing people that BGP can be categorized as a "Directory Service". Perhaps we're over thinking this one. We have NVE, so why not NV Controller (NVC) or NV Orchestrator (NVO)? Lou ... _______________________________________________ nvo3 mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/nvo3
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
