I deleted my tunnel as my current router seems to mangle the tunnel packets, it only works if I put my laptop directly behind the Cable Modem but for me, it primarily is research for a new hosting service (won't mention, I hate spam as much as everyone else does - and my target audience is technical n00bs anyway) I am starting.
Once I replace my router I will create a new one. The geographic location of my tunnel probably wasn't optimal anyway, but Fremont was full so I had to go with Seattle. Maybe when I replace my router, Fremont will have an opening (I'm in Redding). OTOH since my servers are all in Dallas (Linode), maybe that would be a good tunnel location.
Nutshell - I want everything I host to be dual stack. Many emerging markets (especially in Asia) seem to be adopting IPv6 very quickly, I think it is important to my potential clients (even though most will likely be American) that their content be available on IPv6 so that it is not missed by users who may be on IPv6 only networks.
Also, due to the way Apache works, individual SSL certs for hosted domains with name based virtual hosting is problematic.
Thus it is to my advantage to see IPv6 replace IPv4 as quickly as possible. The sooner dual stack becomes the norm, the sooner we'll get to a point where IPv4 drops away and I can go IPv6 only for SSL content. Still years away, but I figure the more interest in IPv6 that is seen by the big corporations the sooner that will happen.
Finally, I do not fully understand the details, but if my impression is correct, it sounds like the technical aspects of IPv6 make load balancing a hell of a lot easier. Something about being able to have a cluster of servers where the first available handles the request without needing to have the cluster behind a load balancer. I definitely want to research that some more and make sure I understand the concepts behind it.