Re: [rtcweb] Finishing up the Video Codec document

Adam Roach <> Thu, 04 December 2014 16:09 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 902281A1A15 for <>; Thu, 4 Dec 2014 08:09:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZW4opFljPCEx for <>; Thu, 4 Dec 2014 08:09:09 -0800 (PST)
Received: from ( [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4D3991AD450 for <>; Thu, 4 Dec 2014 08:09:09 -0800 (PST)
Received: from Orochi.local ( []) (authenticated bits=0) by (8.14.9/8.14.7) with ESMTP id sB4G93jA073276 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Dec 2014 10:09:04 -0600 (CST) (envelope-from
X-Authentication-Warning: Host [] claimed to be Orochi.local
Message-ID: <>
Date: Thu, 04 Dec 2014 08:08:57 -0800
From: Adam Roach <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Peter Saint-Andre - &yet <>, Ron <>,
References: <> <> <20141204150041.GI10449@hex.shelbyville.oz> <>
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] Finishing up the Video Codec document
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: Thu, 04 Dec 2014 16:09:25 -0000

On 12/4/14 07:45, Peter Saint-Andre - &yet wrote:
> On 12/4/14, 8:00 AM, Ron wrote:
>> On Wed, Dec 03, 2014 at 07:20:45PM -0700, Peter Saint-Andre - &yet 
>> wrote:
>>> IMHO we need to either pull out the future-oriented text entirely 
>>> (which has
>>> its own problems) or significantly improve it. I would be happy to 
>>> propose
>>> text for the latter.
>> I'd definitely be interested in seeing proposals from you to improve
>> upon these things.  It seemed premature to explore this until we had
>> some sense of whether this kind of compromise could fly at all, but
>> now that it seems it can, I think these are important details for us
>> to clarify as best we can.
> OK, I'll get to work. :-)

Awesome, thanks. I've always found your prose to be clearer and easier 
to read than mine anyway. :)

When you draft your text, keep in mind that what we're trying to do is 
capture the essence of the agreement that we've formed a critical mass 
around. The less formal (i.e., not really document-ready) version of 
this is:

> "WebRTC devices MUST implement both VP8 and H.264. If compelling 
> evidence arises that one of the codecs is available for use on a 
> royalty-free basis, such as all IPR declarations known for the codec 
> being of (IETF) Royalty-Free or (ISO) type 1, the IETF will change 
> this normative statement to indicate that only that codec is required. 
> For absolute, crystal clarity, this provision is only applicable to 
> WebRTC devices, and not to WebRTC User Agents."

There's nuance to be added there, for sure, but I'd encourage you not to 
color way outside those lines. Expanding scope to discuss issues such as 
*other* circumstances that may cause revisiting the MTI, for example, 
are far more likely to weaken consensus than they are to strengthen it.