said by leibold:However it is not clear whether all customers that were previously able to use AT&T 6to4 relays will also be included in the upcoming 6rd deployment. From the news articles it sounds as if the 6rd deployment will be for uverse customers only.
From what I've read,
anyone can use AT&T's 6rd relays. While I didn't set up a full tunnel, I've confirmed that a ping6 from a (non-AT&T) machine with a he.net tunnel to another (non-AT&T) machine's AT&T 6rd address shows incoming encapsulated IPv6 echo request packets from IPv4 address 12.83.49.81 (AT&T's 6rd gateway). So if it works with two machines that are both on non-AT&T networks, it seems like it should work for AT&T DSL too.
This post also claims that AT&T's 6rd works on AT&T legacy DSL.
Now it's certainly possible (likely?) that
AT&T won't be configuring 6rd for DSL customers, but it doesn't sound like the original poster needs AT&T to do the config for him since he's capable of doing his own 6to4 config.
So, I can see being annoyed that a previously-working 6to4 setup is now broken, and I don't know why it no longer works; but on the other hand, I'm not seeing why it's really a big deal. Just switch to 6rd and get lower latency/faster speeds.