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

David Singer <singer@apple.com> Tue, 09 December 2014 20:29 UTC

Return-Path: <singer@apple.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 2DF891A00BF for <rtcweb@ietfa.amsl.com>; Tue, 9 Dec 2014 12:29:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 w0VkYdSAkR9s for <rtcweb@ietfa.amsl.com>; Tue, 9 Dec 2014 12:29:48 -0800 (PST)
Received: from mail-in2.apple.com (mail-out2.apple.com [17.151.62.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61DD51A0011 for <rtcweb@ietf.org>; Tue, 9 Dec 2014 12:29:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1418156988; x=2282070588; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-transfer-encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=bFyY9vecEEazvezJ+v2oOtdoJbdBm5JycFtl+dvXIr4=; b=tuW+Vyhoh+V05cMu9/oyAjQAvYdt++gBWZYu7qkKkbJpRrv/MP2DKJDZ0ZYTQl96 6DFfWY3GPwzYqSwdaevq5khTwx9yjwb6i9LJMK66zVOVRZylEbzIAUnxOVBRBjZB d1mW5gXgtYr0UjKtzfEiZiKwFXsb4PGQWCH2GgCIwc66gTBWPiCOwIs9moSQ9oAR J1ZYxwZclg08a6f/5QnF13rMh9DEgVooHaxpCA1xPdEvtalPycx7RUfuQHNV+e/S 6Bx8nJMytIuLQR6i7ir/RoS23dx0uDcJ1F/TkeLfg2vgTEluCYWUWLDIF0wFKRHZ uE6fvmUvs+WOXgXzzEnNtg==;
Received: from relay8.apple.com (relay8.apple.com [17.128.113.102]) by mail-in2.apple.com (Apple Secure Mail Relay) with SMTP id 76.14.26546.CBB57845; Tue, 9 Dec 2014 12:29:48 -0800 (PST)
X-AuditID: 11973e11-f79af6d0000067b2-38-54875bbc60f1
Received: from chive.apple.com (chive.apple.com [17.128.115.15]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by relay8.apple.com (Apple SCV relay) with SMTP id EE.84.05452.FBB57845; Tue, 9 Dec 2014 12:29:51 -0800 (PST)
Received: from [17.153.29.83] (unknown [17.153.29.83]) by chive.apple.com (Oracle Communications Messaging Server 7.0.5.30.0 64bit (built Oct 22 2013)) with ESMTPSA id <0NGC00KAT0XN2990@chive.apple.com> for rtcweb@ietf.org; Tue, 09 Dec 2014 12:29:47 -0800 (PST)
Content-type: text/plain; charset=utf-8
MIME-version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: David Singer <singer@apple.com>
In-reply-to: <9BDCD7D8-B274-4970-A01B-D31069AEA935@phonefromhere.com>
Date: Tue, 09 Dec 2014 12:29:46 -0800
Content-transfer-encoding: quoted-printable
Message-id: <D3321473-D2F4-407F-96FB-BE58F38683A2@apple.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> <9BDCD7D8-B274-4970-A01B-D31069AEA935@phonefromhere.com>
To: Tim Panton <tim@phonefromhere.com>
X-Mailer: Apple Mail (2.1993)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrALMWRmVeSWpSXmKPExsUi2FCYprsnuj3E4GwDi8Xaf+3sDoweS5b8 ZApgjOKySUnNySxLLdK3S+DKaJu6nq2gmadi+dojLA2MFzi7GDk5JARMJHbcXM8IYYtJXLi3 nq2LkYtDSGAfo0TDihVMMEXT925mhEh0M0n837qSHc5ZefkscxcjBwezgLrElCm5IA28AnoS TU8egzULC5hLbOw6wgxiswmoSjyYcwxsG6eAq8SnKRfBbBag+Ib7J9khxrhJfN3HDxJmFtCW ePLuAivESBuJG9t2sUKsvcYk0XX+FAtIQkRATeLcj8PMEIfKSvy7eIYdwn7LKvFpjecERuFZ CNfNQnLdLCQrFjAyr2IUyk3MzNHNzDPSSywoyEnVS87P3cQICuLpdoI7GI+vsjrEKMDBqMTD q2HZFiLEmlhWXJl7iFGag0VJnPeGDVBIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QD4xZHt6ct aanOq3qLOiebiFvFv4pkMQu9vjMoM+JjJ69K4KVoHkMGUc7ly9f+NxKTipyzLOfR2m+zU09M VzXZesnWKE+xb6WiGeePa/e7HqvsmP/hFK/B8Q1vrH5f+/LuVHmjvSCTpHa33i4b9syX0wJO Bfyu4Xu54N/0F7oLOkzTMh3uiS0JVWIpzkg01GIuKk4EAJOr4MVDAgAA
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUi2FDMr7s/uj3E4Ps3Xou1/9rZHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CV0TZ1PVtBM0/F8rVHWBoYL3B2MXJySAiYSEzfu5kRwhaTuHBv PVsXIxeHkEA3k8T/rSvZ4ZyVl88ydzFycDALqEtMmZIL0sAroCfR9OQxE4gtLGAusbHrCDOI zSagKvFgzjGwoZwCrhKfplwEs1mA4hvun2SHGOMm8XUfP0iYWUBb4sm7C6wQI20kbmzbxQqx 9hqTRNf5UywgCREBNYlzPw4zQxwqK/Hv4hn2CYwCsxAumoXkollIxi5gZF7FKFCUmpNYaaGX WFCQk6qXnJ+7iREcdoVpOxibllsdYhTgYFTi4dWwbAsRYk0sK67MPcQowcGsJMK7lqU9RIg3 JbGyKrUoP76oNCe1+BCjNAeLkjhv2bvGECGB9MSS1OzU1ILUIpgsEwenFDCAV/DKfGJYMun5 xmA2ww0eZX4/C/wXhO9nfD7DuHzqmQ0r26b27Gas6FVa5r2GQf/Iikq73THVClnOfnrz8lkX u1tP96h1ON8wMUH91pTC45O/r05h7durx78x4unsRf2vHZp2x1zUDrR6ZDDXlEc2uun5wied 2+bOi9iV8McgxHLZrbwNx0OVWIozEg21mIuKEwEEOvdHNwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/K1OUz9ITItk_Fpp_FCwl_dfxsiU
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 20:29:50 -0000

> On Dec 9, 2014, at 11:50 , Tim Panton <tim@phonefromhere.com> wrote:
> 
> 
>> On 9 Dec 2014, at 19:31, David Singer <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?’


Only slightly.  An earlier suggestion on this thread was that one could be conformant with the WebRTC specs if one simply claimed that one was building a webrtc-compatible endpoint;  even if the implementation was of webrtc, in a browser, it would not be labeled as “WebRTC Browser”.

That, to me, is sleight of hand;  a neat trick, but not quite what we want to have happen.  I’d rather not suggest it to anyone.

David Singer
Manager, Software Standards, Apple Inc.