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

"Cavigioli, Chris" <> Tue, 09 December 2014 05:56 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 0AE171A1BFC for <>; Mon, 8 Dec 2014 21:56:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id akDgb1QKjslu for <>; Mon, 8 Dec 2014 21:56:01 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 3D4261A1BF8 for <>; Mon, 8 Dec 2014 21:56:00 -0800 (PST)
Received: from ([]) by with ESMTP; 08 Dec 2014 21:55:24 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.97,862,1389772800"; d="scan'208";a="426768464"
Received: from ([]) by with ESMTP; 08 Dec 2014 21:44:47 -0800
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Mon, 8 Dec 2014 21:55:24 -0800
Received: from ([]) by ([]) with mapi id 14.03.0195.001; Mon, 8 Dec 2014 21:55:23 -0800
From: "Cavigioli, Chris" <>
To: "" <>
Thread-Topic: [rtcweb] confirming sense of the room: mti codec
Thread-Index: AQHQE04qEBti1FXXNkmH1ALOez9gJ5yGwRTA
Date: Tue, 09 Dec 2014 05:55:23 +0000
Message-ID: <>
References: <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [rtcweb] confirming sense of the room: mti codec
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 09 Dec 2014 05:56:03 -0000

I like that proposal, Dave.

+1    INTEL CORP has already implemented both H.264 and VP8 ... both encode and decode.   Done.   

We already demonstrated hardware WebRTC to the public at MWC'14 in Barcelona in February on our smartphone platform.   Done.

We welcome the consensus decision made by IETF and look forward to moving forward with WebRTC.

-----Original Message-----
From: rtcweb [] On Behalf Of David Singer
Sent: Monday, December 08, 2014 5:19 PM
Subject: Re: [rtcweb] confirming sense of the room: mti codec

> On Dec 8, 2014, at 10:00 , Iñaki Baz Castillo <> wrote:
> 2014-12-08 18:55 GMT+01:00 Randell Jesup <>:
>> +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.
> There was a much better solution:
> - Don't make VP8 nor H264 MTI.
> - So for now no MTI video codec.
> - And a W3C compromise: First video codec 100% royalty free would 
> become MTI in WebRTC.
> Things would be exactly as they are now, but at least we avoid a 
> "MUST" that will be ignored by 50% of the market.

That would be more honest, indeed. It is effectively where we are going to be.  And it offers a carrot in the right direction.

I am curious to know how many of the people supporting the proposed position actually would implement both encode and decode of both codecs?  This follows from comments on this thread that people who feel they fall into a different category are asking others to solve their problem.

So, rather than +1, please say “I would expect to implement both” (non-binding, of course) — it would be a more useful thing to see, I think.

Another possible choice:

* admit that we already have possible non-interoperability (WebRTC-compatible Endpoints that choose differently), and that anyone who doesn’t want to do both will say that this what they are making (as was suggested):  simply delete the requirement or definitions for WebRTC User-agent and Device. Nothing stops those that want to from implementing both, without or without the mandate.  I don’t think this would make any material difference to what happens, but it makes the spec and reality a little closer.

Finally, I wonder, what would it be like if we actually tried to get closer to interop: ALL endpoints — anything that can operate at one end of a WebRTC session, be it device, UA, gateway, compatible-endpoint, whatever — must be able to decode (actually, offer to receive) both, and must be able to encode at least one?  I’d have to think about the consequences of doing decode-only, but it’s a loss less work than a decent encoder, for a start. This would result in interop if people actually did it.

David Singer
Manager, Software Standards, Apple Inc.

rtcweb mailing list