Re: [rtcweb] VP8 IPR agreement announced.

Rob Glidden <> Sun, 10 March 2013 20:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6613B21F8984 for <>; Sun, 10 Mar 2013 13:11:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.91
X-Spam-Status: No, score=-4.91 tagged_above=-999 required=5 tests=[AWL=0.688, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id WirLTTN-ANjB for <>; Sun, 10 Mar 2013 13:11:49 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D25B821F8758 for <>; Sun, 10 Mar 2013 13:11:48 -0700 (PDT)
Received: by with SMTP id r10so523035yen.0 for <>; Sun, 10 Mar 2013 13:11:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=7fVLyV7W9YgrdMuKuInyAL84/W/ILEqK17xSMI3SfOE=; b=tvK4IEligTMeeaYt7pucWT//bNFCJfME7q41cBHHAXepc9MiVfZ/TilRdkwvWP/nP6 16jCJtx8HJ1RmCzKNO8f2DM5zXfh8C4PSMt3A8d3Tc3kOscryZvcsFWF9rttKe2vAbw6 zQch1gIYOuceyilSZaz3cT5gbv2+qaXOs+LllV9QGVQ6eJnjL38D7iXqpjmX+FBbGod5 ua78dnY/UZqgmqk1uBJoD6+J7EHIxcuwq+uucVxs0XEoW+QgrJA2aRtBx4N796FjFxXP FR5Q3Od0Yaes+tkbuiDll3KvUmd3hDCFLDxNQdJRbWnaD+NTNmhfcqd8lhpMDpy2W8zQ M3iQ==
X-Received: by with SMTP id b77mr7131818yhj.130.1362946308165; Sun, 10 Mar 2013 13:11:48 -0700 (PDT)
Received: from [] ( []) by with ESMTPS id u3sm20075916yhd.14.2013. (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 10 Mar 2013 13:11:46 -0700 (PDT)
Message-ID: <>
Date: Sun, 10 Mar 2013 13:11:40 -0700
From: Rob Glidden <>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: Stephan Wenger <>
References: <>
In-Reply-To: <>
Content-Type: multipart/alternative; boundary="------------000309040903020503030700"
Cc: "" <>
Subject: Re: [rtcweb] VP8 IPR agreement announced.
X-Mailman-Version: 2.1.12
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: Sun, 10 Mar 2013 20:11:50 -0000


I'm sure you are aware this is straight from the official ISO web site 
where you are listed as the liaison from IETF.

Perhaps I confused you by paraphrasing the term "shall" as "must".  I 
think they mean the same thing here, the former just seems oddly formal 
to use in an email.


On 3/9/2013 3:07 PM, Stephan Wenger wrote:
> Hi Rob,
> Please see inline.
> Stephan
> From: Rob Glidden < <>>
> Date: Saturday, 9 March, 2013 12:21
> To: Harald Alvestrand < <>>
> Cc: " <>" < 
> <>>
> Subject: Re: [rtcweb] VP8 IPR agreement announced.
>     Interesting.  Potential licensees will be aided by the provision
>     of a clear list of the portfolio patents, said the 1997 US
>     Department of Justice review letter of MPEG LA.
> AFAIK, neither a patent list nor a list of potential pool licensors 
> were ever published.  What is known is that there were originally 12 
> parties which each submitted at least one patent (which was found 
> essential) into a possible future pool, and 11 parties (which may or 
> may not be related to the original 12 parties) decided, apparently 
> with MPEG-LA's help, to furnish a sublicenseable license to google 
> (but not to the world).  So we have a closed group of 11 licensors, 
> and a single licensee, who came to an agreement using a facilitator 
> which also happens to administers pools.  To what extent that 
> transaction qualifies as a pooling arrangement from an antitrust law 
> viewpoint surely has been looked at carefully by the parties in 
> question.  Apparently, they came to the conclusion that they do not 
> need to name the licensors, nor the patents in question. 
>  Otherwise, I guess we would know by now.
>     ISO/MPEG IPR rules are clear that proposers must ask for, and
>     rights holders must provide, patent statements for a proposal to
>     proceed.
> Huh?  Is that something special for this MPEG subgroup?  If yes, would 
> there be a doc you can share explaining such procedures?
> My understanding is that ISO/IEC patent matters are generally dealt 
> with under the joint ITU/ISO/IEC patent policy, which requires in 
> practice declarations with RAND terms towards the end of the process 
> (before final approval of the standard, but after it is clear that the 
> patent claim reads on the future standard).  Chairs are also under the 
> obligation to request disclosure during each meeting, but (AFAIK) 
> there are almost never replies to these calls.  When participating in 
> a meeting, I usually to not reply, because I'm not quite sure that a 
> patent claim reads on the final standard before that standard is 
> reasonable frozen.
> I know that the video coding joint teams (JVT, JCT-VC, JCT-3V) have 
> additionally adopted a policy requiring in practice some form of RAND 
> language in each contribution.
> As some here know, I do not participate in this MPEG effort, 
> so I really don't know.
>     Rob
>     On 3/9/2013 2:08 AM, Harald Alvestrand wrote:
>>     On 03/08/2013 09:14 PM, Stephan Wenger wrote:
>>>     Hi Serge,
>>>     This is a great development for VP8.  Congratulations.  I'm sure
>>>     it took a few cycles and dollars to get something like this
>>>     arranged.  I wish your PR would have come out a bit earlier, but
>>>     licensing discussions do take timeā€¦  So better now than never.
>>>     I want to ask two more pieces of information that would allow me
>>>     to put this announcement into context.
>>>     First, who are those 11 rightholders?  I'm sure you agree that,
>>>     in order to make a meaningful risk assessment, that information
>>>     is needed.
>>     Stephan, at the moment, we have no agreement with the
>>     rightsholders that permits us to disclose their names. We're
>>     discussing that topic with them, but we will not name them
>>     without an agreement to do so.
>>     Of course, the rightsholders are free to disclose themselves.
>>>     Second, the link provided to "preview" the possible sublicensing
>>>     terms ( lists a
>>>     bunch of company statements that vary widely among the
>>>     rightholders listed there, which do not include google.  It
>>>     would be great if you could provide more specific information as
>>>     early as possible, especially with respect to the essential
>>>     claims definition and the reciprocity conditions.  That does not
>>>     have to be final legal text, but should be a clear indication of
>>>     your business intentions.  To me, term-sheet level is OK.
>>     That link was a bit weird - the real W3C definition of
>>     "royalty-free" is
>>     - I think the intent of the link was that if you don't find any
>>     of the RF terms listed on that page objectionable, you'll not
>>     find the Google RF terms objectionable either.
>>     _______________________________________________
>>     rtcweb mailing list
>>     rtcweb@ietf.org