Let's not re-use NVO for Orchestrator. NVO is already for *Overlay*. Next ...
Everything in this WG is about network virtualization, and while there may be underlay and overlay networking concepts being discussed, I think underlay networking parameters that may loosely relate to an overlay virtual network construct can still be described by a NVMA (network virtualized mapping authority) aka Policy server / directory, etc... We are talking about a place to retrieve authoritative information on a network construct. I do not understand the TRILL and PBB statement highlighted above. Nor do I see how "V" is orthogonal to anything we are discussing. Truman On Wed, Apr 10, 2013 at 1:04 PM, Lou Berger <[email protected]> wrote: > > > On 4/10/2013 12:22 PM, Linda Dunbar wrote: > >>> 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”. > >> > >> Do I understand your point correctly, that you're suggesting that this > >> discussion is orthogonal to the "V" in technologies such as L3VPN, > >> L2VPN/EVPN, NVGRE, VXLAN, ...? > > > > [Linda] and TRILL, and PBB ... > > So how do you feel about the name of the WG? > (Particularly, the "V" and "O3" parts...) > > Lou > > > > >> > >> Lou > >> > >>> > >>> > >>> > >>> Therefore, I think “Network Mapping Authority” or “Host Location > >>> Information Service” is more accurate. > >>> > > _______________________________________________ > > nvo3 mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/nvo3 > > >
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
