[rtcweb] Proposed Video Selection Process

Magnus Westerlund <magnus.westerlund@ericsson.com> Thu, 21 November 2013 16:51 UTC

Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 555E21AE207 for <rtcweb@ietfa.amsl.com>; Thu, 21 Nov 2013 08:51:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 7baQfyl-dsBj for <rtcweb@ietfa.amsl.com>; Thu, 21 Nov 2013 08:51:09 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se []) by ietfa.amsl.com (Postfix) with ESMTP id DF2AF1AE1FE for <rtcweb@ietf.org>; Thu, 21 Nov 2013 08:51:08 -0800 (PST)
X-AuditID: c1b4fb25-b7eff8e000000eda-1f-528e39f5a9e8
Received: from ESESSHC010.ericsson.se (Unknown_Domain []) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id B1.F4.03802.5F93E825; Thu, 21 Nov 2013 17:51:01 +0100 (CET)
Received: from [] ( by smtp.internal.ericsson.com ( with Microsoft SMTP Server id 14.2.328.9; Thu, 21 Nov 2013 17:51:00 +0100
Message-ID: <528E39F4.4010706@ericsson.com>
Date: Thu, 21 Nov 2013 17:51:00 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrIJMWRmVeSWpSXmKPExsUyM+Jvre5Xy74gg84F0hZr/7WzOzB6LFny kymAMYrLJiU1J7MstUjfLoErY/uUi0wFD2QrdtzfxdbA+F68i5GTQ0LARGLDj6dsELaYxIV7 68FsIYFDjBK7P1t3MXIB2csZJX5cfcgMkuAV0JZY9GstO4jNIqAqcaFlGVicTcBC4uaPRrBm UYFgiau966DqBSVOznzCAmKLCKhLXH54AaxXWEBT4k73M9YuRg6gxeISPY1BIGFmAT2JKVdb GCFseYntb+cwQ9yjLdHQ1ME6gZF/FpKps5C0zELSsoCReRUje25iZk56udEmRmAwHdzyW3UH 451zIocYpTlYlMR5P7x1DhISSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXAKFrK/NLn3Mz+M+um 6Z6Pya4JFJG5UDvlsEnxu3m2eXWXVjxLn7FJd6FoR80LhvK7U1o3b1hZ/vbggYdlM7W3S248 pvtP7f+22OoiM569yqevRXyVd9i4YufWx6d/7doXysDcOe/wzCkVVcHtxypCVNj9AtJuL2Kx XN/5T1Zj+rV8w9IfsaXVxkosxRmJhlrMRcWJAKwOyaH0AQAA
Subject: [rtcweb] Proposed Video Selection Process
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: Thu, 21 Nov 2013 16:51:12 -0000


The WebRTC ecosystem needs to avoid interoperability failure to grow
optimally.  The RTCWEB working group took on the task of establish Audio
and Video MTI codecs as part of meeting that need. We have not succeeded
in finishing that task for video using normal IETF process, but it is
still important.

We (WG chairs) are proposing that the working group consent to a method
that will establish an MTI, even if the MTI chosen does not have rough
consensus.  We would far prefer the normal IETF process, but it is not
proving workable for this selection.

We initially proposed a method from RFC 3929 (external review team), but
now believe that the working group would not consent to that method.
Instead we are proposing a method that leaves the decision in the hands
of the WG.

The method we propose is based on Instant-runoff voting,
http://en.wikipedia.org/wiki/Instant-runoff_voting, with the
understanding that the choice will be the winner according to the
Instant-runoff voting process.

The steps in the proposed process are these (1-5):

1) Establish a final list of alternatives, based on the WG's input to
Gonzalo's email on the 13th of November that requires any additions to
provided by end of the 27th of November.

2) Establish those eligible to vote.  Any participant in the
working group process either electronically or in-person as of yesterday
(20th of November). Who has participated in the Working group process
will be anyone that can be identified from:
 - The Blue Sheets for any RTCWEB WG session during an IETF meeting or
   an interim meeting since the WG's creation.
 - posting of at least one email to the RTCWEB mailing list

The voter must at time of voting prove their eligibility, by pointing to
the mail archive or a particular blue sheet/meeting. Please verify your
own eligibility.

3) Start the the voting period. Those eligible and willing to vote send
their ballot to a vote collector (Matt Lepinski, former Nomcom chair)
within two weeks using email. The vote collector will check when
receiving a ballot the that the voter is eligible and send a
confirmation email on receiving the ballot. During the balloting period
the vote collector will keep all ballots secret.

 - The voter MUST rank ALL alternatives in their ballot from the most
   preferred, marked with rank 1, the second most with 2, all the way
   to the least preferred marked with rank N.

4) When the voting period is over the ballot collector will publish the
results as well as all ballots, including the voters name to the RTCWEB
WG mailing list. This enables all voting individuals to verify that
their ballot is unmodified. And allows anyone to verify the result of
the vote.

5) The selection is recorded in the drafts.

--- End of Process Proposal ---

This message initiates the first step in the working group consensus
call process. Namely a one week comment and discussion period for the
above process.

After that week the WG chairs will update, if necessary, the proposal.
Then using the normal IETF process in which anyone is eligible to
participate, the chairs will ask for (rough) consensus to adopt this
extraordinary process to achieve the working group's stated goals.  The
end date for this consensus call is 2-weeks after the announcement of
the consensus call.

If the working group does not consent to using this extraordinary
process, we will hold a consensus call if the WG can accept
"WebRTC entities MUST support at least one of H.264 or VP8.".

If there is failure to establish consensus even for this statement, the
chairs conclude that the WG can't establish what to say about a MTI
video codec.

The WG Chairs

Magnus Westerlund
Cullen Jennings
Ted Hardie