Re: [rtcweb] On video codec for rtcweb
Roman Shpount <roman@telurix.com> Fri, 23 March 2012 23:22 UTC
Return-Path: <roman@telurix.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 13A7D21E8027 for <rtcweb@ietfa.amsl.com>; Fri, 23 Mar 2012 16:22:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.814
X-Spam-Level:
X-Spam-Status: No, score=-2.814 tagged_above=-999 required=5 tests=[AWL=0.162, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 VV6O2yyzEOzc for <rtcweb@ietfa.amsl.com>; Fri, 23 Mar 2012 16:22:21 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5F08521E8011 for <rtcweb@ietf.org>; Fri, 23 Mar 2012 16:22:21 -0700 (PDT)
Received: by pbbrq13 with SMTP id rq13so3153707pbb.31 for <rtcweb@ietf.org>; Fri, 23 Mar 2012 16:22:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=DyBS7z8OoK8SUjUSazGZtexcusMSNlvqtKz6wnn7OJg=; b=PUZPy2th1W0uu+m/VW6jNrB5SmVs0W5k+M1I8JFkjjR689kYNA7ErtjZ82UiCfuelt FAdLZ4R0G1CzSpbUpxyKJPk8nnqKHEdfLCutxMU8Nd/xjh08LYSgWczgfogJW1B/TTYQ DtAl7adun5vROgYgz3EN1hEwEbj46AZQ8jYaV3v4cgGe0rIjL8nof9R5YGaW8OsaKp+W crSN1ZlDhUVELlzOEmVo5rQkrZmg6R5yCzinehVwthIsB+5jtvxmi49U55SmReuTW0jd BBnwy3TG0mqgVIt9JVUYiSrUjx+5ZPfN20SGZvwM2DCrwerr1XEOu3kDfzSqa6JyPosD v+vw==
Received: by 10.68.203.4 with SMTP id km4mr32832343pbc.53.1332544941204; Fri, 23 Mar 2012 16:22:21 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by mx.google.com with ESMTPS id u10sm6741717pbf.37.2012.03.23.16.22.19 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 23 Mar 2012 16:22:20 -0700 (PDT)
Received: by pbbrq13 with SMTP id rq13so3153690pbb.31 for <rtcweb@ietf.org>; Fri, 23 Mar 2012 16:22:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.221.10 with SMTP id qa10mr32009193pbc.139.1332544939128; Fri, 23 Mar 2012 16:22:19 -0700 (PDT)
Received: by 10.68.6.67 with HTTP; Fri, 23 Mar 2012 16:22:19 -0700 (PDT)
In-Reply-To: <4F6CC86A.3090107@hidayahonline.org>
References: <4F6C5A5E.6050100@ericsson.com> <4F6C6138.6010908@mozilla.com> <E44893DD4E290745BB608EB23FDDB76219E813@008-AM1MPN1-041.mgdnok.nokia.com> <4F6C6DC1.7020606@mozilla.com> <CAD5OKxu3Q45wASxLUhOR5kyPUZZb=81ybvZrpkbFuyqomsRH9Q@mail.gmail.com> <4F6CC86A.3090107@hidayahonline.org>
Date: Fri, 23 Mar 2012 19:22:19 -0400
Message-ID: <CAD5OKxu_668CbS1sPYzfK-Je9XGvDstsGMCmK_6-UbOMFZ2DUQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Basil Mohamed Gohar <abu_hurayrah@hidayahonline.org>
Content-Type: multipart/alternative; boundary="e89a8ff24801be75a604bbf14bfe"
X-Gm-Message-State: ALoCoQlGZFBzdPI6fOnMxTzIz6FrwzvOB3nu/FhEMj4HEYrwICzNos34tsCK/8koOHh5xNkDgCbC
Cc: rtcweb@ietf.org
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 23:22:22 -0000
On Fri, Mar 23, 2012 at 3:00 PM, Basil Mohamed Gohar < abu_hurayrah@hidayahonline.org> wrote: > On 03/23/2012 12:48 PM, Roman Shpount wrote: > > On Fri, Mar 23, 2012 at 8:34 AM, Timothy B. Terriberry > > <tterriberry@mozilla.com <mailto:tterriberry@mozilla.com>> wrote: > > > > With a direct browser-to-browser connection, there is nothing > > sitting between them to do the transcoding. In the DTLS-SRTP case > > with identity verification, which I think a number of people here > > view as highly important, you are in fact _guaranteeing_ that > > nothing but the browser can encode or decode the video. > > > > > > This is not technically correct. You can still build a system that > > implements a media proxy that does nothing but handling ICE, > > encryption, and identity verification without ever transcoding the > > content. The cost of re-encrypting the media is low (ie single E5 Xeon > > CPU can probably do about 10GB/s), but the cost of transcoding video, > > or even audio is huge in comparison. Because of this, supporting a > > comprehensive set of codecs is highly desirable. > While perhaps technically desirable for those already knee-deep in the > existing telecommunications, it will serve to lock-out any WebRTC > implementations that either choose to or cannot implement an encumbered > format, such as free/open source software developers and companies. As > of right now, there *are* no official complete WebRTC implementations to > inconvenience by choosing a mandatory-to-implement codec. It would be > only an inconvenience to existing infrastructure, but because of the > free and open nature of the proposed format, adding support for it in > software would be a minimal effort, especially as it would standardized. > > The reference implementation of VP8 (libvpx) is also licensed in such as > a way as to be equally available to all types of software. > > I am not arguing for making H.264 a base codec. I would actually prefer VP8. All I was saying that despite lack of interoperability on encryption, ICE, and identity, there are still significant benefits of supporting the same codecs when communicating with legacy equipment, since re-encryption and media proxy can be handled separately and using much less resources then transcoding. _____________ Roman Shpount
- 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