No Consensus at IETF, But It’s Not Over Yet
Cisco recently announced that we would open source our H.264 implementation under favorable open source terms, and more importantly, provide a binary distribution of that implementation that could be downloaded and integrated into browsers and other applications. We said we’d cover the MPEG-LA licensing costs for this distribution as well. Mozilla responded by saying that, based on this, they would add H.264 to Firefox, using our technology.
Part of our motivation for making this announcement was to unstick the logjam that has occurred in the standards bodies. The Internet Engineering Task Force (IETF) is defining the standards for how real-time voice and video will work natively in the browser. Selection of a common video codec is part of that process. The group has been highly divided on this topic, with two camps – one (including Cisco), in favor of industry standard H.264, and others in favor of Google’s VP8 technology.
We hoped that our announcement, and Mozilla’s agreement to support H.264 as a common codec, would provide enough impetus to sway the standards to a concrete decision so that the industry could move forward. Alas, that was not the case. Despite what we felt was a fairly objective analysis on the reasons why H.264 was a better choice for the overall success of real-time communications on the web (click here for a recording), the IETF failed to reach consensus.
Obviously, we’re very disappointed by this. However, Cisco is absolutely committed to continue with our efforts on openH.264, and we will continue working with Mozilla to integrate it into Firefox. We hope that real working code that supports H.264 in browsers is the best way to move the industry forward. In parallel, we continue to be engaged in the standards activities. The discussion is not yet over yet! The group is discussing alternative proposals and consensus mechanisms, and we’re working there to see if consensus can yet still be achieved.Tags: