Archive for March, 2012
I’ve been lurking on three IPv6 mailing lists for the past few months: v6ops , ipv6-ops, and ipv6hackers. While there is some overlap in the people and topics discussed, each list is uniquely useful and has a different focus and flavor.
firstname.lastname@example.org – this IETF list has a lot of focus on making sure that Internet standards (RFCs) are operationally practical and useful. There’s a lot of time spent discussing Internet-draft (pre-RFC) documents, in the context of real-world operations.
email@example.com – “This list is a forum for people who are actually deploying IPv6 in the Internet. Its focus is on OPERATIONAL issues (especially BGP routing) and development of the production IPv6 Internet cloud.” This list seems to have a lot more world wide network operators discussing real-world problems with IPv6 either as deployments or as bugs in router code. If you want to see what in-the-trenches network operators are seeing as they deploy IPv6, read this list.
firstname.lastname@example.org – This list “… is meant to provide forum for IPv6 security researchers and IPv6 networking professionals to discuss low-level IPv6 networking and security issues that could eventually lead to advances and improvements in the area of IPv6 security and IPv6 networking.” This list seems to be much lower-volume, and has some overlap with the other two lists. I have seen discussions on IPv6 programming (app development and porting), which I haven’t seen as much in other places.
All three of these lists have been useful. I’ve seen discussions of the things that are blocking users and networks from moving to IPv6 (“my users need Skype”), to bugs in various flavors of router code, to unintended interactions between RFCs that break IPv6 deployments.
While some of what is discussed is beyond the scope of a simple home network, or even a moderately-complex corporate network, seeing all this is valuable. I know that at some point I’ll hit some IPv6 roadblock, and someone on one of these lists will have the answer.
If you’re serious about IPv6, you should join the community, and these lists are where that community is talking about the future.
As part of the IPv6 sprint at work last month, I ended up doing a lot of IPv6 research. For my part, I spent a lot of time researching “customer issues” and MacOS issues in addition to the purely technical work.
When I started the sprint, my laptop was on MacOS X Snow Leopard, which I used for all my home IPv6 work. Halfway through the sprint, I upgraded to MacOS X Lion.
The upgrade to Lion went well, but Apple has changed the behavior of some IPv6 features, and I personally would have to consider Snow Leopard as a better IPv6 platform than Lion.
Apple didn’t “break” IPv6 in Lion, but they did introduce a new problem, which has been dubbed “hampered eyeballs”.
I’ve noticed some newly-hampered IPv6 web browsing since the upgrade. Some sites that came back solidly on IPv6 100% of the time, now come back as IPv4 up to 20% of the time. (Thanks IPvFox!)
This has lots of implications for how consumers will see the new Internet, especially during the transition. According to some anecdotal remarks on some IPv6 mailing lists, this is being used as an excuse by some companies to delay (even more) any IPv6 transition or even dual stacking!
This last week was Game Developer Conference in San Francisco, next week is a global IPv6 meeting in New Jersey. I should have lots more “corporate” IPv6 info on the next 10 days.