Re: [rtcweb] Straw Poll on Video Codec Alternatives

Göran Eriksson AP <goran.ap.eriksson@ericsson.com> Fri, 10 January 2014 15:49 UTC

Return-Path: <goran.ap.eriksson@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 34F251AE0B0 for <rtcweb@ietfa.amsl.com>; Fri, 10 Jan 2014 07:49:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.551
X-Spam-Level:
X-Spam-Status: No, score=-3.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, 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 QTMw0hCUJXIj for <rtcweb@ietfa.amsl.com>; Fri, 10 Jan 2014 07:49:55 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 39D501AE0D9 for <rtcweb@ietf.org>; Fri, 10 Jan 2014 07:49:51 -0800 (PST)
X-AuditID: c1b4fb25-b7eff8e000000eda-e8-52d01694db94
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 8E.06.03802.49610D25; Fri, 10 Jan 2014 16:49:40 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.201]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.02.0347.000; Fri, 10 Jan 2014 16:49:40 +0100
From: Göran Eriksson AP <goran.ap.eriksson@ericsson.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Straw Poll on Video Codec Alternatives
Thread-Index: AQHO9QOTPGzYi6xM1EqayVAcPG13bZp8p54wgAGjqNA=
Date: Fri, 10 Jan 2014 15:49:39 +0000
Message-ID: <532A6DC6F9C115439C41705FF73D13871C4935ED@ESESSMB209.ericsson.se>
References: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com> <BBE9739C2C302046BD34B42713A1E2A22E0DBF18@ESESSMB105.ericsson.se>
In-Reply-To: <BBE9739C2C302046BD34B42713A1E2A22E0DBF18@ESESSMB105.ericsson.se>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKLMWRmVeSWpSXmKPExsUyM+Jvje4UsQtBBo9bJC3W/mtnd2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXRvO6X4wFb5Uqzi48zdjA+EK6i5GTQ0LARGLepSfMELaYxIV7 69m6GLk4hAQOMUrsO/OOGcJZwijRNvszG0gVm4C3xLQVZ1lBbBEBdYnLDy+wg9jCAjYSm5ae YIGI20q82L0NyraSmHXoDJDNzsEioCpxTxgkyivgK7H+1GMWiPFTGCXuzb3E1MXIwcEp4Cex oSkZpIZRQFbi/vd7YFOYBcQlbj2ZzwRxp4DEkj3noW4WlXj5+B8rhK0o0f60gRGiXk/ixtQp bBC2tsSyha+ZIfYKSpyc+YRlAqPoLCRjZyFpmYWkZRaSlgWMLKsY2XMTM3PSy402MQKD/uCW 36o7GO+cEznEKM3BoiTO++Gtc5CQQHpiSWp2ampBalF8UWlOavEhRiYOTqkGRuOq9ljpJ9Jq y+/FlNWy6f1bfc3tvNmv0hXBHPN2CMb+KNpw+97bS3/rvizvjLokLlf61txQTXc1U27SkR6V +fJpx2fLT9xiyLXYapvBusiOFS4r1jxaJLHFYVqaufrcfdZPDL7HxwhF7f155jk7/+Oy+x0z WO894vRKn8Z1WH2fe3Xjs/RN85VYijMSDbWYi4oTATeFLqJIAgAA
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 15:49:59 -0000

Hi all,

Here's my input.

Many regards
Göran


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:
The licensing situation is at the moment still uncertain.

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:

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:

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:

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:

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:
    In case a consensus cannot be reached this time, a no MTI Video is acceptable for the first version 
    of the API since further discussions will continue to delay and take focus from other parts of work.
    This has the effect of also delaying the start of the work in subsequent versions, or phases, of the
    API and the underlying implementation, which is also important for the WebRTC standard competitiveness. 
    It should however be noted that long term, an MTI video is preferable.

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:

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:

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:

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:

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:

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

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:

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:

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:

H.264 is a reference to the proposal in 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/

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