6rd makes use of the v6 subnet router anycast, see section 5 of RFC5969. In short, this allows a CE to construct a ping with a well-known destination that will be returned by one of the BRs. Operators like this because it allows them to fairly easily get a good indication of which BR a given CE is likely traversing when sending traffic.
Also, at the last IETF meeting the DHC WG took on an effort to describe the use of subnet router anycast here: http://tools.ietf.org/html/draft-guo-softwire-6rd-ipv6-config-02 ...in a more generic manner for use with DHCPv6 (which 6rd could in turn use). I suspect the -00 is either just out or will be very soon. - Mark On Jul 4, 2011, at 1:09 PM, Karl Auer wrote: > On Mon, 2011-07-04 at 10:44 +0200, Alexandru Petrescu wrote: >> Thus, anycast and multiple HA on the home link is advantageous for >> reliability of Mobile IPv6. > > Again, I'm not proposing that we deprecate the mechanisms for on-link > anycast. Only that we should not reserve the subnet router anycast > and/or the subnet anycast addresses. > > Regards, K. > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Karl Auer (ka...@biplane.com.au) +61-2-64957160 (h) > http://www.biplane.com.au/kauer/ +61-428-957160 (mob) > > GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687 > Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156 > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > --------------------------------------------------------------------
-------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
