Re: [rtcweb] Congratuiations on the Cisco announcement - but we still prefer VP8

"Mo Zanaty (mzanaty)" <> Thu, 07 November 2013 20:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2C8CC21E81C2 for <>; Thu, 7 Nov 2013 12:33:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.485
X-Spam-Status: No, score=-10.485 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dRLW9cX4w0gq for <>; Thu, 7 Nov 2013 12:33:53 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id C1D8F21E81D0 for <>; Thu, 7 Nov 2013 12:33:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=10793; q=dns/txt; s=iport; t=1383856432; x=1385066032; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=Z9MoZgI3Ew0SToOJmmddMMgdQeeXouoIVDYTZMTLVzc=; b=OhpalsGb6zml6o01vUKVwP3ynj/QNfVINihuJMvRAJ0CrdjdP31TB4wM ANm51QH77gC+z2vFSOUGQ/AP9QgDyrKxHemqLDHBAo7+x3PBSpGoySdGl 8dvAyD0yzr46TaJC80D2/vNCQgyDERqjudZS4CQdl9A3eFqtMNXRJYqhi k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAJ74e1KtJV2Z/2dsb2JhbABagkNEOFO+REqBJhZ0gicBBAEBAWsLEgEIDjEuCxQRAgQBDQUUB4dmDbx2j1UEB4QwA5gMkgqBaIE+gio
X-IronPort-AV: E=Sophos; i="4.93,654,1378857600"; d="scan'208,217"; a="282164966"
Received: from ([]) by with ESMTP; 07 Nov 2013 20:33:42 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id rA7KXfHG024139 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 7 Nov 2013 20:33:42 GMT
Received: from ([]) by ([]) with mapi id 14.03.0123.003; Thu, 7 Nov 2013 14:33:41 -0600
From: "Mo Zanaty (mzanaty)" <>
To: Gustavo Garcia <>, Harald Alvestrand <>
Thread-Topic: [rtcweb] Congratuiations on the Cisco announcement - but we still prefer VP8
Thread-Index: AQHO2/ikT5QE5z7i406gT9fvB0QDJw==
Date: Thu, 07 Nov 2013 20:33:40 +0000
Message-ID: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_CEA14C7D1C48Amzanatyciscocom_"
MIME-Version: 1.0
Cc: "" <>
Subject: Re: [rtcweb] Congratuiations on the Cisco announcement - but we still prefer VP8
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 07 Nov 2013 20:33:58 -0000

The blog makes a good point I would like to highlight and address:
"If you want us to get 100% serious about H.264 for WebRTC, why not just make it free?  MPEG-LA, you’ll get our attention if you declare software implementations of H.264 codecs for WebRTC free and clear of royalties."

Many (of the ~30) member companies in the MPEG-LA AVC pool agree with this point and pushed for amendments to the license to make constrained baseline profile royalty-free. There were a few objections. So the supporting members took this point directly to MPEG itself (all >200 members), to have a new royalty-free standard called WebVC that is H.264 AVC CBP. This has progressed in MPEG to DIS (Draft Intl Std) status, when IPR declarations are typically made.

In short, most MPEG members are not evil, and want the same thing as the open source and broader communities, including royalty-free licensing.

The Cisco announcement is to remove the dependencies on these MPEG and MPEG-LA efforts (which would, however, remove the redistribution restrictions that people have rightfully criticized).


On 11/5/13, 7:23 PM, Gustavo Garcia <<>> wrote:


H.264 licensing as introduced by Cisco is great because it opens the door to truly present H.264 as a viable alternative codec for broad implementation in WebRTC endpoints, but Cisco’s proposal as it stands is not enough to warrant H.264 being adopted as an MTI for WebRTC.

>From TokBox’s point of view, WebRTC needs to be able to solve two needs if true adoption is intended:  1) supporting interoperability with legacy end-points and 2) enabling novel and innovative real-world use-cases on a broad range of software-powered end-points (mobile included, not just browsers)

The option as proposed with H.264 is not really viable in mobile native applications (specifically iOS devices as the situation stands today), whether both endpoints are mobile native or one is browser-based. At TokBox, we are already seeing a wide range of very interesting applications being built on top of WebRTC using native mobile apps as one of the endpoints, and the standard must do the right thing by not preventing these scenarios from playing out.

As far as MTI codecs go, we still believe VP8 is the right option and believe H.264 should be embraced as an optional alternative video codec.The purpose of the WebRTC is not to create a browser compatible with existing solutions (many of which are closed systems) but rather to bring the best possible experience to application developers, extending the capabilities of the web for real-time communication. (More of our views here:

On Thu, Oct 31, 2013 at 11:47 AM, Harald Alvestrand <<>> wrote:

We congratulate Cisco on their intention to make an open source H.264 codec available and usable by the community. We look forward to seeing the result of this effort.

Google still believes that VP8 - a freely available, fully open, high-quality video codec that you can download, compile for your platform, include in your binary, distribute and put into production today - is the best choice of a Mandatory to Implement video codec for the WebRTC effort.

Harald (sending this from my Google address)

rtcweb mailing list<>