IPv6 Deployment Picking Up Speed 158
An anonymous reader writes "The Internet's addressing authority (IANA) ran out of IPv4 Internet addresses in early 2011. The IPv6 protocol (now 15 years old) was designed exactly for this scenario, as it provides many more addresses than our foreseeable addressing needs. However, IPv6 deployment has so far been dismal, accounting for 1% of total traffic (the high-end of estimates). A recent paper by researchers at the Cooperative Association for Internet Data analysis (CAIDA) indicates that IPv6 deployment may be picking up at last. The paper, published at the Internet Measurement Conference (IMC) shows that the IPv6 network shows signs of maturing, with its properties starting to resemble the deployed IPv4 network. Deployment appears to be non-uniform, however; while the 'core' of the network appears to be ready, networks at the 'edges' are lacking. There are geographical differences too — Europe and the Asia Pacific region are ahead of North America."
Stop the Presses! (Score:3, Informative)
That's NEVER happen. Except with everything.
IPv6 was no big deal (Score:4, Informative)
I've been on native IPv6 for a couple of years on my home DSL connection. It works very well - only thing I had to do was check the 'enable IPv6' option in my modem/router and everything 'just worked'. It is rather nice not having to deal with NAT and port forwarding etc.
I'm in Australia (so within the Asia-Pacific/APNIC region, which as the summary mentions, is a bit ahead of the curve when it comes to IPv6 adoption. Most of the major sites are fully IPv6 now too (e.g. all the Google sites, Facebook, etc. etc.) But the point is, done properly, it should be a completely seamless transition to enable dual-stack (and eventually to turn off IPv4, though I'm sure that won't happen for decades!). Hell I usually forget I'm even on IPv6, unless I happen to do a ping/tracert to an IPv6 host and see all those long-ass IPs :)
C:\>tracert www.google.com
Tracing route to www.google.com [2404:6800:4006:800::1014] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms gateway [2001:44b8:(snip!)]
2 7 ms 7 ms 7 ms loop0.lns20.cbr1.internode.on.net [2001:44b8:9010::5]
3 7 ms * 7 ms gi0-0-2.cor3.cbr1.internode.on.net [2001:44b8:9010:14::1]
4 11 ms 11 ms 11 ms te6-0-0.bdr1.syd4.internode.on.net [2001:44b8:9010:e::2]
5 11 ms * 11 ms te0-0-0.bdr1.syd7.internode.on.net [2001:44b8:b070:1::11]
6 11 ms 11 ms 11 ms gi1-2-121.cor2.syd7.internode.on.net [2001:44b8:b060:121::2]
7 11 ms * 12 ms gi6-0-0-101.bdr1.syd7.internode.on.net [2001:44b8:b070:104::1]
8 12 ms 11 ms 12 ms 2001:4860:1:1:0:1283:0:4
9 13 ms 13 ms 12 ms 2001:4860:0:1::1fb
10 13 ms 12 ms 11 ms 2404:6800:4006:800::1014
Re:Come on slashdot ... (Score:5, Informative)
The problem I have faced is that none of my server ISPs will even let me get an IPv6 address even if I know they have it and I beg. That goes for major service providers too. I'm looking at you Amazon Cloud and RackSpace. Amazon kinda has it, but only if you use one of their load balancers.
Re:IPv6 was no big deal (Score:2, Informative)
> Provided me also with a simple firewall as a nice side effect. ;)
I rather suspect you're a troll given how often and exhaustively this has been refuted previously on this site, but oh well.
NAT is not a firewall. The stateful firewall in your home router is a firewall. NAT isn't . There are plenty of technologies to punch holes into NAT, usually developed because NAT is such a fucking pain to deal with for many protocols.
Hah! (Score:4, Informative)
Companies are still shipping network gear that is IPv4 only. Find me a fixed-wireless device that supports IPv6! Sure they're layer 2 devices, but the units themselves don't have IPv6 addressability.
IPv6 will take a long, long time. Maybe 10 years for major crossover. The fanbois and the advocates get shriller every day, but moving to IPv6 - even dual-stack - from an existing network is currently *hard*.