IETF Logo Mail Archive

[rtcweb] Straw Poll on Video Codec Alternatives

"Jeremy Laurenson (jlaurens)" <jlaurens@cisco.com> Mon, 13 January 2014 14:37 UTC

Return-Path: <jlaurens@cisco.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 DF7E61AE15A for <rtcweb@ietfa.amsl.com>; Mon, 13 Jan 2014 06:37:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.039
X-Spam-Level:
X-Spam-Status: No, score=-15.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.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 6TYYzbArVGi2 for <rtcweb@ietfa.amsl.com>; Mon, 13 Jan 2014 06:37:51 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 5157B1AE09C for <rtcweb@ietf.org>; Mon, 13 Jan 2014 06:37:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10290; q=dns/txt; s=iport; t=1389623860; x=1390833460; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=YAo9Pw0TKCPvSRJEbb2bIRUXmkgJARDaXYu4pKbHWNs=; b=Z8vDnLYJBa02gh21ix11L4bifja8Rn/H++PfkWGXI7t6lT+B9niDntTe 0MSyocFMQs/hU+2djIncPZoim6H5QTlBFIdrIc5Eo9uD1isxC9Jc6nq4Q XDLOG9f6gHm+eQJL+fF7t1RH0NPiLYjh8sC+/yS/+KwDDZoPq5HX5tG+Y c=;
X-Files: smime.p7s : 4459
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAFAP3501KtJV2Z/2dsb2JhbABagwuBDrltgREWdIImAQEEgQkCAU4CMCUCBCGHdsUZF48OgySBEwSQM4ExhjOSFYMtgio
X-IronPort-AV: E=Sophos; i="4.95,653,1384300800"; d="p7s'?scan'208"; a="297004477"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-3.cisco.com with ESMTP; 13 Jan 2014 14:37:33 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0DEbXDi018855 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtcweb@ietf.org>; Mon, 13 Jan 2014 14:37:33 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.72]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0123.003; Mon, 13 Jan 2014 08:37:32 -0600
From: "Jeremy Laurenson (jlaurens)" <jlaurens@cisco.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: Straw Poll on Video Codec Alternatives
Thread-Index: AQHPEGz+JuF5FZxy4UqL2lqU7L715g==
Date: Mon, 13 Jan 2014 14:37:32 +0000
Message-ID: <A6807B36-E9AD-4179-A06B-37146B719123@cisco.com>
References: <CAKMa-ggMDVT2EDYCJEYXj4qMHdFAHGfjh2g1b9R-FzWGEitZAQ@mail.gmail.com>
In-Reply-To: <CAKMa-ggMDVT2EDYCJEYXj4qMHdFAHGfjh2g1b9R-FzWGEitZAQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.230.33]
Content-Type: multipart/signed; boundary="Apple-Mail=_626F67E8-C52D-40DC-992B-D628AEA9FC75"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
Subject: [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: Mon, 13 Jan 2014 14:37:54 -0000

My $0.02. I believe for browsers, "the market" will help push some of this along.

All entities MUST support H.264
Are you in favor of this option [Yes/No/Acceptable]: YES
Do you have any objections to this option, if so please summarize them:
All entities MUST support VP8
Are you in favor of this option [Yes/No/Acceptable]: NO
Do you have any objections to this option, if so please summarize them:
Does not solve interoperability to existing video systems, which was the purpose of SDP manipulation in the first place.
All entities MUST support both H.264 and VP8
Are you in favor of this option [Yes/No/Acceptable]: ACCEPTABLE
Do you have any objections to this option, if so please summarize them:
If IPR issues arise for either codec, this would have to be revisited. 'Cost' for non-browsers to impliment is an issue.
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]: YES
Do you have any objections to this option, if so please summarize them:
If IPR issues arise for either codec for browser vendors, this would have to be revisited.
All entities MUST support at least one of H.264 and VP8
Are you in favor of this option [Yes/No/Acceptable]: NO
Do you have any objections to this option, if so please summarize them:
Does not solve for interop, my primary source of issue.
All entities MUST support H.261
Are you in favor of this option [Yes/No/Acceptable]: NO
Do you have any objections to this option, if so please summarize them:
Does not solve for interop, my primary source of issue.
There is no MTI video codec
Are you in favor of this option [Yes/No/Acceptable]:  NO
Do you have any objections to this option, if so please summarize them:
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]: ACCEPTABLE
Do you have any objections to this option, if so please summarize them:
High barrier to entry and substandard 'fallback'
All entities MUST support Theora
Are you in favor of this option [Yes/No/Acceptable]: NO
Do you have any objections to this option, if so please summarize them:
Does not solve for interop, my primary source of issue.
All entities MUST implement at least two of {VP8, H.264, H.261}
Are you in favor of this option [Yes/No/Acceptable]: Acceptable
Do you have any objections to this option, if so please summarize them:
All entities MUST implement at least two of {VP8, H.264, H.263}
Are you in favor of this option [Yes/No/Acceptable]: ACCEPTABLE
Do you have any objections to this option, if so please summarize them:
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
Do you have any objections to this option, if so please summarize them:
Does not solve for interop to existing 264 systems, my primary source of issue.
All entities MUST support H.263:
Are you in favor of this option [Yes/No/Acceptable]: NO
Do you have any objections to this option, if so please summarize them:
All entities MUST implement at least two of {VP8, H.264, Theora}
Are you in favor of this option [Yes/No/Acceptable]: ACEPTABLE
Do you have any objections to this option, if so please summarize them:
All entities MUST support decoding using Theora.
Are you in favor of this option [Yes/No/Acceptable]: NO
Do you have any objections to this option, if so please summarize them:
All entities MUST support Motion JPEG
Are you in favor of this option [Yes/No/Acceptable]: NO
Do you have any objections to this option, if so please summarize them:

v2.23.0 | Report a Bug | By Email