Re: [rtcweb] Video codec selection - way forward

David Singer <singer@apple.com> Tue, 19 November 2013 00:07 UTC

Return-Path: <singer@apple.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 62C2F1AE5F4 for <rtcweb@ietfa.amsl.com>; Mon, 18 Nov 2013 16:07:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.427
X-Spam-Level:
X-Spam-Status: No, score=-7.427 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.525, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 gwMi8iA_RfAC for <rtcweb@ietfa.amsl.com>; Mon, 18 Nov 2013 16:07:10 -0800 (PST)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id BA8CF1AE5F0 for <rtcweb@ietf.org>; Mon, 18 Nov 2013 16:07:10 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay6.apple.com ([17.128.113.90]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MWH000VRHNJ8U41@mail-out.apple.com> for rtcweb@ietf.org; Mon, 18 Nov 2013 16:07:05 -0800 (PST)
X-AuditID: 1180715a-b7f3c6d00000020e-18-528aaba882d1
Received: from aniseed.apple.com (aniseed.apple.com [17.128.115.23]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by relay6.apple.com (Apple SCV relay) with SMTP id 14.2D.00526.8ABAA825; Mon, 18 Nov 2013 16:07:04 -0800 (PST)
Received: from [17.153.17.55] (unknown [17.153.17.55]) by aniseed.apple.com (Oracle Communications Messaging Server 7u4-24.01 (7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTPSA id <0MWH00LO2HNSR410@aniseed.apple.com> for rtcweb@ietf.org; Mon, 18 Nov 2013 16:07:04 -0800 (PST)
From: David Singer <singer@apple.com>
In-reply-to: <52891EDB.2050607@googlemail.com>
Date: Mon, 18 Nov 2013 16:07:04 -0800
Message-id: <D0698C9F-967F-4797-A9F3-E461B9DAE8EB@apple.com>
References: <D9C9C6C10CA24644B3A854DB0C12E7D5014C12B5F1@gbplmail03.genband.com> <52891EDB.2050607@googlemail.com>
To: Maik Merten <maikmerten@googlemail.com>
X-Mailer: Apple Mail (2.1510)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMLMWRmVeSWpSXmKPExsUi2FAsrrtidVeQQet/c4u1/9rZHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVMfdleMES0YrbM7+zNTBOEexi5OSQEDCR+D79PyOELSZx4d56 ti5GLg4hgX4miZ+r9oElhATmMklMPSoDYjMLaEms33mcCcTmFdCT2Ll3G2sXIweHsIClxIXj JiBhNgFViQdzjoG1cgKVtP9+CVbOAhSfteA4C8QYYYnvj+9B2doST95dYIUYaSOxd8dUqLXF Eqf/PQCLiwDVtJ46xg5xp6zE6XPPWSYwCsxCctEsJBfNQjJ2ASPzKkaBotScxEozvcSCgpxU veT83E2M4KArjNrB2LDc6hCjAAejEg/vBPeuICHWxLLiytxDjBIczEoivFKzgEK8KYmVValF +fFFpTmpxYcYpTlYlMR5n/gApQTSE0tSs1NTC1KLYLJMHJxSDYyiXe/j1k7M0SqJ6it8wP4q jOnXZe0kHqfvnSZOS/tdJjCHKAl/KPu57MoBnpkhVd27XZVeRIrcuzQz+BLboZIEmePHFzz5 zfh0dax398d+m71Kcjc32zZfmaQVKX4/+PCRLVvuZktGsp2dXJA5se1hMoOxhcSHID5Ju+7j sS8eVexdufLdNz8lluKMREMt5qLiRADnEtchNgIAAA==
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Video codec selection - way forward
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: Tue, 19 Nov 2013 00:07:12 -0000

It's an interesting idea, but the quality of H.261, the availability of decent implementations, and its (functional) restrictions may mean that people are very loath to spend (waste) engineering time on it.  Is this a MUST that would, in fact, get respected?


On Nov 17, 2013, at 11:54 , Maik Merten <maikmerten@googlemail.com>; 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

David Singer
Multimedia and Software Standards, Apple Inc.