Re: [rtcweb] Straw Poll on Video Codec Alternatives

Roman Shpount <roman@telurix.com> Wed, 11 December 2013 18:15 UTC

Return-Path: <roman@telurix.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 E62961ADFD3 for <rtcweb@ietfa.amsl.com>; Wed, 11 Dec 2013 10:15:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 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, SPF_PASS=-0.001] 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 odZ_mNzrNaP4 for <rtcweb@ietfa.amsl.com>; Wed, 11 Dec 2013 10:15:15 -0800 (PST)
Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) by ietfa.amsl.com (Postfix) with ESMTP id 3897E1AE005 for <rtcweb@ietf.org>; Wed, 11 Dec 2013 10:15:15 -0800 (PST)
Received: by mail-wg0-f43.google.com with SMTP id k14so6884179wgh.10 for <rtcweb@ietf.org>; Wed, 11 Dec 2013 10:15:09 -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=ScWpY7OkVO3j6Dj3lagPCCMrqJ7UlQYcGq3IfSZ83hg=; b=eDQRc2GDL+iQK9OA1eVeE8XEfjP65KOkW7aga+kXxEZlqnhcRpCHkodwgCoZZuoXyh rdDOzh2VTbxxhGy/iw9S25Q5yl7qwwlrHZ0MNelT43ALxdIz6p873XsNWU8bTJcEK21M GOEBvLwC16bUJGNyaCBMzZsnObC44oY/DIwFkRD4Xl8ce5YQgiijcak+UC2gVRSudKg9 d3vYOHC/dUXtc2Hwhmuxfuho9Bj5g1+fnsRHIQwcpBzRKdmoQ7iUdtYUt4OcP22G0gdx zySFrags8bYxSoPsI1tKRIbVNZkWmsV5k6FkjpQtuIn05SLfzqCrS0yfgJGET+BYpbvo RFsQ==
X-Gm-Message-State: ALoCoQniul1ZYq0l5YXxXh7yI3AFo3HUdvY3Y2qZCsm0SYmlkWm6eUZqjWg2LsMqFz+VxA6Z9Boz
X-Received: by 10.180.160.212 with SMTP id xm20mr25201603wib.33.1386785708908; Wed, 11 Dec 2013 10:15:08 -0800 (PST)
Received: from mail-we0-f177.google.com (mail-we0-f177.google.com [74.125.82.177]) by mx.google.com with ESMTPSA id mz10sm17218307wic.2.2013.12.11.10.15.07 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Dec 2013 10:15:07 -0800 (PST)
Received: by mail-we0-f177.google.com with SMTP id u56so6774846wes.22 for <rtcweb@ietf.org>; Wed, 11 Dec 2013 10:15:06 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.23.201 with SMTP id o9mr2717216wjf.67.1386785706524; Wed, 11 Dec 2013 10:15:06 -0800 (PST)
Received: by 10.217.88.133 with HTTP; Wed, 11 Dec 2013 10:15:06 -0800 (PST)
In-Reply-To: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com>
References: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com>
Date: Wed, 11 Dec 2013 13:15:06 -0500
Message-ID: <CAD5OKxuq6C8Gz7oUnvh0-GRRo=k3qwq4dd0zDO3Fg4G-hzfQYw@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="047d7b3a956c6ac82a04ed46358b"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, Cullen Jennings <fluffy@cisco.com>
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, 11 Dec 2013 18:15:19 -0000

   1.

   All entities MUST support H.264
   1.

      Are you in favor of this option [Yes/No/Acceptable]:

 No

   1.

      Do you have any objections to this option, if so please summarize
      them:


 Not acceptable to anybody who is not already using H.264 due to its
licensing schema. To license H.264 you need to make a deal with MPEG-LA.
After this you need to make a deal with Nokia and other people not part of
MPEG-LA. As a result you are going to get rights to decoder. Encoder is not
specified by the standard and there are no obligations for MPEG members to
declare anything, so you are more then likely exposed to addition IPR risks
when implementing a good encoder. You cannot afford not to license since if
you are real business (ie one generating money or taking investor money)
you cannot afford such business risk. Even if you are planning to
distribute less then 100K codec instances you will still need a license
since MPEG-LA terms are ambiguous enough that you would want to have a
contact that clarifies what exactly you can do. After you jumped through
all these licensing hoops you are still exposed to all the potential
undisclosed IPR with your only hope that patent trolls will go after the
bigger guys first (from my experience they will not).


 Using Cisco binary codec is also unacceptable unless you are doing
something basic since it limits what you can do by requiring to use their
pre-built binary. I am building conferencing servers, so I expect that I
will need to optimize the codec for my needs. I will need to build custom
optimized VP8 to H.264 transcoder. I will need to build custom H.264
bitrate adaptation (ie H.264 to H.264 transcoder to adjust bitrate). All of
this is not an option with Cisco binary.



   1.

   All entities MUST support VP8
   1.

      Are you in favor of this option [Yes/No/Acceptable]:

 Acceptable

   1.

      Do you have any objections to this option, if so please summarize
      them:


 It is acceptable since implementation is provided by Google under
reasonable license terms. It is not a strong yes since VP8 is not formally
defined by any standard's body.



   1.

   All entities MUST support both H.264 and VP8
   1.

      Are you in favor of this option [Yes/No/Acceptable]:

 No

   1.

      Do you have any objections to this option, if so please summarize
      them:


 Not acceptable due to H.264 licensing. Creates additional burden on
development and support



   1.

   Browsers MUST support both H.264 and VP8, other entities MUST support at
   least one of H.264 and VP8
   1.

      Are you in favor of this option [Yes/No/Acceptable]:

 No

   1.

      Do you have any objections to this option, if so please summarize
      them:


 Not acceptable due to H.264 licensing. Creates additional burden on
development and support



   1.

   All entities MUST support at least one of H.264 and VP8
   1.

      Are you in favor of this option [Yes/No/Acceptable]:

 No

   1.

      Do you have any objections to this option, if so please summarize
      them:

 Does not result in MTI.



   1.

   All entities MUST support H.261
   1.

      Are you in favor of this option [Yes/No/Acceptable]:

 No

   1.

      Do you have any objections to this option, if so please summarize
      them:

 Quality is not acceptable for modern video communications



   1.

   There is no MTI video codec
   1.

      Are you in favor of this option [Yes/No/Acceptable]:

 No

   1.

      Do you have any objections to this option, if so please summarize
      them:

 Video is essential to WebRTC



   1.

   All entities MUST support H.261 and all entities MUST support at least
   one of H.264 and VP8
   1.

      Are you in favor of this option [Yes/No/Acceptable]:

 No

   1.

      Do you have any objections to this option, if so please summarize
      them:

 Essentially makes H.261 an MTI, but its quality is not acceptable for
modern video communications



   1.

   All entities MUST support Theora
   1.

      Are you in favor of this option [Yes/No/Acceptable]:

 No

   1.

      Do you have any objections to this option, if so please summarize
      them:

 No better then VP8 since it never went through a standard body, but much
worse quality wise.



   1.

   All entities MUST implement at least two of {VP8, H.264, H.261}
   1.

      Are you in favor of this option [Yes/No/Acceptable]:

 No

   1.

      Do you have any objections to this option, if so please summarize
      them:


 Additional burden on implementation and support with a strong option of
using H.261 for call which is not acceptable due to quality.



   1.

   All entities MUST implement at least two of {VP8, H.264, H.263}
   1.

      Are you in favor of this option [Yes/No/Acceptable]:

 No

   1.

      Do you have any objections to this option, if so please summarize
      them:


 Additional burden on implementation and support with a strong option of
using H.263 for call which is not acceptable due to quality and additional
IPR licensing requirements



   1.

   All entities MUST support decoding using both H.264 and VP8, and MUST
   support encoding using at least one of H.264 or VP8
   1.

      Are you in favor of this option [Yes/No/Acceptable]:

 No

   1.

      Do you have any objections to this option, if so please summarize
      them:

 Decoding H.264 has exactly the same licensing issues as encoding it, so it
is as unacceptable for me as simple H.264 support



   1.

   All entities MUST support H.263
   1.

      Are you in favor of this option [Yes/No/Acceptable]:

 No

   1.

      Do you have any objections to this option, if so please summarize
      them:

 Quality is much worse then H.264 and VP8. Still requires IPR licensing



   1.

   All entities MUST implement at least two of {VP8, H.264, Theora}
   1.

      Are you in favor of this option [Yes/No/Acceptable]:

 No

   1.

      Do you have any objections to this option, if so please summarize
      them:


 Additional support burden. Theora can be used for communications but its
quality is much worse then VP8 or H.264



   1.

   All entities MUST support decoding using Theora.
   1.

      Are you in favor of this option [Yes/No/Acceptable]:

 No

   1.

      Do you have any objections to this option, if so please summarize
      them:

 Does not create an MTI



   1.

   All entities MUST support Motion JPEG
   1.

      Are you in favor of this option [Yes/No/Acceptable]:

 No

   1.

      Do you have any objections to this option, if so please summarize
      them:


 Resulting quality would be so bad it would be almost unusable.

______________

Roman Shpount