Re: [rtcweb] Congratuiations on the Cisco announcement - but we still prefer VP8

Randell Jesup <randell-ietf@jesup.org> Mon, 04 November 2013 04:20 UTC

Return-Path: <randell-ietf@jesup.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 42E7021E80F8 for <rtcweb@ietfa.amsl.com>; Sun, 3 Nov 2013 20:20:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 XVPPDu26OhJJ for <rtcweb@ietfa.amsl.com>; Sun, 3 Nov 2013 20:20:09 -0800 (PST)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id 512B621E80F3 for <rtcweb@ietf.org>; Sun, 3 Nov 2013 20:20:09 -0800 (PST)
Received: from [64.114.24.114] (port=50308 helo=[142.131.18.239]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <randell-ietf@jesup.org>) id 1VdBe3-000AUj-8n for rtcweb@ietf.org; Sun, 03 Nov 2013 22:20:07 -0600
Message-ID: <52772073.6090000@jesup.org>
Date: Sun, 03 Nov 2013 20:20:03 -0800
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:25.0) Gecko/20100101 Thunderbird/25.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CAOqqYVEER_HprgauRawO+_gGdLdMY1MUY8jrMhhi3yVDL31bFg@mail.gmail.com> <CAPvvaaLpbWGZPBB1EMOPKQd_+t95bvG51NG4DnKhtEp1WSwRhg@mail.gmail.com> <BLU406-EAS3033A38C2A9CA480AFFD3B93F40@phx.gbl>
In-Reply-To: <BLU406-EAS3033A38C2A9CA480AFFD3B93F40@phx.gbl>
Content-Type: multipart/alternative; boundary="------------070106090907040607050703"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - r2-chicago.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jesup.org
X-Get-Message-Sender-Via: r2-chicago.webserversystems.com: authenticated_id: randell@jesup.org
Subject: Re: [rtcweb] Congratuiations on the Cisco announcement - but we still prefer VP8
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, 04 Nov 2013 04:20:15 -0000

On 11/2/2013 7:00 AM, Bernard Aboba wrote:
> Those enterprise scenarios often either involve a defined software 
> image that could include the Cisco plugin (does it always have to be 
> downloaded?) OR involve a relatively recent OS, with native H.264 
> support. So I am not sure this need come up that often.

IANAPL (I Am Not A Patent Lawyer) - but if you make an image that 
includes Cisco's plugin for imaging machines, that would be a violation 
of the rules - you would be the one distributing it to end-use systems.  
While you're unlikely to get pinged on it, the company lawyers may not 
see it that way, and it might show up flagged in an audit, and IT guys 
don't like that.

There are also some systems that don't generally allow plugins of any 
sort (such as Metro IIRC); though those might have native H.264 
encode/decode support.  Note that platform encode/decode support for 
WebRTC is more problematic than software support, since the H.264 
encoders (hell, even decoders) may be of questionable stability. (You'll 
note the blacklists/whitelists Mozilla uses for platform decoder support 
on Android, for example, because some of them have problems.)  How 
serious that problem is (and how serious it is for encoders) is not 
clear.   There's also the issue of what knobs are available to tune the 
encoder, especially for resiliency options.

>
> On Nov 2, 2013, at 3:35 AM, "Emil Ivov" <emcho@jitsi.org 
> <mailto:emcho@jitsi.org>> wrote:
>>
>> Also, while Cisco's grant is quite interesting for certain scenarios 
>> it could be very problematic for others. For example: enterprises 
>> where installations are handled in a controlled and automated way 
>> (e.g. scripted image deployment) and where subsequent Internet access 
>> could be limited for various reasons.
>>
>> Emil
>>
>> --
>>


-- 
Randell Jesup
randell-ietf@jesup.org