Re: [rtcweb] Proposed Video Selection Process

Basil Mohamed Gohar <> Thu, 21 November 2013 21:54 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id C4ED31AE1F5 for <>; Thu, 21 Nov 2013 13:54:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id INlix65v4JZg for <>; Thu, 21 Nov 2013 13:54:13 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 859FF1AE1D6 for <>; Thu, 21 Nov 2013 13:54:13 -0800 (PST)
Received: from [] ( []) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: by (Postfix) with ESMTPSA id 732AD659871 for <>; Thu, 21 Nov 2013 16:54:06 -0500 (EST)
Message-ID: <>
Date: Thu, 21 Nov 2013 16:54:03 -0500
From: Basil Mohamed Gohar <>
Organization: Libre Video
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
To: "" <>
References: <> <> <> <> <> <20131121204147.GV3245@audi.shelbyville.oz> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] Proposed Video Selection Process
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 21 Nov 2013 21:54:16 -0000

On 11/21/2013 04:14 PM, Eric Rescorla wrote:
> Agreed.
> To take a not-so-random example, given that Firefox will soon
> support both H.264 and VP8, what additional implementations
> will it be able to talk to if it does H.261?
> -Ekr

(I apparently replied only to Ekr, and not the whole list originally)

None, but that's not the point.  Firefox is a special case for which VP8
is not considered a legal liability (by Mozilla) and they can be
satisfied, for the most part, by Cisco's proposal with OpenH264 as a
downloadable plugin/module.

So, this doesn't open up anything for Firefox that it is not already
planning to handle.

What it does open up is for, say, a small firm that cannot afford H.264
licensing, and cannot make use of Cisco's binary plugin for legal or
technical reasons, and can only implement VP8 and H.261, and, say, a
device whose manufacturers do not wish to implement VP8 for perceived
IPR risk but already license H.264.

Both cases above have an H.261 implementation that will allow mutual
video, even though they do not share a common high-end codec implementation.

There are cases outside of browsers that are interested in rtcweb, after

Libre Video