Open Stack

Hi Vinay,

I understand your concerns about conflicts with already assigned OUIs.
It is however my opinion that it is not up to the Openstack Foundation, but
to entities deploying Openstack, to buy MAC OUIs.
As regards Quantum, we should ensure the default MAC range we use is
locally assigned; unfortunately I do not know enough about nova-network.
Also, it is my opinion that a locally-assigned OUI would be sufficient for
many use cases, without the need for a globally assigned one.

Regards,
Salvatore

On 20 October 2012 04:05, Vinay Bannai <vbannai at gmail.com> wrote:

> I was talking to Nachi and Gary during the Quantum design session about
> the need to have a proper MAC OUI allocation scheme for Openstack
> development folks. They suggested that I send it out for wider discussion
> on the mailing list.
>
> It turns out that it would be useful for the Openstack foundation to apply
> for a MAC OUI from IEEE that can be used for development purposes and
> testing. This way we don't unwittingly use someone else MAC allocation.
> Here are the details
>
> http://standards.ieee.org/develop/regauth/oui/index.html
>
> The cost to get a OUI allocation is around $2000 dollars. Remember if we
> use random MAC OUI,  the actual owners can assert their legal claim on the
> MAC address in the event of a conflict now that we have support for more
> sophisticated tunnels that allow connections from public and private
> clouds.
>
> Comments welcome.
>
> Vinay
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121020/9bb87e2e/attachment.html>