Re: [rtcweb] Straw Poll on Video Codec Alternatives

Bo Burman <bo.burman@ericsson.com> Fri, 10 January 2014 00:23 UTC

Return-Path: <bo.burman@ericsson.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 884851AD34C for <rtcweb@ietfa.amsl.com>; Thu, 9 Jan 2014 16:23:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level:
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, 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 KiDrNt87A6N3 for <rtcweb@ietfa.amsl.com>; Thu, 9 Jan 2014 16:23:13 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id C63371ACCEC for <rtcweb@ietf.org>; Thu, 9 Jan 2014 16:23:12 -0800 (PST)
X-AuditID: c1b4fb30-b7f228e000003e6c-aa-52cf3d66ff12
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 67.75.15980.66D3FC25; Fri, 10 Jan 2014 01:23:02 +0100 (CET)
Received: from ESESSMB105.ericsson.se ([169.254.5.37]) by ESESSHC004.ericsson.se ([153.88.183.30]) with mapi id 14.02.0347.000; Fri, 10 Jan 2014 01:23:01 +0100
From: Bo Burman <bo.burman@ericsson.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Straw Poll on Video Codec Alternatives
Thread-Index: AQHO9QOT5NGlgE/askO/+wQU0SKbjJp8p54w
Date: Fri, 10 Jan 2014 00:23:01 +0000
Message-ID: <BBE9739C2C302046BD34B42713A1E2A22E0DBF18@ESESSMB105.ericsson.se>
References: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com>
In-Reply-To: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKLMWRmVeSWpSXmKPExsUyM+JvjW6a7fkgg73XhCzW/mtnd2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxs1n5gULtSoazs5gamDsU+pi5OSQEDCR2N0+gx3CFpO4cG89 WxcjF4eQwCFGiSMXZjJDOIsZJfZsW8UMUsUmoCExf8ddRhBbREBd4vLDC2DdwgI2EpuWnmCB iNtKvNi9Dco2kvjQfRKsnkVAVeLVkx1gcV4BX4lfv7qZQGwhgQCJb9uWAcU5ODgFAiUWr4oC CTMKyErc/34PrJxZQFzi1pP5TBCHCkgs2XOeGcIWlXj5+B8rhK0ksfbwdqh6HYkFuz+xQdja EssWvmaGWCsocXLmE5YJjKKzkIydhaRlFpKWWUhaFjCyrGJkz03MzEkvN9/ECAz6g1t+G+xg 3HRf7BCjNAeLkjjvh7fOQUIC6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoYD8T8OFN8+ZFXfVIA 26bbIanFqvOXNb1kvRTBU9uiP/HT3nvvTq9ZfSIwTUrSc6pW2/K9b93sSk8fM5rTHtzrHc54 zmbftdLkya9XZngbTAn8IMI4Q2//s+0sJfWzTqzo2/f39/+zF8r+XH4p9+ClWrbf23afG1Ef 53rVWzZZMv95/Txiq/bERUosxRmJhlrMRcWJAM7YROpIAgAA
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: Fri, 10 Jan 2014 00:23:15 -0000

Here's 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
 . Are you in favor of this option [Yes/No/Acceptable]:
NO
a. Do you have any objections to this option, if so please summarize them:
VP8 does not provide any technical advantage over H.264, is not developed or maintained through any recognized standardization process, and is currently formally not possible to license.

3. All entities MUST support both H.264 and VP8
 . Are you in favor of this option [Yes/No/Acceptable]:
NO
a. Do you have any objections to this option, if so please summarize them:
VP8 does not provide any technical advantage over H.264, is not developed or maintained through any recognized standardization process, and is currently formally not possible to license.

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]:
NO
a. Do you have any objections to this option, if so please summarize them:
It seems less than obvious how to define exactly what is a "browser" in this context.
VP8 does not provide any technical advantage over H.264, is not developed or maintained through any recognized standardization process, and is currently formally not possible to license.

5. All entities MUST support at least one of H.264 and VP8
. Are you in favor of this option [Yes/No/Acceptable]:
NO
a. Do you have any objections to this option, if so please summarize them:
Does not provide interoperability between all WebRTC implementations.

6. All entities MUST support H.261
 . Are you in favor of this option [Yes/No/Acceptable]:
NO
a. Do you have any objections to this option, if so please summarize them:
H.261 cannot support sufficient quality or bandwidth efficiency and is not widely supported.

7. There is no MTI video codec
 . Are you in favor of this option [Yes/No/Acceptable]:
Acceptable
a. Do you have any objections to this option, if so please summarize them:
Acceptable as outcome if no other MTI consensus can be found.

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]:
NO
a. Do you have any objections to this option, if so please summarize them:
The fallback H.261 cannot support sufficient quality or bandwidth efficiency and is not widely supported.

9. All entities MUST support Theora
 . Are you in favor of this option [Yes/No/Acceptable]:
NO
a. Do you have any objections to this option, if so please summarize them:
Theora has unclear performance and licensing and is not widely supported.

10. All entities MUST implement at least two of {VP8, H.264, H.261}
 . Are you in favor of this option [Yes/No/Acceptable]:
NO
a. Do you have any objections to this option, if so please summarize them:
H.261 cannot support sufficient quality or bandwidth efficiency and is not widely supported.

11. All entities MUST implement at least two of {VP8, H.264, H.263}
 . Are you in favor of this option [Yes/No/Acceptable]:
NO
a. Do you have any objections to this option, if so please summarize them:
Expect that option 13 will effectively be the same and that option is preferable since it is more lightweight.

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]:
NO
a. Do you have any objections to this option, if so please summarize them:
Don't really see the benefit compared to option 3.
VP8 does not provide any technical advantage over H.264, is not developed or maintained through any recognized standardization process, and is currently formally not possible to license.

13. All entities MUST support H.263
 . Are you in favor of this option [Yes/No/Acceptable]:
Acceptable
a. Do you have any objections to this option, if so please summarize them:
Sufficient quality and bandwidth efficiency for some use cases and thus better fallback option than MJPEG, H.261 or Theora.

14. All entities MUST implement at least two of {VP8, H.264, Theora}
 . Are you in favor of this option [Yes/No/Acceptable]:
NO
a. Do you have any objections to this option, if so please summarize them:
VP8 does not provide any technical advantage over H.264, is not developed or maintained through any recognized standardization process, and is currently formally not possible to license.
Theora has unclear performance and licensing and is not widely supported.

15. All entities MUST support decoding using Theora.
 . Are you in favor of this option [Yes/No/Acceptable]:
NO
a. Do you have any objections to this option, if so please summarize them:
Don't see any practical point with just specifying decoding in a communication scenario.
Theora has unclear performance and licensing and is not widely supported.

16. All entities MUST support Motion JPEG
 . Are you in favor of this option [Yes/No/Acceptable]:
NO
a. Do you have any objections to this option, if so please summarize them:
MJPEG does not provide sufficient bandwidth efficiency for most use cases.