Re: [rtcweb] Platforms that support H264

"Mo Zanaty (mzanaty)" <mzanaty@cisco.com> Tue, 05 November 2013 02:52 UTC

Return-Path: <mzanaty@cisco.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 4782111E82CF for <rtcweb@ietfa.amsl.com>; Mon, 4 Nov 2013 18:52:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.765
X-Spam-Level:
X-Spam-Status: No, score=-9.765 tagged_above=-999 required=5 tests=[AWL=-0.833, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 H9Ez8PSt8AqU for <rtcweb@ietfa.amsl.com>; Mon, 4 Nov 2013 18:52:41 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 949C511E8317 for <rtcweb@ietf.org>; Mon, 4 Nov 2013 18:52:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7341; q=dns/txt; s=iport; t=1383619954; x=1384829554; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=ru2D5m2dpKVulo2TXCeXid48Xk77cVVqZD5wmhA4G9Q=; b=jITXCxUdAQADkqP7HpQt0YtY2H2IA5MPsKzVI4Eog3ICtGkkIa5fHfA9 GRPfclejz8Sd3zrdlUIvwBAJVWThUCljp6FgczFoHOsLP7XDcZzeGzxKM pyVKzm0vVW2G8OhGMHm4QdHJA/QLXP2eWn8Qvqji4P3+26HMOA2ZCLAkB M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkYFACpdeFKtJV2c/2dsb2JhbABZgkNEOFO+cEuBKBZ0gicBBAEBAWsLEgEIPygGCxQRAgQBDQUUB4dUAw8NtDwNiWcEjFuCbAQHhC4Dlh+Ba4xShTeBO4Frgio
X-IronPort-AV: E=Sophos; i="4.93,637,1378857600"; d="scan'208,217"; a="280661073"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-7.cisco.com with ESMTP; 05 Nov 2013 02:52:34 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id rA52qYJf025470 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Nov 2013 02:52:34 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.50]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0123.003; Mon, 4 Nov 2013 20:52:33 -0600
From: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
To: Kaiduan Xie <kaiduanx@gmail.com>, Eric Rescorla <ekr@rtfm.com>
Thread-Topic: [rtcweb] Platforms that support H264
Thread-Index: AQHO2dIT0OsOgTLqXE2Wnbsc3UuMdA==
Date: Tue, 5 Nov 2013 02:52:33 +0000
Message-ID: <CE9DC5C8.1B814%mzanaty@cisco.com>
In-Reply-To: <CACKRbQceMN7Qvqr-zEnJ8TgU-Ti0HKmf-V+MimTH3oAune2mwA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.8.130913
x-originating-ip: [10.82.248.160]
Content-Type: multipart/alternative; boundary="_000_CE9DC5C81B814mzanatyciscocom_"
MIME-Version: 1.0
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: Tue, 05 Nov 2013 02:52:46 -0000

I think you meant *every* phone, tablet, laptop, desktop, set-top, camera…


On 11/2/13, 7:41 PM, Kaiduan Xie <kaiduanx@gmail.com<mailto:kaiduanx@gmail.com>> wrote:

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<mailto:ekr@rtfm.com>> wrote:



On Sat, Nov 2, 2013 at 1:01 PM, Gili <cowwoc@bbs.darktech.org<mailto: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<mailto: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<mailto:rtcweb@ietf.org>
https://www.ietf.org/mailman/listinfo/rtcweb


_______________________________________________
rtcweb mailing list
rtcweb@ietf.org<mailto:rtcweb@ietf.org>
https://www.ietf.org/mailman/listinfo/rtcweb