Re: [rtcweb] Straw Poll on Video Codec Alternatives

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Fri, 10 January 2014 10:21 UTC

Return-Path: <keith.drage@alcatel-lucent.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 B372D1ADF9D for <rtcweb@ietfa.amsl.com>; Fri, 10 Jan 2014 02:21:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] 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 VcgtS9bZ62jW for <rtcweb@ietfa.amsl.com>; Fri, 10 Jan 2014 02:21:06 -0800 (PST)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id DCCBE1ADF7F for <rtcweb@ietf.org>; Fri, 10 Jan 2014 02:21:05 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s0AAKsXI007669 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <rtcweb@ietf.org>; Fri, 10 Jan 2014 04:20:55 -0600 (CST)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s0AAKr9m031875 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtcweb@ietf.org>; Fri, 10 Jan 2014 11:20:54 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.203]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Fri, 10 Jan 2014 11:20:54 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Straw Poll on Video Codec Alternatives
Thread-Index: AQHO9QO2ubcd8jULd0mZjw0Bzj7W3Jp9xLQAgAAEkACAAAr6gIAAG//w
Date: Fri, 10 Jan 2014 10:20:52 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B101649@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com> <E8F5F2C7B2623641BD9ABF0B622D726D2B513475@xmb-rcd-x11.cisco.com> <2DA16AA9-5CE3-4243-93E2-F48F4F673037@cisco.com> <52CFBF3F.3030708@orange.com>
In-Reply-To: <52CFBF3F.3030708@orange.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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: Fri, 10 Jan 2014 10:21:07 -0000

My responses:

Keith

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:

Not applicable

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

We are interested in interworking webrtc communications with the existing telecommunications infrastructure. All video there is currently H.264.

This would point the market to being only VP8 and would ensure that all communications outside webrtc would need the video transcoded. While that is technically feasible, we would prefer to limit those scenarios where it is necessary, e.g. multiparty conference.

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:

The addition of VP8 means additional costs and real-time performance risks for interworking equipment with existing telecommunications infrastructure which we would prefer to avoid.

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:

The addition of VP8 means additional costs and real-time performance risks for interworking equipment with existing telecommunications infrastructure which we would prefer to avoid.

If this option is adopted, then a clear definition of browser will need to be provided.

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:

This provides no solution to interworking with existing telecommunication infrastructure assuming the implementation decision is effectively made by the browser provider rather than the application.

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:

There is no existing current telecommunications infrastructure implementing this and therefore to promote this is as a solution would be wasted effort that would achieve no interoperability with existing telecommunications infrastructure. The quality over a wireless access technology is unknown.

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:

Given the amount of resource spent trying to find a MTI codec without success, we would rather park the issue and move on. In any case, the decision on an MTI codec would need to be taken again in a few years time. We believe that lack of an MTI codec is not a major barrier to deployment.

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

NO

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

See answers to 5) and 6).

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:

See answers to 5) and 6).

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

NO

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

This option can result in the exclusion on H.264, which is the main codec deployed in existing telecommunications environments, and therefore there will be no interoperability with existing telecommunications environments without transcoding.

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:

See 10)

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

NO

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

See 10)

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:

See 10)

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:

See 10)

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:

See 10)

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:

See 10)