Re: [rtcweb] Straw Poll on Video Codec Alternatives

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 19 December 2013 12:37 UTC

Return-Path: <dromasca@avaya.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 312D51A1F7B for <rtcweb@ietfa.amsl.com>; Thu, 19 Dec 2013 04:37:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.137
X-Spam-Level:
X-Spam-Status: No, score=-3.137 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] 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 v_q-LfRcibYU for <rtcweb@ietfa.amsl.com>; Thu, 19 Dec 2013 04:37:40 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 80CB21A1F58 for <rtcweb@ietf.org>; Thu, 19 Dec 2013 04:37:37 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuIOAG/nslLGmAcV/2dsb2JhbABPCoJHIyE4VaQVB4wuiBBPgRQWdIIlAQEBAQECEggTQRsCAQgNBAQBAQsWAQYHMhQJCAIEEwgBEAmHYgEMpkWjZheOMAYKAgEeLQoBgi51gRMEmUaFPIsogyuCKg
X-IronPort-AV: E=Sophos; i="4.95,512,1384318800"; d="scan'208,217"; a="36113729"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 19 Dec 2013 07:37:32 -0500
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 19 Dec 2013 07:29:26 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0158.001; Thu, 19 Dec 2013 13:37:30 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Straw Poll on Video Codec Alternatives
Thread-Index: AQHO9QOUBPg2mbaPYkKEaR8XgJJMrZpbfkpQ
Date: Thu, 19 Dec 2013 12:37:30 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA129F56E8@AZ-FFEXMB04.global.avaya.com>
References: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com>
In-Reply-To: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.45]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA129F56E8AZFFEXMB04globa_"
MIME-Version: 1.0
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: Thu, 19 Dec 2013 12:37:47 -0000

FWIW - here is my input:


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]:  Acceptable

b.            Do you have any objections to this option, if so please summarize them: There are still unresolved IPR claims. Availability of a binary distribution would alleviate these concerns.



3.All entities MUST support both 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: There are still unresolved IPR claims on VP8. Availability of a binary distribution would alleviate these concerns



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]: Acceptable

b.            Do you have any objections to this option, if so please summarize them: are still unresolved IPR claims on VP8. Availability of a binary distribution would alleviate these concerns



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: No interoperability



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: Unacceptable RT quality



7. There is no MTI video codec

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 interoperability. This would change in 'Acceptable' if a videocodec WG is chartered immediately to develop an IPR-clean video codec specification, on the lines of the work done for the audio codec which resulted in OPUS, and the RTCWEB commits to adopt it as MTI codec



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: RT quality is not guaranteed



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: uncertain IPR status for Theora



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: RT quality is not guaranteed



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]: Acceptable

b.            Do you have any objections to this option, if so please summarize them: RT quality is not guaranteed



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: are still unresolved IPR claims on VP8.





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:  unacceptable RT quality



14. All entities MUST implement at least two of {VP8, H.264, 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:  uncertain IPR status on Theora, there are still unresolved IPR claims on VP8.



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:  uncertain IPR status on Theora





16. All entities MUST support Motion JPEG

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: inefficient codec, high BW requirements, IPR issues




From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Ted Hardie
Sent: Monday, December 09, 2013 7:25 PM
To: rtcweb@ietf.org; Gonzalo Camarillo; Richard Barnes; Magnus Westerlund; Cullen Jennings
Subject: [rtcweb] Straw Poll on Video Codec Alternatives


Dear WG,


This is the email announcing the straw poll across the video codec alternatives proposed to the WG. If you haven't read the "Next Steps in Video Codec Selection Process" (http://www.ietf.org/mail-archive/web/rtcweb/current/msg10448.html )then please do that before you continue to read.


The straw poll's purpose is to make it clear to the WG which of the alternatives that are favored or disfavored and what objections you have, if any, against a particular alternative. The WG chairs will use the information from this straw poll to identify an alternative to put as a single consensus question to the group. Thus, everyone that has an opinion on at least one alternative should answer this poll. Provide your poll input by replying to this email to the WG mailing list. The poll will run until the end of the 12th of January 2014.


As can be seen below, the poll lists the alternative that have proposed to the WG. For each alternative two questions are listed.


The first question is "Are you in favor of this option [Yes/No/Acceptable]:". These three levels allow you to indicate that you: Yes= I would be fine with the WG choosing this option. No = I really don't favor this, and it should not be picked. Acceptable = I can live with this option but I prefer something else to be picked.


The second question is "Do you have any objections to this option, if so please explain it:" If you have any objection at a minimum indicate it with a "Yes".   Please also add a short (1-sentence) summary of each of the objections you believe applies.  (If you wish to provide a longer explanation, please do so in a separate thread).  If you have no objection, leave that question blank.


Please provide input on as many of the alternatives as you like and feel comfortable to do. The more inputs, the more well informed decision the WG chairs can take when identifying the option to be brought forward for consensus. Any alternative that you chose to leave blank, will simply be considered as one without any input from you.


WG participants, please do not comment on anyone's input in this thread! If you want to comment, then create a separate thread and change the subject line to something else. Otherwise you are making life for the chairs very difficult to track the results of this straw poll.


If discussion causes you to update your position, please feel free to send an update via email on the straw poll thread prior to the closing date.


1.  All entities MUST support H.264

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

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

2.  All entities MUST support VP8

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

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

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

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

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

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

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

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

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

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

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

6.  All entities MUST support H.261

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

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

7.  There is no MTI video codec

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

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

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

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

9.  All entities MUST support Theora

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

a.    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}

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

a.    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}

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

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

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

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

13.  All entities MUST support H.263

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

a.    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}

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

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

15.  All entities MUST support decoding using Theora.

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

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

16.  All entities MUST support Motion JPEG

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

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


H.264 is a reference to the proposal in https://datatracker.ietf.org/doc/draft-burman-rtcweb-h264-proposal/<https://datatracker.ietf.org/doc/draft-burman-rtcweb-h264-proposal/>


VP8 is a reference to the proposal in https://datatracker.ietf.org/doc/draft-alvestrand-rtcweb-vp8/<https://datatracker.ietf.org/doc/draft-alvestrand-rtcweb-vp8/>


Theora is a reference to Xiph.org Theora Specification from March 16, 2011 (http://www.xiph.org/theora/doc/Theora_I_spec.pdf)


H.263 is a reference to profile 0 level 70 defined in annex X of ITU-T rec H.263 (http://www.itu.int/rec/T-REC-H.263/)


H.261 is a reference to http://tools.ietf.org/html/rfc4587


Motion JPEG is a reference to http://tools.ietf.org/html/rfc2435


Thanks,


The Chairs