Re: [rtcweb] Video codec selection - way forward

Magnus Westerlund <magnus.westerlund@ericsson.com> Mon, 18 November 2013 12:43 UTC

Return-Path: <magnus.westerlund@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 EE17511E84B4 for <rtcweb@ietfa.amsl.com>; Mon, 18 Nov 2013 04:43:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.713
X-Spam-Level:
X-Spam-Status: No, score=-105.713 tagged_above=-999 required=5 tests=[AWL=0.536, 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 qyFlh4C35ZQM for <rtcweb@ietfa.amsl.com>; Mon, 18 Nov 2013 04:42:55 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0B8E911E849B for <rtcweb@ietf.org>; Mon, 18 Nov 2013 04:42:44 -0800 (PST)
X-AuditID: c1b4fb25-b7eff8e000000eda-c0-528a0b437c9b
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 0A.48.03802.34B0A825; Mon, 18 Nov 2013 13:42:43 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.62) with Microsoft SMTP Server id 14.2.328.9; Mon, 18 Nov 2013 13:42:42 +0100
Message-ID: <528A0B41.2050107@ericsson.com>
Date: Mon, 18 Nov 2013 13:42:41 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Maik Merten <maikmerten@googlemail.com>, <rtcweb@ietf.org>
References: <D9C9C6C10CA24644B3A854DB0C12E7D5014C12B5F1@gbplmail03.genband.com> <52891EDB.2050607@googlemail.com>
In-Reply-To: <52891EDB.2050607@googlemail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpgluLIzCtJLcpLzFFi42KZGfG3VteZuyvI4MFrCYvHzV9YLNb+a2d3 YPJ4OmEyu8eSJT+ZApiiuGxSUnMyy1KL9O0SuDKmrpzBVrBNrKLnSG0D4x/BLkZODgkBE4m7 W1YzQ9hiEhfurWfrYuTiEBI4xCgx6cA5VghnOaPE559bgao4OHgFtCW6r5aCNLAIqEoc7rnP AmKzCVhI3PzRyAZiiwoES5x/tZgdxOYVEJQ4OfMJWI2IgJ3Eqg8v2UDGCAtYSlw4bgISFhIo lLjc/BdsOqeAnsTKRWUgpoSAuERPYxBIBTNQdMrVFkYIW16ieetsZohObYmGpg7WCYyCs5Ds moWkZRaSlgWMzKsY2XMTM3PSy402MQJD8eCW36o7GO+cEznEKM3BoiTO++Gtc5CQQHpiSWp2 ampBalF8UWlOavEhRiYOTqkGxnXvzB1Y9YxviZ2b2nLAX00/K73inS0rX+r/xM+l4kpnzpYl v39c8dTuKWs0a4PcodMzT+SudBZRVlhomly/wLLIsvWQqgev+ITYhcmSisvCYy6+2LVl6Snb 9cnt2YY5zikh22ZlxE65toLp1+e7F/8r799yS+rBnTVSOoHe/K8q193sstzuqMRSnJFoqMVc VJwIACSv2RcTAgAA
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: Mon, 18 Nov 2013 12:43:01 -0000

Hi,

I have added this to the list of alternatives proposed.

/Magnus

On 2013-11-17 20:54, Maik Merten wrote:
> Hello,
> 
> just wondering if something like
> 
> "9. All entities SHOULD support both H.264 and VP8. All entities MUST at
> least implement one of those. Entities that do not support both H.264
> and VP8 MUST implement H.261."
> 
> has already popped up. My reasoning is that implementations supporting
> both high performance codecs will always negotiate to use on of those -
> H.261 should never be relevant there.
> 
> It appears that all implementors are willing to implement either H.264
> or VP8 (but not necessarily both). This obviously means that negotiation
> failure regarding a high-performance codec is a possiblity. In this case
> H.261 is actually useful so that basic video calls can still be
> established (for instance, I guess deaf people may always appreciate a
> video connection, as long as sign language can be transmitted).
> 
> 
> Maik
> 
> 
> Am 14.11.2013 12:37, schrieb Jeremy Fuller:
>> 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
>>
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------