IETF Logo Mail Archive

Re: [rtcweb] Discussion on codec choices from a developer who doesn't come to IETF

Ted Hardie <ted.ietf@gmail.com> Tue, 08 May 2012 21:40 UTC

Return-Path: <ted.ietf@gmail.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 D794E11E8074 for <rtcweb@ietfa.amsl.com>; Tue, 8 May 2012 14:40:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.594
X-Spam-Level:
X-Spam-Status: No, score=-3.594 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 t91H5UqPYLxF for <rtcweb@ietfa.amsl.com>; Tue, 8 May 2012 14:40:49 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4FBBF11E8072 for <rtcweb@ietf.org>; Tue, 8 May 2012 14:40:49 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so2077990vbb.31 for <rtcweb@ietf.org>; Tue, 08 May 2012 14:40:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=loL5oHA7L3E8qexU76ASenO7lNpsTAJnE+VMhhVPQPU=; b=F71MMOA7iEtRN42Cs9mC/Il/pN8cMxuUXb0edPo5eSjuXY5HdytJNDuKyPf18i8EiH 4TGMVrVTETuiorWp+l1PpVQz32sB7SfpJlDFnRnoUBkMkDHTv76zqAYue0SMbvXpFsKT VYOyJLxh8OPisA2DEEDBnf7/FFDs4HJOs9EXoGzzbObnSLCsLujeDgMx0hUbEinX/tZx ssx3Mhms22TA37IgJMNeVBw754RxxosolDgTKRkLehvEY7TMaaMFUgxR4+4sawuyUo64 UebpZXpyoUogel7VNhQL4rWFczJgxwUuM6ZVjlywNKT/sisd+Tf0GXoq2IAuGhRN12Jk 4PGQ==
MIME-Version: 1.0
Received: by 10.52.69.38 with SMTP id b6mr3554188vdu.22.1336513245103; Tue, 08 May 2012 14:40:45 -0700 (PDT)
Received: by 10.52.162.99 with HTTP; Tue, 8 May 2012 14:40:45 -0700 (PDT)
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE23305F970@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <5B26F813B14D224999A508377061EDBBB1215C@EX2K10MB1.vb.loc> <A9FB11DB-8617-4ED6-BDB4-689FD5E7C0C7@softarmor.com> <20120504104446.2d7b2715@lminiero-acer> <CAOHm=4scg-+QnU2g_Tbmc1c615rrRO=oiUCAQ3nL4JORU+3Zmg@mail.gmail.com> <4FA3E48E.1050204@freedesktop.org> <BLU169-W20EE1AD0881F6C8F48B31932C0@phx.gbl> <CAOJ7v-0=MxAYGjxEyRcizfNYMnDJw6XiHoVuCzmnznFUy2YncA@mail.gmail.com> <4FA94E5E.4000102@mozilla.com> <EDC0A1AE77C57744B664A310A0B23AE23305F970@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Date: Tue, 08 May 2012 14:40:45 -0700
Message-ID: <CA+9kkMCUsk651aJ==GK9Cd6Bk4pRGFqxor_fOqJaHWVN5Uu-ZA@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Discussion on codec choices from a developer who doesn't come to IETF
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: Tue, 08 May 2012 21:40:50 -0000

On Tue, May 8, 2012 at 11:35 AM, DRAGE, Keith (Keith)
<keith.drage@alcatel-lucent.com> wrote:
> Most mobile devices (at least those on 3GPP standards) trying to do anything other than RTCWEB with their screens and cameras will need to support H.264 anyway.
>

My faulty memory is that the availability of hardware acceleration for
certain audio codecs used to be restricted and that VoIP clients on
3GPP devices had no access to them.  Is that situation cleared up?
Can any installed application now access hardware accelerated codec
support?

regards,

Ted

v2.14.0 | Report a Bug | By Email