IETF Logo Mail Archive

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

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Wed, 30 October 2013 21:40 UTC

Return-Path: <fluffy@cisco.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 9D81211E8286 for <rtcweb@ietfa.amsl.com>; Wed, 30 Oct 2013 14:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.299
X-Spam-Level:
X-Spam-Status: No, score=-110.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_74=0.6, 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 DgeAD4tqLe1n for <rtcweb@ietfa.amsl.com>; Wed, 30 Oct 2013 14:40:12 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id F050211E8244 for <rtcweb@ietf.org>; Wed, 30 Oct 2013 14:40:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=729; q=dns/txt; s=iport; t=1383169209; x=1384378809; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=X6iIZcGjMuWKzlUjXcj04SjNlOTZZzZmawMs5ZqISUE=; b=lF2wM1seZQmUapdMrL7e2FJIqTzb6zTd5nYvOrFB/6xEgkCBR3r/MR+c nC5hW8Yg9u8PqzBCSR43QevjPCQ6mjdtt4swrYrwadoqrz2f8G8MI6ygt kTKI6/PHkuHJiEMx3pIwZbxdGmzdHL/AKP1I89q0YjhH1hkPXaGoYnLon A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFAAN8cVKtJV2b/2dsb2JhbABZgweBDL9XAQmBKhZ0giUBAQEDAXkFCwIBCA4UJCERJQIEDgUIE4daAwkGsQ0NiWuMX4I9AjEHgx+BDQOJB40Yjj2FN4Mmgio
X-IronPort-AV: E=Sophos;i="4.93,604,1378857600"; d="scan'208";a="278677597"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-7.cisco.com with ESMTP; 30 Oct 2013 21:40:08 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r9ULe8Jd003439 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 30 Oct 2013 21:40:08 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.143]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.004; Wed, 30 Oct 2013 16:40:08 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Leon Geyser <lgeyser@gmail.com>
Thread-Topic: [rtcweb] On the topic of MTI video codecs
Thread-Index: AQHO1bia3d+Iz9aO0UWTLuasWULgLg==
Date: Wed, 30 Oct 2013 21:40:08 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB123CFB76A@xmb-aln-x02.cisco.com>
References: <527147FF.5010506@nostrum.com> <CAGgHUiRH81UAmLaan=MRGuk-RoJBuCJ7SsuB5516TiZcNi8FFA@mail.gmail.com>
In-Reply-To: <CAGgHUiRH81UAmLaan=MRGuk-RoJBuCJ7SsuB5516TiZcNi8FFA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <69FC795EA726F6448D259BF054BAAD7C@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 21:40:23 -0000

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.

v2.8.7 | Report a Bug | By Email