IETF Logo Mail Archive

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

"Olle E. Johansson" <oej@edvina.net> Thu, 31 October 2013 09:36 UTC

Return-Path: <oej@edvina.net>
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 217AD21E80D1 for <rtcweb@ietfa.amsl.com>; Thu, 31 Oct 2013 02:36:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.081
X-Spam-Level:
X-Spam-Status: No, score=-2.081 tagged_above=-999 required=5 tests=[AWL=-0.082, BAYES_00=-2.599, J_CHICKENPOX_74=0.6]
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 LF+tZBxtOgmD for <rtcweb@ietfa.amsl.com>; Thu, 31 Oct 2013 02:36:00 -0700 (PDT)
Received: from smtp7.webway.se (smtp7.webway.se [IPv6:2a02:920:212e::205]) by ietfa.amsl.com (Postfix) with ESMTP id 2BAE421E80A1 for <rtcweb@ietf.org>; Thu, 31 Oct 2013 02:35:51 -0700 (PDT)
Received: from [192.168.40.22] (h87-96-134-129.dynamic.se.alltele.net [87.96.134.129]) by smtp7.webway.se (Postfix) with ESMTPA id B8CDD93C2A2; Thu, 31 Oct 2013 09:35:50 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
From: "Olle E. Johansson" <oej@edvina.net>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB123CFB76A@xmb-aln-x02.cisco.com>
Date: Thu, 31 Oct 2013 10:35:49 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B1C09EEE-5862-4D33-8CCC-F458D467B846@edvina.net>
References: <527147FF.5010506@nostrum.com> <CAGgHUiRH81UAmLaan=MRGuk-RoJBuCJ7SsuB5516TiZcNi8FFA@mail.gmail.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123CFB76A@xmb-aln-x02.cisco.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
X-Mailer: Apple Mail (2.1816)
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
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 09:36:10 -0000

On 30 Oct 2013, at 22:40, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote:

> 
> On Oct 30, 2013, at 12:20 PM, Leon Geyser <lgeyser@gmail.com> wrote:
> 
>> Unfortunately like Jonathan pointed out H.264 will only be able to be used royalty free on certain(most popular) platforms.
>> To be able to avoid negotiation failure we need a MTI codec that every potential now/future browser would be able to implement freely.
>> I like what Cisco did, but the solution seems a bit half-baked.
>> 
> 
> I think that Mozilla put it pretty nicely in their blog. What this annoucement gives us is not a perfect world. Mozilla is working towards a better future but in the mean time, this is the best thing we could possibly figure out on how to make the internet today be the best it can be for users. 
> 

For the Open Source community in general I beleve this is a big move forward and I want to thank everyone involved in getting this done. It can not have been an easy internal struggle through all layers of the company. Everyone will benefit from it.

For us in the Asterisk community I believe this opens up for use of video in a whole new way. I've been struggling to find legal ways to do things like video IVR for many years. The experiences we get from working with this will lead to new applications, regardless of which codecs we use in the future.

This statement is outside of the discussion of MTI for webrtc though. I still haven't sorted up my views of that part of the discussion... 

/O

v2.23.0 | Report a Bug | By Email