Re: [rtcweb] Video Codec Selection Plan
Iñaki Baz Castillo <ibc@aliax.net> Fri, 13 September 2013 17:21 UTC
Return-Path: <ibc@aliax.net>
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 A301711E80FC for <rtcweb@ietfa.amsl.com>; Fri, 13 Sep 2013 10:21:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.676
X-Spam-Level:
X-Spam-Status: No, score=-2.676 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 KARUQt7K68IK for <rtcweb@ietfa.amsl.com>; Fri, 13 Sep 2013 10:21:41 -0700 (PDT)
Received: from mail-qc0-f171.google.com (mail-qc0-f171.google.com [209.85.216.171]) by ietfa.amsl.com (Postfix) with ESMTP id 49F3E21F9FC6 for <rtcweb@ietf.org>; Fri, 13 Sep 2013 10:21:41 -0700 (PDT)
Received: by mail-qc0-f171.google.com with SMTP id x19so1050634qcw.2 for <rtcweb@ietf.org>; Fri, 13 Sep 2013 10:21:39 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=W4X/UCSG/SRnOZjUSO56h69fd4euA3+QTac6DY1SnpQ=; b=GtPzEnG3pt7Kv55M5TcQl07c8kTSiQirrsC9kv9VfY98cqkTqZ6toqf5SKPfY49OPH SqYQWKTRp5AuoANtwh4sC9hjBqFNd2cL0QuY5LvHzU0wJe/40k0EVDgrLPr0N9BtuVNQ O0A5fxs+9RDI8xONXQCwIUPXlUCuqi6FoQ1tsDtlYdLHYt1M+bXNcfhLy1rJaIq3Chq8 TzSNa0PYzz2rOwTb5NzKEQcB0GBZKtrWsc/mTSeZLuSRWqGGh+DDtpKDSKfKKMQZ8+Hh YHhFfXDq9J2Ucx98jh7HNzIGPJDJnBuGtEhY1KES5hlIAGF8v+G1hPio+H4UCTuuQgD7 uw5A==
X-Gm-Message-State: ALoCoQn3opsjkJIIgO0b0EM2UwraT0/YHw0O+wGe1n25hOaB0SFyXbieMqaM7Xhu/OtMtR39BM6a
MIME-Version: 1.0
X-Received: by 10.49.99.98 with SMTP id ep2mr27248967qeb.9.1379092899454; Fri, 13 Sep 2013 10:21:39 -0700 (PDT)
Received: by 10.49.16.71 with HTTP; Fri, 13 Sep 2013 10:21:39 -0700 (PDT)
Received: by 10.49.16.71 with HTTP; Fri, 13 Sep 2013 10:21:39 -0700 (PDT)
In-Reply-To: <CA+9kkMAvdtq_gufKmDNCNCL+kKcxyi0MGUoVHetd9_DzbEdEnA@mail.gmail.com>
References: <CA+9kkMAvdtq_gufKmDNCNCL+kKcxyi0MGUoVHetd9_DzbEdEnA@mail.gmail.com>
Date: Fri, 13 Sep 2013 19:21:39 +0200
Message-ID: <CALiegfk1rArkDGx6_3NaiKuSVe7udcHSBrotg51ctH-dc2PpsA@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="047d7bd76bb462972304e64716fe"
Cc: Cullen Jennings <fluffy@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Video Codec Selection Plan
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, 13 Sep 2013 17:21:45 -0000
Do not take me wrong, but IMHO this decision should be taken by the W3C WebRTC group. -- Iñaki Baz Castillo <ibc@aliax.net> El 13/09/2013 18:52, "Ted Hardie" <ted.ietf@gmail.com> escribió: > WG, > > The chairs have created a plan for how to perform the Video Codec > selection in our WG. The chairs are asking for review of our plan on > how to undertake the mandatory-to-implement video codec selection. > We'd much prefer to have comments on the mechanics before they begin, > so please review now. Proponents of a particular proposal should > note both the actions required and the timelines proposed. > > The main goal of this plan is to hold a consensus call on which of > the proposed alternatives we as a WG should select at one of the WG > sessions in Vancouver. Such a consensus call will of course be > verified on the mailing list for anyone who can't participate. The > chairs will recuse themselves from judging this particular > consensus. > > In the WG session each codec proposal will be allowed an equal amount > of time to highlight the arguments for their proposal. After that a > there will be a slot for discussion and clarifying questions. > > To enable the WG participants to get answers to any questions, the > proposals in draft form and any supporting material MUST be made > available by 6th of October. This is to ensure that the WG > participants can verify or object to any claims or statements in > the proposal material prior to the WG session. We chairs would really > not like to see the proponents bring up new arguments at their > presentation. Also the WG participants are expected to raise any > arguments on the list ahead of time to enable the proponents to > respond to such arguments. > > The proposed consensus questions will be of the following form: > > 1. If you support H.264 as the mandatory to implement codec or are > willing to live with it as the MTI, please raise your hand now. > > 2. If you support VP8 as the mandatory to implement codec or are > willing to live with it as the MTI, please raise your hand now. > > You may indicate support on both questions and we encourage you to do > so if you can live with either, even if you have a preference for one > over the other. > > Additional proposals than the previous ones are welcome, but must be > submitted as draft and their proponents must notify the chairs no later > than the 6th of October that they also have a candidate proposal. > > In case the WG fails to reach consensus we chairs propose that we use > the alternative decision process as discussed in RFC3929. The method > and its usage will be discussed on the list should the WG not > establish consensus on a proposal for mandatory to implement video codec. > > regards, > > Magnus, Cullen, and Ted > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb > >
- Re: [rtcweb] Video Codec Selection Plan Pete Resnick
- Re: [rtcweb] Video Codec Selection Plan John Leslie
- [rtcweb] Video Codec Selection Plan Ted Hardie
- Re: [rtcweb] Video Codec Selection Plan Matthew Kaufman
- Re: [rtcweb] Video Codec Selection Plan Bernard Aboba
- Re: [rtcweb] Video Codec Selection Plan Iñaki Baz Castillo
- Re: [rtcweb] Video Codec Selection Plan Ralph Giles
- Re: [rtcweb] Video Codec Selection Plan Ted Hardie
- Re: [rtcweb] Video Codec Selection Plan Iñaki Baz Castillo
- Re: [rtcweb] Video Codec Selection Plan Bernard Aboba
- Re: [rtcweb] Video Codec Selection Plan Adam Roach
- Re: [rtcweb] Video Codec Selection Plan Cullen Jennings (fluffy)
- Re: [rtcweb] Video Codec Selection Plan Matthew Kaufman (SKYPE)
- Re: [rtcweb] Video Codec Selection Plan Ted Hardie
- Re: [rtcweb] Video Codec Selection Plan Pete Resnick
- Re: [rtcweb] Video Codec Selection Plan Ted Hardie
- Re: [rtcweb] Video Codec Selection Plan Lorenzo Miniero
- Re: [rtcweb] Video Codec Selection Plan Roni Even
- Re: [rtcweb] Video Codec Selection Plan Bossiel
- Re: [rtcweb] Video Codec Selection Plan Simon Perreault
- Re: [rtcweb] Video Codec Selection Plan Bossiel
- Re: [rtcweb] Video Codec Selection Plan Magnus Westerlund
- Re: [rtcweb] Video Codec Selection Plan Chris Wendt
- Re: [rtcweb] Video Codec Selection Plan cb.list6
- Re: [rtcweb] Video Codec Selection Plan cowwoc
- Re: [rtcweb] Video Codec Selection Plan Christer Holmberg
- Re: [rtcweb] Video Codec Selection Plan cowwoc
- Re: [rtcweb] Video Codec Selection Plan Ted Hardie
- Re: [rtcweb] Video Codec Selection Plan Bernard Aboba
- Re: [rtcweb] Video Codec Selection Plan Eric Rescorla
- Re: [rtcweb] Video Codec Selection Plan Leon Geyser
- Re: [rtcweb] Video Codec Selection Plan Monty Montgomery
- Re: [rtcweb] Video Codec Selection Plan Basil Mohamed Gohar
- Re: [rtcweb] Video Codec Selection Plan Gili