Hi Zhenqiang,

6rd is stateless, so anycast address might be used for BR
loadbalancing. I guess, that might be the reason why IP literal is
prefered over fqdn for 6rd case.

THanks,
washam

在 2011年7月3日 上午2:12, <[email protected]> 写道:
> Thanks, Washam, I got the intense debate.
>
> But for 6rd, the IPv4 address of the BR is recommended to use in the DHCP 
> option. Thus, different options are recommended for different technologies. I 
> want to know the reason. Using the similar method to do the similar thing is 
> better, isn't it? So, shall we modify the specification of 6rd to use a FQDN 
> for the BR configuration on CEs?
>
> Best Regards,
> Zhenqiang Li
> 2011-07-03
>
>
> ----- Original Message -----
> From: Washam Fan
> Sent: 2011-07-01  13:04:46
> To: [email protected]
> CC: [email protected]
> Subject: Re: [Softwires] Why not use AFTR IPv6 address for the new DHCPv6 
> option?
>
> Hi,
>
> There was a debate between ip literal v.s. fqdn for this issue. Please
> search the old mail archive to check it out. If I recall correctly, a
> major argument would be, many ISPs prefer dns server to do load
> balancing over dhcp server.
>
> Thanks,
> washam
>
> 2011/6/30   <[email protected] >:
>> Hi All,
>>
>> One question about the new DHCPv6 option for AFTR discovery. Maybe I missed 
>> the previous discussion. Sorry for that.
>> According to draft-ietf-softwire-ds-lite-tunnel-option, a FQDN is suggested 
>> to be deliveried in the new DHCPv6 option to the B4. When receiving the 
>> FQDN, B4 has to do the DNS resolution to get the AFTR IPv6 address. The FQDN 
>> of the AFTR has to be configured in the DNS server. So, I think delivering 
>> the IPv6 address of the AFTR directly to the B4 is better. We can use DHCPv6 
>> option to do this. The address of the AFTR only needs to be configured in 
>> the DHCPv6 server.
>>
>> Best Regards,
>> Zhenqiang Li
>> 2011-06-30
>> _______________________________________________
>> Softwires mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/softwires
>>
_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires

Reply via email to