Re: [rtcweb] On video codec for rtcweb
Basil Mohamed Gohar <abu_hurayrah@hidayahonline.org> Fri, 23 March 2012 13:24 UTC
Return-Path: <abu_hurayrah@hidayahonline.org>
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 D952421F84A7 for <rtcweb@ietfa.amsl.com>; Fri, 23 Mar 2012 06:24:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.276
X-Spam-Level:
X-Spam-Status: No, score=-2.276 tagged_above=-999 required=5 tests=[AWL=0.323, BAYES_00=-2.599]
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 qYpgmQm3cP9p for <rtcweb@ietfa.amsl.com>; Fri, 23 Mar 2012 06:24:47 -0700 (PDT)
Received: from mail.zaytoon.hidayahonline.net (zaytoon.hidayahonline.net [173.193.202.83]) by ietfa.amsl.com (Postfix) with ESMTP id E4F7621F84A6 for <rtcweb@ietf.org>; Fri, 23 Mar 2012 06:24:46 -0700 (PDT)
Received: from [10.10.40.98] (rrcs-98-103-138-67.central.biz.rr.com [98.103.138.67]) by mail.zaytoon.hidayahonline.net (Postfix) with ESMTPSA id 94FDB65246E for <rtcweb@ietf.org>; Fri, 23 Mar 2012 09:24:45 -0400 (EDT)
Message-ID: <4F6C7997.3080603@hidayahonline.org>
Date: Fri, 23 Mar 2012 09:24:39 -0400
From: Basil Mohamed Gohar <abu_hurayrah@hidayahonline.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Lightning/1.0b3pre Thunderbird/3.1.16
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <4F6C5A5E.6050100@ericsson.com> <4F6C6138.6010908@mozilla.com> <E44893DD4E290745BB608EB23FDDB76219E813@008-AM1MPN1-041.mgdnok.nokia.com> <E36D1A4AE0B6AA4091F1728D584A6AD215EC3936@ORSMSX104.amr.corp.intel.com>
In-Reply-To: <E36D1A4AE0B6AA4091F1728D584A6AD215EC3936@ORSMSX104.amr.corp.intel.com>
X-Enigmail-Version: 1.1.2
OpenPGP: id=5AF4B362
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: Re: [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 13:24:49 -0000
On 03/23/2012 08:34 AM, Cavigioli, Chris wrote: > Let's be clear on profiles. If we seek widest mobile hardware footprint: > - ITU-T H.264 Constrained Baseline Profile is probably the most ubiquitous hardware video codec today with reasonable power/performance ratio > - ITU-T G.711, both u_law (North America) and A_law (Europe) formats, can be supported by everyone with very trivial software burden > -chris Seeking the widest mobile hardware footprint is a very narrow view considering the scope of WebRTC. WebRTC is a technology with browsers as the main endpoints. While mobile devices make up a significant portion of that population, they are by no means the only one, and there are no guarantees that this will be the major use case of WebRTC in the future. Time and again, success and adoption of standards across all markets, devices, and platforms has been rooted in the usage of a open, royalty-free formats. Mandating H.264 for this or any other purpose while it remains unlicensable for usage in free/open source software projects invalidates the universality of WebRTC. This would setup the protocol to be yet another proprietary system that claims to be open but in practice will be limited to usage solely by existing MPEG-LA licensors/licensees and other existing players in the telecommunications market. This makes the project, and the standard, dead in the water as far as a lot of the players interested in this project are concerned. Having said that, WebRTC at this point remains open and free, and to ensure that, the only technologies that should be included are those that are royalty free and licensed for use within free/open-source software project. This is the *only* way for WebRTC to be successful and to achieve the goals of its (intended) open nature.
- Re: [rtcweb] On video codec for rtcweb Bernard Aboba
- Re: [rtcweb] On video codec for rtcweb Matthew Kaufman
- [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 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 Tim Panton
- 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 Roman Shpount
- Re: [rtcweb] On video codec for rtcweb Jean-Marc Valin