IETF Logo Mail Archive

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

Harald Alvestrand <harald@alvestrand.no> Sun, 03 November 2013 18:10 UTC

Return-Path: <harald@alvestrand.no>
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 99E2A21E80FF for <rtcweb@ietfa.amsl.com>; Sun, 3 Nov 2013 10:10:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level:
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 xTGXmHPxaL+I for <rtcweb@ietfa.amsl.com>; Sun, 3 Nov 2013 10:10:24 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 5DA7021E80F5 for <rtcweb@ietf.org>; Sun, 3 Nov 2013 10:10:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 7214939E176 for <rtcweb@ietf.org>; Sun, 3 Nov 2013 19:10:23 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hk3+RMDKQnGi for <rtcweb@ietf.org>; Sun, 3 Nov 2013 19:10:22 +0100 (CET)
Received: from [172.19.244.5] (unknown [216.239.45.130]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 68D4239E091 for <rtcweb@ietf.org>; Sun, 3 Nov 2013 19:10:22 +0100 (CET)
Message-ID: <5276918B.4040207@alvestrand.no>
Date: Sun, 03 Nov 2013 19:10:19 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: rtcweb@ietf.org
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>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0C6D75@FR712WXCHMBA11.zeu.alcatel-lucent.com>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/alternative; boundary="------------020800050505030801020808"
Subject: [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 18:10:30 -0000

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.23.0 | Report a Bug | By Email