On 2010-01-11 00:45, WashamFan wrote:
...
> 3. section 6 says 6rd addresses should be treated as native
> addresses and no changes are needed for address selection.
>
> 6rd is a native-equivalent IPv6, but not native IPv6 after all.
> When a customer is connected to a 6rd IPv6 and native IPv6
> at the same time, (s)he might only want to use 6rd address
> when (s)he communicates with hosts within the 6rd domain.
Well, consider what is said about the equivalent issue for
6to4, in RFC 3056:
If both hosts have a 6to4 address and a native IPv6 address, then
either the 6to4 address should be used for both, or the native IPv6
address should be used for both. The choice should be configurable.
The default configuration should be native IPv6 for both.
In other words, if the RFC 3484 default doesn't do what the customer
wants, an extra policy would be needed for the specific prefixes
concerned. It seems to me that the draft is correct: treat the 6rd
prefix exactly as if it was native.
Brian
_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires
