Re: [rtcweb] Straw Poll on Video Codec Alternatives

Daniel-Constantin Mierla <miconda@gmail.com> Fri, 10 January 2014 22:30 UTC

Return-Path: <miconda@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 901181AE1BC for <rtcweb@ietfa.amsl.com>; Fri, 10 Jan 2014 14:30:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 Ow1AWFRTA2Vn for <rtcweb@ietfa.amsl.com>; Fri, 10 Jan 2014 14:30:17 -0800 (PST)
Received: from mail-ea0-x22e.google.com (mail-ea0-x22e.google.com [IPv6:2a00:1450:4013:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB4F1ACC84 for <rtcweb@ietf.org>; Fri, 10 Jan 2014 14:30:17 -0800 (PST)
Received: by mail-ea0-f174.google.com with SMTP id b10so2302608eae.33 for <rtcweb@ietf.org>; Fri, 10 Jan 2014 14:30:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :content-type; bh=zzKEkkcqTS1OR9e3ymdSYSE8eR28yCjInF4TLyl0vdw=; b=x5891VsL89c9cAJBvvgAVe2xtcHZkwUKh4STe6pRh53QF8lenM8GwMJJcIhhHIWf0k N64BqF6P7va5GeBOHXPFtf+UFM/H2Hz1ga0mTwGBb7QewS7I1eCOAJDkTkLlBvbIqiLK H0W+K9E+D+jNQH/n2f+x9iR7r/STSVY/inMZ3QV86zw4CIPBSenfjfSX6TqmlX7q4bk4 7blMVd52izcsO4q9CWtBmAIh7wr6UMJ3lzcwek6wpsddgiqRI1MmDanH1eA3T3eXI5ny mV+s85K+bKqYTSDdirQsZb7tGjN5A3xNa9U6nxFuh2OrRVblsenxhRnTRANQitW2qpK3 gJrQ==
X-Received: by 10.15.56.132 with SMTP id y4mr6276726eew.61.1389393006906; Fri, 10 Jan 2014 14:30:06 -0800 (PST)
Received: from [127.0.0.1] (ns.asipto.com. [213.133.111.169]) by mx.google.com with ESMTPSA id e3sm18028631eeg.11.2014.01.10.14.30.02 for <rtcweb@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Jan 2014 14:30:05 -0800 (PST)
Message-ID: <52D0746B.9070305@gmail.com>
Date: Fri, 10 Jan 2014 23:30:03 +0100
From: Daniel-Constantin Mierla <miconda@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: rtcweb@ietf.org
Content-Type: multipart/alternative; boundary="------------080706030701020008020305"
Subject: Re: [rtcweb] Straw Poll on Video Codec Alternatives
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: miconda@gmail.com
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: Fri, 10 Jan 2014 22:30:22 -0000

1. All entities MUST support H.264
   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:
*Too many IPR issues and licensing constraints that makes its usage 
effectively impossible in a lot of cases****. It has royalty fees (some 
known, but many unknown) -- imposing a financial revenue from 
implementers/users towards various companies via Internet/IEFT standards 
is beyond common sense, openness for everyone and target for innovation 
that governed Internet evolution so far. Full hardware H.264 
encoders/decoders don't really exist at scale, especially on exiting 
mobile devices where it would be relevant, or at least not exposed to 
any third parties -- expecting that some vendors will do it is 
comparable with expecting all claims of VP8 IPR will be dismissed.
*


2. All entities MUST support 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:


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:
*Too many already known IPR, licensing and other kinds of issues for 
H.264 (See 1)****.*


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:
*Too many already known IPR, licensing and other kinds of issues for 
H.264 (See 1)**.*
*

*
5. 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:
*R**equires transcoding to operate with all of 'fully compliant' 
implementations and, with that, exposes to all the issues of H.264.*


6. All entities MUST support H.261
   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:


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:
*Better let the market to decide than impose upfront a wrong choice**.*


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]: *Acceptable*
   b. Do you have any objections to this option, if so please summarize 
them:
**

9. All entities MUST support Theora
   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:

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]: *Acceptable*
   b. Do you have any objections to this option, if so please summarize 
them:


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]: *No*
   b. Do you have any objections to this option, if so please summarize 
them:
*No if there are risks on**H.263 IPR/licensing***not to be royalty free 
for all use cases*, then better use VP8 that has higher chances to be 
cleared out of issues. Yes, otherwise.

*

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]: *Acceptable*
   b. Do you have any objections to this option, if so please summarize 
them:
*Only if there are no **IPR/licensing issues **decoding H.264.*

13. All entities MUST support H.263
   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:
*If there are risks on**H.263 IPR/licensing***not to be royalty free for 
all use cases*, then better use VP8 that has higher chances to be 
cleared out of issues.**Yes, otherwise.*

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:
*If there are risks on**Theora IPR/***licensing* not to be royalty free 
for all use cases, then better use VP8 that has higher chances to be 
cleared out of issues.**Yes, otherwise.


*
15. All entities MUST support decoding using Theora.
   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:
*Only if there are no **IPR/licensing issues **decoding Theora.*


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:

*
*

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda