Re: [rtcweb] Video codec selection - way forward

Bernard Aboba <bernard_aboba@hotmail.com> Thu, 14 November 2013 04:02 UTC

Return-Path: <bernard_aboba@hotmail.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 AAB9721E817D for <rtcweb@ietfa.amsl.com>; Wed, 13 Nov 2013 20:02:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.333
X-Spam-Level:
X-Spam-Status: No, score=-102.333 tagged_above=-999 required=5 tests=[AWL=0.265, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 S1JLOSZpxVpY for <rtcweb@ietfa.amsl.com>; Wed, 13 Nov 2013 20:02:18 -0800 (PST)
Received: from blu0-omc4-s3.blu0.hotmail.com (blu0-omc4-s3.blu0.hotmail.com [65.55.111.142]) by ietfa.amsl.com (Postfix) with ESMTP id E8CEA21E8091 for <rtcweb@ietf.org>; Wed, 13 Nov 2013 20:02:17 -0800 (PST)
Received: from BLU406-EAS97 ([65.55.111.135]) by blu0-omc4-s3.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 13 Nov 2013 20:02:11 -0800
X-TMN: [H+jDXuOccB4JhiEWaP0Fe3dxv5C59nIH]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU406-EAS97AAAF10E9930ACD6891CC93F80@phx.gbl>
Content-Type: multipart/related; boundary="_f95510b1-0930-43b3-88af-d43f59cd2afd_"
References: <5283DFDC.4010906@ericsson.com> <CEA93953.AA11A%stewe@stewe.org> <CA+23+fHWsaz3mbTfmw+so_9Mj5BXKAEkQCvNfr5bo+0G9s80mw@mail.gmail.com>
From: Bernard Aboba <bernard_aboba@hotmail.com>
MIME-Version: 1.0 (1.0)
In-Reply-To: <CA+23+fHWsaz3mbTfmw+so_9Mj5BXKAEkQCvNfr5bo+0G9s80mw@mail.gmail.com>
Date: Wed, 13 Nov 2013 20:02:08 -0800
To: Jonathan Rosenberg <jdrosen@jdrosen.net>
X-OriginalArrivalTime: 14 Nov 2013 04:02:11.0432 (UTC) FILETIME=[4B874E80:01CEE0EE]
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 04:02:22 -0000

Assuming we are talking about native support, Option #4 maximizes legal liability. Since this the major underlying issue it will be the hardest option to get past the legal department. If we aren't talking native but plugins then it is more forward thinking to focus on next generation codec support. Either way, Option 4 loses out to either 1, 2, or 7. 

> On Nov 13, 2013, at 18:26, "Jonathan Rosenberg" <jdrosen@jdrosen.net>; wrote:
> 
> Regarding number 4, here is how I think of it:
> 
> If browsers implement both, it means that an application provider wishing to offer a service (take Hangouts or Skype as examples), can pick the one they like, implement just that in their native apps (mobile, desktop, etc.) where the app provider has control over the full stack, and still work with clients of that service which run in the browser, where the app provider does not have control over the full stack as the real-time media stack is provided by the browser and not the web app. 
> 
> The benefit of this approach is that it enables interoperability between clients on different platforms for the same provider.
> 
> The drawback is, for inter-service federation (which requires much more than just codecs to be aligned), you might run into a case where a user using a mobile app from provider 1 (say, Skype) calls a user using a mobile app from provider 2 (say, Hangouts), and then since each chose a different video codec, there is no common codec. Of course that assumes the two providers in question are willing to even federate in the first place. 
> 
> -Jonathan R.
> 
> 
> 
> 
>> On Wed, Nov 13, 2013 at 5:17 PM, Stephan Wenger <stewe@stewe.org>; 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
>> 
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
> 
> 
> 
> -- 
> Jonathan Rosenberg, Ph.D.
> jdrosen@jdrosen.net
> http://www.jdrosen.net
> _______________________________________________
> 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