Re: [rtcweb] Video Codec discussion in Thursday agenda slot

"Wang, Ye-Kui" <yekuiw@qti.qualcomm.com> Thu, 14 March 2013 19:08 UTC

Return-Path: <yekuiw@qti.qualcomm.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 432F121F8E57 for <rtcweb@ietfa.amsl.com>; Thu, 14 Mar 2013 12:08:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level:
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 ahWgnsvar+FY for <rtcweb@ietfa.amsl.com>; Thu, 14 Mar 2013 12:08:35 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id D92E721F8E43 for <rtcweb@ietf.org>; Thu, 14 Mar 2013 12:08:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1363288114; x=1394824114; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=udifaZXOVy9Z7pcSFE3LFUyz2zDWjy3R3e+Yr2XXnvM=; b=xvCiDZDSwJ5ArBXSsDbs2xD4u7A8ggGOiEvnu37+i6C5geeQluJF5D9+ fv2tDf3G0csWvdzvGhwvIK3NnsUgpIPMDriRCvBHHUybXQMYttv9940R1 v6AG/w8EYXPNoXui5B2JrwuagFYPa/kPdFg+mTDWFvWywBWYTtc32c24Z 4=;
X-IronPort-AV: E=Sophos; i="4.84,846,1355126400"; d="scan'208,217"; a="30014145"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by sabertooth01.qualcomm.com with ESMTP; 14 Mar 2013 12:08:34 -0700
X-IronPort-AV: E=Sophos; i="4.84,846,1355126400"; d="scan'208,217"; a="451622000"
Received: from nasanexhc10.na.qualcomm.com ([172.30.48.3]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 14 Mar 2013 12:08:34 -0700
Received: from NASANEXD02F.na.qualcomm.com ([169.254.8.64]) by nasanexhc10.na.qualcomm.com ([172.30.48.3]) with mapi id 14.02.0318.004; Thu, 14 Mar 2013 12:08:33 -0700
From: "Wang, Ye-Kui" <yekuiw@qti.qualcomm.com>
To: Rob Glidden <rhglidden@gmail.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Video Codec discussion in Thursday agenda slot
Thread-Index: AQHOH0jr3vjUB09c8EG4MhtYHbfvE5ii0RyAgAAIloCAAAHrgIABTYKAgAACnQD//7k88IAA5mkA///RB+2AATDnAP//wfZQ
Date: Thu, 14 Mar 2013 19:08:33 +0000
Message-ID: <8BA7D4CEACFFE04BA2D902BF11719A8331B19D77@nasanexd02f.na.qualcomm.com>
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> <5141F120.3020400@gmail.com>
In-Reply-To: <5141F120.3020400@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.202.210]
Content-Type: multipart/alternative; boundary="_000_8BA7D4CEACFFE04BA2D902BF11719A8331B19D77nasanexd02fnaqu_"
MIME-Version: 1.0
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 19:08:36 -0000

Surely it is not.

Note that the context here is on the MTI codec discussion in IETF, not at all the context the POSSIBLE standardization of VP8 in MPEG (which, if to happen, would most likely be subject to more development taking the current VP8 as the basis rather than rubberstamping as is).

BR, YK

From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Rob Glidden
Sent: Thursday, March 14, 2013 8:48 AM
To: Wang, Ye-Kui; rtcweb@ietf.org
Subject: Re: [rtcweb] Video Codec discussion in Thursday agenda slot

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<mailto:rtcweb@ietf.org>

https://www.ietf.org/mailman/listinfo/rtcweb