Re: [rtcweb] Video codec selection - way forward

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Thu, 14 November 2013 07:38 UTC

Return-Path: <gonzalo.camarillo@ericsson.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 25FDA11E811D for <rtcweb@ietfa.amsl.com>; Wed, 13 Nov 2013 23:38:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.614
X-Spam-Level:
X-Spam-Status: No, score=-105.614 tagged_above=-999 required=5 tests=[AWL=0.635, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 BaeGfY4Jf5uk for <rtcweb@ietfa.amsl.com>; Wed, 13 Nov 2013 23:38:24 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 97A3E11E8116 for <rtcweb@ietf.org>; Wed, 13 Nov 2013 23:38:23 -0800 (PST)
X-AuditID: c1b4fb30-b7f228e000003e6c-62-52847dec8f8e
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id B9.DC.15980.CED74825; Thu, 14 Nov 2013 08:38:21 +0100 (CET)
Received: from [131.160.126.80] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.68) with Microsoft SMTP Server id 14.2.328.9; Thu, 14 Nov 2013 08:38:20 +0100
Message-ID: <52847DEC.2020406@ericsson.com>
Date: Thu, 14 Nov 2013 09:38:20 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Stephan Wenger <stewe@stewe.org>
References: <CEA93953.AA11A%stewe@stewe.org>
In-Reply-To: <CEA93953.AA11A%stewe@stewe.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprALMWRmVeSWpSXmKPExsUyM+Jvre7b2pYgg9UvFSzW/mtnt7jeuInd gcljyZKfTB6L179nDGCK4rJJSc3JLEst0rdL4Mr4ea+ZpeAIb8W2A63sDYw3uLoYOTkkBEwk Pjz5xw5hi0lcuLeerYuRi0NI4BCjxPbLc5khnDWMEvtWPQCr4hXQlujon8UKYrMIqEq0vj3M AmKzCVhIbLl1H8wWFYiS2LD9AgtEvaDEyZlPwGwRARWJQzd/gNnMAuoSdxafA5rJwSEsYClx 4bgJSFhIQEfi4KfHYKs4BXQl7l+dzARxnKTElhft7BCtehJTrrYwQtjyEs1bZzND9GpLLH/W wjKBUWgWks2zkLTMQtKygJF5FSN7bmJmTnq5+SZGYKge3PLbYAfjpvtihxilOViUxHk/vHUO EhJITyxJzU5NLUgtii8qzUktPsTIxMEp1cB45IiV8MSXciderV8ncOzC7YpbU2TnHVXU8FS6 wczpk9vuVHHNTWlxSYSq0aYH212X5EtPlJggMstxA9cjua+zr0fN2x7xsOi1Vbj8vR7Be+3p UlXM/KtztkU8N4tVWmgtO6+s5McKXU+e17K/+pc+VinS2eKW+5FN5Z8X5+NtHIfv60XzCgQq sRRnJBpqMRcVJwIA2334OCMCAAA=
Cc: "rtcweb@ietf.org" <rtcweb@ietf.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: Thu, 14 Nov 2013 07:38:29 -0000

Hi Stephan,

yes, the wording you suggest captures the idea in a clearer way.

Thanks,

Gonzalo

On 14/11/2013 12:17 AM, Stephan Wenger wrote:
> 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
>