Re:H.264 Support Lands in Firefox 20 Nightly on Windows
by ZeroGravitas on Thursday December 20, 2012 @06:57AM
(#4947225)
Have the IETF actually chosen VP8 as the/a mandatory to implement video codec for RTCWeb yet?
The same people that shot it down as a standard web codec have been recycling the same FUD for this debate. The last I recall was Google sending this rather mysterious email the day before the decision was supposed to be taken:
"Google understands that concerns have been raised within the IETF RTCWEB WG in regards to VP8 IPR. We endeavored to properly address these concerns in time for this IETF meeting but did not meet the deadline.
We hereby commit to addressing this by the next IETF meeting in Orlando. Our proposal will address prevalent IPR issues.
Google believes strongly that the VP8 codec is the best technical option for a mandatory to implement codec.
We therefore kindly ask to postpone this decision and hope the workgoup will take this opportunity to make progress on other vital topics."
The same people that shot it down as a standard web codec have been recycling the same FUD for this debate. The last I recall was Google sending this rather mysterious email the day before the decision was supposed to be taken:
http://www.ietf.org/mail-archive/web/rtcweb/current/msg05698...
"Google understands that concerns have been raised within the IETF RTCWEB WG in regards to VP8 IPR. We endeavored to properly address these concerns in time for this IETF meeting but did not meet the deadline.
We hereby commit to addressing this by the next IETF meeting in Orlando. Our proposal will address prevalent IPR issues.
Google believes strongly that the VP8 codec is the best technical option for a mandatory to implement codec.
We therefore kindly ask to postpone this decision and hope the workgoup will take this opportunity to make progress on other vital topics."