Re: [rtcweb] Congratuiations on the Cisco announcement - but we still prefer VP8

Eric Rescorla <ekr@rtfm.com> Sat, 02 November 2013 14:10 UTC

Return-Path: <ekr@rtfm.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 06BB011E80E3 for <rtcweb@ietfa.amsl.com>; Sat, 2 Nov 2013 07:10:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.772
X-Spam-Level:
X-Spam-Status: No, score=-102.772 tagged_above=-999 required=5 tests=[AWL=0.204, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 s7FElrmI78rX for <rtcweb@ietfa.amsl.com>; Sat, 2 Nov 2013 07:09:58 -0700 (PDT)
Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) by ietfa.amsl.com (Postfix) with ESMTP id BB78D11E8115 for <rtcweb@ietf.org>; Sat, 2 Nov 2013 07:09:57 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id f4so2157812wiw.10 for <rtcweb@ietf.org>; Sat, 02 Nov 2013 07:09:56 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=8lySq0j0aK4PeEoZ8jnIoUkBysylyhgbiChJUaPpbPk=; b=g4/bnxqfnkYIoU7Jy6I8CepfxLDStpqA4EtloALYRrBs4wiRIcPBqtQvHk6DlMVbii PqYnSO5CMaq1n3L74wZGQoIk+KBx5hroifikZzmt+OpMiFmHAOVPGt6k/CtPRnUab/Hq UcsbiXKDjQ7KJ1uJS4r7Cs+LGqtI7ltx93DSdtRM43VOqjnXj7/jspajXvUlGhKpv5Qz z7UC0mgsqeMzAejsD9Di1ZT5sLd+FhdObjpP/ANH+7m5O7My9DKXt4u9CFnSauHZEgBn rB3rv3IyNc+15vJ/5sBdbb5Yp5e1DVdvKPJeMFXvqhW3oS53k7UP6hWlkZldaSyxPGUr A7ig==
X-Gm-Message-State: ALoCoQnNKgDG0JJ7Y3hkmNNQCF9CL5ddopuPlwKzytr6stHs5ysaEhaVT99BLs1KG5egCARXdG2f
X-Received: by 10.180.24.137 with SMTP id u9mr5853059wif.5.1383401396173; Sat, 02 Nov 2013 07:09:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.152.137 with HTTP; Sat, 2 Nov 2013 07:09:16 -0700 (PDT)
X-Originating-IP: [74.95.2.168]
In-Reply-To: <CAGgHUiTpW=Na5F24zcQH0BjebhBepDvCSfmzUQRd+17LnbrLOw@mail.gmail.com>
References: <CAOqqYVEER_HprgauRawO+_gGdLdMY1MUY8jrMhhi3yVDL31bFg@mail.gmail.com> <52740478.6030109@nostrum.com> <CAOJ7v-2+_4QZwc8vEtdwVDWSP-d-z+ggB0u+VM6WnA=f-k4-XA@mail.gmail.com> <BLU404-EAS261C783EDA4575EE1A7E53593F40@phx.gbl> <CAGgHUiTpW=Na5F24zcQH0BjebhBepDvCSfmzUQRd+17LnbrLOw@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 02 Nov 2013 07:09:16 -0700
Message-ID: <CABcZeBOZyWusoAa5Z89G13z40giwGN_dvX8FDJjAPM5XtVJ0zw@mail.gmail.com>
To: Leon Geyser <lgeyser@gmail.com>
Content-Type: multipart/alternative; boundary="f46d04447f67cd027604ea323cff"
Cc: Harald Alvestrand <hta@google.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Congratuiations on the Cisco announcement - but we still prefer VP8
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: Sat, 02 Nov 2013 14:10:03 -0000

On Sat, Nov 2, 2013 at 4:56 AM, Leon Geyser <lgeyser@gmail.com> wrote:

> Like Firefox and Opera...and the browser I might create in the future? :)
> Firefox only has decoding support on some platforms, because it uses the
> operating system's H.264 decoder if it has one so far as I know.
>

I anticipate that Firefox will use HW codecs on phones. We haven't
determined what we will do on operating systems with good H.264
codecs built in to the platform.

-Ekr

On 2 November 2013 13:31, Bernard Aboba <bernard_aboba@hotmail.com> wrote:
>
>> Not sure I understand this completely. Isn't support for "the Rube
>> Goldberg Machine" needed only on platforms that do not natively support
>> H.264?
>>
>> On Nov 1, 2013, at 1:14 PM, "Justin Uberti" <juberti@google.com> wrote:
>>
>> I also want to reiterate that having a MTI codec means Mandatory To
>> Implement.
>>
>> That means, that should we decide to go down the H.264 path, Firefox and
>> others will be forced to support this Rube Goldberg machine for obtaining
>> H.264 for an indeterminate amount of time, long after WebRTC has moved on
>> to prefer other codecs.
>>
>>
>> On Fri, Nov 1, 2013 at 12:43 PM, Adam Roach <adam@nostrum.com> wrote:
>>
>>>  On 10/31/13 13:47, Harald Alvestrand wrote:
>>>
>>>  We congratulate Cisco on their intention to make an open source H.264
>>> codec available and usable by the community. We look forward to seeing the
>>> result of this effort.
>>>
>>>  Google still believes that VP8 - a freely available, fully open,
>>> high-quality video codec that you can download, compile for your platform,
>>> include in your binary, distribute and put into production today - is the
>>> best choice of a Mandatory to Implement video codec for the WebRTC effort.
>>>
>>>
>>> I agree with Harald that VP8 is a better codec than H.264 baseline in a
>>> number of important ways.
>>>
>>> But I also want to reiterate that having an MTI codec has never been
>>> about choosing the best codec or even a good codec. It's about choosing an
>>> emergency backup codec-of-last-resort. It's about having one single
>>> mandated codec that everyone has in their back pocket in case nothing else
>>> works.
>>>
>>> The core of RTCWEB is about session *negotiation*. Endpoints will
>>> negotiate the best codec they have in common. Once the next generation of
>>> codecs come out, this "best codec in common" will only be the MTI if they
>>> were about to fail anyway.
>>>
>>> So it doesn't have to be good.
>>>
>>> It just has to be better than failure.
>>>
>>> /a
>>>
>>> _______________________________________________
>>> rtcweb mailing list
>>> rtcweb@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtcweb
>>>
>>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
>>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>