Re: [rtcweb] Straw Poll on Nokia mincing

Mohammed Raad <mohammedsraad@raadtech.com> Thu, 19 December 2013 07:32 UTC

Return-Path: <mohammedsraad@raadtech.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 428691AE1AD for <rtcweb@ietfa.amsl.com>; Wed, 18 Dec 2013 23:32:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 yBK4N1B72_6j for <rtcweb@ietfa.amsl.com>; Wed, 18 Dec 2013 23:32:05 -0800 (PST)
Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com [209.85.212.176]) by ietfa.amsl.com (Postfix) with ESMTP id EE5731AE1D7 for <rtcweb@ietf.org>; Wed, 18 Dec 2013 23:32:04 -0800 (PST)
Received: by mail-wi0-f176.google.com with SMTP id hq4so6418133wib.9 for <rtcweb@ietf.org>; Wed, 18 Dec 2013 23:32:02 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=DfnSkjJbJyIGVYvnG4fwG+PwaL2J+XXI9OuLNPz7hNM=; b=SCFbtUH8aHzUMWdz0tCC8XiVeano85bM/yZg2bWHXF1NqkG+eK5h9GQfDHO0yiooOs je3q4rgzTmncvsUaMFx8alqbJVKnjP/dKg+Kb0Szkw32N5LAgokRoSRyhf82Abt8aeYb ti77biJauOk/hvTuyV+YJ5lfNy2BuT4If0JkzAg3ZJKwFcVCeh8fNQpBN+gfIS2EsT6C obCtb+3hp81MtNGYjrmBlufFLKBWH8dQd5FU4xCcwcO4gqIA94nQjiCOMoIOuVVwBldf G5RZRj6hMv1DfjseJs3cg2dUBYi2ai9m7Y/cCcuJTM4jyUlcIpJTfdMSUXltzNJu3u2N zTZA==
X-Gm-Message-State: ALoCoQkxS2UPmkkrwidmlcCp+LMv8pt+k23D3ML+aMtjTQJ8UGD2WJ/1O098G+KGA4c41tdZq2y2
MIME-Version: 1.0
X-Received: by 10.194.185.113 with SMTP id fb17mr27118867wjc.29.1387438322731; Wed, 18 Dec 2013 23:32:02 -0800 (PST)
Received: by 10.194.179.166 with HTTP; Wed, 18 Dec 2013 23:32:02 -0800 (PST)
In-Reply-To: <CAHp8n2m5XNC8UfDswGfD=0qCPaddcsrg08FJKXnDsz-A+tWqzQ@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> <CAHp8n2m5XNC8UfDswGfD=0qCPaddcsrg08FJKXnDsz-A+tWqzQ@mail.gmail.com>
Date: Thu, 19 Dec 2013 18:32:02 +1100
Message-ID: <CA+E6M0mwWVEAv6zeET1fwdL6oDB-Cxag64XNV1EJhk-oP3241g@mail.gmail.com>
From: Mohammed Raad <mohammedsraad@raadtech.com>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Content-Type: multipart/alternative; boundary="047d7bd6bb0e5fe64404edde28f0"
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 07:32:08 -0000

Well, many of those same people saying that they only want to maintain one
codec have been more than willing to keep on developing new standardized
codecs and to pile on profiles, which, in many practical situations means
different code bases.

A compromise, by definition, is taking what one can get, which simply has
to be acceptable and may not match what one was aiming for.

What members of this WG have been saying, and writing, is that they want
interoperability. OK, so that can be achieved with at least one of the
options in the straw poll that VP8 proponents have indicated is acceptable.
It would seem logical and reasonable to expect AVC proponents to take up
that option also. I started commenting when I noticed that was not
happening, which raised the question in my mind as to whether or not there
is an intention to achieve interoperability, or whether there were still
genuine misunderstandings wrt the IPR situation.

Best Regards,
Mohammed



On Thu, Dec 19, 2013 at 5:50 PM, Silvia Pfeiffer
<silviapfeiffer1@gmail.com>wrote:

> 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
> >
>



-- 
Mohammed Raad, PhD.
Partner
RAADTECH CONSULTING
P.O. Box 113
Warrawong
NSW 2502 Australia
Phone: +61 414451478
Email: mohammedsraad@raadtech.com