[rtcweb] On video codec for rtcweb
Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com> Fri, 23 March 2012 11:11 UTC
Return-Path: <stefan.lk.hakansson@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C47A21F8564 for <rtcweb@ietfa.amsl.com>; Fri, 23 Mar 2012 04:11:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.91
X-Spam-Level:
X-Spam-Status: No, score=-9.91 tagged_above=-999 required=5 tests=[AWL=0.689, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iV2ouRTYXVyp for <rtcweb@ietfa.amsl.com>; Fri, 23 Mar 2012 04:11:32 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id CE5AC21F8568 for <rtcweb@ietf.org>; Fri, 23 Mar 2012 04:11:28 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c6fae0000045c0-ab-4f6c5a5f7593
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 5B.DA.17856.F5A5C6F4; Fri, 23 Mar 2012 12:11:27 +0100 (CET)
Received: from [150.132.142.245] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.213.0; Fri, 23 Mar 2012 12:11:27 +0100
Message-ID: <4F6C5A5E.6050100@ericsson.com>
Date: Fri, 23 Mar 2012 12:11:26 +0100
From: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120310 Thunderbird/11.0
MIME-Version: 1.0
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Subject: [rtcweb] On video codec for rtcweb
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Mar 2012 11:11:36 -0000
I think most agrees to that it would be advantageous if there could be an agreement on mandatory to implement codecs (at least one for audio and at least one for video), for interoperability between implementations (among other things). I would like to discuss a bit on mandatory to implement video codec support. There are many factors to consider, three of them are: 1. Coding efficiency: As more and more of the available capacity on the Internet is consumed by video, I think that codecs that are clearly inferior to the state of art regarding compression efficiency should not be considered. 2. Implementation status: Another factor to consider is the implementation status in end user equipment, and, especially for battery powered devices, to what extend platforms have (optimized/HW accelerated) implementations. 3. Interoperability with existing services (it can be argued that webrtc is a green field, but on the other hand there seems to be a lot of people wanting interoperability). To me, h.264 is a good candidate considering the factors above. It is competitive regarding compression efficiency, it is widely implemented (in all kinds of devices and platforms) and is the by far mostly used video codec currently. Notably, a recent study ([1]) says that h.264 is the leading format also for the html video element. In addition, licensing for h.264 seems straightforward, and the large number of implementations in commercial use indicates that vendors do not perceive the risk for licensing/patent issues down the road as being unacceptable big (this is an observation from the outside; I'm not a lawyer and I don't deal with licensing). So, I propose that h.264 should be mandatory to implement. Stefan [1] http://blog.mefeedia.com/html5-dec-2011
- [rtcweb] On video codec for rtcweb Stefan Hakansson LK
- Re: [rtcweb] On video codec for rtcweb Timothy B. Terriberry
- Re: [rtcweb] On video codec for rtcweb Lorenzo Miniero
- Re: [rtcweb] On video codec for rtcweb Markus.Isomaki
- Re: [rtcweb] On video codec for rtcweb Timothy B. Terriberry
- Re: [rtcweb] On video codec for rtcweb Cavigioli, Chris
- Re: [rtcweb] On video codec for rtcweb Markus.Isomaki
- Re: [rtcweb] On video codec for rtcweb Basil Mohamed Gohar
- Re: [rtcweb] On video codec for rtcweb Timothy B. Terriberry
- Re: [rtcweb] On video codec for rtcweb Bernard Aboba
- Re: [rtcweb] On video codec for rtcweb Matthew Kaufman
- Re: [rtcweb] On video codec for rtcweb Timothy B. Terriberry
- Re: [rtcweb] On video codec for rtcweb Timothy B. Terriberry
- Re: [rtcweb] On video codec for rtcweb Timothy B. Terriberry
- Re: [rtcweb] On video codec for rtcweb Martin Thomson
- Re: [rtcweb] On video codec for rtcweb Matthew Kaufman
- Re: [rtcweb] On video codec for rtcweb Basil Mohamed Gohar
- Re: [rtcweb] On video codec for rtcweb Roman Shpount
- Re: [rtcweb] On video codec for rtcweb Serge Lachapelle
- Re: [rtcweb] On video codec for rtcweb Basil Mohamed Gohar
- Re: [rtcweb] On video codec for rtcweb Schleef, David
- Re: [rtcweb] On video codec for rtcweb Roman Shpount
- Re: [rtcweb] On video codec for rtcweb Gregory Maxwell
- Re: [rtcweb] On video codec for rtcweb Cameron Byrne
- Re: [rtcweb] On video codec for rtcweb Tim Panton
- Re: [rtcweb] On video codec for rtcweb Roman Shpount
- Re: [rtcweb] On video codec for rtcweb Jean-Marc Valin