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

Andrew Allen <> Mon, 08 December 2014 18:35 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 75E561ACD76 for <>; Mon, 8 Dec 2014 10:35:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id WCJi9jl95fgV for <>; Mon, 8 Dec 2014 10:35:08 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 7B2771ACD70 for <>; Mon, 8 Dec 2014 10:35:06 -0800 (PST)
Received: from ([]) by with ESMTP/TLS/AES128-SHA; 08 Dec 2014 13:34:59 -0500
Received: from ([fe80::28c6:fa1c:91c6:2e23]) by ([fe80::d824:6c98:60dc:3918%16]) with mapi id 14.03.0210.002; Mon, 8 Dec 2014 13:34:59 -0500
From: Andrew Allen <>
To: Roman Shpount <>, Harald Alvestrand <>
Thread-Topic: [rtcweb] confirming sense of the room: mti codec
Thread-Index: AQHQEJCKEBti1FXXNkmH1ALOez9gJ5yGNFiAgAAoiQD//6yQEA==
Date: Mon, 08 Dec 2014 18:34:58 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-CA, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_BBF5DDFE515C3946BC18D733B20DAD233998A6A5XMB122CNCrimnet_"
MIME-Version: 1.0
Cc: "" <>
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: Mon, 08 Dec 2014 18:35:10 -0000

I think it’s pretty clear from my statements in the IETF session on this topic and on this list that I don’t support having two MTI  video codecs for any WebRTC entity and I don’t think it is technically justified. But I state this here formally.

From: rtcweb [] On Behalf Of Roman Shpount
Sent: Monday, December 08, 2014 1:31 PM
To: Harald Alvestrand
Subject: Re: [rtcweb] confirming sense of the room: mti codec

I support the rough consensus as presented by the chair.

Roman Shpount

On Mon, Dec 8, 2014 at 11:05 AM, Harald Alvestrand <<>> wrote:
Since others who were present in the room are repeating their position
on the list, I'll do so too.

I support the rough consensus as presented by the chair.

Den 05. des. 2014 14:36, skrev Sean Turner:
> All,
> At the 2nd RTCweb WG session @ IETF 91, we had a lively discussion about codecs, which I dubbed "the great codec compromise."  The compromise text that was discussed appears in slides 12-14 at [4] (which is a slight editorial variation of the text proposed at [2]).
> This message serves to confirm the sense of the room.
> In the room, I heard the following objections and responses (and I’m paraphrasing here), which I’ll take the liberty of categorizing as IPR, Time, and Trigger:
> 1) IPR:
> Objections: There are still IPR concerns which may restrict what a particular organization feels comfortable with including in their browser implementations.
> Response:  IPR concerns on this topic are well known.  There is even a draft summarizing the current IPR status for VP8: draft-benham-rtcweb-vp8litigation.  The sense of the room was still that adopting the compromise text was appropriate.
> 2) Time:
> 2.1) Time to consider decision:
> Objection: The decision to consider the compromise proposal at this meeting was provided on short notice and did not provide some the opportunity to attend in person.
> Response:  Six months ago the chairs made it clear discussion would be revisited @ IETF 91 [0]. The first agenda proposal for the WG included this topic [1], and the topic was never removed by the chairs.    More importantly, all decisions are confirmed on list; in person attendance is not required to be part of the process.
> 2.2) Time to consider text:
> Objection: The proposed text [2] is too new to be considered.
> Response: The requirement for browsers to support both VP8 and H.264 was among the options in the straw poll conducted more than six months ago.  All decisions are confirmed on list so there will be ample time to discuss the proposal.
> 3) Trigger:
> Objection: The “trigger” sentence [3] is all kinds of wrong because it’s promising that the future IETF will update this specification.
> Response: Like any IETF proposal, an RFC that documents the current proposal can be changed through the consensus process at any other time.
> After the discussion, some clarifying questions about the hums, and typing the hum questions on the screen, there was rough consensus in the room to add (aka “shove”) the proposed text into draft-ietf-rtcweb-video.  In keeping with IETF process, I am confirming this consensus call on the list.
> If anyone has any other issues that they would like to raise please do by December 19th.
> Cheers,
> spt (as chair)
> [0]
> [1]
> [2]
> [3] The one that begins with "If compelling evidence ..."
> [4]
> _______________________________________________
> rtcweb mailing list

rtcweb mailing list<>