Two Points here. 1, For stateless 6rd, using anycast does provide BR redundancy, but not loadbalancing. Generally loadbalancing can not be achieved by anycast, see RFC4786 Operation of Anycast Services for more information.
2, Using AFTR IPv6 address in the new DHCPv6 option does dot mean to use anycast for the stateful dslite loadbalancing. DHCPv6 server sends different IPv6 addresses of AFTRs to different B4s by some critera. Then, user traffic can be balanced among these AFTRs throngh these B4s. I do not think stateless or stateful is the key point. Both FQDN and IP address can be used in the DHCP option to complete the gateway discovery. If the operators want, both FQDN and IP address can also be used to do the load balancing. However, according to the respective RFC, 6rd selects IP address, dslite selects FQDN. I am wondering why not use the same method? Best Regards, Zhenqiang Li ----- Original Message ----- Date: Mon, 4 Jul 2011 02:07:37 +0000 From: "Lee, Yiu" <[email protected]> To: "[email protected]" <[email protected]> Subject: Re: [Softwires] Why not use AFTR IPv6 address for the new DHCPv6 option? Message-ID: <ca369744.115ac%[email protected]> Content-Type: text/plain; charset="us-ascii" No disagreement here. However, we can't argue that using anycast for stateless 6rd BR does provide redundancy if an ISP designs the network properly. On the other hand, stateful dslite can't use anycast. _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
