Re: [rtcweb] API standardization on phones? (Re: Platforms that support H264)

Randell Jesup <randell-ietf@jesup.org> Mon, 04 November 2013 04:44 UTC

Return-Path: <randell-ietf@jesup.org>
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 CC2F321F9BC1 for <rtcweb@ietfa.amsl.com>; Sun, 3 Nov 2013 20:44:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 jYnJb1U5nL5P for <rtcweb@ietfa.amsl.com>; Sun, 3 Nov 2013 20:44:34 -0800 (PST)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id 7198711E818A for <rtcweb@ietf.org>; Sun, 3 Nov 2013 20:44:31 -0800 (PST)
Received: from [64.114.24.114] (port=51008 helo=[142.131.18.239]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <randell-ietf@jesup.org>) id 1VdC1e-000Gxu-Vg for rtcweb@ietf.org; Sun, 03 Nov 2013 22:44:31 -0600
Message-ID: <5277262E.3050600@jesup.org>
Date: Sun, 03 Nov 2013 20:44:30 -0800
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:25.0) Gecko/20100101 Thunderbird/25.0
MIME-Version: 1.0
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="------------080009010509060703020004"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - r2-chicago.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jesup.org
X-Get-Message-Sender-Via: r2-chicago.webserversystems.com: authenticated_id: randell@jesup.org
Subject: Re: [rtcweb] API standardization on phones? (Re: Platforms that support H264)
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: Mon, 04 Nov 2013 04:44:39 -0000

On 11/3/2013 12:34 PM, DRAGE, Keith (Keith) wrote:
> The only stuff I am aware of is done by
> http://www.khronos.org/
> But that is as far as my knowledge goes.

My understanding from someone at Skype who worked with OMX stuff was 
that it was horribly poorly compatible because most people never ran any 
of the test suites that Kronos charges for.  Take with a huge grain of 
salt as this is second-hand and wasn't the primary topic.

> It would certainly be desireable that there is an standardised API 
> that everyone uses to get access to embedded hardware codec support.

Always a good thing, if it's done well.

> Keith
>
>     ------------------------------------------------------------------------
>     *From:* rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org]
>     *On Behalf Of *Harald Alvestrand
>     *Sent:* 03 November 2013 18:10
>     *To:* rtcweb@ietf.org
>     *Subject:* [rtcweb] API standardization on phones? (Re: Platforms
>     that support H264)
>
>     On 11/03/2013 06:52 PM, DRAGE, Keith (Keith) wrote:
>>     And this is where it would be useful to see some work done,
>>     although probably not by IETF.
>>     There a a few bits of API work out there, but nowhere do we see
>>     much push for adoption. As fae as I see there is no political
>>     reason why they should not be adopted, or even a fresh effort
>>     adopted to create some new ones. The only thing seems to be lack
>>     of impetus.
>
>     What's the industry state on standardization of APIs for phones?
>
>     Most of what I see seems to be platform specific, with some
>     exceptions (OpenGL / WebGL for graphics, OpenES for audio).
>
>     But it's not where I spend the most time looking; it would be good
>     to have someone who knows this space summarize 
>

-- 
Randell Jesup
randell-ietf@jesup.org