2011-12-12
Google may be very careful with making t ... 8 years ago
Google may be very careful with making their services available via IPv6, but internally they are going further already: Usenix: Google deploys IPv6 for internal network - ITWorld.Google has learned that an IPv6 migration involves more than just updating the software and hardware. It also requires buy-in from management and staff, particularly administrators who already are juggling too many tasks. And, for early adopters, it requires a lot of work with vendors to get them to fix buggy and still-unfinished code.The migration to IPv6 is not an L3 problem. It is more of an L7-9 problem: resources, vendor relation-ship/management, and organizational buy-in.Paper: Deploying IPv6 in the Google Enterprise Network. Lessons learned. Haythum Babiker, Irena Nikolova, Kiran Kumar Chittimaneni. The paper notes that a big problem with "IPv6 support" in networking devices means "support in software" which will cause CPU load at real usage. Some interesting bugs in IPv6 implementations were also showing, such as router announcement packets leaking from one wireless VLAN to the other. My best guess: a not-too-brilliant implementation of multicast. Google also received the big vendor IPv6 lie:When trying to talk to the ven-dors they were always saying - if there is a demand for IPv6 support at all, we’ve never heard it before.That is what they tell every client with questions about IPv6. Found via Google Deploys IPv6 For Internal Network - Slashdot.