Re: [rtcweb] Straw Poll on Nokia mincing

Silvia Pfeiffer <silviapfeiffer1@gmail.com> Thu, 19 December 2013 06:50 UTC

Return-Path: <silviapfeiffer1@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 301131AE081 for <rtcweb@ietfa.amsl.com>; Wed, 18 Dec 2013 22:50:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cROZ43k7Sqlo for <rtcweb@ietfa.amsl.com>; Wed, 18 Dec 2013 22:50:23 -0800 (PST)
Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id ABC151AE07B for <rtcweb@ietf.org>; Wed, 18 Dec 2013 22:50:23 -0800 (PST)
Received: by mail-oa0-f53.google.com with SMTP id m1so796625oag.12 for <rtcweb@ietf.org>; Wed, 18 Dec 2013 22:50:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=aYKHxnjiklFwU+1R0oMpjG3ZXK4RSUml66bYl6Aj6RE=; b=bNXzhWAa4td0yVu6nYDWpi2lhWfK9STl6lF2dZWFvzUsAs5u/y2FFkynOTjIYbiX2Z /mPegEj3+Hz8QHf5C9B7jOizJx3vXE6Uno8Zi59ZTWQ4sPifdTfjiSDYJMXgLiCIHise rOgJHuaUh126uNA9gvEGnZGP6OiPBXPA32aVoZp4imqm9WMEv/4U7PGKR8rw61aDxZ/e 3JNAHkOakVYNwDZbhGAi0OSGLziE8GPYetnlIpDSpstwlkCHYaa3VUd3WbedANSeByst tS682u53aAMURkO6n8lRLRG/4IeXehXruylhrXxA/ASFBNoJ3XMleKNneeB4edEsinJN J1uA==
X-Received: by 10.182.135.165 with SMTP id pt5mr118884obb.66.1387435821930; Wed, 18 Dec 2013 22:50:21 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.68.106 with HTTP; Wed, 18 Dec 2013 22:50:00 -0800 (PST)
In-Reply-To: <CA+E6M0n9frSRbbrXh=jczQETX13HX6LDGUCq2P4=6voXx93ZVA@mail.gmail.com>
References: <CA+E6M0m5O1OqjBm13qNoRAtYZKwOs+4fs3evyO2VuuO1uqQ5eA@mail.gmail.com> <CED773F0.2D6AA%stewe@stewe.org> <20131219033000.GK3245@audi.shelbyville.oz> <CA+E6M0n9frSRbbrXh=jczQETX13HX6LDGUCq2P4=6voXx93ZVA@mail.gmail.com>
From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Thu, 19 Dec 2013 17:50:00 +1100
Message-ID: <CAHp8n2m5XNC8UfDswGfD=0qCPaddcsrg08FJKXnDsz-A+tWqzQ@mail.gmail.com>
To: Mohammed Raad <mohammedsraad@raadtech.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Straw Poll on Nokia mincing
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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, 19 Dec 2013 06:50:25 -0000

I think the biggest problem is that people only want to maintain code
for one codec. If you already have H.264 support implemented, you will
oppose every other codec, no matter how big the advantages.
Therefore, a compromise is not possible with such a position.

Silvia.


On Thu, Dec 19, 2013 at 5:44 PM, Mohammed Raad
<mohammedsraad@raadtech.com> wrote:
> Correct on changing the subject line, this really started as a clarification
> question and then grew, sorry.
>
> What is relevant to the straw poll thread is that we should have a correct
> summary of where the IPR situation really is.
>
> It has been pointed out that the MTI should satisfy options a) or b) on the
> ietf declaration form. As matters stand AVC/h264 does not satisfy that, this
> has been made very clear through the ISO process. On the other hand, VP8 has
> so far withstood court challenges, as you point out - something which AVC
> could not BTW - and the technology owning entities willing to license VP8
> relevant technology under the required royalty free terms has grown
> significantly during the past year.
>
> It would seem very clear that the codec that is closer to the royalty free
> ideal situation is VP8.
>
> As such, it is surprising to see AVC proponents opposing the adoption of
> VP8, even as one of two MTI codecs - something that VP8 proponents appear to
> be saying is acceptable - based on IPR arguments.
>
> If members of this WG wish to move towards a compromise that allows webrtc
> to fulfill the potential that it has then this is their opportunity. I
> certainly encourage them to take this opportunity.
>
> Mohammed
>
>
> Please people, changing the subject for side discussions like the Chairs
> requested isn't rocket science ...
>
>
> On Wed, Dec 18, 2013 at 11:47:14PM +0000, Stephan Wenger wrote:
>> My gosh.  Nokia has people at the IETF, and they made statements
>> and have not minced words.
>
> They also have people making statements in the courts, where they
> seem to be getting, well, thoroughly minced!
>
>
> The interesting question isn't Nokia's intention here, I don't think
> anyone seriously doubts what it is.  The interesting questions are
> twofold:
>
>  a) Do they even have the slimmest leg to stand on with their claims
>     against VP8?  There's so far no supporting evidence to say that
>     they do, and plenty stacking up against them.
>
>  b) Given their stubborn refusal to make any declaration about their
>     intentions or IPR for H.264 here, does anybody have even the
>     slightest idea what their terms are for licencing the Cisco blob?
>
>
> Meritorious or meretricious, the devil is in such little details.
>
>   Ron
>
>
> _______________________________________________
> 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
>