IETF Logo Mail Archive

Re: [rtcweb] MTI Video Codec: a novel proposal

Adam Roach <adam@nostrum.com> Tue, 11 November 2014 20:46 UTC

Return-Path: <adam@nostrum.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 9080C1A913E for <rtcweb@ietfa.amsl.com>; Tue, 11 Nov 2014 12:46:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.494
X-Spam-Level:
X-Spam-Status: No, score=-2.494 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.594] 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 W0b-Ikrcv31L for <rtcweb@ietfa.amsl.com>; Tue, 11 Nov 2014 12:46:45 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 42A801A9108 for <rtcweb@ietf.org>; Tue, 11 Nov 2014 12:46:45 -0800 (PST)
Received: from dhcp-b419.meeting.ietf.org (dhcp-b419.meeting.ietf.org [31.133.180.25]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id sABKkdNi067836 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Nov 2014 14:46:40 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <546275AF.10006@nostrum.com>
Date: Tue, 11 Nov 2014 10:46:39 -1000
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Ron <ron@debian.org>, rtcweb@ietf.org
References: <54611529.7010007@nostrum.com> <BBF5DDFE515C3946BC18D733B20DAD2339956982@XMB122CNC.rim.net> <20141111194603.GU8092@hex.shelbyville.oz>
In-Reply-To: <20141111194603.GU8092@hex.shelbyville.oz>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/1kWgXLfCzUQX3p5ZYgqTd7MICC4
Subject: Re: [rtcweb] MTI Video Codec: a novel proposal
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: Tue, 11 Nov 2014 20:46:46 -0000

On 11/11/14 09:46, Ron wrote:
> Possibly the only outcome that would have our bowl of petunias thinking
> "Oh no, not again" would be if team H.264 bottles it on the eve of an
> RF announcement for VP8 by ISO and declares their codec to be also RF
> at the same time.  Which might be good for the world in general, but
> would leave us back at a stalemate again over our decision trigger.

This scenario certainly came up in thinking about the possible solution 
space. I simply filed it off into the "problems I wish I had" bucket and 
moved on. Given how remote this possibility is, I think we can cross 
this bridge when we come to it.

/a

v2.23.0 | Report a Bug | By Email