IETF Logo Mail Archive

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

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Sun, 03 November 2013 20:35 UTC

Return-Path: <keith.drage@alcatel-lucent.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 4ACD011E8143 for <rtcweb@ietfa.amsl.com>; Sun, 3 Nov 2013 12:35:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.505
X-Spam-Level:
X-Spam-Status: No, score=-110.505 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 JZI-RP1l-upi for <rtcweb@ietfa.amsl.com>; Sun, 3 Nov 2013 12:35:04 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 31B3C11E8123 for <rtcweb@ietf.org>; Sun, 3 Nov 2013 12:35:04 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id rA3KYwDC003904 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 3 Nov 2013 14:34:59 -0600 (CST)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id rA3KYvwR025431 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 3 Nov 2013 21:34:57 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.239]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Sun, 3 Nov 2013 21:34:57 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Harald Alvestrand <harald@alvestrand.no>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] API standardization on phones? (Re: Platforms that support H264)
Thread-Index: AQHO2MAAeqJEr6VKRUS16n0ERsAx65oT9j1Q
Date: Sun, 03 Nov 2013 20:34:56 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B0C6F9D@FR712WXCHMBA11.zeu.alcatel-lucent.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> <CABcZeBOnHGdRCUK2k5ys5n7fs6rYSd+RzMjy13X2J0o2eP2sjA@mail.gmail.com> <A6085C80-87B7-45AD-8DA4-8D52EBD1096A@phonefromhere.com> <949EF20990823C4C85C18D59AA11AD8B0C6D75@FR712WXCHMBA11.zeu.alcatel-lucent.com> <5276918B.4040207@alvestrand.no>
In-Reply-To: <5276918B.4040207@alvestrand.no>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: multipart/alternative; boundary="_000_949EF20990823C4C85C18D59AA11AD8B0C6F9DFR712WXCHMBA11zeu_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
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: Sun, 03 Nov 2013 20:35:10 -0000

The only stuff I am aware of is done by

http://www.khronos.org/

But that is as far as my knowledge goes.

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

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.

v2.27.8 | Report a Bug | By Email | System Status