[rtcweb] Next Steps in Video Codec Selection Process
Ted Hardie <ted.ietf@gmail.com> Mon, 09 December 2013 17:20 UTC
Return-Path: <ted.ietf@gmail.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 1FDC21AE2DE for <rtcweb@ietfa.amsl.com>; Mon, 9 Dec 2013 09:20:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 HX6pVVYrsnmu for <rtcweb@ietfa.amsl.com>; Mon, 9 Dec 2013 09:20:33 -0800 (PST)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 3E0831AE287 for <rtcweb@ietf.org>; Mon, 9 Dec 2013 09:20:32 -0800 (PST)
Received: by mail-ie0-f181.google.com with SMTP id e14so6643316iej.12 for <rtcweb@ietf.org>; Mon, 09 Dec 2013 09:20:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=idWrWLAOGy0IAjE2oVQJyFT/SxWJwXwSnQo2pZLvj0s=; b=tJ4/SeI2iFiHhCToGkhxpg+tfgL4uo5oLl5tOsgId8uu7BVzU9hf/S8IvTQY4oAO9L BG+USAacGNs87C0ai1cSsz4X2yxFGFyWUZhk+1guVSThITKbUUx1LRWNxO3ws6h24QVw FEzBAz5fvgr9JdgO5KNBbpw7XUi4tPaL1OxwoyGUdsUDTh2FPzozjhHDSxupQry17EVJ 3dEOEeur5AiwTdocWCQknG5mrMjDlcpBVfNDg6xunoajWQIOVACK0HSOQlCBN4Y7ZwjZ MhDP+WBE2UvOj3ay6Yhj3IqLpUKR0sFd3P+NhVS9CKURsxsZmTETyzgoZ164O7wnthjG MDWQ==
MIME-Version: 1.0
X-Received: by 10.43.138.148 with SMTP id is20mr70203838icc.23.1386609627289; Mon, 09 Dec 2013 09:20:27 -0800 (PST)
Received: by 10.43.104.130 with HTTP; Mon, 9 Dec 2013 09:20:27 -0800 (PST)
Date: Mon, 09 Dec 2013 09:20:27 -0800
Message-ID: <CA+9kkMDTWY9Q9FPoUcqesb6ChzyxqfXDpxJ6XjJO_5n2GTsH+A@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Richard Barnes <rlb@ipv.sx>, Cullen Jennings <fluffy@cisco.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: multipart/alternative; boundary="001a11c2f08a47292104ed1d36fc"
Subject: [rtcweb] Next Steps in Video Codec 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: Mon, 09 Dec 2013 17:20:39 -0000
Dear WG, The WG chairs have read and considered the WG’s and the wider IETF community's input on our proposal for video codec selection process. Based on this we have reconsidered the next steps and have another process to try to build and achieve consensus. The goal of this process is to allow anyone, without exception, to provide input on the large set of alternatives proposed to the WG, thus ensuring that we fairly consider all the alternatives to MTI that has been raised and allowing us all to consider if there is a compromise position that will enable us to meet our goal to prevent interoperability failure for video and achieve consensus in the WG. This process is only a first step to establish a working position on which alternative to specify in a WG document. The WG will confirm this consensus later in a WG last call. This will be followed by establishing the IETF consensus on the WG document in the IETF last call. The process we are going to use is to first run a straw poll across all alternatives provided so far. In that straw poll anyone is free to provide their position on each of the alternative and raise the objections they see with each alternative. This straw poll will not decide the issue; it is not a vote. It is an input to the process to identify an alternative for the following consensus call. At the conclusion of the straw poll, the chairs will identify an option based on the results of the straw poll and then put it forward for a specific yes/no consensus call on whether specific text should be added in the WG’s documents. A detailed message on the straw poll, with the full set of alternatives, will follow but a summary of the overall process is thus as follows: -- Conduct a straw poll to gather information on which option might achieve consensus -- Chairs identify an option based on the results of the straw poll and issue a consensus call -- If there is consensus (as judged by Richard Barnes), the selected option is reflected in a WG document -- The WG document is confirmed via the normal process of WGLC and IETF LC A message initiating the straw poll will follow shortly. Thanks, The Chairs