* Gert Doering wrote:
Use of the same (known and working) technology without extra global routes (assuming that the ISP has a "normal" prefix in addition to the prefix used for 6rd) and without the mess created by not-really-working 6to4 relays and asymmetric paths.
You are suggesting to assign a new IP prefix every time, some implemtations out there fucked up? If you can't live with anycast, go and announce our unicast more specific!
With 2002:: in use inside an ISP, packets from 6to4 aware peer hosts out in the world will be encapsulated into IPv4 at the sending host, and then travel over potentially broken IPv4 paths, instead of travelling natively IPv6 up to the ISPs relay...
No, they don't otherwise firewalls would not work with IPv6 and 6to4 at all. Any nativly IPv6 connected host respond to any request from IPv6 addresses using IPv6. I see you point, that more specifics of 2002::/16 are disallowed by RFC3056, but this can easily be changed. 6rd uses the same way to modify RFC3056: It requires a huge parallel prefix (and route) per ISP. In order to overcome the situation I submitted a draft to the IETF. http://www.ietf.org/id/draft-donnerhacke-softwire-ipv6-6to4-00.txt Have fun.