Re: [rtcweb] H.264's high-low play (Was: H.264 IPR disclosures (or persistent lack thereof))

cowwoc <cowwoc@bbs.darktech.org> Mon, 16 December 2013 05:36 UTC

Return-Path: <cowwoc@bbs.darktech.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 49B391AE0EB for <rtcweb@ietfa.amsl.com>; Sun, 15 Dec 2013 21:36:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 MqkBXx0c1lso for <rtcweb@ietfa.amsl.com>; Sun, 15 Dec 2013 21:36:08 -0800 (PST)
Received: from mail-ie0-f169.google.com (mail-ie0-f169.google.com [209.85.223.169]) by ietfa.amsl.com (Postfix) with ESMTP id 04A391AE08D for <rtcweb@ietf.org>; Sun, 15 Dec 2013 21:36:07 -0800 (PST)
Received: by mail-ie0-f169.google.com with SMTP id e14so5962652iej.0 for <rtcweb@ietf.org>; Sun, 15 Dec 2013 21:36:07 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=3Ggi0yU9s8CILx+67XvaR8RpkUmQMaTmcUmi2tk7AE0=; b=MRh52EP584kGjC7SYSBZORKVUdsTeqkLc9TFGmSvEQg3Q2noZp/z7W5ukqNAhD4uxm 2oWoTB2QDbephBMtfgTl7RUDJ1dLaG6fTqnHfx8EbdfNRPSOOOv9YBdKYWW0wTOfUAQl //vEyaxo3+ft3mu+oHWAGDLMcNo3xKK4qc+2w+qh1mcvR1I+xH+/uuJEn9tIYAWB0iUr 44foZmWHBGq0HzQx2KMYkoSff1qWX2cmvwBJ5D2ZNii0T0qYdSeMHTxo65psTo+yzvNv Ol2yy/u2ewiOfG9ScpkUFcmUhzgrBN0WyEbK7wkCWBpWPOcSi/1nwtURuRSuuN0MTSf/ sfXw==
X-Gm-Message-State: ALoCoQkNiGhjfHDj6CjCpMGHREwwACulj0HEfqJnuEfEMxGSMIZZo9fVUoENIg2bTF7nWau0YgOa
X-Received: by 10.43.138.8 with SMTP id iq8mr10787370icc.37.1387172166964; Sun, 15 Dec 2013 21:36:06 -0800 (PST)
Received: from [192.168.1.100] (206-248-171-209.dsl.teksavvy.com. [206.248.171.209]) by mx.google.com with ESMTPSA id da14sm14509994igc.1.2013.12.15.21.36.05 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 15 Dec 2013 21:36:06 -0800 (PST)
Message-ID: <52AE9129.8090702@bbs.darktech.org>
Date: Mon, 16 Dec 2013 00:35:37 -0500
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Eric Rescorla <ekr@rtfm.com>
References: <949EF20990823C4C85C18D59AA11AD8B0F88D6@FR712WXCHMBA11.zeu.alcatel-lucent.com> <20131213033344.GW3245@audi.shelbyville.oz> <CECFF758.205FF%mzanaty@cisco.com> <E44893DD4E290745BB608EB23FDDB7620A16219B@008-AM1MPN1-042.mgdnok.nokia.com> <20131214102855.GY3245@audi.shelbyville.oz> <20131214122049.604352b3@rainpc> <20131214132520.GZ3245@audi.shelbyville.oz> <52AC7B89.3030103@bbs.darktech.org> <CAMwTW+g6q0gRbdioEkw8aUjpBY1s=V=sHbPNXaebFbhr6WihJQ@mail.gmail.com> <CABcZeBNx5wpKDgd6TgA9U3_nxEKXdCsXpo8Kp663yQ6e_iN9vQ@mail.gmail.com> <20131215075757.GB3245@audi.shelbyville.oz> <52AE54F8.5070300@bbs.darktech.org> <CABcZeBNqE25O+BNLboXDrJ1ypp26uRAw8ehwtyor9gJccpuzGw@mail.gmail.com> <52AE759C.7020209@bbs.darktech.org> <CABcZeBMjTGs41t7y=xvaLdn4i63HxC2YQUkrd-itq=VkuKvpTA@mail.gmail.com>
In-Reply-To: <CABcZeBMjTGs41t7y=xvaLdn4i63HxC2YQUkrd-itq=VkuKvpTA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------050904040908020405060000"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] H.264's high-low play (Was: H.264 IPR disclosures (or persistent lack thereof))
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: Mon, 16 Dec 2013 05:36:13 -0000

On 15/12/2013 11:04 PM, Eric Rescorla wrote:
> On Sun, Dec 15, 2013 at 7:38 PM, cowwoc <cowwoc@bbs.darktech.org> wrote:
>> I've seen multiple VP8 proponents rate the following options as Acceptable:
>>
>> H.261 as MTI
>> Theora as MTI
>> Implement two of [H.261, H.264, VP8] as MTI
>>
>> They might not love the option but they are willing to accept it as a
>> compromise. On the flip side, I've seen multiple H.264 backers rate "H.264 s
>> MTI" as "Yes" and all other options as "No". They did not include a single
>> option as "Acceptable".
> You might try taking a closer look at the survey results. I'm not a mind-reader
> so I don't know what an "H.264 backer" is, but the following people voted
> positively for H.264 and negatively for VP8. I've listed their votes below
> (accreting Yes and Acceptable, since the difference doesn't seem relevant
> here):
>
> Stefan Hakkansson   (264, None, 2/3 [VP8, H263, H.264], 263)
> Bernard Aboba (264 only)
> Sal Loreto (264, None, 263 only)
>
> Perhaps I missed some, since I just went by responses to the thread, but this
> seems sufficient to demonstrate that your characterization of the data isn't
> accurate.
On second thought, I think you're right.

Based on the limited number of straw poll votes cast so far, people 
objected to codecs for one of two reasons:

  * IPR concerns
  * Video quality

VP8 proponents objected to H.264 (and H.263) for IPR reasons, and H.264 
proponents objected to VP8 for IPR reasons.
Some people objected to the use of older codecs for video quality 
reasons (if I remember correctly, VP8 proponents were more willing to 
accept a lower-quality codec than H.264 proponents)
Both objections (IPR and video quality) are quite reasonable.
(I don't view "None" as a compromise. Anyone voting for this is not 
giving anything up. They are saying "I'll do what I want, and you do 
what you want" and they do so at the cost of interoperability.)

At the end of the day, I don't think there is a "right answer" for 
everyone because one business might trade legal risk for high-quality 
video, while another will prefer to trade video quality for reduced 
legal risk. This is a subjective decision which is best left up to the 
business. At the same time, I think the interoperability requirement 
should outweigh this.

Consider what will happen if we end up with "No MTI". Some devices will 
support VP8, others will support H.264. Do people realize that sticking 
a transcoder in the middle exposes you to the exact same IPR risks that 
they are complaining about? I mean, H.264 folks will be force to 
implement VP8 in the transcoder, and VP8 folks will be forced to 
implement H.264 in the transcoder. Doesn't this open you up to the same 
IPR risk as "Both H.264 and VP8 are MTI"?

Gili