RFC 5798 - ipv6 link-local configuration

Alexey Razuvaev <[email protected]> Thu, 17 May 2012 10:10:49 -0400
Newsgroups gmane.ietf.vrrp
Message-ID <CADvgzaEkTDoxAYAGvD9HkzhO7aW8=jzhLKxXEBrsAdz3m6j76A@mail.gmail.com>
--===============0942881979250641594==
Content-Type: multipart/alternative; boundary=0015175cd100ea353704c03c01f8

--0015175cd100ea353704c03c01f8
Content-Type: text/plain; charset=ISO-8859-1

Hi,
VRRPv3 for IPv6 specifies that the first address should be a link-local
address. If that is configured by an operator and not generated by
software, how do we make sure that there are no collisions with existing
link local addresses? Since the protocol spec does not mention any
link-local address range dedicated to VRRP, how do
current implementations make sure that it doesn't collide with anyone else
on the network? I understand that IPv4 has similar issues, but in IPv4 case
the network would be statically configured, unlike in IPv6 case where
link-local addresses are generated from MAC.

Additionally what is the reasoning behind not allowing to use Virtual MAC
address to generate link-local address? It seems like it would simplify the
set up, but I think I am missing some crucial detail.

Also, if I were to allow global IPv6 to be configured for virtual router, I
would have to force the operator to also configure a link-local address,
correct?

Thanks,
Alexey.

--0015175cd100ea353704c03c01f8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<div>VRRPv3 for IPv6 specifies that the first address should be a link-l=
ocal address. If that is configured by an operator and not generated by sof=
tware, how do we make sure that there are no collisions with existing link =
local addresses? Since the protocol spec does not mention any link-local ad=
dress range dedicated to VRRP, how do current=A0implementations=A0make sure=
 that it doesn&#39;t collide with anyone else on the network? I understand =
that IPv4 has similar issues, but in IPv4 case the network would be statica=
lly configured, unlike in IPv6 case where link-local addresses are generate=
d from MAC.</div>

<div><br></div><div>Additionally what is the reasoning behind not allowing =
to use Virtual MAC address to generate link-local address? It seems like it=
 would simplify the set up, but I think I am missing some crucial detail.</=
div>

<div><br></div><div>Also, if I were to allow global IPv6 to be configured f=
or virtual router, I would have to force the operator to also configure a l=
ink-local address, correct?</div><div><br></div><div>Thanks,</div><div>

Alexey.</div>

--0015175cd100ea353704c03c01f8--

--===============0942881979250641594==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
vrrp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/vrrp

--===============0942881979250641594==--