Re: [rtcweb] Platforms that support H264 (was: Congratuiations on the Cisco announcement - but we still prefer VP8)

Eric Rescorla <ekr@rtfm.com> Sat, 02 November 2013 22:43 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 566D621E8114 for <rtcweb@ietfa.amsl.com>; Sat, 2 Nov 2013 15:43:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level:
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[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 tq9CJ+-9YXJt for <rtcweb@ietfa.amsl.com>; Sat, 2 Nov 2013 15:43:52 -0700 (PDT)
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by ietfa.amsl.com (Postfix) with ESMTP id E5AEC21E80B8 for <rtcweb@ietf.org>; Sat, 2 Nov 2013 15:43:51 -0700 (PDT)
Received: by mail-wi0-f179.google.com with SMTP id hm4so2402840wib.0 for <rtcweb@ietf.org>; Sat, 02 Nov 2013 15:43:51 -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=HyLFfL/pDZhms3Y64tjinF0WdfpyHduVYRWbFyXEXnA=; b=R/kCNsXPAHYXbNpmpXmMabR1L7YW6fdho78V5g8nKMrrMYaqDxU5UVyGjoOlYO5FmC SvwkT2v7OXyCLfLP2GaHSb3wV0YuZSRT99LLjnMRixDKRr8rtRTvj9t1mmf6lmZSfyWM WBEoJu2TK76EnKqZBojvU4suFpN1IzqwI7OZAjBABMEJO9z1PAC+sXabnYK9xGXmst6f 3R0kKTdcxtHz61MNzTFxvtVK2lm7d921spkyZcCRFhuc9cEIfGXTmAKs307WFMS1TErL J+UkVgRHBVMMaPDYzAYzBz0oE42a0aYwbyIk5GDTMFzfmN3kNDDpVTIeYDZrfp5r8c6P njdA==
X-Gm-Message-State: ALoCoQm8Fz6056oOLjYFuHUPgiwmhn7dg/WvHW3FO7y7Uqr1ijgMyqM2rt6aCGWAVyZSfQi0bvmE
X-Received: by 10.194.58.104 with SMTP id p8mr7199129wjq.1.1383432231051; Sat, 02 Nov 2013 15:43:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.152.137 with HTTP; Sat, 2 Nov 2013 15:43:09 -0700 (PDT)
X-Originating-IP: [2001:67c:370:176:a427:d50c:2c74:28c4]
In-Reply-To: <CAPvvaa+eDRkDk5XNDh2QcgLy4wDjrNeCmGJvqac_z+F4r_ev5Q@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> <52750E3C.9060206@bbs.darktech.org> <CABkgnnVR9=oWVzRaRuD701tvZCtp+SO1n6c65hJELLVfB8QcOA@mail.gmail.com> <C21C6AC2-29F8-4DFF-BB48-5E3D625DCD65@phonefromhere.com> <CAPvvaaK-bKt-zDEq2qibRrm51VbRGAV=95JShKFdCpJszw5Tww@mail.gmail.com> <CABcZeBMG1ApkN7u_uyO_9H9se22ixLhaYc6pZsncvc6d+k8rEQ@mail.gmail.com> <CAPvvaa+eDRkDk5XNDh2QcgLy4wDjrNeCmGJvqac_z+F4r_ev5Q@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 02 Nov 2013 15:43:09 -0700
Message-ID: <CABcZeBOnHGdRCUK2k5ys5n7fs6rYSd+RzMjy13X2J0o2eP2sjA@mail.gmail.com>
To: Emil Ivov <emcho@jitsi.org>
Content-Type: multipart/alternative; boundary="047d7ba97804b4004e04ea396a26"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Platforms that support H264 (was: 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 22:43:57 -0000

On Sat, Nov 2, 2013 at 3:28 PM, Emil Ivov <emcho@jitsi.org> wrote:

> I'd encourage you to read back.
>
> This part of the thread started with the claim that most of the time it
> won't come to downloading Cisco's binary because there is already
> widespread OS support for H.264 encoding on all OSes
>

I assume you're referring to Bernard's comment? If so, I don't think that's
actually
what he said.

In any case, speaking as someone who actually has to deal with this, it's
more
work to maintain more code paths. Thus, I anticipate using Cisco's binary on
all desktop platforms and only using platform codecs where it offers a
significant
performance advantage, e.g., on mobile.

On a related note: it's a mistake to assume that just because there aren't
currently good interfaces to the existing H.264 encoding hardware that those
interfaces will never exist. For instance, the iPhone clearly has real-time
capable encoding hardware, and Apple certainly could make it available
if they wanted. That's a much simpler proposition than adding hardware
where none exists.

-Ekr