Re: [rtcweb] On the topic of MTI video codecs

"Olle E. Johansson" <> Thu, 31 October 2013 15:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E0EF821E8099 for <>; Thu, 31 Oct 2013 08:10:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.354
X-Spam-Status: No, score=-2.354 tagged_above=-999 required=5 tests=[AWL=0.245, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 1UZHkfVxFFAc for <>; Thu, 31 Oct 2013 08:10:29 -0700 (PDT)
Received: from ( [IPv6:2a02:920:212e::205]) by (Postfix) with ESMTP id 1B95C21E808F for <>; Thu, 31 Oct 2013 08:10:28 -0700 (PDT)
Received: from [] ( []) by (Postfix) with ESMTPA id 11EFD93C2A3; Thu, 31 Oct 2013 15:10:28 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
From: "Olle E. Johansson" <>
In-Reply-To: <>
Date: Thu, 31 Oct 2013 16:10:27 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
To: Neil Stratford <>
X-Mailer: Apple Mail (2.1816)
Cc: "" <>
Subject: Re: [rtcweb] On the topic of MTI video codecs
X-Mailman-Version: 2.1.12
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, 31 Oct 2013 15:10:30 -0000

On 31 Oct 2013, at 10:02, Neil Stratford <> wrote:

> On 30 Oct 2013, at 17:55, Adam Roach <> wrote:
>> As Jonathan mentioned earlier, this morning Cisco announced that it will be open sourcing an H.264 implementation as well as gratis binary modules compiled from that source and hosted by Cisco for download. Mozilla will be modifying Firefox to support H.264 by downloading Cisco's binary module.
> It seems like most of the groundwork is being done here for a real codec plugin API which would obviate the need for any particular codec to be selected as MTI.
> Can we encourage this new codec plugin API to be developed in an open way as part of the standards process and therefore be supported in all browsers? (Enabling for example the addition of VP8 to a browser that may not natively ship with it.)

I don't agree. The idea was to create a realtime web platform without the need for any plugins or downloadable modules. We've had that for ages and it is not a good solution.

I am still for a MTI codec or set of codecs so we always can set up video calls, regardless of implementation and if it's possible to download by policy or network conditions a specific binary.