IETF Logo Mail Archive

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

Lorenzo Miniero <lorenzo@meetecho.com> Wed, 13 March 2013 23:55 UTC

Return-Path: <lorenzo@meetecho.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6EAA21F8C1F for <rtcweb@ietfa.amsl.com>; Wed, 13 Mar 2013 16:55:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level:
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MIrGqCKzKsZz for <rtcweb@ietfa.amsl.com>; Wed, 13 Mar 2013 16:55:46 -0700 (PDT)
Received: from smtpdg10.aruba.it (smtpdg5.aruba.it [62.149.158.235]) by ietfa.amsl.com (Postfix) with ESMTP id 323E821F8C1A for <rtcweb@ietf.org>; Wed, 13 Mar 2013 16:55:44 -0700 (PDT)
Received: from lminiero-acer ([130.129.133.212]) by smtpcmd05.ad.aruba.it with bizsmtp id BBvg1l00M4b720a01BvhkM; Thu, 14 Mar 2013 00:55:42 +0100
Date: Thu, 14 Mar 2013 00:55:28 +0100
From: Lorenzo Miniero <lorenzo@meetecho.com>
To: Jonathan Rosenberg <jdrosen@jdrosen.net>
Message-ID: <20130314005528.1420e4e9@lminiero-acer>
In-Reply-To: <CA+23+fE3WRs5SxAUcsjWbxcjzQKxCtW7sdfHtAsbd7MbPyHAtQ@mail.gmail.com>
References: <CA+23+fE3WRs5SxAUcsjWbxcjzQKxCtW7sdfHtAsbd7MbPyHAtQ@mail.gmail.com>
Organization: Meetecho
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.0; i386-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] A different perspective on the video codec MTI discussion
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 13 Mar 2013 23:55:46 -0000

Il giorno Wed, 13 Mar 2013 18:06:47 -0400
Jonathan Rosenberg <jdrosen@jdrosen.net> 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

-- 
Lorenzo Miniero, COB

Meetecho s.r.l.
Web Conferencing and Collaboration Tools
http://www.meetecho.com

v2.23.0 | Report a Bug | By Email