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

David Singer <singer@apple.com> Tue, 09 December 2014 19:35 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 58A691A87C3 for <rtcweb@ietfa.amsl.com>; Tue, 9 Dec 2014 11:35:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.101
X-Spam-Level:
X-Spam-Status: No, score=-4.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, 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 tEoxWuT_e-lP for <rtcweb@ietfa.amsl.com>; Tue, 9 Dec 2014 11:35:07 -0800 (PST)
Received: from mail-in4.apple.com (mail-out4.apple.com [17.151.62.26]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 351FB1A0075 for <rtcweb@ietf.org>; Tue, 9 Dec 2014 11:35:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1418153706; x=2282067306; 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=BTM9IFRBbH3iyEvhhldAEkEvlsEOsEd6CRitgrEMSVo=; b=C/4WaO4ALY4MHHD9pjQXjImGaUMzPVqEZshj002GANxWwecBDjZjErpDhsG/2WtF 3A68a9q/0xMNST325Mz5BngtzrxYaTuhHYitwrzXlibZMjGOoOdpZPofClNRNHLd 8c00vjbj29mgnMCzqKAFQ12H+/vrwq8HzHqxIj9Cv2OSgo7yDrEKj86ieJFdfeV0 +CNhmJNqgPsWxVmDpu5JZQ6sUB5Bt208bQl/3xspQCvZ35UFITTJwLCZJEQdpKXj Bj1BPhAkLxah2biIKap2dwqzC4rWRubvzbSNy4fh6jVbO00ZXqDClO5Ozlhjevz0 0m5XUarI/EMT94CdcwXRPA==;
Received: from relay2.apple.com (relay2.apple.com [17.128.113.67]) by mail-in4.apple.com (Apple Secure Mail Relay) with SMTP id FD.DF.12074.AEE47845; Tue, 9 Dec 2014 11:35:06 -0800 (PST)
X-AuditID: 11973e12-f79f86d000002f2a-17-54874eea4758
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 relay2.apple.com (Apple SCV relay) with SMTP id 07.61.05858.4EE47845; Tue, 9 Dec 2014 11:35:00 -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 <0NGB00K00YEF2970@chive.apple.com> for rtcweb@ietf.org; Tue, 09 Dec 2014 11:35:05 -0800 (PST)
Content-type: text/plain; charset=us-ascii
MIME-version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: David Singer <singer@apple.com>
In-reply-to: <CA+E6M0mfHomZByk0h1Fdxis3Q+Z0cOPve+qWqq_BVOtq9qB6sg@mail.gmail.com>
Date: Tue, 09 Dec 2014 11:35:05 -0800
Content-transfer-encoding: quoted-printable
Message-id: <D18AB097-8C30-40BC-83DF-D2249D615CF4@apple.com>
References: <5486C48D.8040602@alvestrand.no> <F092E8C6-380C-4B20-B71F-449162617BC5@apple.com> <CA+E6M0mfHomZByk0h1Fdxis3Q+Z0cOPve+qWqq_BVOtq9qB6sg@mail.gmail.com>
To: Mohammed Raad <mohammedsraad@raadtech.com>
X-Mailer: Apple Mail (2.1993)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMLMWRmVeSWpSXmKPExsUi2FDorPvKrz3E4PIjM4u1/9rZHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVcbWtm6lgLXvFtQ+LGRsYX7B2MXJySAiYSPQdPsAOYYtJXLi3 nq2LkYtDSGAvo8S/9XfYYIp6Nk1ggkh0M0lsXrwZwbn4eitYFbOAlsT6nceZQGxeAT2JpieP wWxhAXOJjV1HmEFsNgFViQdzjjGC2JwCwRLHt14Es1mA4g0HHrBAzLGV2HPrK9RMbYkn7y6w Qsy0kdj28C+YLSSwjFHi95Q8EFsEaNfVt9uhLpWV+HfxDDvIcRICT1klJvRcYJnAKDwLyX2z kNw3C8mOBYzMqxiFchMzc3Qz80z0EgsKclL1kvNzNzGCQnm6ndAOxlOrrA4xCnAwKvHwali2 hQixJpYVV+YeYpTmYFES571pAxQSSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXAOKHs6I2wn74H D3s77p/AU6jsK8K9TjL+/5WyoJ0CW068XKE0362mXXTrNZM5h31/+n07tElu64ZyMSPRbK+p 9e3T5wsG1G8qPyfGsdE0QHwqh1kxQ0+3+isjp+Swkg2bH7M9WP9fou/h/TJm0Wcnmx7kM6Wl BvP+tfzSGquXpSlx6+3y4+u8lFiKMxINtZiLihMBgmHyDEYCAAA=
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGLMWRmVeSWpSXmKPExsUi2FDMr/vErz3EYMdGeYu1/9rZHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVcbWtm6lgLXvFtQ+LGRsYX7B2MXJySAiYSPRsmsAEYYtJXLi3 nq2LkYtDSKCbSWLz4s1McM7F11vZQKqYBbQk1u88DtbBK6An0fTkMZgtLGAusbHrCDOIzSag KvFgzjFGEJtTIFji+NaLYDYLULzhwAMWiDm2EntufYWaqS3x5N0FVoiZNhLbHv4Fs4UEljFK /J6SB2KLAO26+nY7G8SlshL/Lp5hn8AoMAvJSbOQnDQLydgFjMyrGAWKUnMSK430EgsKclL1 kvNzNzGCQ6/QeQfjsWVWhxgFOBiVeHg1LNtChFgTy4orcw8xSnAwK4nwrmVpDxHiTUmsrEot yo8vKs1JLT7EKM3BoiTOm/OuMURIID2xJDU7NbUgtQgmy8TBKdXAaPhQfd8W4/Jvi/+fr5y5 Vf4ff8VFt2bef2k6LzpY5i/648QR9/joDl4/k4v5NyOUwi+9k8vmFlt0e3ntPi4FtbTnBp/a qngYK5LYbd13Wl3dNf/ggqcKxd0h2yd58V+bF7bcI/dSmsUdifmqWhdEJsl754hL+tfFHdl2 OnmFNmtSP1ez/eI/SizFGYmGWsxFxYkAUFzqazkCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/eiVh81P3nRneegPZohK6njoJpWA
Cc: 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:35:08 -0000

> On Dec 9, 2014, at 11:31 , Mohammed Raad <mohammedsraad@raadtech.com> wrote:
> 
> You know, that's a very strange path to take. I mean it really does sound like attempting to come to an agreement regarding what features future products should have by limiting participation in this technical decision process to those committed to deploy specific technologies. I think you ought to read the definition of anti competitive practice again.

Please be respectful of your language.

I am trying to find out a simple answer:  how many endpoints would, in fact, expect to support both codecs?


I am not trying to limit participation.  I am trying to find out whether we would actually get the purported effect.

If all the people humming yes make webrtc-compatible endpoints, we do not get the effect we want.  Is it that hard to see that?



David Singer
Manager, Software Standards, Apple Inc.