World IPv6 Day proved to be a success. Major service providers and websites are ready for IPv6, but some experience response times lower than when using IPv4. Experts draw attention to a possible security flaw in IPv6 implementations.
June 8th 2011 is World IPv6 day, where many large internet organisations such as Google and YouTube, and social networks like Facebook have IPv6 enabled their sites for at least the next 24 hours. If you have an IPv6 connection, then when you visit these sites you'll be going over the IPv6 network instead of the IPv4 network.
Google has enhanced WebP, their open source image compressing format with higher image quality, progressive decoding, reduced pixelation along edges, and JNI support. Alpha channel support will be added soon, along with more speed improvements. The format is currently supported only by Google and Opera.
"Embrace HTML5" was held in Shanghai last week. Jeremy Keith, the author of "DOM Scripting" and “HTML5 for Web Designers”, presented a speech on the design principles of HTML5. He also introduced the history of HTML and answered some questions from the audience.
Microsoft released IE9, its flagship internet browser, at the SxSW conference yesterday. This brings IE into closer alignment with current web browsers, as it introduces some level of HTML5 support and achieves a 95% pass rate on the Acid 3 tests.
APNIC have requested two IPv4/8 address blocks, resulting in the final five IPv4/8 address blocks being distributed as per RIPE-436. IANA has no more IPv4 addresses to distribute, and the major RIRs will likely run out of IPv4 addresses before the end of this year. IPv6 is the only way out of this predicament.
The Internet Society has called for a World IPv6 Day on 8th June 2011 to promote the use of IPv6 by major organisations such as Google, Facebook and Akami. With IPv4 blocks expected to run out in the next week, the timing for the announcement could not be better.
The Google Chrome team have announced that they will remove H264 support from the HTML5's video tag in Chrome in the next couple of months. Opinions are polarised as to the effect this will have on HTML5 video adoption.
Some allegations regarding backdoors implemented at FBI’s request in OpenBSD’s IPsec stack were made earlier this month. After auditing the code, Theo de Raadt, the founder of OpenBSD, has concluded that there are no such threats in the open source operating system.
Microsoft has decided not to include emerging web technologies still under development in IE9, providing instead HTML5 Labs, a website for testing prototype technologies such as IndexedDB and WebSockets.
Google wants to shrink images transferred over the Internet by proposing a new lossy format called WebP. They claim they have achieved 39% reduction in image byte size leading to speedier page load.
The MPEG LA, who hold the patent pool on the MPEG H.264 video format, have recently extended their pledge for free web-based video to last for the lifetime of the license. In a Press Release (pdf) yesterday, they confirmed the continuation of the free license, which had been due to expire in December 2015. But what does this mean for HTML5 browsers?
Google has open-sourced WebM, a royalty free media file format for compressing and encoding video. While this is good news for many industry players which have shown their support for the new standard, some of the questions which have been raised so far have included concerns around licensing and code quality.
Dean Hachamovitch, General Manager for Internet Explorer at Microsoft, has announced that IE9 will use only the H.264 standard to play HTML 5 video. Microsoft seems to have become very committed to HTML 5, while Flash loses even more ground. The announcement came the same day Steve Jobs detailed why Apple does not accept Flash on iPhone and iPad.
Google uses WebGL to natively render 3D graphics inside Chrome. The problem is that WebGL relies on OpenGL 2.0, and not all Windows systems have its drivers installed. The ANGLE (Almost Native Graphics Layer Engine) project is intended as a thin layer between WebGL and DirectX, enabling Chrome to do 3D on any Windows system.