Re: [rtcweb] A different perspective on the video codec MTI discussion

Andrew Allen <> Thu, 14 March 2013 02:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1A35521F8E57 for <>; Wed, 13 Mar 2013 19:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.286
X-Spam-Status: No, score=-5.286 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Wa-yRbVvRufP for <>; Wed, 13 Mar 2013 19:11:15 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D6DC621F8E55 for <>; Wed, 13 Mar 2013 19:11:14 -0700 (PDT)
X-AuditID: 0a412830-b7ef86d00000339d-6c-514131bb57c1
Received: from ( []) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by (SBG) with SMTP id 46.19.13213.BB131415; Wed, 13 Mar 2013 21:11:07 -0500 (CDT)
Received: from ([fe80::2494:a63d:e3:723b]) by ([fe80::c8f6:ae2e:c42b:3614%21]) with mapi id 14.02.0328.009; Wed, 13 Mar 2013 21:11:07 -0500
From: Andrew Allen <>
To: "" <>, "" <>
Thread-Topic: [rtcweb] A different perspective on the video codec MTI discussion
Thread-Index: AQHOIDcSOkRmQf4WtE6ygJUWSvBGGJikn90A///SE+U=
Date: Thu, 14 Mar 2013 02:11:06 +0000
Message-ID: <>
In-Reply-To: <20130314005528.1420e4e9@lminiero-acer>
Accept-Language: en-CA, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrLKsWRmVeSWpSXmKPExsXC5Zyvo7vb0DHQ4PgyY4vm58vYLbZvWcBk sfZfO7sDs8eSJT+ZPFrXz2T06Hh4nz2AOaqB0SYpsaQsODM9T9/OJjEvL78ksSRVISW1ONlW ySc1PTFHIaAosywxuVLBJbM4OScxMze1SEkhM8VWyURJoSAnMTk1NzWvxFYpsaAgNS9FyY5L AQPYAJVl5imk5iXnp2TmpdsqeQb761pYmFrqGirZ6SZ08mS8OmtacEGgYl23aQPjPt4uRk4O CQETiVlzNrJD2GISF+6tZ+ti5OIQEmhjkpjzaRozhLOZUWL5mxtgVWwCWhL7D09nArFFBBIk Hk06yAZiMwuoS9xZfA6sRlggUGLrlN2MEDVBEp/O3WGBsK0kVm06C2azCKhKrHw/C6ieg4NX wEPiQK8DSJgT6KCt0/rAxjMKyErsPnudCWK8uMStJ/OZIA4VkFiy5zwzhC0q8fLxP1YIW1Hi 797vrBD1ehI3pk6BOk1bYtnC12D1vAKCEidnPmGZwCg6C8nYWUhaZiFpmYWkZQEjyypGwdyM YgMzw+S8ZL2izFy9vNSSTYyg9OCoYbCD8f17i0OMAhyMSjy84sqOgUKsiWXFlbmHGCU4mJVE eA/KAoV4UxIrq1KL8uOLSnNSiw8xugIDYiKzFHdyPjB15ZXEGxsY4OYoifOKBIoGCgmkAxNP dmpqQWoRzBwmDk6QPVxSIsXA9JFalFhakhEPSnLxxcA0J9XAuE62UG+HwrppFnLJlx7k8YUd uckalP0oTaYu6PfcpMBrRZ/jWT7qbL6u785c3rSC6XrsgdhLKof8rjfPPT/fw+Sylr8+NwOD nVyl9vQ2ZU4pkeWcd+oKnndUHZ7DU9zqnyCZxGCpLRvjXy2UIWdTp//m9i5Rzn2PL+vtmhIx Re1H6Iet9guUWIozEg21mIuKEwFi0L4oUAMAAA==
Cc: "" <>
Subject: Re: [rtcweb] A different perspective on the video codec MTI discussion
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, 14 Mar 2013 02:11:16 -0000


A good piece of advice when shopping is to always beware of the places where the price is not well advertised - the fact that the price is not known in advance does not mean its free - and often quite the opposite!


----- Original Message -----
From: Lorenzo Miniero []
Sent: Wednesday, March 13, 2013 06:55 PM Central Standard Time
To: Jonathan Rosenberg <>
Cc: <>
Subject: Re: [rtcweb] A different perspective on the video codec MTI discussion

Il giorno Wed, 13 Mar 2013 18:06:47 -0400
Jonathan Rosenberg <> ha scritto:

> I have one more thing to say - speaking now as a developer.
> As some of you may know, I recently returned to Cisco as CTO of the
> cloud collaboration group, which is responsible for Webex. Webex was
> one of the first services to do voice and video on the web, using
> plugins of course. For our business, a key requirement is
> interoperability with other video systems in the Cisco portfolio,
> including our video clients and telepresence units. Those are all
> based on H.264. Consequently, much as I would like to avoid the need
> for a plugin, the benefits of eliminating the plugin do not outweigh
> the drawbacks of having to transcode from VP8 to H.264. If IETF
> selects VP8 as the MTI codec, this will make it dramatically more
> difficult and expensive for us to use webRTC. If H.264 is the MIT
> codec, it will make it much easier for us to use webRTC.

Speaking as a developer working for a company with much less money than
yours, if the IETF selects H.264 as the MTI codec, this will make it
even more dramatically difficult and expensive (if not impossible) for
pretty much everybody else to use webRTC, or at least to develop
services based on it.


Lorenzo Miniero, COB

Meetecho s.r.l.
Web Conferencing and Collaboration Tools
rtcweb mailing list

This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.