Re: [rtcweb] Straw Poll on Video Codec Alternatives

Mohammed Raad <mohammedsraad@raadtech.com> Wed, 18 December 2013 20:56 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 AAE111AE1EC for <rtcweb@ietfa.amsl.com>; Wed, 18 Dec 2013 12:56:22 -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 GVcuS-XRvt6J for <rtcweb@ietfa.amsl.com>; Wed, 18 Dec 2013 12:56:19 -0800 (PST)
Received: from mail-we0-f176.google.com (mail-we0-f176.google.com [74.125.82.176]) by ietfa.amsl.com (Postfix) with ESMTP id 7067D1AE192 for <rtcweb@ietf.org>; Wed, 18 Dec 2013 12:56:19 -0800 (PST)
Received: by mail-we0-f176.google.com with SMTP id p61so192744wes.21 for <rtcweb@ietf.org>; Wed, 18 Dec 2013 12:56:17 -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=zSGcDt4WOAF0Krol+6i6IVc08p3ZNmPmMDIBRnZYXDo=; b=ZyRVzGQlGQn8xe6ZBxSrcabQJ2h6jkZF7PF4PI05ZCxH7m3Kc3QMyxM9QCGTQ9NBs2 F5sJeLsHk8E/BDIp6hS5/3ndudHn8DNpxIqIk5uhXZ0WLHQ88P5fsFai+BR3OTHf3f5x B+0KkBtW3xx2CC8tVtOViw79akl5ZwgLB9cgYkMHv4fCBNYvyJyMGNCWTLTpGsowh3bC +OZJyutcqqg+jHJkICByAvBeQHqcQwgGJ+z6xp2OUkol6Tv5ZZ7tiFLt8jEeP0tjubyh KwI6+T3ZNbSkfzbbQCpHmKnoDAHQpuY16wndClMFHGkv9D8+O6qoBOgJua/YcddlpvWX sxbw==
X-Gm-Message-State: ALoCoQkwQ1uTXuhnYwCquGmyYar9oFdY7+0+cnAVxrGYkfSXc7tCULYMVI+M/dChgdgz29itvdxB
MIME-Version: 1.0
X-Received: by 10.180.228.132 with SMTP id si4mr9903535wic.2.1387400177255; Wed, 18 Dec 2013 12:56:17 -0800 (PST)
Received: by 10.194.179.166 with HTTP; Wed, 18 Dec 2013 12:56:16 -0800 (PST)
Received: by 10.194.179.166 with HTTP; Wed, 18 Dec 2013 12:56:16 -0800 (PST)
In-Reply-To: <CB1E0DB6-013B-411E-BBBE-7A43A815B339@apple.com>
References: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com> <4742CE35-61CC-4485-AE76-FF56AB348AC5@apple.com> <CB1E0DB6-013B-411E-BBBE-7A43A815B339@apple.com>
Date: Thu, 19 Dec 2013 07:56:16 +1100
Message-ID: <CA+E6M0km6xU1AsEShvo2qGTrf5EkStktX-FBPTr6b1GM3HLHeA@mail.gmail.com>
From: Mohammed Raad <mohammedsraad@raadtech.com>
To: David Singer <singer@apple.com>
Content-Type: multipart/alternative; boundary="001a1136129eba1f4804edd546eb"
Cc: Cullen Jennings <fluffy@cisco.com>, Richard Barnes <rbarnes@bbn.com>, rtcweb@ietf.org
Subject: Re: [rtcweb] Straw Poll on Video Codec Alternatives
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: Wed, 18 Dec 2013 20:56:22 -0000

David,

Is it your understanding that Nokia is unwilling to license the patents
they have listed in the declaration that you refer to and so you repeatedly
say that VP8 has unlicensable IPR?

My understanding is that they are not willing to license under the options
provided on the form, not that they are unwilling to license.

Mohammed
On Dec 19, 2013 6:31 AM, "David Singer" <singer@apple.com> wrote:

> I should say I only put in the ‘negative’ statements here, not reasons to
> say ‘yes’, since only objections were requested.
>
> For example, why is Motion JPEG OK but 261 not?  Because MJPEG is I-frame
> only, one can send reasonable visual quality at low frame rates, and the
> user is aware of the other end and that the system works, and systems all
> have JPEG implemented today, and the RTP format is not complex to add.
>
> On Dec 18, 2013, at 8:51 , David Singer <singer@apple.com> wrote:
>
> >>
> >> 1..        All entities MUST support H.264
> >>        a.         Are you in favor of this option [Yes/No/Acceptable]:
> >
> > Yes
> >
> >>        b.         Do you have any objections to this option, if so
> please summarize them:
> >> 2..        All entities MUST support VP8
> >>        a.         Are you in favor of this option [Yes/No/Acceptable]:
> >
> > No
> >
> >>        b.         Do you have any objections to this option, if so
> please summarize them:
> >
> > VP8 has a formal declaration of unlicensable IPR,
> https://ietf.org/ipr/2035/  .
> >
> >> 3.         All entities MUST support both H.264 and VP8
> >>        a.         Are you in favor of this option [Yes/No/Acceptable]:
> >
> > No
> >
> >>        b.         Do you have any objections to this option, if so
> please summarize them:
> >
> > VP8 has a formal declaration of unlicensable IPR,
> https://ietf.org/ipr/2035/  .
> >
> >> 4.         Browsers MUST support both H.264 and VP8, other entities
> MUST support at least one of H.264 and VP8
> >>        a.         Are you in favor of this option [Yes/No/Acceptable]:
> >
> > No
> >
> >>        b.         Do you have any objections to this option, if so
> please summarize them:
> >
> > VP8 has a formal declaration of unlicensable IPR,
> https://ietf.org/ipr/2035/  .
> > Also, ‘browser’ is ill-defined, and it is not correct to try to divide
> the world in this way.
> >
> >> 5.         All entities MUST support at least one of H.264 and VP8
> >>        a.         Are you in favor of this option [Yes/No/Acceptable]:
> >
> > Yes
> >
> >>        b.         Do you have any objections to this option, if so
> please summarize them:
> >> 6.         All entities MUST support H.261
> >>        a.         Are you in favor of this option [Yes/No/Acceptable]:
> >
> > No
> >
> >>        b.         Do you have any objections to this option, if so
> please summarize them:
> >
> > Few have H.261 implemented any more, and those that don’t, will not
> implement to comply with this requirement.
> >
> >> 7.         There is no MTI video codec
> >>        a.         Are you in favor of this option [Yes/No/Acceptable]:
> >
> > Acceptable.
> >
> >>        b.         Do you have any objections to this option, if so
> please summarize them:
> >> 8.         All entities MUST support H.261 and all entities MUST
> support at least one of H.264 and VP8
> >>        a.         Are you in favor of this option [Yes/No/Acceptable]:
> >
> > No
> >
> >>        b.         Do you have any objections to this option, if so
> please summarize them:
> >
> > Few have H.261 implemented any more, and those that don’t, will not
> implement to comply with this requirement.
> >
> >> 9.         All entities MUST support Theora
> >>        a.         Are you in favor of this option [Yes/No/Acceptable]:
> >
> > No
> >
> >>        b.         Do you have any objections to this option, if so
> please summarize them:
> >
> > Theora is not ‘current’, it has an unclear license situation, is poorly
> supported in hardware.
> >
> >> 10.       All entities MUST implement at least two of {VP8, H.264,
> H.261}
> >>        a.         Are you in favor of this option [Yes/No/Acceptable]:
> >
> > No
> >
> >>        b.         Do you have any objections to this option, if so
> please summarize them:
> >
> > Few have H.261 implemented any more, and those that don’t, will not
> implement to comply with this requirement.
> > VP8 has a formal declaration of unlicensable IPR,
> https://ietf.org/ipr/2035/  .
> >
> >> 11.       All entities MUST implement at least two of {VP8, H.264,
> H.263}
> >>        a.         Are you in favor of this option [Yes/No/Acceptable]:
> >
> > Yes
> >
> >>        b.         Do you have any objections to this option, if so
> please summarize them:
> >> 12.       All entities MUST support decoding using both H.264 and VP8,
> and MUST support encoding using at least one of H.264 or VP8
> >>        a.         Are you in favor of this option [Yes/No/Acceptable]:
> >
> > No
> >
> >>        b.         Do you have any objections to this option, if so
> please summarize them:
> >
> > VP8 has a formal declaration of unlicensable IPR,
> https://ietf.org/ipr/2035/  .
> >
> >> 13.       All entities MUST support H.263
> >>        a.         Are you in favor of this option [Yes/No/Acceptable]:
> >
> > Yes
> >
> >>        b.         Do you have any objections to this option, if so
> please summarize them:
> >> 14.       All entities MUST implement at least two of {VP8, H.264,
> Theora}
> >>        a.         Are you in favor of this option [Yes/No/Acceptable]:
> >
> > No
> >
> >>        b.         Do you have any objections to this option, if so
> please summarize them:
> >
> > Theora is not ‘current’, it has an unclear license situation, is poorly
> supported in hardware.
> > VP8 has a formal declaration of unlicensable IPR,
> https://ietf.org/ipr/2035/  .
> >
> >> 15.       All entities MUST support decoding using Theora.
> >>        a.         Are you in favor of this option [Yes/No/Acceptable]:
> >
> > No
> >
> >>        b.         Do you have any objections to this option, if so
> please summarize them:
> >
> > Theora is not ‘current’, it has an unclear license situation, is poorly
> supported in hardware.
> >
> >> 16.       All entities MUST support Motion JPEG
> >>        a.         Are you in favor of this option [Yes/No/Acceptable]:
> >
> > Acceptable
> >
> >>        b.         Do you have any objections to this option, if so
> please summarize them:
> >>
> >
> >
> > David Singer
> > Multimedia and Software Standards, Apple Inc.
> >
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb
>
> David Singer
> Multimedia and Software Standards, Apple Inc.
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>