gt; require multiple addresses to be allowed on a single MAC.
>>> -Anthony
>>>
>>> From: Martinx - ?`????
>>> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>>>
>>> Date: Thursday, May 15, 2014 at 14:1
tack.org>>
Date: Thursday, May 15, 2014 at 14:18
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron][IPv6] Privacy extension
Hello!
I agree that there is no need for Privacy Extension
Date: Thursday, May 15, 2014 at 14:18
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [Neutron][IPv6] Privacy extension
>
> Hello!
>
> I agree that there is no need for
t 14:18
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron][IPv6] Privacy extension
Hello!
I agree that there is no need for Privacy Extensions in a Cloud environment,
sin
Hello!
I agree that there is no need for Privacy Extensions in a Cloud
environment, since MAC address are fake... No big deal...
Nevertheless, I think that should be nice to allow 1 Instance to have more
than 1 IPv6 addr, since IPv6 is (almost) virtually unlimited... This way, a
VM with, for exam
I was just about to respond to that in the session when we ran out of
time. I would vote for simply insisting that VMs run without the privacy
extension enabled, and only permitting the expected ipv6 address based on
MAC. Its primary purpose is to conceal your MAC address so that your IP
address
Hi, guys:
Nice to meet with all of you in the technical session and design session. I
mentioned the challenge of privacy extension in the meeting, but would like to
hear your opinions of how to address the problem. If you have any comments or
suggestions, please let me know. I will create a BP
