IETF Logo Mail Archive

Re: [rtcweb] VP8 vs H.264 - the core issue

<Markus.Isomaki@nokia.com> Fri, 25 October 2013 08:15 UTC

Return-Path: <Markus.Isomaki@nokia.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 9425D21E80A6 for <rtcweb@ietfa.amsl.com>; Fri, 25 Oct 2013 01:15:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 nUc3RgQkozvh for <rtcweb@ietfa.amsl.com>; Fri, 25 Oct 2013 01:15:41 -0700 (PDT)
Received: from mgw-sa02.nokia.com (smtp.nokia.com [147.243.1.48]) by ietfa.amsl.com (Postfix) with ESMTP id 54DD121E8094 for <rtcweb@ietf.org>; Fri, 25 Oct 2013 01:15:40 -0700 (PDT)
Received: from smtp.mgd.nokia.com ([65.54.30.59]) by mgw-sa02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r9P8BuME024607 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 25 Oct 2013 11:11:57 +0300
Received: from 008-AM1MPN1-043.mgdnok.nokia.com ([169.254.3.235]) by 008-AM1MMR1-004.mgdnok.nokia.com ([65.54.30.59]) with mapi id 14.03.0136.001; Fri, 25 Oct 2013 08:11:56 +0000
From: Markus.Isomaki@nokia.com
To: cowwoc@bbs.darktech.org, rtcweb@ietf.org
Thread-Topic: [rtcweb] VP8 vs H.264 - the core issue
Thread-Index: AQHO0VimRcO5ZGLqUUag+6tiIuKaVJoFDwMQ
Date: Fri, 25 Oct 2013 08:11:56 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7620A0F2748@008-AM1MPN1-043.mgdnok.nokia.com>
References: <52681A96.2020904@alvestrand.no> <526826AF.5030308@librevideo.org> <52690090.2050609@alvestrand.no> <BBE9739C2C302046BD34B42713A1E2A22DFCD683@ESESSMB105.ericsson.se> <AE1A6B5FD507DC4FB3C5166F3A05A4843D45DC08@TK5EX14MBXC266.redmond.corp.microsoft.com> <5269764C.4030801@librevideo.org> <52698758.5040404@bbs.darktech.org> <CAD6AjGSb5syh0HO+89fH8cGZ0zqM6gYLPj3aeTRQLN0u8W4cSg@mail.gmail.com> <5269F098.2020904@alvestrand.no> <526A25C0.6080406@bbs.darktech.org>
In-Reply-To: <526A25C0.6080406@bbs.darktech.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-tituslabs-classifications-30: TLPropertyRoot=Nokia; Confidentiality=Nokia Internal Use Only; Project=None;
x-titus-version: 3.5.9.3
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7IiWc+o8hXFUdLEV0dd3jRi9ZSnsyh2XxM9weacZlWDiXp2iugdu9/GeoD1NA6FKLHcwaKBRAiccUJ0MNT8h9MBXc/rgYtLrRsB5pMO+FxzwPovcKyyYUD6X9TbWJu8NgcZi7McFgkluASQ00lfICVg6apNxFMnyGEEuExlpdykNE18BSUlOpvQLyhfy/vKX6vQk6IExW9utbu+gZQFMDBmthSHLcbECFAcwYBHig4JX1
x-originating-ip: [172.21.80.105]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Nokia-AV: Clean
Subject: Re: [rtcweb] VP8 vs H.264 - the core issue
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, 25 Oct 2013 08:15:47 -0000

Hi,

cowwoc wrote:
> 
>      I think the real elephant in the room is whether Apple and Microsoft (who
> are on the H264 bandwagon) will decide to implement VP8 just because you
> mandate it or whether they will side-step WebRTC altogether. FireFox's
> market-share is decline so more and more this is becoming a story of Chrome
> vs IE (on desktop) + Safari (on mobile).
> 

I think we can equally well ask whether Chrome and Firefox will support H.264 for WebRTC if IETF mandates that codec.

If the answer to both of these questions is "no", the value of the IETF decision is not that great. 

Markus

v2.23.0 | Report a Bug | By Email