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

Eric Rescorla <ekr@rtfm.com> Mon, 16 December 2013 05:50 UTC

Return-Path: <ekr@rtfm.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 D56B61AE0EB for <rtcweb@ietfa.amsl.com>; Sun, 15 Dec 2013 21:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, 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 7dq4ie0vw04d for <rtcweb@ietfa.amsl.com>; Sun, 15 Dec 2013 21:50:54 -0800 (PST)
Received: from mail-we0-f174.google.com (mail-we0-f174.google.com [74.125.82.174]) by ietfa.amsl.com (Postfix) with ESMTP id 710751AE104 for <rtcweb@ietf.org>; Sun, 15 Dec 2013 21:50:53 -0800 (PST)
Received: by mail-we0-f174.google.com with SMTP id q58so4058707wes.5 for <rtcweb@ietf.org>; Sun, 15 Dec 2013 21:50:52 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=EC92tjYZk+GeoBVBKS4EBYI0k3FU4MflYdR8DBTZQJE=; b=PwfIn2udvIhkUAq+Qp2DHU4bCMSemcM58+0rN1C+mEtf2mUnD+OeIo5PNtpz52lZMz IGdrddc3rl9bn8n9ud3heQ00No4FgXatEBlz8ZGeZN8Oc+vpLmLqEf9OdgNat8Gwuyqc BoGMMSmsaWqR2LcJr9tLjCz0qO5I5pbzPSyQls6y9itTpeCqjv9NIu1IlolEagAT8NSM V39DrV6Er7I64Tv5QY1QARNZZk9FSbSGhPbuVskXCfAe8hdgjx1zsjX2Kzp5s8uFg9wf nye0NKw+BVBiqMEq5URbEPxU4kDXDA5nhDV9kM+TkpXPDyJlSUEEDUR72XiSnyOvHB63 tP5A==
X-Gm-Message-State: ALoCoQmqonMy7NXoOoTWZzEC6CEZzoP2/NLPldtjoyxQTZ9utK696URgqe6tEGJFVlj7RG2XPg/g
X-Received: by 10.194.77.202 with SMTP id u10mr11893576wjw.39.1387173052461; Sun, 15 Dec 2013 21:50:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.54.194 with HTTP; Sun, 15 Dec 2013 21:50:12 -0800 (PST)
X-Originating-IP: [74.95.2.168]
In-Reply-To: <52AE9129.8090702@bbs.darktech.org>
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> <52AE9129.8090702@bbs.darktech.org>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 15 Dec 2013 21:50:12 -0800
Message-ID: <CABcZeBPOxqa2YQxOrTp9sVF-tQrpg-Kn=CbazBXOx_9dajhUZA@mail.gmail.com>
To: cowwoc <cowwoc@bbs.darktech.org>
Content-Type: text/plain; charset="ISO-8859-1"
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:50:58 -0000

Gili writes:
>  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.

At the risk of pressing the point, this seems like it would be a good
time for you to explicitly retract your comments about the motives of
H.264 proponents.


> 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

Well, as I've said a number of times, there are people who are
in favor of H.264 because they care about interop with non-WebRTC
H.264 devices. I realize that that's not yet appeared in the
survey results, but it was in JDR's presentation at IETF and
we've only seen a very small number of results.


> 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"?

No, because "you" is different people.

To take a simple example, consider the case of a browser which
implements VP8-only. Clearly, the browser has no H.264 IPR risk, at
the cost of not being able to talk to people who do H.264. However, If
someone else (say a conferencing system) decides to build a system
with a VP8-H.264 transcoder, then *they* are the person incurring the
IPR risk. That's really not the same thing at all.

I'm certainly not suggesting that no-MTI is a good thing, but it
isn't the same as MTI-X from the perspective of IPR exposure.

-Ekr