Re: [rtcweb] Platforms that support H264

Kaiduan Xie <kaiduanx@gmail.com> Sat, 02 November 2013 23:41 UTC

Return-Path: <kaiduanx@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 140F311E8143 for <rtcweb@ietfa.amsl.com>; Sat, 2 Nov 2013 16:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.933
X-Spam-Level:
X-Spam-Status: No, score=-0.933 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_HTML_USL_OBFU=1.666]
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 2pNSk9mnoe-5 for <rtcweb@ietfa.amsl.com>; Sat, 2 Nov 2013 16:41:39 -0700 (PDT)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id B625711E8260 for <rtcweb@ietf.org>; Sat, 2 Nov 2013 16:41:36 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id w61so807525wes.38 for <rtcweb@ietf.org>; Sat, 02 Nov 2013 16:41:35 -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=ztcDaReOdKMibvM9O2Iz390NgUUfPvksXL8bGKvCXoM=; b=0mywfWdg07ZS2IkuyNKmGNOVAwH2U6DBpR4BEQLRav8F2ih2CJ7/4/tOq8CU5fWgPH vAoqzt9clkuFVOCf5S3y/vMAYqWnL9jVlkDcbnXclaf9Y7CN50Sxxat2VYgv82C8pkhe FzLcE6qjzZs65VmEcjhteuduavkLm1vHRuIe2jVkZ/dAItJXWXfK420uV/aN0bIqSQ8G hg1uDfGBatzDN8kobLUwLHxRxQT4wh6j07jlYGoRe1sHBPzlQ9FsHGGLwjxQjMoRxD0V oGyz08gtZo+H0GnBr/XvnlrzO60fat01Ab2knBpk6SjORjC6rRxhzZrCH5E/77Ij+n8d zI/w==
MIME-Version: 1.0
X-Received: by 10.180.90.116 with SMTP id bv20mr6895502wib.50.1383435695834; Sat, 02 Nov 2013 16:41:35 -0700 (PDT)
Received: by 10.216.183.202 with HTTP; Sat, 2 Nov 2013 16:41:35 -0700 (PDT)
In-Reply-To: <CABcZeBNka8AO7EOGfHKDqNSrOAzDVRK5ywpPc=1OXAK17n+Jhw@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> <52755A0E.4020007@bbs.darktech.org> <CABcZeBNka8AO7EOGfHKDqNSrOAzDVRK5ywpPc=1OXAK17n+Jhw@mail.gmail.com>
Date: Sat, 2 Nov 2013 19:41:35 -0400
Message-ID: <CACKRbQceMN7Qvqr-zEnJ8TgU-Ti0HKmf-V+MimTH3oAune2mwA@mail.gmail.com>
From: Kaiduan Xie <kaiduanx@gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Content-Type: multipart/alternative; boundary=f46d043c7f4e384d5504ea3a3963
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] 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: Sat, 02 Nov 2013 23:41:40 -0000

Every BlackBerry 10 phone has H.264 hardware encoder/decoder.

/Kaiduan


On Sat, Nov 2, 2013 at 6:18 PM, Eric Rescorla <ekr@rtfm.com> wrote:

>
>
>
> On Sat, Nov 2, 2013 at 1:01 PM, Gili <cowwoc@bbs.darktech.org> wrote:
>
>> Martin,
>>
>>     I fully understand why Firefox would be happy but as someone who plan
>> to integrate WebRTC into a non-browser application, especially on iOS,
>> Cisco's solution simply does not work. I appreciate their contribution, but
>> again, it simply doesn't help my use-case.
>>
>
> I haven't seen  you explain how your use case is different from that of
> a browser. Could you please do so?
>
> -Ekr
>
>
>> Gili
>>
>>
>> On 11/2/2013 11:02 AM, Martin Thomson wrote:
>>
>>> On 2 November 2013 07:37, cowwoc <cowwoc@bbs.darktech.org> wrote:
>>>
>>>>      I can't think of a single platform that supports real-time H.264
>>>> encoding/decoding natively today.
>>>>
>>> That's a very strange way to put the question.
>>>
>>> Let me put another spin on it, and please excuse the example...
>>>
>>> Skype runs on more platforms than you might think.  Those platforms
>>> can all support H.264 to the extent that Skype requires.
>>>
>>> Cisco's generous offer opens almost the same capability to anyone,
>>> with the caveat that some platforms currently remain closed.  Of
>>> course, you could let your ideals get in the way of progress.  Me, I'm
>>> a pragmatist.  This gift represents a great opportunity for people who
>>> actually care about the practical outcomes.
>>>
>>> There's been a lot of mouth-gazing of gift horses on this list of
>>> late.  I sure hope that this isn't representative of the real
>>> sentiment of the community.  I'd like to think that people are better
>>> than that.
>>>
>>> (BTW, I understand and respect Harald's position.  From where he sits,
>>> I'm sure that his conclusion makes perfect sense.)
>>>
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>