Re: [rtcweb] Video Codec discussion in Thursday agenda slot
Rob Glidden <rhglidden@gmail.com> Thu, 14 March 2013 15:47 UTC
Return-Path: <rhglidden@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
with ESMTP id BD93911E8230 for <rtcweb@ietfa.amsl.com>;
Thu, 14 Mar 2013 08:47:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xDFHKx-0PWYZ for
<rtcweb@ietfa.amsl.com>; Thu, 14 Mar 2013 08:47:50 -0700 (PDT)
Received: from mail-qa0-f52.google.com (mail-qa0-f52.google.com
[209.85.216.52]) by ietfa.amsl.com (Postfix) with ESMTP id AD7B311E821F for
<rtcweb@ietf.org>; Thu, 14 Mar 2013 08:47:50 -0700 (PDT)
Received: by mail-qa0-f52.google.com with SMTP id bs12so1304611qab.18 for
<rtcweb@ietf.org>; Thu, 14 Mar 2013 08:47:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=x-received:message-id:date:from:user-agent:mime-version:to:cc
:subject:references:in-reply-to:content-type;
bh=KNgvPG36r/Q4X3RYcpZx+kZQ+daGAfDQVKEvdTQlnJQ=;
b=fwElQseGFSFbd6RVhcqavejdBVZvEXEA0vy2TMYiYDMZUXix3ErQ/ravb5mnpO+3mG
2RVQhrzxtsOG48kDv6qiiMVWy0Lu8Iabyp4K8NoL/wqNTZ0fqtOQ3HKa5HxJObVsGzPy
tEYSLO6V41P1J9/YWLIxDVCnoPvm1lJQTcP5zpa2uRzShAVB/6Ls7dQm+koypM26eiNN
PLCtkp1avsdrpl7w+WxKBppxshsFN8uM0an/wLxPNt1/fQdAItyIippHk0fs5aD9Nm+T
gMoyuGQZnY+HzR5bkI0il+3/aWDrOHMSBPgn6ya7NR4iBt7bFfmcItWoCKQy0jfqBNFI XUFA==
X-Received: by 10.224.207.72 with SMTP id fx8mr3461466qab.66.1363276070151;
Thu, 14 Mar 2013 08:47:50 -0700 (PDT)
Received: from [10.0.0.10] (99-25-33-39.lightspeed.sntcca.sbcglobal.net.
[99.25.33.39]) by mx.google.com with ESMTPS id
q6sm3949348qeu.1.2013.03.14.08.47.47 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA
bits=128/128); Thu, 14 Mar 2013 08:47:49 -0700 (PDT)
Message-ID: <5141F120.3020400@gmail.com>
Date: Thu, 14 Mar 2013 08:47:44 -0700
From: Rob Glidden <rhglidden@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64;
rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "Wang, Ye-Kui" <yekuiw@qti.qualcomm.com>,
"rtcweb@ietf.org" <rtcweb@ietf.org>
References: <513F68C0.4010106@ericsson.com>
<DD34B1B0-2C18-4081-81CC-584192CC726C@apple.com>
<513F7745.3020302@alvestrand.no>
<CBC4C75B-0397-4953-8C06-4E236DA15250@apple.com>
<BBE9739C2C302046BD34B42713A1E2A22DE30E9C@ESESSMB105.ericsson.se>
<AEDB506D-E350-4E14-B8ED-F2D07C16D57A@nomor.de>
<8BA7D4CEACFFE04BA2D902BF11719A8331B17F22@nasanexd02f.na.qualcomm.com>,
<1363220674.82166.YahooMailNeo@web132106.mail.ird.yahoo.com>
<2981F523-72AC-4330-8D1F-7DC4E2168C5A@qti.qualcomm.com>
In-Reply-To: <2981F523-72AC-4330-8D1F-7DC4E2168C5A@qti.qualcomm.com>
Content-Type: multipart/alternative;
boundary="------------070907060301060800010909"
Subject: Re: [rtcweb] Video Codec discussion in Thursday agenda slot
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 14 Mar 2013 15:47:54 -0000
Sure it is, there's an open MPEG meeting resolution on the MPEG VP8 proposal to that effect, apparently even National Body comment. Rob On 3/13/2013 9:36 PM, Wang, Ye-Kui wrote: > Sure - but that is clearly not the context here. > > Sent from my iPhone > > On Mar 13, 2013, at 17:24, "Gerard Fernando" <gerardmxf@yahoo.co.uk > <mailto:gerardmxf@yahoo.co.uk>> wrote: > >> Hello YK, >> >> The disclosure process in MPEG is not based on who you are, or on >> your Business model. >> >> Kind regards >> >> Gerard >> >> >> ------------------------------------------------------------------------ >> *From:* "Wang, Ye-Kui" <yekuiw@qti.qualcomm.com >> <mailto:yekuiw@qti.qualcomm.com>> >> *To:* Stockhammer Thomas <stockhammer@nomor.de >> <mailto:stockhammer@nomor.de>>; Bo Burman <bo.burman@ericsson.com >> <mailto:bo.burman@ericsson.com>> >> *Cc:* "rtcweb@ietf.org <mailto:rtcweb@ietf.org>" <rtcweb@ietf.org >> <mailto:rtcweb@ietf.org>> >> *Sent:* Wednesday, 13 March 2013, 10:40 >> *Subject:* Re: [rtcweb] Video Codec discussion in Thursday agenda slot >> >> > > How many others who did not respond to MPEG LA's call but have IPR >> > > are >> > there? >> > >> > [TS] Just one more hypothesis: If I would have, what would be my >> > obligation/motivation to do so now? >> >> Speaking of the motivation part; that would depend on who YOU are and >> what kind of business model or plan YOU have in mind. >> >> BR, YK >> >> > -----Original Message----- >> > From: rtcweb-bounces@ietf.org <mailto:rtcweb-bounces@ietf.org> >> [mailto:rtcweb-bounces@ietf.org <mailto:rtcweb-bounces@ietf.org>] On >> Behalf >> > Of Stockhammer Thomas >> > Sent: Wednesday, March 13, 2013 7:53 AM >> > To: Bo Burman >> > Cc: rtcweb@ietf.org <mailto:rtcweb@ietf.org> >> > Subject: Re: [rtcweb] Video Codec discussion in Thursday agenda slot >> > >> > >> > > How many others who did not respond to MPEG LA's call but have >> IPR are >> > there? >> > >> > [TS] Just one more hypothesis: If I would have, what would be my >> > obligation/motivation to do so now? >> > >> > >>> >> > >>> We appreciate the need to have time to evaluate the specific words >> > >>> of the license statements that are forthcoming, and the need >> for the >> > >>> people who haven't made their IPR declarations over the last couple >> > >>> of years of discussion to do so within the next couple of weeks - >> > >>> but we do think that it is important to use the face to face time >> > >>> that we have here in Orlando to lay to rest any *other* issues than >> > >>> the licensing terms and other issues derived from Google's >> > announcement. >> > >> >> > >> I am not sure we can have a reasoned consideration of 'other issues >> > derived' >> > >> at such short notice. >> > >> >> > >> Look, I'd like our discussions and decisions to be informed and >> > >> considered, and there simply isn't time for either. >> > >> >> > >>> >> > >>> Harald >> > >>> >> > >>> _______________________________________________ >> > >>> rtcweb mailing list >> > >>> rtcweb@ietf.org <mailto:rtcweb@ietf.org> >> > >>> https://www.ietf.org/mailman/listinfo/rtcweb >> > >> >> > >> David Singer >> > >> Multimedia and Software Standards, Apple Inc. >> > >> >> > >> _______________________________________________ >> > >> rtcweb mailing list >> > >> rtcweb@ietf.org <mailto:rtcweb@ietf.org> >> > >> https://www.ietf.org/mailman/listinfo/rtcweb >> > > >> > >> > --- >> > Dr. Thomas Stockhammer (CEO) || stockhammer@nomor.de >> <mailto:stockhammer@nomor.de> || phone +49 >> > 89 978980 02 || cell +491725702667 || http://www.nomor-research.com >> <http://www.nomor-research.com/> >> > Nomor Research GmbH - Sitz der Gesellschaft: München - >> Registergericht: >> > München, HRB 165856 - Umsatzsteuer-ID: DE238047637 - Geschäftsführer: >> > Dr. Thomas Stockhammer, Dr. Ingo Viering. >> > >> > >> > >> > _______________________________________________ >> > rtcweb mailing list >> > rtcweb@ietf.org <mailto:rtcweb@ietf.org> >> > https://www.ietf.org/mailman/listinfo/rtcweb >> _______________________________________________ >> rtcweb mailing list >> rtcweb@ietf.org <mailto:rtcweb@ietf.org> >> https://www.ietf.org/mailman/listinfo/rtcweb >> >> >> _______________________________________________ >> rtcweb mailing list >> rtcweb@ietf.org <mailto:rtcweb@ietf.org> >> https://www.ietf.org/mailman/listinfo/rtcweb > > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb
- [rtcweb] Video Codec discussion in Thursday agend… Magnus Westerlund
- Re: [rtcweb] Video Codec discussion in Thursday a… David Singer
- Re: [rtcweb] Video Codec discussion in Thursday a… Matthew Kaufman
- Re: [rtcweb] Video Codec discussion in Thursday a… Ted Hardie
- Re: [rtcweb] Video Codec discussion in Thursday a… Gaelle Martin-Cocher
- Re: [rtcweb] Video Codec discussion in Thursday a… Timothy B. Terriberry
- Re: [rtcweb] Video Codec discussion in Thursday a… Harald Alvestrand
- Re: [rtcweb] Video Codec discussion in Thursday a… David Singer
- Re: [rtcweb] Video Codec discussion in Thursday a… Ted Hardie
- Re: [rtcweb] Video Codec discussion in Thursday a… Gaelle Martin-Cocher
- Re: [rtcweb] Video Codec discussion in Thursday a… Ted Hardie
- Re: [rtcweb] Video Codec discussion in Thursday a… David Singer
- Re: [rtcweb] Video Codec discussion in Thursday a… Ted Hardie
- Re: [rtcweb] Video Codec discussion in Thursday a… Coban, Muhammed
- Re: [rtcweb] Video Codec discussion in Thursday a… Robert Sparks
- Re: [rtcweb] Video Codec discussion in Thursday a… Ted Hardie
- Re: [rtcweb] Video Codec discussion in Thursday a… Gaelle Martin-Cocher
- Re: [rtcweb] Video Codec discussion in Thursday a… Gonzalo Camarillo
- Re: [rtcweb] Video Codec discussion in Thursday a… Bo Burman
- Re: [rtcweb] Video Codec discussion in Thursday a… Stockhammer Thomas
- Re: [rtcweb] Video Codec discussion in Thursday a… Wang, Ye-Kui
- Re: [rtcweb] Video Codec discussion in Thursday a… Gerard Fernando
- Re: [rtcweb] Video Codec discussion in Thursday a… Wang, Ye-Kui
- Re: [rtcweb] Video Codec discussion in Thursday a… Rob Glidden
- Re: [rtcweb] Video Codec discussion in Thursday a… Wang, Ye-Kui
- Re: [rtcweb] Video Codec discussion in Thursday a… Rob Glidden