Re: [rtcweb] Video codec selection - way forward

Jeremy Fuller <jeremy.fuller@genband.com> Thu, 14 November 2013 11:38 UTC

Return-Path: <jeremy.fuller@genband.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5201F21E81B2 for <rtcweb@ietfa.amsl.com>; Thu, 14 Nov 2013 03:38:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vIKfa2KQ-oG1 for <rtcweb@ietfa.amsl.com>; Thu, 14 Nov 2013 03:37:58 -0800 (PST)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe003.messaging.microsoft.com [216.32.180.186]) by ietfa.amsl.com (Postfix) with ESMTP id 57CBE21E8095 for <rtcweb@ietf.org>; Thu, 14 Nov 2013 03:37:58 -0800 (PST)
Received: from mail109-co1-R.bigfish.com (10.243.78.251) by CO1EHSOBE022.bigfish.com (10.243.66.85) with Microsoft SMTP Server id 14.1.225.22; Thu, 14 Nov 2013 11:37:57 +0000
Received: from mail109-co1 (localhost [127.0.0.1]) by mail109-co1-R.bigfish.com (Postfix) with ESMTP id A3A65D60501 for <rtcweb@ietf.org>; Thu, 14 Nov 2013 11:37:57 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:63.149.188.7; KIP:(null); UIP:(null); IPV:NLI; H:owa.genband.com; RD:63-149-188-7.dia.static.qwest.net; EFVD:NLI
X-SpamScore: 0
X-BigFish: VPS0(zzc85fhzz1f42h2148h208ch1ee6h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz18c673hz2fh109h2a8h839hd25hf0ah1288h12a5h12bdh137ah1441h14ddh1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h1b0ah1b2fh1bceh224fh1fb3h1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1e1dh1fe8h1ff5h20f0h2216h1155h)
Received-SPF: pass (mail109-co1: domain of genband.com designates 63.149.188.7 as permitted sender) client-ip=63.149.188.7; envelope-from=jeremy.fuller@genband.com; helo=owa.genband.com ; .genband.com ;
Received: from mail109-co1 (localhost.localdomain [127.0.0.1]) by mail109-co1 (MessageSwitch) id 1384429075816008_17848; Thu, 14 Nov 2013 11:37:55 +0000 (UTC)
Received: from CO1EHSMHS030.bigfish.com (unknown [10.243.78.249]) by mail109-co1.bigfish.com (Postfix) with ESMTP id B9A7A30003F for <rtcweb@ietf.org>; Thu, 14 Nov 2013 11:37:55 +0000 (UTC)
Received: from owa.genband.com (63.149.188.7) by CO1EHSMHS030.bigfish.com (10.243.66.40) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 14 Nov 2013 11:37:55 +0000
Received: from GBPLMAIL03.genband.com ([fe80::cc33:96c3:49a1:aa21]) by GBEX01.genband.com ([::1]) with mapi id 14.03.0158.001; Thu, 14 Nov 2013 05:37:54 -0600
From: Jeremy Fuller <jeremy.fuller@genband.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: Re: Video codec selection - way forward
Thread-Index: Ac7hK8ukTfQjcL8nT66qZ+XigA9SjQ==
Date: Thu, 14 Nov 2013 11:37:54 +0000
Message-ID: <D9C9C6C10CA24644B3A854DB0C12E7D5014C12B5F1@gbplmail03.genband.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.16.21.173]
Content-Type: multipart/alternative; boundary="_000_D9C9C6C10CA24644B3A854DB0C12E7D5014C12B5F1gbplmail03gen_"
MIME-Version: 1.0
X-OriginatorOrg: genband.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: Re: [rtcweb] Video codec selection - way forward
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 14 Nov 2013 11:38:04 -0000

Hi,

Gaining IETF consensus on making it mandatory to support only H.264 or only VP8 has clearly failed. I would welcome anyone to share their thoughts on why they believe this situation will change anytime in the next few years.  Therefore, can I suggest that we remove items 1 and 2 from the list. Hopefully this will speed up the process by focusing efforts towards gaining agreement on one of the remaining options.


The following alternatives has been proposed:
1.      All entities MUST support H.264
2.      All entities MUST support VP8
3.      All entities MUST support both H.264 and VP8
4.      Browsers MUST support both H.264 and VP8, other entities MUST support at least one of H.264 and VP8
5.      All entities MUST support at least one of H.264 and VP8
6.      All entities MUST support H.261
7.      There is no MTI video codec
8.      All entities MUST support H.261 and all entities MUST support at least one of H.264 and VP8
Regards,
Jeremy Fuller