IETF Logo Mail Archive

Re: [rtcweb] Plan for MTI video codec?

Matthew Kaufman <matthew@matthew.at> Thu, 16 October 2014 21:17 UTC

Return-Path: <matthew@matthew.at>
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 D65B11A8881 for <rtcweb@ietfa.amsl.com>; Thu, 16 Oct 2014 14:17:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level:
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HTML_MESSAGE=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 30qKy35fJvbj for <rtcweb@ietfa.amsl.com>; Thu, 16 Oct 2014 14:17:20 -0700 (PDT)
Received: from mail.eeph.com (mail.eeph.com [192.135.198.155]) by ietfa.amsl.com (Postfix) with ESMTP id 8D19D1A882F for <rtcweb@ietf.org>; Thu, 16 Oct 2014 14:17:20 -0700 (PDT)
Received: from [IPv6:2001:5a8:4:39d0:d5fe:6e06:c62e:6418] (unknown [IPv6:2001:5a8:4:39d0:d5fe:6e06:c62e:6418]) (Authenticated sender: matthew@eeph.com) by mail.eeph.com (Postfix) with ESMTPSA id 3AAEE4A047A for <rtcweb@ietf.org>; Thu, 16 Oct 2014 14:17:18 -0700 (PDT)
Message-ID: <544035DE.8000606@matthew.at>
Date: Thu, 16 Oct 2014 14:17:18 -0700
From: Matthew Kaufman <matthew@matthew.at>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: rtcweb@ietf.org
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>
In-Reply-To: <CA+9kkMAZufR7gUrwkS7Tf5GOfg+ZtsZWGcn-8YLCvnmYnTgfFw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------050307000004080905020408"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/piTAXF2pw6FcmWTWSAud7F_qyBk
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:17:22 -0000

On 10/15/2014 10:10 AM, Ted Hardie wrote:
> Hi Victor,
>
> As you may remember, we tabled discussion of video codecs back in 
> January, and said that the topic could be re-opened 6 weeks prior to 
> IETF 91.  We do anticipate discussing it at this meeting, likely in 
> the Thursday slot (since there is a related BoF earlier that day).
>

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)

Matthew Kaufman

v2.23.0 | Report a Bug | By Email