[rtcweb] On the form of the question (was Re: Alternative consensus and MTI video codecs)
Adam Roach <adam@nostrum.com> Fri, 08 November 2013 16:01 UTC
Return-Path: <adam@nostrum.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 D3E2A21E8130 for <rtcweb@ietfa.amsl.com>; Fri, 8 Nov 2013 08:01:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.513
X-Spam-Level:
X-Spam-Status: No, score=-102.513 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 W4BuAxVeu391 for <rtcweb@ietfa.amsl.com>; Fri, 8 Nov 2013 08:01:27 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id EB4C521E8140 for <rtcweb@ietf.org>; Fri, 8 Nov 2013 08:01:18 -0800 (PST)
Received: from dhcp-9081.meeting.ietf.org (dhcp-9081.meeting.ietf.org [31.133.144.129]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id rA8G19XV058356 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 8 Nov 2013 10:01:10 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <527D0AC4.1080704@nostrum.com>
Date: Fri, 08 Nov 2013 08:01:08 -0800
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Ron <ron@debian.org>, rtcweb@ietf.org
References: <CAAS2fgQ730sjjv5Ly0_TFmdz=ryhPN13+A69_0_MedotHGEthg@mail.gmail.com> <527C38FF.6040000@nostrum.com> <20131108123109.GF3245@audi.shelbyville.oz>
In-Reply-To: <20131108123109.GF3245@audi.shelbyville.oz>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 31.133.144.129 is authenticated by a trusted mechanism)
Subject: [rtcweb] On the form of the question (was Re: Alternative consensus and MTI video codecs)
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, 08 Nov 2013 16:01:37 -0000
On 11/8/13 04:31, Ron wrote: > ...what we had today was essentially "just a vote". If it had been conclusive, that would have been great, but it wasn't... Well, to be fair, it did involve a rather long discussion of the various factors impacting the decision. The show of hands was ostensibly an attempt to suss out whether the arguments had proven compelling enough to push forward with one codec over the other. Sadly, the form of the question, when combined with the method of measurement, precluded doing so. I'm not claiming that there was consensus in the room. I'm claiming that its presence would not have been detected by the methodology employed. Consider: if everyone in the room raised their hand for both options, Richard would have been compelled to call it "no consensus" even though that result would logically mean that no one objects to either option. Clearly, that didn't happen. On the other hand, what *did* happen was that we had roughly 50% of the room say that they were willing to live with H.264, and roughly 30% of the room say they were willing to live with VP8. This, after the chairs *strongly* *encouraged* people who could live with either option to raise their hands for both options. We didn't explicitly ask for who was in both camps (and those people at the front of the room facing the participants did nothing to gauge overlap), nor did we try to suss out who was abstaining by not raising their hand. As a result, the numbers are meaningless. On one extreme: If those sets of people were completely disjoint, then we're nowhere near consensus. At the other extreme: if the set of people who could accept VP8 were a strict subset of the set of people who could accept H.264, then we would have obvious consensus and could move forward. I know that neither of these scenarios are true, but measuring where the participants fell in that continuum would have been the true measure of the sense of the room. So, sadly, we learned nothing. For the record, and I'm hoping others will follow suit (since, as you pointed out, consensus is measured on the list): I'm of the opinion that either of the two options on the table are acceptable[1][2]. /a ___ [1] I recognize that approaches other than H.264 and VP8 have been casually mentioned on-list; but, if an approach is so unpopular that it hasn't yet found a proponent willing to spend the meager amount of time necessary to type up and submit an internet draft advocating it, then I have to assume that its chances of reaching critical mass are approximately zero. I will not waste my time or yours favoring or rebutting them until someone gets serious about them. [2] Ironically, I'm somewhat regretting that I indicated this in the room: I was trying to be accommodating to both positions, and I know several other people who did the same. Had the indications of support been more partisan, it's possible that one of the two camps would have been revealed to be in the rough.
- [rtcweb] H.261 vs No MTI (was: Alternative consen… cowwoc
- [rtcweb] Alternative consensus and MTI video code… Gregory Maxwell
- Re: [rtcweb] Alternative consensus and MTI video … Adam Roach
- Re: [rtcweb] Alternative consensus and MTI video … Gregory Maxwell
- Re: [rtcweb] Alternative consensus and MTI video … Ron
- Re: [rtcweb] Alternative consensus and MTI video … Adam Roach
- Re: [rtcweb] H.261 vs No MTI cowwoc
- [rtcweb] On the form of the question (was Re: Alt… Adam Roach
- Re: [rtcweb] H.261 vs No MTI Leon Geyser
- Re: [rtcweb] H.261 vs No MTI (was: Alternative co… Tim Panton
- Re: [rtcweb] H.261 vs No MTI Tim Panton
- Re: [rtcweb] H.261 vs No MTI Leon Geyser
- Re: [rtcweb] H.261 vs No MTI cb.list6
- Re: [rtcweb] On the form of the question (was Re:… Markus.Isomaki
- Re: [rtcweb] H.261 vs No MTI cowwoc
- Re: [rtcweb] H.261 vs No MTI cb.list6
- Re: [rtcweb] H.261 vs No MTI cowwoc
- Re: [rtcweb] On the form of the question (was Re:… Ron