Re: [rtcweb] Plan for MTI video codec?

Martin Thomson <martin.thomson@gmail.com> Thu, 16 October 2014 21:28 UTC

Return-Path: <martin.thomson@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 F3A121A89A8 for <rtcweb@ietfa.amsl.com>; Thu, 16 Oct 2014 14:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 0kSfqkf0X3DT for <rtcweb@ietfa.amsl.com>; Thu, 16 Oct 2014 14:28:11 -0700 (PDT)
Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 058F01A88D7 for <rtcweb@ietf.org>; Thu, 16 Oct 2014 14:28:10 -0700 (PDT)
Received: by mail-lb0-f169.google.com with SMTP id 10so3572777lbg.28 for <rtcweb@ietf.org>; Thu, 16 Oct 2014 14:28:09 -0700 (PDT)
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=K/0FpVvXIUDDitDUwKd3t8rv7UU5ZzJfAMz2D//UB/M=; b=IXCX3mwYn5+kaguvesB1DvtXyJkVISE+M1kZ6Zi0dfjobV9MHsy7HahKPWPWg/tA/F t3vhPTVsPLpyFbRmdEtHQW/mfdWiAjXyeLnHBGMDGp3K2dSgsrJOM+K/nLolSVtQx3Er UcjQe81iks6gHjHjzzsZeMtvwinbIi8Upr3S1tVepHirI/0W2p94FsgzSH3mEOVjWqH4 FvmgsnI56RMSSRE2x0hOXwnO17wQmL4kcYKtd2I/8gaUd87/IX454kG5Zuyz85bVvbeq 8KDNK3HDMUnxYk1Kbj06Lae+/dtczLZ37y/U4jmtQIcRlE8d0uY95OVRx6qba+mzuHTY jmuQ==
MIME-Version: 1.0
X-Received: by 10.152.204.103 with SMTP id kx7mr4406273lac.7.1413494889334; Thu, 16 Oct 2014 14:28:09 -0700 (PDT)
Received: by 10.25.215.217 with HTTP; Thu, 16 Oct 2014 14:28:09 -0700 (PDT)
In-Reply-To: <544035DE.8000606@matthew.at>
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>
Date: Thu, 16 Oct 2014 14:28:09 -0700
Message-ID: <CABkgnnUNgWaauS6-nZ5fcExjsMPy4ZGPXaahduzA39=iqh9+fQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Matthew Kaufman <matthew@matthew.at>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/2wWfIWHNxGVvXBY85tEvu1WwI_k
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] 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: Thu, 16 Oct 2014 21:28:19 -0000

On 16 October 2014 14:17, Matthew Kaufman <matthew@matthew.at> wrote:
> And that's because something substantive has changed, or simply because
> wasting the WG time on this again is more entertaining than actually
> finishing a specification that can be independently implemented by all
> browser vendors? (A specification that we are nowhere near having, as far as
> I can tell)

Personally, I've found the reprieve from this fight refreshing.  And
it would appear that we've made some real progress as a result.  I'd
suggest that if we don't have new information, we continue to spend
our time productively.  If we can't find topics to occupy our meeting
agenda time, then maybe we can free an agenda slot.