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

Daniel-Constantin Mierla <miconda@gmail.com> Thu, 31 October 2013 21:08 UTC

Return-Path: <miconda@gmail.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 D981821E80A9 for <rtcweb@ietfa.amsl.com>; Thu, 31 Oct 2013 14:08:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599]
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 X0uNDo2Ihq3m for <rtcweb@ietfa.amsl.com>; Thu, 31 Oct 2013 14:08:34 -0700 (PDT)
Received: from mail-ee0-x229.google.com (mail-ee0-x229.google.com [IPv6:2a00:1450:4013:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id B134121E80FF for <rtcweb@ietf.org>; Thu, 31 Oct 2013 14:08:27 -0700 (PDT)
Received: by mail-ee0-f41.google.com with SMTP id e53so1654839eek.14 for <rtcweb@ietf.org>; Thu, 31 Oct 2013 14:08:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=dgtH1//cyFevOQOkA4FZEs8385eLyW/55P0MlVibnsM=; b=qmevsqrLwUzxHluLtACYznDF1bNFLqNvU0B7vtEibVnAIz00G0DaipJ+3iTLBe4BQe IUUJwMTRFwDN+K9Kbm09y9bZURir01X6A694i6zkNxCU71Vikf5ptaGtBrx8ENqystQq bdLqTwQGsPAop+KvFntSquh3JG6jbj0SVKVR3hqSFTQi2Jooeu0NL45cwQdA5BOLCYXi pEtrZ3wkC8DRX+NcoTGMz+6Aqeh4eiGeU04EtjcXwZVNRymR4KDNNJlvnoI+xLEQOdta O6C7PtvWtg7jxsCiEbVzEM68iWSbR0r0GIL/TB9oh2UcCFISqSo9yDQay7GdRqdbfK0E 5uhg==
X-Received: by 10.14.42.6 with SMTP id i6mr4965395eeb.65.1383253706704; Thu, 31 Oct 2013 14:08:26 -0700 (PDT)
Received: from [127.0.0.1] (ns.asipto.com. [213.133.111.169]) by mx.google.com with ESMTPSA id bn13sm14014676eeb.11.2013.10.31.14.08.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 31 Oct 2013 14:08:25 -0700 (PDT)
Message-ID: <5272C6C8.3070006@gmail.com>
Date: Thu, 31 Oct 2013 22:08:24 +0100
From: Daniel-Constantin Mierla <miconda@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: "Olle E. Johansson" <oej@edvina.net>, Neil Stratford <neils@vipadia.com>
References: <527147FF.5010506@nostrum.com> <C72DB04F-F363-45A9-A51F-31900037C239@vipadia.com> <C81F0BD3-F5E6-4E1A-955D-16D55E698BD1@edvina.net>
In-Reply-To: <C81F0BD3-F5E6-4E1A-955D-16D55E698BD1@edvina.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] On the topic of MTI video codecs
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: miconda@gmail.com
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: Thu, 31 Oct 2013 21:08:37 -0000

On 10/31/13 4:10 PM, Olle E. Johansson wrote:
> On 31 Oct 2013, at 10:02, Neil Stratford <neils@vipadia.com> wrote:
>
>> On 30 Oct 2013, at 17:55, Adam Roach <adam@nostrum.com> 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.
Downloading a binary opens doors for tons of risks, knowing that lot of 
carriers do caching or interpose themselves (e.g., it happens very 
commonly for dns to redirect you to some adds page when typing an 
invalid domain), thus is easy to replace the original source, so a 
rather complex security mechanism has to be put in place.

Even the argument that the code can be compiled and signatures compared 
is not really feasible - simply it cannot be done by mobile devices - 
they don't have the sdk installed.

I can't see an impediment for Cisco to grant the main web browsers 
(e.g., Mozilla, ...) to simply have the codec built in, using the BSD 
open sourced codec. If the webrtc is going to the masses, then the 
yearly fee cap will be reached anyhow.

For the sake of clarification, I am not in a favor of a particular video 
codec, but the one to be selected has to be embedded directly in all 
browsers, specially in those open source, for full transparency. 
Otherwise, better as Neil said, make it a plugin API so there can be 
many providers - with binary blob download, there has to be an API 
anyhow, make that the standard.

Daniel

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28
   - more details about Kamailio trainings at http://www.asipto.com -