Pat,
I can see that some might have an issue with the NIC association.
While I still prefer NVC, I think NVA is a reasonable alternative.
I also think map/mapping has a bunch of context-specific connotations
beyond what we're considering, so either of the above TLAs would
definitely be better than NVMA...
Lou
On 4/10/2013 6:43 PM, Pat Thaler wrote:
> I'd prefer
> NVA - Network Virtualization Authority
> - for an authoritative repository for mapping and possibly other information
> on Network Virtualization
>
> NVMA - Network Virtualization Mapping Authority
> - my second choice but I don't see an need for the additional word even if we
> end up specifying it only doing mapping
>
> "Controller" to me implies active control - so leans toward push rather than
> pull. Also, controller is used in the industry for the device on the NIC
> controlling access to the network.
>
> Pat
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of Lou
> Berger
> Sent: Tuesday, April 09, 2013 6:05 PM
> To: Larry Kreeger (kreeger)
> Cc: [email protected]
> Subject: Re: [nvo3] NVO3 Terminology changes
>
> 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]> 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]> 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]
>> https://www.ietf.org/mailman/listinfo/nvo3
>>
>>
>>
>>
> _______________________________________________
> nvo3 mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/nvo3
>
>
>
>
>
>
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
