Re: [rtcweb] On the topic of MTI video codecs

Daniel-Constantin Mierla <> Fri, 01 November 2013 07:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EEB3E11E82B6 for <>; Fri, 1 Nov 2013 00:38:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_74=0.6]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 0ATHIrblArpO for <>; Fri, 1 Nov 2013 00:38:01 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4013:c01::22a]) by (Postfix) with ESMTP id 1C79A21E80A8 for <>; Fri, 1 Nov 2013 00:37:48 -0700 (PDT)
Received: by with SMTP id q10so1547871eaj.29 for <>; Fri, 01 Nov 2013 00:37:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=mpJYgqE8xcu4YMjnq91oMZYaKXrCejKmvmCYc4+zZ4w=; b=WRztPuZpc/lh/PdnKlm20N3rmV72b0jdas4e43XsFvji5KXNm/FEmCfHQDZ6uSQxja aM2Yoyg4wFZW+fd08vCoRrRD2399cGzB/homhoY/RgPe42G8kX+j2UBo2j2MXtSzaA0X NWK+kwGn9XUjzQamAVf8hrPPPcXrDqml8X1zJ4BPJoDfdIUukF3XhpX7Vat1hGDke8e1 TclylNP+JSCjNNPHOzFcs0lIaeCld1Uv6zGt8qagha3eCYGstNOSxnEXHsXTGbaovgvG kttHYrUV1DenAigxNxIGWz/RlI0J3DZDDi2pPZ2WI0GxjUsbnbBiSqD4NESgkNxy8LRu WFWg==
X-Received: by with SMTP id n41mr123159eea.129.1383291458440; Fri, 01 Nov 2013 00:37:38 -0700 (PDT)
Received: from [] ( []) by with ESMTPSA id e13sm4324056eeu.4.2013. for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 01 Nov 2013 00:37:37 -0700 (PDT)
Message-ID: <>
Date: Fri, 01 Nov 2013 08:37:35 +0100
From: Daniel-Constantin Mierla <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: "Olle E. Johansson" <>
References: <> <> <> <> <> <>
In-Reply-To: <>
Content-Type: multipart/alternative; boundary="------------050407040504070602080704"
Cc: "" <>
Subject: Re: [rtcweb] On the topic of MTI video codecs
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: Fri, 01 Nov 2013 07:38:02 -0000

On 11/1/13 8:07 AM, Olle E. Johansson wrote:
> On 31 Oct 2013, at 21:51, Daniel-Constantin Mierla <> wrote:
>> On 10/31/13 10:35 AM, Olle E. Johansson wrote:
>>> On 30 Oct 2013, at 22:40, Cullen Jennings (fluffy) <> wrote:
>>>> On Oct 30, 2013, at 12:20 PM, Leon Geyser <> wrote:
>>>>> Unfortunately like Jonathan pointed out H.264 will only be able to be used royalty free on certain(most popular) platforms.
>>>>> To be able to avoid negotiation failure we need a MTI codec that every potential now/future browser would be able to implement freely.
>>>>> I like what Cisco did, but the solution seems a bit half-baked.
>>>> I think that Mozilla put it pretty nicely in their blog. What this annoucement gives us is not a perfect world. Mozilla is working towards a better future but in the mean time, this is the best thing we could possibly figure out on how to make the internet today be the best it can be for users.
>>> For the Open Source community in general I beleve this is a big move forward and I want to thank everyone involved in getting this done. It can not have been an easy internal struggle through all layers of the company. Everyone will benefit from it.
>>> For us in the Asterisk community I believe this opens up for use of video in a whole new way.
>> To my understanding, the release of the codec is for webrtc only, and particularly for client side/browsers. For clarification, is this codec/blob available to use for free in any application, no matter its relation with webrtc sessions?
> THe text on says:
> "Cisco is announcing today that we will take our H.264 implementation, and open source it under BSD license terms. Development and maintenance will be overseen by a board from industry and the open source community. Furthermore, we will provide a binary form suitable for inclusion in applications across a number of different operating systems (Windows, MacOS, Linux x86, Linux ARM and Android ARM), and make this binary module available for download from the Internet. We will not pass on our MPEG-LA licensing costs for this module, and based on the current licensing environment, this will effectively make H.264 free for use on supported platforms."
> Doesn't even mention WebRTC - does it?
quick check on that site and I couldn't sport it, maybe there were other 
blogs/news/... claiming that. On the site, it is still one questionable 
FAQ, imo:

*Q. Can I take advantage of the H.264 codec binary module in my project?*
A: Yes. Your users can download this module to utilize the H.264 video 
codec with your project.

"Your users" -- that sound like "not you" as service provider, more 
like: it can be used by client applications, not servers.


Daniel-Constantin Mierla -!/miconda -
Kamailio Advanced Trainings - Berlin, Nov 25-28
   - more details about Kamailio trainings at -