Report from the TXv6TF summit – (C) Stephan Lagerholm September 16, 2011
The Texas IPv6 Task force summit in Austin took place between September 14 and 15. Here is a brief summary of the most interesting talks and conclusions. All presentations are already online if you want to deep dive.
IPv6 capable Wireless
First of all, I recently got a new laptop and I haven’t have time yet to test IPv6 on it. AT&T generously provided a WLAN with IPv6 support. Since I’m using Windows 7 I thought it would just work and that I would get a SLAAC address. However it turned out that I didn’t get on the IPv6 internet but everybody around me did. After some troubleshooting I realized that my host firewall that is built in with my antivirus actually IS BLOCKING IPV6 BY DEFAULT. Thanks for that F-secure, you just lost my business for my next renewal.
About a year ago, there were a lot of talks about how enabling IPv6 and adding AAAA records for your web servers could break a small fraction of clients. Although this breakage only would be a fraction of a percent it was still too high of a number for some large content providers.
Several speakers including myself concluded that the breakage appears to not be as severe as initially thought. Unless you are on the Alexa top 100 list, I think it is safe to say that you can enable IPv6 on your web server and publishing a quad-A record in your DNS without experiencing any problem.
IPv6 day is still going on
Yves Poppes from TATA communication as well as Ron Broersma from DREN shared some statistics about the IPv6 usage. It turns out that the IPv6 traffic has grown since the IPv6 day even if some large content providers decided to turn off IPv6 after the IPv6 day concluded. Ron concluded that they had around 15% IPv6 traffic on their network normally. Sometimes the IPv6 traffic spiked to up to 30%. Since his network is fully dual stacked, this is an indication on how much IPv6 content there are out there, probably more than you expected…
IPv4 run out?
Many presenters showed new statistics about when the different RIRs will run out. I shared some data from my IPv4depletion.com site. The consensus is that we might have a little bit more time with IPv4, especially in the ARIN region. This does however not mean that you can slack off on your IPv6 deployment.
Owen Delong from HE says: “I don’t think any IPv4 prediction that goes beyond 2012 for any RIR is accurate”. My personal opinion is that ARIN might have IPv4 addresses for some years longer than that, but again that does not mean that you can slack off on your IPv6 rollout.
There were a lot of discussion about rouge Router Advertisement and the security implication. I always thought that the problem as analog to a rogue DHCP server in IPv4. However Ron Broersma brought up a good point that the problem is mostly accidental and not malicious. If you turn on connection sharing in windows then all clients on the LAN might send you traffic. This is somewhat different from what you will have to do to accomplish the same thing on IPv4 with a DHCP server. In the IPv4 case you actually would have to download and activate a DHCP server, something that you don’t do by accident (Although I have to admit that I once pissed off a network admin by accidentally just doing that)
The next TXv6TF meeting will most likely be in Houston around March of next year. We hope to see you there.