IETF Logo Mail Archive

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

Adam Roach <adam@nostrum.com> Wed, 30 October 2013 18:30 UTC

Return-Path: <adam@nostrum.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 0694A21E814B for <rtcweb@ietfa.amsl.com>; Wed, 30 Oct 2013 11:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.157
X-Spam-Level:
X-Spam-Status: No, score=-102.157 tagged_above=-999 required=5 tests=[AWL=-0.157, BAYES_00=-2.599, J_CHICKENPOX_74=0.6, SPF_PASS=-0.001, 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 mYUrpvfUh7pa for <rtcweb@ietfa.amsl.com>; Wed, 30 Oct 2013 11:30:54 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8C911E8192 for <rtcweb@ietf.org>; Wed, 30 Oct 2013 11:30:53 -0700 (PDT)
Received: from orochi-2.roach.at (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r9UIUkNU028065 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 30 Oct 2013 13:30:47 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <52715051.1090206@nostrum.com>
Date: Wed, 30 Oct 2013 13:30:41 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Leon Geyser <lgeyser@gmail.com>
References: <527147FF.5010506@nostrum.com> <CAGgHUiRH81UAmLaan=MRGuk-RoJBuCJ7SsuB5516TiZcNi8FFA@mail.gmail.com>
In-Reply-To: <CAGgHUiRH81UAmLaan=MRGuk-RoJBuCJ7SsuB5516TiZcNi8FFA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 99.152.145.110 is authenticated by a trusted mechanism)
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: Wed, 30 Oct 2013 18:30:55 -0000

On 10/30/13 13:20, Leon Geyser 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.

Fortunately, as I pointed out in an earlier message, the stated 
intention of Cisco's project is to support as many platforms as the 
development community is willing to work on. In light of that fact: is 
there a specific existing and viable platform that you think cannot 
support H.264 already *and* cannot use the OpenH264 library?

If not, can you tell a credible story about how such a platform might arise?

/a

v2.23.0 | Report a Bug | By Email