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

Harald Alvestrand <harald@alvestrand.no> Fri, 15 March 2013 18:31 UTC

Return-Path: <harald@alvestrand.no>
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 6F65721F8667 for <rtcweb@ietfa.amsl.com>; Fri, 15 Mar 2013 11:31:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 96OyKUyjo0U3 for <rtcweb@ietfa.amsl.com>; Fri, 15 Mar 2013 11:31:26 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 2A18121F867B for <rtcweb@ietf.org>; Fri, 15 Mar 2013 11:31:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 0DB1839E23A; Fri, 15 Mar 2013 19:31:17 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zklXZbGDg5HO; Fri, 15 Mar 2013 19:31:16 +0100 (CET)
Received: from [IPv6:2001:470:de0a:27:dc4b:da73:da24:d309] (unknown [IPv6:2001:470:de0a:27:dc4b:da73:da24:d309]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 36AA839E03A; Fri, 15 Mar 2013 19:31:16 +0100 (CET)
Message-ID: <514368F3.2010401@alvestrand.no>
Date: Fri, 15 Mar 2013 19:31:15 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130221 Thunderbird/17.0.3
MIME-Version: 1.0
To: Daryl Malas <D.Malas@cablelabs.com>
References: <FEA80D86BEEC134D88CA45E53A0D3408180DA31B@EXCHANGE.cablelabs.com>
In-Reply-To: <FEA80D86BEEC134D88CA45E53A0D3408180DA31B@EXCHANGE.cablelabs.com>
Content-Type: multipart/alternative; boundary="------------080607000506020900030108"
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: Fri, 15 Mar 2013 18:31:26 -0000

On 03/14/2013 05:18 AM, Daryl Malas wrote:
> I would like to add my support to Jonathan's comments.  I have had 
> discussions with multiple cable operators, which are evaluating the 
> potential use cases of deploying webRTC.  The resounding comment is 
> that if webRTC supports H.264, their flexibility to deploy it in the 
> near-term on a number of devices improves dramatically.  If VP8 is the 
> only allowable codec, this will significantly limit the deployment, 
> because the relevant devices out there already support H.264 and not VP8.
Repeat message: There will never be a restriction on additional codecs.
It's a business decision by product vendors which codecs they offer in 
addition to the MTI.