Re: [rtcweb] Video codec selection - way forward

Stephan Wenger <stewe@stewe.org> Wed, 13 November 2013 22:17 UTC

Return-Path: <stewe@stewe.org>
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 8402C21E8181 for <rtcweb@ietfa.amsl.com>; Wed, 13 Nov 2013 14:17:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.796
X-Spam-Level:
X-Spam-Status: No, score=-2.796 tagged_above=-999 required=5 tests=[AWL=0.803, BAYES_00=-2.599, 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 anR57bwVeMeD for <rtcweb@ietfa.amsl.com>; Wed, 13 Nov 2013 14:17:21 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0208.outbound.protection.outlook.com [207.46.163.208]) by ietfa.amsl.com (Postfix) with ESMTP id CF24E21E808A for <rtcweb@ietf.org>; Wed, 13 Nov 2013 14:17:19 -0800 (PST)
Received: from CO1PR07MB363.namprd07.prod.outlook.com (10.141.75.22) by CO1PR07MB363.namprd07.prod.outlook.com (10.141.75.22) with Microsoft SMTP Server (TLS) id 15.0.785.10; Wed, 13 Nov 2013 22:17:09 +0000
Received: from CO1PR07MB363.namprd07.prod.outlook.com ([169.254.3.167]) by CO1PR07MB363.namprd07.prod.outlook.com ([169.254.3.167]) with mapi id 15.00.0785.001; Wed, 13 Nov 2013 22:17:08 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Video codec selection - way forward
Thread-Index: AQHO4K5Rz+wX6FYb/UKirjPpKIT5XZojNKuA
Date: Wed, 13 Nov 2013 22:17:07 +0000
Message-ID: <CEA93953.AA11A%stewe@stewe.org>
In-Reply-To: <5283DFDC.4010906@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [24.5.171.95]
x-forefront-prvs: 0029F17A3F
x-forefront-antispam-report: SFV:NSPM; SFS:(164054003)(51704005)(24454002)(189002)(199002)(81816001)(81342001)(46102001)(36756003)(83072001)(80976001)(51856001)(19580405001)(19580395003)(83322001)(53806001)(54356001)(2656002)(87936001)(85306002)(69226001)(81542001)(31966008)(74706001)(74662001)(74876001)(47446002)(74502001)(74366001)(56776001)(63696002)(54316002)(77096001)(79102001)(56816003)(50986001)(77982001)(4396001)(81686001)(76796001)(59766001)(76482001)(66066001)(76176001)(65816001)(80022001)(76786001)(47736001)(561944002)(87266001)(47976001)(49866001)(42262001); DIR:OUT; SFP:; SCL:1; SRVR:CO1PR07MB363; H:CO1PR07MB363.namprd07.prod.outlook.com; CLIP:24.5.171.95; FPR:; RD:InfoNoRecords; MX:1; A:0; LANG:en;
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B7284A8100354447B55776842628D9FC@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
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: Wed, 13 Nov 2013 22:17:28 -0000

Hi Gonzalo, 
Re your point 5.: ³either or² is often understood as an exclusive or.  I
don¹t think anyone proposed that.  A better way to express 5. would be
³All entities MUST support at least one of H.264 and VP8².
Stephan

On 11.13.2013, 12:23 , "Gonzalo Camarillo"
<Gonzalo.Camarillo@ericsson.com>; wrote:

>Folks,
>
>I hope everybody had a safe trip back home after Vancouver.
>
>As you all know, we need to make progress regarding the selection of the
>MTI video codec. The following are some of the alternatives we have on
>the table:
>
> 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
> 5. All entities MUST support either H.264 or VP8
> 6. All entities MUST support H.261
> 7. There is no MTI video codec
>
>If you want the group to consider additional alternatives to the ones
>above, please let the group know within the following *two weeks*. At
>that point, the chairs will be listing all the received alternatives and
>proposing a process to select one among them.
>
>Please, send your proposals in an email to the list. You do not need to
>write a draft; just send the text you would like to see in the final
>document regarding video codecs.
>
>Thanks,
>
>Gonzalo
>Responsible AD for this WG
>
>_______________________________________________
>rtcweb mailing list
>rtcweb@ietf.org
>https://www.ietf.org/mailman/listinfo/rtcweb