According to my IPv6 tunnelbroker Hurricane Electric the world will end in approximately 712 days when we finally run out of IPv4 addresses.
Would it be possible to enable IPv6 access to the Stack Exchange family of websites?
I've done some checking and www.stackoverflow.com is currently hosted on an IPv4 address that belongs to peer1, so this must be PA space.
Looking on ARIN's whois, Peer1 (PER1) have lots of IPv6 space:
So you can get an allocation from the 2001:1978:: space.
I've had a look at Peer1's IPv6 routing and it seems to be pretty much first-class, so there's no ISP excuses for not having IPv6.
I know that stackoverflow have private BGP (from the SF blog) so they should be able to just get an IPv6 allocation, and announce their routes through BGP.
The web servers (being Windows 2008) support IPv6 straight out of the box, so the constraints I can see are:
Conclusion: StackOverflow could operate on native IPv6 without too much of a hassle, and it would be nice to do so and will get steadily more and more important.
How about World IPv6 day (8 June 2011) as a target for IPv6 native throughout?
|show 1 more comment|
Are you suggesting to start by spoiling the IPv6 space with sites that already have an IP address assigned?
We'll run out of IPv6 addresses in the year 53985251 AD, and people living by then are going to be seriously pissed off when they find out about this.
Whatever happened to ideas like mapping addresses so that IPv4 w.x.y.z becomes IPv6 ::ffff:w.x.y.z? Or other compatibility ideas?
There's no reason to be assigning IPv6 addresses to sites that already have IPv4 ones, no reason at all. There are compatibility mechanisms to handle the transition already.