Re: [video-codec] The Can Has Landed
Thomas Daede <tdaede@mozilla.com> Fri, 20 March 2015 00:41 UTC
Return-Path: <tdaede@mozilla.com>
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 A18781A1F20 for <video-codec@ietfa.amsl.com>; Thu, 19 Mar 2015 17:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 cH1pdJ1m37Ut for <video-codec@ietfa.amsl.com>; Thu, 19 Mar 2015 17:41:52 -0700 (PDT)
Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 120051A1F16 for <video-codec@ietf.org>; Thu, 19 Mar 2015 17:41:50 -0700 (PDT)
Received: by pacwe9 with SMTP id we9so91296538pac.1 for <video-codec@ietf.org>; Thu, 19 Mar 2015 17:41:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=9VP5WMxVvi0w3CnKBD9dCoiPcHSgIG5+u/S5UF1639E=; b=FQri1QFAx0DyGKuOCyAP4/AcD/iLsDMBJDcKb1hTbuM/94KWWbuH9Z1RV3bwpiFuC6 XSXlqJMYLz27ZIGTMbX1Yn13g0dwmxyYSqlZXdiyyur1o4iqr25dX6boWvKBc8NrLJ47 ctw5XjaFrm36sxe+nPWKRnY3/LL+t25+RT8MTcj2QJlEmwAqVNN4s2wNJrCxZo9ekpDD FgZ+Z2esAPXWkoB6rYMzek+Pc3XNf/ZHQECpJmkgfIivg1Og+xpglkVIYQCCclh0ZGM+ HwcMdmb5hteeb3NHlpZVui/bzriLNvpL0hlHBrpiS92w6Q8pH953Dh+YUSVEPjB4ctKo 2bag==
X-Gm-Message-State: ALoCoQm6VSw0Z58oDsUNTX53DGKFTnb3NS5ifFAn6Ftqwpa1GamhulOvi1fCuJWQ6CTRIW24E3f9
X-Received: by 10.66.55.74 with SMTP id q10mr181291501pap.94.1426812110518; Thu, 19 Mar 2015 17:41:50 -0700 (PDT)
Received: from ?IPv6:2620:101:80fc:224:7e7a:91ff:fe9e:8126? ([2620:101:80fc:224:7e7a:91ff:fe9e:8126]) by mx.google.com with ESMTPSA id tr8sm5015928pab.4.2015.03.19.17.41.49 for <video-codec@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Mar 2015 17:41:49 -0700 (PDT)
Message-ID: <550B6CCC.70706@mozilla.com>
Date: Thu, 19 Mar 2015 17:41:48 -0700
From: Thomas Daede <tdaede@mozilla.com>
User-Agent: http://a.pomf.se/cszdno.opus
MIME-Version: 1.0
To: video-codec@ietf.org
References: <CACrD=+_D+psUeWevMuwp0bnxqdcJpo3Zo3Og4E6kkGH1uuzxdA@mail.gmail.com> <CAMzhQmNymkEMgbw-gUGhKEgCYh1yXo8MRkP-8FNfQm8tVNhzbA@mail.gmail.com>
In-Reply-To: <CAMzhQmNymkEMgbw-gUGhKEgCYh1yXo8MRkP-8FNfQm8tVNhzbA@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/video-codec/6OnVV8KRMwwyeQT5IRGxDLfG4P4>
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: Fri, 20 Mar 2015 00:41:55 -0000
On 03/19/2015 05:17 PM, Keith Winstein 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"? If VP9 could be shown to meet our requirements for performance and licensing, I would be supportive of that path. However, I don't believe that it currently does. In the testing draft, while I specified methods of testing codecs, I did not specify an absolute performance goal. We will need to set one. Opus achieved state-of-the-art performance, which was highly beneficial to its adoption. VP9 does not achieve this yet. In regards to licensing, it is clear that many companies are quite happy shipping VP9 right now. However, others are not nearly as comfortable with it, as seen on RTCWEB. These concerns arise from other, non MPEG-LA rights holders. We need to make sure that we address those concerns in a working group one way or another. One way to do that is just to stay well clear of the patents in question. > Google said in May 2013 that "a draft bitstream specification is well > underway." For whatever reason, they still haven't published it yet. (There > is also no independent implementation of a decoder written by a > non-Google-employee, afaik, much less of an encoder.) ffmpeg's VP9 decoder was written by a couple of non-Google employees: https://blogs.gnome.org/rbultje/
- [video-codec] The Can Has Landed Monty Montgomery
- Re: [video-codec] The Can Has Landed Keith Winstein
- Re: [video-codec] The Can Has Landed Thomas Daede
- Re: [video-codec] The Can Has Landed Keith Winstein
- Re: [video-codec] The Can Has Landed Monty Montgomery
- Re: [video-codec] The Can Has Landed Timothy B. Terriberry
- [video-codec] Performances, measurement of same (… Harald Alvestrand
- [video-codec] Performances, measurement of same (… Harald Alvestrand
- Re: [video-codec] Performances, measurement of sa… Mohammed Raad
- Re: [video-codec] Performances, measurement of sa… Harald Alvestrand
- Re: [video-codec] Performances, measurement of sa… Timothy B. Terriberry
- Re: [video-codec] Performances, measurement of sa… Mo Zanaty (mzanaty)