Re: [rtcweb] On video codec for rtcweb
Serge Lachapelle <sergel@webrtc.org> Fri, 23 March 2012 18:23 UTC
Return-Path: <sergel@google.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 9FBFD21F862F for <rtcweb@ietfa.amsl.com>; Fri, 23 Mar 2012 11:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.71
X-Spam-Level:
X-Spam-Status: No, score=-100.71 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666, USER_IN_WHITELIST=-100]
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 JjAL6YJCbETV for <rtcweb@ietfa.amsl.com>; Fri, 23 Mar 2012 11:23:23 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 62FFE21F8629 for <rtcweb@ietf.org>; Fri, 23 Mar 2012 11:23:23 -0700 (PDT)
Received: by ggmi1 with SMTP id i1so3342870ggm.31 for <rtcweb@ietf.org>; Fri, 23 Mar 2012 11:23:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :x-system-of-record; bh=i3gzrb6g+LjbaYJq62p2bv3K54sYhkrkOXFR3snw0is=; b=SommVj2VK1nHRNCeE+nULKc4SkRwUZBUlMYAwQU1ZOjKN9LFlMcqRthOkSVwXCzxDV KhGlsPfOCUR8TlMa2WySfUgD5oOmWcYzXmnBa4NpoyhWDJ8KD0cZbc860aO7k9HwBEep pKyvz6TLDCSE5bRwWmVecoK+MkvraHU6I1TwIXzhBmc29EurExKt5dxC8vhaky207RNI pBJ0HSbvIZxKtP4NSxpoz3md718yzbfOjW2vmi/Dg7cbegvgGR08n+T4EwUYf1PvJCtZ SiIVr32ilYJHo17ntC0H0CwfXD9HJfKtkOydqkmd+xaGB8AFadjSbzF8OOjHUjK5uKYp nQUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :x-system-of-record:x-gm-message-state; bh=i3gzrb6g+LjbaYJq62p2bv3K54sYhkrkOXFR3snw0is=; b=H06dtMXTHyYrlymNyUdgLB7ow4/24x5zWT91qdPbeL/gk1otIHrcxnIr4CAs1vaKjG cRsOPuu6rscM1QUf56bly1lZlusYbqslso1Ln+5EnK4U449MCq8r/AaOVuBonSuqE5y8 +Ji+gf9W/z5kz2noHjOucd4OEKG6Gf5ri0KEelAXyhAONAPfaaqdyRdwS8J+GqvsTDC0 /EjIrnx8lPq7xBsXydGL8Pww4s2Mx92VPopsUW+dwZW2RDNJSoqwHyvyF6OvX61pyGFl ya6FidUSIPhm0RAg9JN5qoOwJ7eunca0j3L06G193ENDM9pFu9h3mukwLg+m+W+oeraQ uKzw==
Received: by 10.60.28.33 with SMTP id y1mr11149134oeg.62.1332527002759; Fri, 23 Mar 2012 11:23:22 -0700 (PDT)
Received: by 10.60.28.33 with SMTP id y1mr11149126oeg.62.1332527002659; Fri, 23 Mar 2012 11:23:22 -0700 (PDT)
MIME-Version: 1.0
Sender: sergel@google.com
Received: by 10.182.69.226 with HTTP; Fri, 23 Mar 2012 11:22:52 -0700 (PDT)
In-Reply-To: <4F6C6138.6010908@mozilla.com>
References: <4F6C5A5E.6050100@ericsson.com> <4F6C6138.6010908@mozilla.com>
From: Serge Lachapelle <sergel@webrtc.org>
Date: Fri, 23 Mar 2012 19:22:52 +0100
X-Google-Sender-Auth: LIwQn18EfiYkwQpaVmJVSDpA75A
Message-ID: <CAMKM2LyCmyPhQg9Rys_QkRB=QqF5xU7KUMXX87ruGaVY7vGgzg@mail.gmail.com>
To: rtcweb@ietf.org
Content-Type: multipart/alternative; boundary="e89a8fb1fffaa5aaa904bbed1e13"
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQnRrLf+1cnaCpcHbdC6SYR9KfJWZBTWkhlpwM/P+DCzPrFZGQAuPe4KfnGSMevBtfjgGy2PXdEwqZFn2lqolAHl7Gv7/9lnu4fNMTMe2ZX3MbFEvdwVFwG50BCkC4zzylSVPipC
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 18:23:27 -0000
Chrome's WebRTC stack will only include the VP8 codec. Best Regards, /Serge On Fri, Mar 23, 2012 at 12:40, Timothy B. Terriberry < tterriberry@mozilla.com> wrote: > Stefan Hakansson LK wrote: > >> So, I propose that h.264 should be mandatory to implement. >> > > Mozilla strongly opposes such a proposal. Many will be familiar with our > announcements regarding our use of platform codecs on B2G and possibly > Android last week. The primary reasoning behind that decision, i.e. the one > factor that was not in our power to change, was the availability of content > on websites. This is not a problem for WebRTC, as browsers control both > ends of the communication. > > What _is_ a problem is licensing and distributing encoders in an > open-source project. This is quite a bit different than using system > decoders, as outside of mobile, encoders are usually not available, and > even if they were, they might not have particularly good quality, nor the > features to control latency, loss robustness, and other aspects necessary > for real-time communication. > > If you thought that a concession in one place would make Mozilla more > likely to compromise in others, I assure you the opposite is true. > Maintaining the use of RF codecs in WebRTC is now even more important than > it was before. See the words directly from Mozilla's CTO: > http://groups.google.com/**group/mozilla.dev.platform/** > msg/53892ad3ea9eeb98<http://groups.google.com/group/mozilla.dev.platform/msg/53892ad3ea9eeb98> > > ______________________________**_________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/**listinfo/rtcweb<https://www.ietf.org/mailman/listinfo/rtcweb> > Google Sweden AB | Kungsbron 2, SE-111 22 Stockholm | Org. nr. 556656-6880 > > Apparently, this footer is required in Europe. Apologies. This email may > be confidential or privileged. If you received this communication by > mistake, please don't forward it to anyone else,please erase all copies and > attachments, and please let me know that it went to the wrong person. > Thanks. > <https://www.ietf.org/mailman/listinfo/rtcweb>
- 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