[rtcweb] VP8 in ISO (Re: Plan for MTI video codec?)

Harald Alvestrand <harald@alvestrand.no> Sat, 18 October 2014 21:25 UTC

Return-Path: <harald@alvestrand.no>
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 B1CA11A1AA0 for <rtcweb@ietfa.amsl.com>; Sat, 18 Oct 2014 14:25:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 l3NgaOO4MRGk for <rtcweb@ietfa.amsl.com>; Sat, 18 Oct 2014 14:25:16 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id 4C07E1A1A8A for <rtcweb@ietf.org>; Sat, 18 Oct 2014 14:25:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 3263D7C4E74; Sat, 18 Oct 2014 23:25:15 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qNdOUVP5utF6; Sat, 18 Oct 2014 23:25:05 +0200 (CEST)
Received: from [172.30.42.84] (c-58f0e555.03-217-73746f1.cust.bredbandsbolaget.se [85.229.240.88]) by mork.alvestrand.no (Postfix) with ESMTPSA id EB7BF7C4C1E; Sat, 18 Oct 2014 23:25:04 +0200 (CEST)
Message-ID: <5442DAAF.6020304@alvestrand.no>
Date: Sat, 18 Oct 2014 23:25:03 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Alexandre GOUAILLARD <agouaillard@gmail.com>
References: <CAGTXFp-HVJDwd86207PNM2QVYO4Z_K4WF-KarnRs1fb7nvy4zA@mail.gmail.com> <CA+9kkMDfES8gpi0-PTXpCnQHjFYUSF2r44TNzH5B4UfDGo8PtA@mail.gmail.com> <CAGTXFp8O-7ACksk3v3f=KjCkcDb4e8G=t-e=EJ1503vt7TkpCQ@mail.gmail.com> <CAGTXFp867AMUZ_fEKxG9uAoR1H1AirVHi3-ayJ=KTQk9L+C7+g@mail.gmail.com> <CA+9kkMAZufR7gUrwkS7Tf5GOfg+ZtsZWGcn-8YLCvnmYnTgfFw@mail.gmail.com> <544035DE.8000606@matthew.at> <CABkgnnUNgWaauS6-nZ5fcExjsMPy4ZGPXaahduzA39=iqh9+fQ@mail.gmail.com> <D5D11F2B-9E32-4932-A601-F1D7FD50C706@gmail.com> <544117FB.6050706@alvestrand.no> <CAHgZEq6GTk5ei+LLpWPM5povpieompD66VU9F+u7--WJVgapaQ@mail.gmail.com>
In-Reply-To: <CAHgZEq6GTk5ei+LLpWPM5povpieompD66VU9F+u7--WJVgapaQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/kztjj9jAYV9R_InA21YWK1rnc88
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: [rtcweb] VP8 in ISO (Re: Plan for MTI video codec?)
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: Sat, 18 Oct 2014 21:25:18 -0000

Changing the subject line, since this is information that more people
may be interested in having called out clearly:

On 10/18/2014 11:08 PM, Alexandre GOUAILLARD wrote:
> +1 to not having MTI codec discussion unless some progress has been
> made on VP8 at MPEG. Any news on that?

The VCB spec (VP8 in ISO) is in DIS ballot, and the ballot closes in
January.
ISO processes are complex, and I don't always understand them, but if
the ballot results are positive, the standard should be approved.

So far, we have not seen any official feedback, but all the unofficial
feedback I've seen has been more or less editorial in nature.

There are no technical changes that would cause any issues in
compatibility between VP8 and VCB.