Re: [rtcweb] Straw Poll on Video Codec Alternatives

<stephane.proust@orange.com> Wed, 08 January 2014 14:49 UTC

Return-Path: <stephane.proust@orange.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 658A11AD9AE for <rtcweb@ietfa.amsl.com>; Wed, 8 Jan 2014 06:49:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 ro65JtSwjW2F for <rtcweb@ietfa.amsl.com>; Wed, 8 Jan 2014 06:49:11 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id B57031ACCE2 for <rtcweb@ietf.org>; Wed, 8 Jan 2014 06:49:09 -0800 (PST)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id 11C542DC44B for <rtcweb@ietf.org>; Wed, 8 Jan 2014 15:49:00 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id EFE0135C069 for <rtcweb@ietf.org>; Wed, 8 Jan 2014 15:48:59 +0100 (CET)
Received: from PEXCVZYM14.corporate.adroot.infra.ftgroup ([fe80::a42f:c628:bc76:d592]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0174.001; Wed, 8 Jan 2014 15:48:59 +0100
From: stephane.proust@orange.com
To: "'rtcweb@ietf.org'" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Straw Poll on Video Codec Alternatives
Thread-Index: AQHPDA+KNkNL8d3kRfKareLqRrJC45p60HUAgAAWVqA=
Date: Wed, 08 Jan 2014 14:48:58 +0000
Message-ID: <24246_1389192540_52CD655C_24246_10551_1_2842AD9A45C83B44B57635FD4831E60A06CBBE09@PEXCVZYM14.corporate.adroot.infra.ftgroup>
References: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com> <20140108011831.GA18453@verdi> <CAMKM2Lyo0zvRGEhdtz7ea+xySt3nUBuwgSX3FBQyYR2k4aOxow@mail.gmail.com>
In-Reply-To: <CAMKM2Lyo0zvRGEhdtz7ea+xySt3nUBuwgSX3FBQyYR2k4aOxow@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.38.1]
Content-Type: multipart/alternative; boundary="_000_2842AD9A45C83B44B57635FD4831E60A06CBBE09PEXCVZYM14corpo_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.1.8.120916
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: Wed, 08 Jan 2014 14:49:14 -0000

Please find below my answer to the straw poll on video codec alternatives as requested by the Chairs

http://www.ietf.org/mail-archive/web/rtcweb/current/msg10449.html


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

b.    Do you have any objections to this option, if so please summarize them: Lack of interoperability with existing video services + financial risks due to unclear IPR status



3.    All entities MUST support both 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: Since H.264 must be supported, the addition of VP8 means additional costs and risks with no value added for interop.



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

b.    Do you have any objections to this option, if so please summarize them: Same reasons as for 3



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: Does not ensure 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: Low quality, Does not provide interoperability with existing video services



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: Does not ensure interoperability



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: Same reasons as for 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: Does not ensure interoperability with existing video services. Increase potential future transcoding use cases



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: Same reasons as for 5 and 6



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: Same reasons as for 5 and 6



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: Does not ensure interoperability with existing video services



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: Lower quality than H.264 or VP8, Market footprint limited and decreasing



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: Same reasons as for 5 and 9



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: Does not ensure  interoperability



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: Not acceptable from bit rate/quality perspective




_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.