Re: [rtcweb] H.261 vs No MTI (was: Alternative consensus and MTI video codecs)

Tim Panton <thp@westhawk.co.uk> Fri, 08 November 2013 11:34 UTC

Return-Path: <thp@westhawk.co.uk>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBAA221E80C6 for <rtcweb@ietfa.amsl.com>; Fri, 8 Nov 2013 03:34:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[AWL=0.350, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_23=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oXS08kbEuvDz for <rtcweb@ietfa.amsl.com>; Fri, 8 Nov 2013 03:34:04 -0800 (PST)
Received: from smtp002.apm-internet.net (smtp002.apm-internet.net [85.119.248.221]) by ietfa.amsl.com (Postfix) with ESMTP id 6A58421E80BE for <rtcweb@ietf.org>; Fri, 8 Nov 2013 03:34:02 -0800 (PST)
Received: (qmail 4714 invoked from network); 8 Nov 2013 11:34:01 -0000
X-AV-Scan: clean
X-APM-Authkey: 83769 4701
Received: from unknown (HELO zimbra003.verygoodemail.com) (85.119.248.218) by smtp002.apm-internet.net with SMTP; 8 Nov 2013 11:34:01 -0000
Received: from zimbra003.verygoodemail.com (localhost [127.0.0.1]) by zimbra003.verygoodemail.com (Postfix) with ESMTP id EB9EC18A0B00; Fri, 8 Nov 2013 11:34:00 +0000 (GMT)
Received: from limit.westhawk.co.uk (limit.westhawk.co.uk [192.67.4.33]) by zimbra003.verygoodemail.com (Postfix) with ESMTPSA id A733E18A0123; Fri, 8 Nov 2013 11:34:00 +0000 (GMT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_A415A316-3436-4581-855F-029C6751A3A0"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
From: Tim Panton <thp@westhawk.co.uk>
In-Reply-To: <527C7CFE.4080700@bbs.darktech.org>
Date: Fri, 8 Nov 2013 11:31:33 +0000
Message-Id: <1E0D9A14-E629-4CB2-AC67-5860B24DB7D7@westhawk.co.uk>
References: <CAAS2fgQ730sjjv5Ly0_TFmdz=ryhPN13+A69_0_MedotHGEthg@mail.gmail.com> <527C38FF.6040000@nostrum.com> <CAAS2fgSGdmFaxZ4jtYjyG9tDqKv09-L8FXSybeHrgvzNtdqYpQ@mail.gmail.com> <527C7CFE.4080700@bbs.darktech.org>
To: cowwoc <cowwoc@bbs.darktech.org>
X-Mailer: Apple Mail (2.1816)
X-Mailman-Approved-At: Fri, 08 Nov 2013 08:53:56 -0800
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] H.261 vs No MTI (was: Alternative consensus and MTI video codecs)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 08 Nov 2013 11:34:08 -0000

On 8 Nov 2013, at 05:56, cowwoc <cowwoc@bbs.darktech.org> wrote:

> 
> I'll bring up a related point that I brought up a few days ago (I changed to subject to avoid hijacking the thread).
> 
> Say we can't agree on whether to use VP8 or H.264 as MTI. We can then simply settle on a codec with expired IPR such as H.261. H.261 is the codec everyone loves to hate but allow me to point out the following:
> If H.261 is MTI, you can still upgrade to VP8
> If H.261 is MTI, you can still upgrade to H.264
> If H.261 is MTI, you can still use transcoding to connect VP8 to H.264
> Using H.261 as MTI is a big win over no MTI because "no MTI" means we're forced to do transcoding, whereas H.261 as MTI means         we can still do transcoding if we want, but we don't have to.
> And yes, I agree that a more ideal solution is to choose VP8 or H.264 as MTI (or both) than H.261... but if worse comes to worse, I don't see a benefit to choosing "no MTI" over H.261.
> Does anyone have a counter-point?
> 

Ok, I'll bite. (Despite having proposed H261 at the mic in Paris, I've changed my mind in the meanwhile.)

The H261 option makes _everyone_ equally unhappy. 

The browser makers have to support and test 2 codecs - one of which they don't want anyone to use.

The javascript folks have to do massive amounts of digging in the SDP to try and work out if the remote offer of h264 is
transcoded in a middlebox or is direct vp8 or perhaps that h261 is the best option - or perhaps no video is applicable.

The middlebox guys get to implement 3 different codecs, and test transcode paths between all of them. The video mixer guys
can't do video size switching well because h261 hasn't got that concept.

The user gets a totally variable experience based on factors she cant control. There will be lots of dissatisfied users who's
first video call happened to be h261 and never go back to the service - better to fail back to audio than connect with a poor experience.

Part of the problem is that O/A + SDP isn't a rich enough medium for the application to make a sensible/correct decision.
Given that we are stuck with OA+SDP for version 1.0 at least, lets not make it worse by complicating the SDP and degrading the 
user experience at the same time.

Sorry to be so negative. 
I'll try and come up with a more positive solution next :-)

T.


> Gili
> On 07/11/2013 9:22 PM, Gregory Maxwell wrote:
>> On Thu, Nov 7, 2013 at 5:06 PM, Adam Roach <adam@nostrum.com> wrote:
>>> Our situation is radically different: there are a number of actual arguments
>>> to be made for both options.
>> We've heard these arguments, at long length, and have, apparently, not
>> found them sufficiently decisive or we wouldn't be at this juncture.
>> 
>> I must have failed to make the point I was attempting to make
>> sufficiently clear.  Let me retry: If we believe that an MTI video
>> codec, regardless of what it is, was an independently important thing
>> to have then "no MTI" shouldn't be the result of failing to achieve an
>> MTI in discussion, because there exist _an option_, any option, to
>> achieve a MTI video codec.  So I was hoping to see any support for "no
>> MTI" (which sounded very popular in the room) to come with arguments
>> for why an MTI doesn't actually matter.
>> 
>> Without intending any "push", strong or otherwise, I'll point out that
>> the apparent difficulty in responding to my message without
>> allegations of irrational arguments and emotional investments
>> increases my estimation that locating a set of "randomly selected
>> neutral parties" which is sufficiently non-partisan to not cloud the
>> process is not obviously possible.  Without that kind of doubt in mind
>> it's not clear to me if that alternative process could be successful,
>> which is why I attempted to illustrate my point with the 4.4 coinflip.
>> Coinflip will produce a result, and the result it will produce will
>> achieve the goal of selecting an MTI codec (especially in
>> consideration of substantial support for either option, both on the list
>> and in the room), and it doesn't require selecting non-partisan
>> parties.  I wasn't trying to say it was _good_ though, only that it
>> was enough to say failure to pick an MTI alone isn't enough to justify
>> removing MTI for the sake of MTI from the goals.
>> 
>> (There are plenty of other arguments that can be made about the
>> non-optimality of the 3929 panel process— e.g. the requirement to meet
>> nomcom requirements with physical meeting attendance would generally
>> make it easy for large corporate contributors, especially ones with
>> diverse participation, to be over represented. But, to be frank, your
>> response has made me feel uncomfortable pointing that much out... I
>> didn't start this thread with an intention to argue against it, but I
>> wonder after your message if anyone else would dare.)
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

Tim Panton - Web/VoIP consultant and implementor
www.westhawk.co.uk