Re: [rtcweb] Video codecs and the staw poll

Harald Alvestrand <harald@alvestrand.no> Tue, 28 January 2014 15:17 UTC

Return-Path: <harald@alvestrand.no>
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 B6A6E1A0379 for <rtcweb@ietfa.amsl.com>; Tue, 28 Jan 2014 07:17:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.435
X-Spam-Level:
X-Spam-Status: No, score=-7.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535] 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 jnVd30Tr8WoV for <rtcweb@ietfa.amsl.com>; Tue, 28 Jan 2014 07:17:42 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 266F51A039B for <rtcweb@ietf.org>; Tue, 28 Jan 2014 07:17:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 1E66839E125 for <rtcweb@ietf.org>; Tue, 28 Jan 2014 16:17:48 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ugo6splAocCq for <rtcweb@ietf.org>; Tue, 28 Jan 2014 16:17:45 +0100 (CET)
Received: from [10.1.1.234] (64-71-23-98.static.wiline.com [64.71.23.98]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 4680039E0FD for <rtcweb@ietf.org>; Tue, 28 Jan 2014 16:17:45 +0100 (CET)
Message-ID: <52E7CA0D.2070509@alvestrand.no>
Date: Tue, 28 Jan 2014 16:17:33 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <BFDBDCA9-937E-4B90-97B1-A23EEB65CF9A@iii.ca>
In-Reply-To: <BFDBDCA9-937E-4B90-97B1-A23EEB65CF9A@iii.ca>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] Video codecs and the staw poll
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, 28 Jan 2014 15:17:45 -0000

Just to be 100% sure:

This is the US version of "table" (put aside), not the UK version of
"table" (start working on), right?
This is one of the words I try avoid using.

http://en.wikipedia.org/wiki/Table_(parliamentary_procedure)

Apart from that, +1 on both the decision to postpone and the conclusion
that there doesn't seem to be a basis for forming a consensus on any
proposal but 1, 2, 3 and 4.


On 01/28/2014 06:13 AM, Cullen Jennings wrote:
> Dear WG,
>
> After reviewing the poll results found here: http://www.ietf.org/mail-archive/web/rtcweb/current/pdfWd2PIhOY9y.pdf the chairs concludes that the working group still believes that an MTI is required for the WebRTC ecology to develop.    There are a number of options which did not garner significant support; essentially only options 1, 2, 3, 4 seem to have enough support that they might be the eventual basis of working group consensus.  The chairs do not view the other options as having sufficient support to warrant further working group activity or discussion.
>
> There is no obvious leader between VP8 and H.264, however, nor obvious support for selecting both.  Each has similar numbers of supporting positions and objections, and both have the support of well over half the participants in the straw poll.  Given that, we are no closer to being able to choose between them at this time.  
>
> The chairs therefore propose tabling the discussion of a mandatory to implement video codec until about 6 week before the start of the IETF 91 meeting in November 2014. This is so that the working group can focus its energy on completing other work.  We do expect to begin work on the video document (draft-ietf-rtcweb-video) to meet its milestone of December, but initially without specifying which of the two codecs is the WG consensus for MTI.
>
> When we return to the discussion, the working group chairs currently expect to run a consensus call on support for each codec to be mandatory to implement.  This expectation may change, however, based on new information or working group experience.
>
> If anyone has concerns about tabling this discussion until September 29, 2014 please let us know by February 4.
>
> Thank you, 
>
> Cullen, Magnus, Ted <the chairs>
>
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb


-- 
Surveillance is pervasive. Go Dark.