Re: [rtcweb] Video codecs and the staw poll

Ted Hardie <ted.ietf@gmail.com> Tue, 28 January 2014 16:14 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 071F61A02D3 for <rtcweb@ietfa.amsl.com>; Tue, 28 Jan 2014 08:14:52 -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 HZcVUzsQzux0 for <rtcweb@ietfa.amsl.com>; Tue, 28 Jan 2014 08:14:49 -0800 (PST)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 1E2F41A023D for <rtcweb@ietf.org>; Tue, 28 Jan 2014 08:14:49 -0800 (PST)
Received: by mail-ig0-f175.google.com with SMTP id uq10so12479431igb.2 for <rtcweb@ietf.org>; Tue, 28 Jan 2014 08:14:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+NU8arQ3gMuUGdbvf18WyjKT0kW2KmXJDJH+omyxquQ=; b=piFruWIyvH+N90ZhA8Il7E6/bhLpez1TWBgx5vtGQxpoFXuKp0pFZPNZqJbNGE7NIp z8Zks7b8f3x9730RDB0VUriJTDipj5V36aw/3B0AU1xrj6Gm1TzSF+DB8VJMHhSwlo6m 1wMIqjL60GZBnNKk4DvCuUmT4JQjFYL85NusmtUynhvYRwCXE5oWVrlb+ghaZ4Kagzk2 ReBg52DCD4AhruwsJjJ8aDUGyv0E8KypJk4HNzkEz9TlZ+WaKpb+nHjGIQ/Y8s3DFd5h cB//iqxSFJ/xtd9tNGVScXnogC2w+ncMK7fN6jp0GMZsfjgdWj3lbMSFkTy3mPMXqZXO yNMw==
MIME-Version: 1.0
X-Received: by 10.42.228.65 with SMTP id jd1mr1790224icb.62.1390925686500; Tue, 28 Jan 2014 08:14:46 -0800 (PST)
Received: by 10.43.65.14 with HTTP; Tue, 28 Jan 2014 08:14:46 -0800 (PST)
In-Reply-To: <52E7CA0D.2070509@alvestrand.no>
References: <BFDBDCA9-937E-4B90-97B1-A23EEB65CF9A@iii.ca> <52E7CA0D.2070509@alvestrand.no>
Date: Tue, 28 Jan 2014 08:14:46 -0800
Message-ID: <CA+9kkMCdB_e=noUmDsCsy1c2=3Cs2iHTyzen2bNYBRrgwSf6jw@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: multipart/alternative; boundary="001a1132e4cc73f03704f10a1f82"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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 16:14:52 -0000

On Tue, Jan 28, 2014 at 7:17 AM, Harald Alvestrand <harald@alvestrand.no>wrote:

> 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.
>
>
We mean "put aside".  Sorry for any lack of clarity; we thought the
"until  about six weeks before IETF 91"
eliminated the confusion, but probably should have just said "put aside.".

Ted




> 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.
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>