Re: [rtcweb] Request to postpone the question on VP8 as MTI

Cameron Byrne <cb.list6@gmail.com> Sun, 10 March 2013 18:57 UTC

Return-Path: <cb.list6@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 02C5021F859B for <rtcweb@ietfa.amsl.com>; Sun, 10 Mar 2013 11:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 XhgdDyaBJ3gA for <rtcweb@ietfa.amsl.com>; Sun, 10 Mar 2013 11:57:37 -0700 (PDT)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id A18BB21F8530 for <rtcweb@ietf.org>; Sun, 10 Mar 2013 11:57:36 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id ds1so1380185wgb.0 for <rtcweb@ietf.org>; Sun, 10 Mar 2013 11:57:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=q7EF7+kThBSsNLPBDL/yVeL+tInWIjeOMG7trL8N1Og=; b=M228mHQn6oz0UTt/vtcHX1jBH9fc0jyoJbLZJUiWCERMSB1oqr0Z1yGxUI7j1zMs27 7IQBR14HE1rhIdpJ8xm92hPHx1cfCIuW/+Zzb3qNZ7vjFV1w2dO/NMKcDLyt2erhSl2J NfBkf0vHNzp7tNNt8J7CiAW+dRMx6Ufp1sJ+YarWiTtW3iIrwUh1ZLPjTvGmKZ9JTwk7 aCLq3sOWVrH99EunuqAR/3wzJY1Sax7ibCYxPp2/HNBI2Zh8egjUvptrk6lKil7YmWyW UClJG+fMkk2vxNeFdbzykLIlgan/d15a+FGJXj+WJ6Ef1cj8RH3fMluyJMM/O4h9kup2 DFOQ==
MIME-Version: 1.0
X-Received: by 10.194.242.163 with SMTP id wr3mr14819711wjc.35.1362941855781; Sun, 10 Mar 2013 11:57:35 -0700 (PDT)
Received: by 10.194.20.35 with HTTP; Sun, 10 Mar 2013 11:57:35 -0700 (PDT)
In-Reply-To: <C56A8C6C-1D28-42EF-B4E3-F2471E20AD48@iii.ca>
References: <92D0D52F3A63344CA478CF12DB0648AA26537A69@XMB106BCNC.rim.net> <C56A8C6C-1D28-42EF-B4E3-F2471E20AD48@iii.ca>
Date: Sun, 10 Mar 2013 11:57:35 -0700
Message-ID: <CAD6AjGQ3nsDiaE1QT2Ox4=FrcKYNO91WyExzffFY4hXx5fTVZw@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Request to postpone the question on VP8 as MTI
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: Sun, 10 Mar 2013 18:57:38 -0000

After seeing this play out over the last few months,  i believe we
need to strongly consider no MTI for video.

It's unfortunate, but i believe the various stakeholder have
irreconcilable difference.  IPR is a dark art and the IETF has no
method for dealing with it beyond running away.  That said, run away.

CB

On Sun, Mar 10, 2013 at 8:52 AM, Cullen Jennings <fluffy@iii.ca> wrote:
>
> Gaelle,
>
> I think these are good points and other have erased similar points. I need to discuss it with my co-chairs but I suspect that for the points you raised, we will need delay this to IETF 86. Again, I need to talk to my co-chairs before we can make a decision on this but I would guess that is the direction things will need to go.
>
> Cullen (One of the co-chairs)
>
>
> On Mar 10, 2013, at 9:45 AM, Gaelle Martin-Cocher <gmartincocher@blackberry.com> wrote:
>
>> Dear All,
>>
>> In light of the recent announcements (both MPEG-LA and the VP8 litigation), I believe that more time is needed to make a proper risk assessment on VP8 and an informed decision. On one side the MPEG-LA announcement provides some relief but also confirms that VP8 does not come for free and that concerns were/are justified. This is further confirmed by the second announcement.
>> It will take more efforts for VP8 supporters (and Google does not need to be alone in that process) to reach the goal of an RF video codec (or a codec with a suitable licensing terms). I think it is understood by now, that this would likely be more prone to success in a standardization body than anywhere else . (speaking here as a WebVC proponent that went through that process too).
>> It is also apparent that the MPEG-LA/Google agreement raises additional questions.
>>
>> Here are the reasons I believe we need more time and should postpone the question on VP8 (I am not saying that this should not be asked at a later time):
>> -The license is not yet published (and the meeting starts tomorrow)
>> -Some negotiations are still ongoing (e.g. names of the licensors).
>> -Some questions were/are raised and not answered yet, below are the one that matters to me:
>> - Will the patent list be provided?
>> - Who are the licensors  and how that group of licensors relates to the initial 12 patent holders identified by MPEG-LA?
>> - Will there be alignment of licenses across WebM, RFC, MPEG, and is that even feasible with the possible new license terms?
>> - Questions related to clarifications of the different grants inside/outside the RFC and their applicability to the RFC itself still need to be answered (aka: how  section 20: 27 apply to the RFC code itself or to the code provided in MPEG)
>> - Questions related to the status of VP8 as a standard as it was mentioned that the RFC will not progress to the standard track still remain
>> - In light of the litigation announcement, was due diligence done by VP8 proponents toward patent holders that are not MPEG-LA members?  (e.g. possibly on a model similar to what was done in WebVC)
>> - More questions will likely be raised once the license is published.
>> -We need to give enough time to Google to finalize its license and provide answers on those above points.
>> -VP8 is not (yet) a standard in IETF nor in MPEG (MPEG only saw an input contribution for the first time in January). It would be desirable that RTCWeb points to a standard or that VP8 reaches a certain stage in MPEG so that it can be considered as an MPEG deliverable. VP8 may reach that status at a next MPEG meeting in April or July, I don’t see how that can be accelerated further. We need to give MPEG the time to proceed properly.
>> -legal entities will need time to review both the new license and the answers to the various questions that were asked. This cannot be achieved in 3 days.
>>
>> Further, I just came across an informational RFC for VP9:
>> -Is VP9 going to “deprecate” VP8?
>> - What is the timeframe for VP9 in IETF?
>> -if VP9 going to be proposed for a next generation of RTCWeb Client? Which timeframe?
>> I don’t think it would be desirable to mandate VP8 today if VP9 is around the corner and will be proposed for RTCWeb as well.
>> Requesting two codecs to be implemented instead of one in a short timeframe is obviously an issue for implementers that cannot do a simple software upgrade of their products.
>>
>>
>> I hope all of you will find that request reasonable.
>> Sincerely,
>>
>>
>> Gaëlle Martin-Cocher
>> Standards Manager
>> Office: (905) 629-4746 x14591
>> BlackBerry: (647) 267-0569
>> PIN: 2835485E
>> <image001.gif>
>> www.rim.com
>>
>> ---------------------------------------------------------------------
>> This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb