Re: [rtcweb] H.264 as MTI

Ron <ron@debian.org> Sat, 11 January 2014 16:41 UTC

Return-Path: <ron@debian.org>
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 B5CD01AE06D for <rtcweb@ietfa.amsl.com>; Sat, 11 Jan 2014 08:41:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 HuTzw9xx3Vg3 for <rtcweb@ietfa.amsl.com>; Sat, 11 Jan 2014 08:41:32 -0800 (PST)
Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:2:7]) by ietfa.amsl.com (Postfix) with ESMTP id 8034B1AE05B for <rtcweb@ietf.org>; Sat, 11 Jan 2014 08:41:32 -0800 (PST)
Received: from ppp118-210-34-29.lns20.adl2.internode.on.net (HELO audi.shelbyville.oz) ([118.210.34.29]) by ipmail07.adl2.internode.on.net with ESMTP; 12 Jan 2014 03:11:20 +1030
Received: from localhost (localhost [127.0.0.1]) by audi.shelbyville.oz (Postfix) with ESMTP id 0640D4F8F3 for <rtcweb@ietf.org>; Sun, 12 Jan 2014 03:11:20 +1030 (CST)
X-Virus-Scanned: Debian amavisd-new at audi.shelbyville.oz
Received: from audi.shelbyville.oz ([127.0.0.1]) by localhost (audi.shelbyville.oz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ePdtVbdY0J8E for <rtcweb@ietf.org>; Sun, 12 Jan 2014 03:11:19 +1030 (CST)
Received: by audi.shelbyville.oz (Postfix, from userid 1000) id 60F394F902; Sun, 12 Jan 2014 03:11:19 +1030 (CST)
Date: Sun, 12 Jan 2014 03:11:19 +1030
From: Ron <ron@debian.org>
To: rtcweb@ietf.org
Message-ID: <20140111164119.GC3245@audi.shelbyville.oz>
References: <CAD5OKxtqQmd0zdq5YnnsL8=q-jG3U5hMHumk0sJMQr09w1e84Q@mail.gmail.com> <AE1A6B5FD507DC4FB3C5166F3A05A4844195E339@TK5EX14MBXC295.redmond.corp.microsoft.com> <52D15760.4020904@alvestrand.no>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <52D15760.4020904@alvestrand.no>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [rtcweb] H.264 as MTI
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, 11 Jan 2014 16:41:35 -0000

On Sat, Jan 11, 2014 at 03:38:24PM +0100, Harald Alvestrand wrote:
> On 01/10/2014 08:10 PM, Matthew Kaufman (SKYPE) wrote:
> >
> > Unfortunately, you can substitute VP8 for H.264 and tweak only a
> > little of the language used in the below and have it also be true.
> >
> >
> > This being said, if [H.264] "VP8" proponents want it to be the video
> > MTI, they should work on [changing the licensing policy,] "developing
> > their video codec specifications within a recognized standards
> > organization
> 
> Coincidentally, I'm at the MPEG meeting trying to be allowed to develop
> a VP8 specification within MPEG, which probably fits the definition of
> "a recognized standards organization".
> 
> So far, it's been slow going. I've been asked multiple times whether
> it's actually worth the effort to continue trying.
> 
> Since MPEG's rules are somewhat opaque to me about what I can say in
> public about what goes on at MPEG, I'll leave it at that.


That's the fun thing about "tweaking language" to replace something
that is fundamentally relevant with something that is completely
arbitrary and pretending they are the same.

Next they'll tell you that you don't have the right school tie or
some such.

Or that this group couldn't accept a perfectly good existing RFC as
a WG document relevant here.

  Ron