Re: [rtcweb] Straw Poll on Video Codec Alternatives

Gunnar Hellstrom <gunnar.hellstrom@omnitor.se> Tue, 24 December 2013 21:48 UTC

Return-Path: <gunnar.hellstrom@omnitor.se>
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 C407F1AE079 for <rtcweb@ietfa.amsl.com>; Tue, 24 Dec 2013 13:48:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 WmuZHjfETRHO for <rtcweb@ietfa.amsl.com>; Tue, 24 Dec 2013 13:48:04 -0800 (PST)
Received: from vsp-authed-02-02.binero.net (vsp-authed02.binero.net [195.74.38.226]) by ietfa.amsl.com (Postfix) with ESMTP id 3479A1AE0C6 for <rtcweb@ietf.org>; Tue, 24 Dec 2013 13:48:01 -0800 (PST)
Received: from smtp01.binero.se (unknown [195.74.38.28]) by vsp-authed-02-02.binero.net (Halon Mail Gateway) with ESMTPS for <rtcweb@ietf.org>; Tue, 24 Dec 2013 22:47:50 +0100 (CET)
Received: from [172.20.10.6] (109.58.148.144.bredband.tre.se [109.58.148.144]) (Authenticated sender: gunnar.hellstrom@omnitor.se) by smtp-09-01.atm.binero.net (Postfix) with ESMTPA id C7CC63A11B for <rtcweb@ietf.org>; Tue, 24 Dec 2013 22:47:48 +0100 (CET)
Message-ID: <52BA0105.9090801@omnitor.se>
Date: Tue, 24 Dec 2013 22:47:49 +0100
From: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com>
In-Reply-To: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070407030002050809090301"
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: Tue, 24 Dec 2013 21:48:09 -0000

My views:
On 2013-12-09 18:24, Ted Hardie wrote:
>
>
> 1.
>
>     All entities MUST support H.264
>
>     1.
>
>         Are you in favor of this option [Yes/No/Acceptable]: Yes
>
>     2.
>
>         Do you have any objections to this option, if so please
>         summarize them:
>
> 2.
>
>     All entities MUST support VP8
>
>     1.
>
>         Are you in favor of this option [Yes/No/Acceptable]: Acceptable
>
>     2.
>
>         Do you have any objections to this option, if so please
>         summarize them: Will cause more interoperability problems with
>         other environmnets than H.264.
>
> 3.
>
>     All entities MUST support both H.264 and VP8
>
>     1.
>
>         Are you in favor of this option [Yes/No/Acceptable]: Acceptable
>
>     2.
>
>         Do you have any objections to this option, if so please
>         summarize them: More complex than plain H.264
>
> 4.
>
>     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]: Acceptable.
>
>     2.
>
>         Do you have any objections to this option, if so please
>         summarize them: Will cause more problems with interop with
>         other environments than plain H.264.
>
> 5.
>
>     All entities MUST support at least one of H.264 and VP8
>
>     1.
>
>         Are you in favor of this option [Yes/No/Acceptable]: No
>
>     2.
>
>         Do you have any objections to this option, if so please
>         summarize them: Does not encourage interoperability sufficiently.
>
> 6.
>
>     All entities MUST support H.261
>
>     1.
>
>         Are you in favor of this option [Yes/No/Acceptable]: No
>
>     2.
>
>         Do you have any objections to this option, if so please
>         summarize them: H.261 has no suitable formats for modern cameras.
>
> 7.
>
>     There is no MTI video codec
>
>     1.
>
>         Are you in favor of this option [Yes/No/Acceptable]: No
>
>     2.
>
>         Do you have any objections to this option, if so please
>         summarize them:
>         Does not encourage interoperability sufficiently. Acceptable
>         if MTI is agreed by another powerful organization.
>
> 8.
>
>     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
>
>     2.
>
>         Do you have any objections to this option, if so please
>         summarize them: H.261 has no suitable formats for modern cameras.
>
> 9.
>
>     All entities MUST support Theora
>
>     1.
>
>         Are you in favor of this option [Yes/No/Acceptable]: No
>
>     2.
>
>         Do you have any objections to this option, if so please
>         summarize them: Not sufficiently wide spread before to be of
>         interest.
>
>10.
>
>     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
>
>     2.
>
>         Do you have any objections to this option, if so please
>         summarize them: Complex construction. H.261 is not sufficient.
>
>11.
>
>     All entities MUST implement at least two of {VP8, H.264, H.263}
>
>     1.
>
>         Are you in favor of this option [Yes/No/Acceptable]: Acceptable
>
>     2.
>
>         Do you have any objections to this option, if so please
>         summarize them: Will cause risk for transcoding to achieve
>         interop with other environments.
>
>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
>
>     1.
>
>         Are you in favor of this option [Yes/No/Acceptable]: No
>
>     2.
>
>         Do you have any objections to this option, if so please
>         summarize them: Asymmetric support have interoperability risks
>
>13.
>
>     All entities MUST support H.263
>
>     1.
>
>         Are you in favor of this option [Yes/No/Acceptable]: Acceptable
>
>     2.
>
>         Do you have any objections to this option, if so please
>         summarize them: Quite good, but sad to not agree on latest
>         generation.
>
>14.
>
>     All entities MUST implement at least two of {VP8, H.264, Theora}
>
>     1.
>
>         Are you in favor of this option [Yes/No/Acceptable]: No
>
>     2.
>
>         Do you have any objections to this option, if so please
>         summarize them: Theora is too little implemented to be of
>         interest.
>
>15.
>
>     All entities MUST support decoding using Theora.
>
>     1.
>
>         Are you in favor of this option [Yes/No/Acceptable]: No
>
>     2.
>
>         Do you have any objections to this option, if so please
>         summarize them: Theora is too little implemented
>
>16.
>
>     All entities MUST support Motion JPEG
>
>     1.
>
>         Are you in favor of this option [Yes/No/Acceptable]: No
>
>     2.
>
>         Do you have any objections to this option, if so please
>         summarize them: MJPEG is too bandwidth hungry
>
>
>
/Gunnar
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb