IETF Logo Mail Archive

Re: [rtcweb] Video codecs: Clear positions....

Tim Panton <tim@phonefromhere.com> Tue, 09 December 2014 19:50 UTC

Return-Path: <tim@phonefromhere.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96B171A036B for <rtcweb@ietfa.amsl.com>; Tue, 9 Dec 2014 11:50:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XuJUpIPTaQhc for <rtcweb@ietfa.amsl.com>; Tue, 9 Dec 2014 11:50:34 -0800 (PST)
Received: from smtp002.apm-internet.net (smtp002-out2.apm-internet.net [85.119.248.225]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D8E91A0248 for <rtcweb@ietf.org>; Tue, 9 Dec 2014 11:50:34 -0800 (PST)
Received: (qmail 70296 invoked from network); 9 Dec 2014 19:50:32 -0000
X-AV-Scan: clean
X-APM-Authkey: 83769 13846
Received: from unknown (HELO zimbra003.verygoodemail.com) (85.119.248.218) by smtp002.apm-internet.net with SMTP; 9 Dec 2014 19:50:32 -0000
Received: from zimbra003.verygoodemail.com (localhost [127.0.0.1]) by zimbra003.verygoodemail.com (Postfix) with ESMTP id CCFCE18A150B; Tue, 9 Dec 2014 19:50:26 +0000 (GMT)
Received: from limit.westhawk.co.uk (unknown [192.67.4.33]) by zimbra003.verygoodemail.com (Postfix) with ESMTPSA id AF24A18A0AC9; Tue, 9 Dec 2014 19:50:26 +0000 (GMT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_0B8A542D-D3E9-46B1-9991-EED40BBAE134"
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Tim Panton <tim@phonefromhere.com>
In-Reply-To: <AE151623-3747-4835-AF3E-2953F442E995@apple.com>
Date: Tue, 09 Dec 2014 19:50:25 +0000
Message-Id: <9BDCD7D8-B274-4970-A01B-D31069AEA935@phonefromhere.com>
References: <5486C48D.8040602@alvestrand.no> <F092E8C6-380C-4B20-B71F-449162617BC5@apple.com> <54873575.3030804@nostrum.com> <CAOW+2dskg9CQF9qw3oktcEGySdWJZCF6sXHXdgAnwc8ph1iVtw@mail.gmail.com> <54874B66.5050700@nostrum.com> <AE151623-3747-4835-AF3E-2953F442E995@apple.com>
To: David Singer <singer@apple.com>
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/SIWfk6AI2TbHm1it7Kt8Wmh8rYI
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Video codecs: Clear positions....
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Dec 2014 19:50:36 -0000

> On 9 Dec 2014, at 19:31, David Singer <singer@apple.com <mailto:singer@apple.com>> wrote:

> 
> That’s why I said that saying that a WebRTC implementation, in a browser, is not a WebRTC Browser but a WebRTC-Compatible Endpoint, though formally possible, is questionable — it would appear to be skirting the intent of the spec.

I’m deeply confused by that remark. To answer the question I think you are asking, (i.e. ’can you show me a non-browser webrtc compliant endpoint?'). The best example I can think of that is public is E/// ’s openwebRTC - which implements both codecs, but doesn’t implement a browser or the w3C javascript API. - Note that they leave the issue of h264 licence fees to the app developer to sort out (although they plan to let it use native os exposed codecs and ride that license I think)

Or did I misunderstand?

Tim.

v2.23.0 | Report a Bug | By Email