Re: [rtcweb] Video codec selection - way forward

David Singer <singer@apple.com> Fri, 15 November 2013 02:26 UTC

Return-Path: <singer@apple.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 7BE3911E8169 for <rtcweb@ietfa.amsl.com>; Thu, 14 Nov 2013 18:26:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4
X-Spam-Level:
X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-4]
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 m5He0z5wXmcI for <rtcweb@ietfa.amsl.com>; Thu, 14 Nov 2013 18:26:10 -0800 (PST)
Received: from mail-in1.asia.apple.com (mail-out.asia.apple.com [17.82.254.63]) by ietfa.amsl.com (Postfix) with ESMTP id A997711E8167 for <rtcweb@ietf.org>; Thu, 14 Nov 2013 18:26:06 -0800 (PST)
Received: from relay3.asia.apple.com ( [17.82.200.17]) by mail-in1.asia.apple.com (Apple Singapore Mail Gateway) with SMTP id B3.0F.21841.A9285825; Fri, 15 Nov 2013 10:10:34 +0800 (MYT)
X-AuditID: 1152fe11-b7f256d000005551-98-5285829aa011
Received: from sng-mmpp-sz01.asia.apple.com ( [17.82.200.58]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by relay3.asia.apple.com (Apple Singapore relay) with SMTP id D7.90.26194.A9285825; Fri, 15 Nov 2013 10:10:34 +0800 (MYT)
Received: from [17.85.192.135] (unknown [17.85.192.135]) by sng-mmpp-sz01.asia.apple.com (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MWA00KOX8PK6W20@sng-mmpp-sz01.asia.apple.com> for rtcweb@ietf.org; Fri, 15 Nov 2013 10:10:34 +0800 (SGT)
Content-type: text/plain; charset=windows-1252
MIME-version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: David Singer <singer@apple.com>
In-reply-to: <CA+23+fFyNzK_tZVAv3qn00uVvBWjU6Rh3CDsPKyJUSYgerwjjQ@mail.gmail.com>
Date: Fri, 15 Nov 2013 10:10:32 +0800
Content-transfer-encoding: quoted-printable
Message-id: <4A450D6F-603B-4A9D-9C1F-531D176F465A@apple.com>
References: <D9C9C6C10CA24644B3A854DB0C12E7D5014C12B5F1@gbplmail03.genband.com> <CA+23+fFyNzK_tZVAv3qn00uVvBWjU6Rh3CDsPKyJUSYgerwjjQ@mail.gmail.com>
To: Jonathan Rosenberg <jdrosen@jdrosen.net>
X-Mailer: Apple Mail (2.1510)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrALMWRmVeSWpSXmKPExsUiGHRCUHdWU2uQweyDShZr/7WzOzB6LFny kymAMYrLJiU1J7MstUjfLoEr40/bJLaC18IVf24+ZW1gfMvfxcjJISFgInF55RMWCFtM4sK9 9WxdjFwcQgK7GSX6pkxmhylaue0EI0RiMpPEgf93oaq2MEnMnLWAqYuRg4NZQE/i/kUtkAZe IHPn3m2sIGFhAUuJC8dNQMJsAqoSD+YcYwQJcwoESyw5WgoSZgEKb3m1jRHEZhYIkbjc/oYJ wtaWePLuAivERBuJY6/vs0JsncYocaN5KTNIQkRAR2Lr3SOMEHfKSpw+95wFpEhC4COrxJxN 7xgnMArPQrhuFpLrZiHZsYCReRWjeG5iZo5uZp6hXmJxZqJeYkFBTqpecn7uJkZwOP8T3ME4 daHhIUYBDkYlHt69P1uChFgTy4orcw8xSnAwK4nwPktoDRLiTUmsrEotyo8vKs1JLT7EKM3B oiTOK5pSGyQkkJ5YkpqdmlqQWgSTZeLglGpgLHDfram9Sf6AbKOFcj7HlS/vvb/f+avpY/Pi 4tbbl/6v2it2VWfGO8PFh82al5bd9F5e361RzZzcUjEhc1FdUferm0HTdX/cePs5nc/0ZM6i g6Fb5t2a+3zuac9GtTzZQz0hs3evf/I+5Mst0ccsVn9P8q2ICftsKS+yytZLt/XlmaOc66Md NJRYijMSDbWYi4oTAW3OPjVjAgAA
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrBLMWRmVeSWpSXmKPExsUiGHTCSndWU2uQweI98hZr/7WzOzB6LFny kymAMYrLJiU1J7MstUjfLoEr40/bJLaC18IVf24+ZW1gfMvfxcjJISFgIrFy2wlGCFtM4sK9 9WxdjFwcQgKTmSQO/L8L5Wxhkpg5awFTFyMHB7OAnsT9i1ogDbxA5s6921hBwsIClhIXjpuA hNkEVCUezDnGCBLmFAiWWHK0FCTMAhTe8mob2CpmgRCJy+1vmCBsbYkn7y6wQky0kTj2+j4r xNZpjBI3mpcygyREBHQktt49AnWnrMTpc89ZJjAKzEI4aBaSg2YhGbuAkXkVo2hRak5ipbFe YnFmol5iQUFOql5yfu4mRkj4Ce5g/DDV8BCjAAejEg9v3P3aICHWxLLiytxDjBIczEoivM8S WoOEeFMSK6tSi/Lji0pzUosPMUpzsCiJ86akAFULpCeWpGanphakFsFkmTg4pRoYvQ44X1QI D+9zrhD3fvww5pH+7r7ZPlZ79wQu2ygdt6cw+Hb3m2xzX7dvtVIZszZlVzBknV603tZV+Oxd 5kXfjMJ/PbzYOTsxbe3ndkZfp3/X2qbwmTEo3O57PWWrq9CTL3O2nJ//5M5V79+71zPyiTCI MN4VYt7UysaZaBHXrFGwQNGlUGefEktxRqKhFnNRcSIAtMfMEzsCAAA=
Cc: Jeremy Fuller <jeremy.fuller@genband.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Video codec selection - way forward
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: Fri, 15 Nov 2013 02:26:15 -0000

On Nov 14, 2013, at 23:57 , Jonathan Rosenberg <jdrosen@jdrosen.net>; wrote:

> I agree with others that SHOULD implement both, or other variations on SHOULD, are not helpful. They will anyway be ignored and amount to more or less the no-interop situation we're in if we continue on the current path and have no consensus.  No consensus means the various players doing as they prefer, which is what they'd do if there is a SHOULD.

I don't agree.  I think that MUST implement at least one of them, and SHOULD do both, provides both clear guidance as to the interop points, and clear pressure to implement both.  I think it's as close to interop as we are likely to get.  

I have no idea why browsers should be singled out for special pain, nor whether that is remotely reasonable, nor whether there is a good definition of one (look at the places where projects such as webkit are embedded, for example).


> 
> 
> On Thu, Nov 14, 2013 at 6:37 AM, Jeremy Fuller <jeremy.fuller@genband.com>; wrote:
> Hi,
>  
> Gaining IETF consensus on making it mandatory to support only H.264 or only VP8 has clearly failed. I would welcome anyone to share their thoughts on why they believe this situation will change anytime in the next few years.  Therefore, can I suggest that we remove items 1 and 2 from the list. Hopefully this will speed up the process by focusing efforts towards gaining agreement on one of the remaining options.
>  
> The following alternatives has been proposed:
> 	• All entities MUST support H.264
> 	• All entities MUST support VP8
> 	• All entities MUST support both H.264 and VP8
> 	• Browsers MUST support both H.264 and VP8, other entities MUST support at least one of H.264 and VP8
> 	• All entities MUST support at least one of H.264 and VP8
> 	• All entities MUST support H.261
> 	• There is no MTI video codec
> 	• All entities MUST support H.261 and all entities MUST support at least one of H.264 and VP8
> Regards,
> Jeremy Fuller
>  
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
> 
> 
> 
> 
> -- 
> Jonathan Rosenberg, Ph.D.
> jdrosen@jdrosen.net
> http://www.jdrosen.net
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

David Singer
Multimedia and Software Standards, Apple Inc.