Randy,
I may need some time to review your latest code change to the blueprint you
mentioned. But I think we can discuss this in the coming IPv6 sub team
meeting.
Xuhan
On Mon, Mar 3, 2014 at 11:20 AM, Randy Tuttle wrote:
> Hi Yuhan
>
> Sorry I am slow to respond, but I was catching up on some
Hi Yuhan
Sorry I am slow to respond, but I was catching up on some emails and found
this one from you. Regarding your comments on the RA from the router
gateway port...
I disagree that the LLA for the qg- interface is (or should be) the
gateway for the tenant's subnet. On the contrary, it sho
Robert,
Thanks for your comments! See my replies inline.
On Thu, Feb 27, 2014 at 9:56 PM, Robert Li (baoli) wrote:
> Hi Xuhan,
>
> Thank you for your summary. see comments inline.
>
> --Robert
>
> On 2/27/14 12:49 AM, "Xuhan Peng" wrote:
>
>As the follow up action of IPv6 sub-team me
Hi Xuhan,
Thank you for your summary. see comments inline.
--Robert
On 2/27/14 12:49 AM, "Xuhan Peng"
mailto:pengxu...@gmail.com>> wrote:
As the follow up action of IPv6 sub-team meeting [1], I created a new blueprint
[2] to store both IPv6 LLA and GUA address on router interface port.
Here
As the follow up action of IPv6 sub-team meeting [1], I created a new
blueprint [2] to store both IPv6 LLA and GUA address on router interface
port.
Here is what it's about:
Based on the two modes (ipv6-ra-mode and ipv6-address-mode) design[3], RA
can be sent from both openstack controlled dnsmas
