Re: [rtcweb] confirming sense of the room: mti codec

"Cavigioli, Chris" <chris.cavigioli@intel.com> Mon, 08 December 2014 18:14 UTC

Return-Path: <chris.cavigioli@intel.com>
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 0015E1ACD6B for <rtcweb@ietfa.amsl.com>; Mon, 8 Dec 2014 10:14:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 m4XqzFiJig1Z for <rtcweb@ietfa.amsl.com>; Mon, 8 Dec 2014 10:14:40 -0800 (PST)
Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by ietfa.amsl.com (Postfix) with ESMTP id 7318B1A87B2 for <rtcweb@ietf.org>; Mon, 8 Dec 2014 10:14:40 -0800 (PST)
Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 08 Dec 2014 10:14:39 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.07,539,1413270000"; d="scan'208,217";a="644360134"
Received: from orsmsx101.amr.corp.intel.com ([10.22.225.128]) by fmsmga002.fm.intel.com with ESMTP; 08 Dec 2014 10:14:39 -0800
Received: from fmsmsx102.amr.corp.intel.com (10.18.124.200) by ORSMSX101.amr.corp.intel.com (10.22.225.128) with Microsoft SMTP Server (TLS) id 14.3.195.1; Mon, 8 Dec 2014 10:14:38 -0800
Received: from fmsmsx118.amr.corp.intel.com ([169.254.1.40]) by FMSMSX102.amr.corp.intel.com ([169.254.10.94]) with mapi id 14.03.0195.001; Mon, 8 Dec 2014 10:14:39 -0800
From: "Cavigioli, Chris" <chris.cavigioli@intel.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] confirming sense of the room: mti codec
Thread-Index: AQHQExCSNiUFbQ5Va0mwaH6oHJ3FE5yF/qzQ
Date: Mon, 8 Dec 2014 18:14:38 +0000
Message-ID: <E36D1A4AE0B6AA4091F1728D584A6AD24011A566@fmsmsx118.amr.corp.intel.com>
References: <E3FA0C72-48C5-465E-AE15-EB19D8D563A7@ieca.com> <54820E74.90201@mozilla.com> <5485E627.5050706@jesup.org>
In-Reply-To: <5485E627.5050706@jesup.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.1.200.108]
Content-Type: multipart/alternative; boundary="_000_E36D1A4AE0B6AA4091F1728D584A6AD24011A566fmsmsx118amrcor_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/frWrKzs9bYKX0V_bFWF96qmVcOE
Subject: Re: [rtcweb] confirming sense of the room: mti codec
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: Mon, 08 Dec 2014 18:14:43 -0000

+1      ...fully support the consensus, even if rough and non-unanimous

Chris Cavigioli
Intel Corp, System Architecture and Planning, Video/Multimedia, Mobile and Communications Group (MCG)
*
This e-mail may contain confidential and privileged material for the sole use of the intended recipient(s).  Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.




-----Original Message-----
From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Randell Jesup
Sent: Monday, December 08, 2014 9:56 AM
To: rtcweb@ietf.org
Subject: Re: [rtcweb] confirming sense of the room: mti codec



On 12/5/2014 2:58 PM, Jean-Marc Valin wrote:

> Considering that:

> 1) We have committed to an MTI video codec

> 2) All consensus calls on "VP8 only" and "H.264 only" have failed

> 3) This is the only proposal that gets support from both camps I

> strongly support this MTI proposal.

> Please, let's close this debate once and for all. This compromise is

> by no means great, but it's much better than anything else we're going

> to get otherwise (i.e. more wasted time and still no MTI).



+1 - it's by no means my preferred solution, but it's one I can live

with, and better than the alternative of the status-quo - no MTI at all.  If it wasn't for OpenH264, my answer would be different.



I can't see adopting H.264 as sole MTI, and I can't see that we'd get consensus to adopt VP8 as sole MTI.  That basically leaves stone knives and bear skins (aka H.261) just to claim we have MTI, nothing (wild west), or this.  (Unless magically MPEG-LA changes their mind - in which case that might trigger the kickout here.)



--

Randell Jesup -- rjesup a t mozilla d o t com



_______________________________________________

rtcweb mailing list

rtcweb@ietf.org<mailto:rtcweb@ietf.org>

https://www.ietf.org/mailman/listinfo/rtcweb