IETF Logo Mail Archive

Re: [video-codec] The Can Has Landed

"Timothy B. Terriberry" <tterribe@xiph.org> Mon, 23 March 2015 01:19 UTC

Return-Path: <tterribe@xiph.org>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 064EF1A8734 for <video-codec@ietfa.amsl.com>; Sun, 22 Mar 2015 18:19:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.277
X-Spam-Level:
X-Spam-Status: No, score=-3.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-2.3, SPF_FAIL=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 Foz4cE5POdSm for <video-codec@ietfa.amsl.com>; Sun, 22 Mar 2015 18:19:46 -0700 (PDT)
Received: from smtp.mozilla.org (mx1.corp.phx1.mozilla.com [63.245.216.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 569501A872F for <video-codec@ietf.org>; Sun, 22 Mar 2015 18:19:46 -0700 (PDT)
Received: from localhost (localhost6.localdomain [127.0.0.1]) by mx1.mail.corp.phx1.mozilla.com (Postfix) with ESMTP id 7C026F217D for <video-codec@ietf.org>; Sun, 22 Mar 2015 18:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at mozilla.org
Received: from smtp.mozilla.org ([127.0.0.1]) by localhost (mx1.mail.corp.phx1.mozilla.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ZDrkecYkxRm for <video-codec@ietf.org>; Sun, 22 Mar 2015 18:19:45 -0700 (PDT)
Received: from [31.133.161.125] (dhcp-a17d.meeting.ietf.org [31.133.161.125]) (Authenticated sender: tterriberry@mozilla.com) by mx1.mail.corp.phx1.mozilla.com (Postfix) with ESMTPSA id 0B4E9F2152 for <video-codec@ietf.org>; Sun, 22 Mar 2015 18:19:44 -0700 (PDT)
Message-ID: <550F6A30.5080403@xiph.org>
Date: Sun, 22 Mar 2015 18:19:44 -0700
From: "Timothy B. Terriberry" <tterribe@xiph.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 SeaMonkey/2.26
MIME-Version: 1.0
To: "video-codec@ietf.org" <video-codec@ietf.org>
References: <CACrD=+_D+psUeWevMuwp0bnxqdcJpo3Zo3Og4E6kkGH1uuzxdA@mail.gmail.com> <CAMzhQmPLVuCkUjr_W7vcHaU-3p4d=3T1Bq16ytu6+PTVmq94nA@mail.gmail.com> <CACrD=+820jfn6VE9XBpB+0Bc-Ao=0+o_5ZPfkLzvt6qyNqMc0g@mail.gmail.com>
In-Reply-To: <CACrD=+820jfn6VE9XBpB+0Bc-Ao=0+o_5ZPfkLzvt6qyNqMc0g@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/video-codec/OqyjxUmod-PPlGV7Kmd1ZA9WrDE>
Subject: Re: [video-codec] The Can Has Landed
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec/>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2015 01:19:48 -0000

Monty Montgomery wrote:
> I know Thomas already responded, but...
>
> On Thu, Mar 19, 2015 at 7:35 PM, Keith Winstein <keithw@cs.stanford.edu> wrote:
>> But what are the merits of an IETF working group performing this kind of
>> high-risk, high-reward research, versus doing something much more boring
>> like "writing a specification for VP9 to enable interoperable
>> implementations, and then iterating on that technology"?
>
> Personally, I'd like to see Google submit their VPx work as an input
> to this process and even more interested in seeing them participate in
> development.  Just like with Opus, I don't think the IETF is

Well, I think that's what Keith meant by "iterating on that technology". 
I think if Google wanted to contribute their VPx work we should be very 
happy to see it. VP9 has real-time encoding that shows significant 
performance gains over prior generations and a decoder faster than 
H.264's. Google got usable open source encoder and decoder 
implementations to market before HEVC, and significant hardware support 
agreements with some major chip vendors. If Google codec engineers are 
going to actively participate and bring VPx to the party, that would be 
a real asset.

v2.23.0 | Report a Bug | By Email