IETF Logo Mail Archive

Re: [rtcweb] MTI Video Codec: a novel proposal

Florian Weimer <fw@deneb.enyo.de> Sat, 15 November 2014 21:05 UTC

Return-Path: <fw@deneb.enyo.de>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 096651A6FEB for <rtcweb@ietfa.amsl.com>; Sat, 15 Nov 2014 13:05:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.144
X-Spam-Level:
X-Spam-Status: No, score=-2.144 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.594] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1RHiyWLnU0EM for <rtcweb@ietfa.amsl.com>; Sat, 15 Nov 2014 13:05:01 -0800 (PST)
Received: from albireo.enyo.de (albireo.enyo.de [46.237.207.196]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61D591A6FEE for <rtcweb@ietf.org>; Sat, 15 Nov 2014 13:05:00 -0800 (PST)
Received: from [172.17.203.2] (helo=deneb.enyo.de) by albireo.enyo.de with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) id 1XpkWf-0008Gf-AA; Sat, 15 Nov 2014 22:04:57 +0100
Received: from fw by deneb.enyo.de with local (Exim 4.80) (envelope-from <fw@deneb.enyo.de>) id 1XpkWf-0007bc-2Q; Sat, 15 Nov 2014 22:04:57 +0100
From: Florian Weimer <fw@deneb.enyo.de>
To: Gaelle Martin-Cocher <gmartincocher@blackberry.com>
References: <54601E19.8080203@nostrum.com> <92D0D52F3A63344CA478CF12DB0648AADF312676@XMB111CNC.rim.net>
Date: Sat, 15 Nov 2014 22:04:57 +0100
In-Reply-To: <92D0D52F3A63344CA478CF12DB0648AADF312676@XMB111CNC.rim.net> (Gaelle Martin-Cocher's message of "Tue, 11 Nov 2014 22:41:02 +0000")
Message-ID: <87egt45g5i.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/V5Xli-y1RxNSf9qb7RS2lQasAYY
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] MTI Video Codec: a novel proposal
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 15 Nov 2014 21:05:05 -0000

* Gaelle Martin-Cocher:

> Some device/OS vendors have released API to hardware supported codec
> (BlackBerry included). One of the goal is to offer codec access
> without additional cost to non-platform-native
> UA/browser/device/non-browser, hence maximizing interoperability for
> WebRTC endpoints. And without having multiple occurrences of codecs
> being loaded on the platform.

The API maybe there, but it does not necessarily confer a patent
license to application developers, just like a patent license obtained
by a WebRTC implementor does not necessarily extend to a service that
integrates WebRTC.

v2.23.0 | Report a Bug | By Email