Re: [rtcweb] The MTI Codec Questions (what to ask and how to ask them)

cowwoc <cowwoc@bbs.darktech.org> Thu, 06 November 2014 20:08 UTC

Return-Path: <cowwoc@bbs.darktech.org>
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 D96BB1A1F04 for <rtcweb@ietfa.amsl.com>; Thu, 6 Nov 2014 12:08:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 LtL5nR74HRlg for <rtcweb@ietfa.amsl.com>; Thu, 6 Nov 2014 12:08:18 -0800 (PST)
Received: from mail-ie0-f169.google.com (mail-ie0-f169.google.com [209.85.223.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 951A01A1A17 for <rtcweb@ietf.org>; Thu, 6 Nov 2014 12:08:17 -0800 (PST)
Received: by mail-ie0-f169.google.com with SMTP id tr6so3789897ieb.0 for <rtcweb@ietf.org>; Thu, 06 Nov 2014 12:08:17 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=9meUzzd+JKTFLi42cb3LzcLo9Hr01V6U6ZpWszlapWM=; b=LBcGISMy1wjlXlApWvodojhkfRice7XRWJKTsm/o8MSMMYtQrgplYctN9LCRNpkaAO CwZ6RjWSDsxGXUr+4hLPztnQXEAYrdxc3j88DWvdlTQ7Z1lPr7b3FqnS4UpaYQRGsfSZ 9yyCANnS93S5mZQYIKwFHM+5kAkRWGhHeymjzQmFiD+w7AClC8QwOLItDY/YRnny7dpA e0xx0w4SF3bawW75+NjU5E0eB1eIs1qqXuliN1dpYOFmRFWJXYKv6HFDqT2HbKcNpMIa Lwir2j015T7LxJqGpWWgFQvnKGJ5DkoybcUHO1YQVtsKllkOLw76Ak1oBuiqjUA963I2 K9YA==
X-Gm-Message-State: ALoCoQkPxguBRPjvvy8zT1kscaxF8I0OxtXNVhIbTr7da+QlFcXtWfsOp67tBbZQoKWnYdSfwadO
X-Received: by 10.107.13.6 with SMTP id 6mr7591128ion.68.1415304496951; Thu, 06 Nov 2014 12:08:16 -0800 (PST)
Received: from [192.168.1.100] (206-248-171-209.dsl.teksavvy.com. [206.248.171.209]) by mx.google.com with ESMTPSA id b32sm3327810ioj.26.2014.11.06.12.08.16 for <rtcweb@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Nov 2014 12:08:16 -0800 (PST)
Message-ID: <545BD51B.9060907@bbs.darktech.org>
Date: Thu, 06 Nov 2014 15:07:55 -0500
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <98200BCB-ABC9-4BE0-B11D-B7AEC9F8B2A4@ieca.com> <7594FB04B1934943A5C02806D1A2204B1D4E50D8@ESESSMB209.ericsson.se> <E78E8017-A08F-4061-B2BA-FB3900B1C681@phonefromhere.com> <CAGTXFp-9AtQakpLt+O_eNRNr71uyh26igLb-_56LDUTQ+g5iJg@mail.gmail.com> <545A6281.4050601@gmail.com> <EC89515C-4FD9-4C08-A80A-42B36004A516@phonefromhere.com> <545A7E0B.4070505@gmail.com> <C17546AB-1419-49C2-A634-49296C122347@phonefromhere.com> <CABcZeBOWyy3hagGpjMzmbPJjCaBdUjUUs5zat-t7h75Xa+Fzkg@mail.gmail.com> <20141106182937.GH8092@hex.shelbyville.oz> <D0812C0A.3DDD9%mzanaty@cisco.com>
In-Reply-To: <D0812C0A.3DDD9%mzanaty@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/-ivIQwpaSp1vVpcNeRI0vyOqTss
Subject: Re: [rtcweb] The MTI Codec Questions (what to ask and how to ask them)
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: Thu, 06 Nov 2014 20:08:20 -0000

First a question and then a rant :)

Question: What are you proposing to replace with a GStreamer plugin?
Rant: 2 years ago I tried to get Gstreamer working on iOS. Let's just 
say it felt like taking a drill to the head. The codebase depended on 
many Linux-specific dependencies (which did not exist on BSD) and some 
of them were very poorly maintained (committers who were unreachable or 
dead .. no joke .. for years). Once I got past that point, it used to 
break randomly in mysterious ways (i.e. the API's error handling sucks, 
once you report a bug it sits unfixed for months)

I know that GStreamer is very popular and that GStreamer SDK has since 
been published for iOS and OSX, but I still don't trust that codebase. I 
wouldn't want to have to maintain a project on top of it.

Gili

On 06/11/2014 2:11 PM, Mo Zanaty (mzanaty) wrote:
> We are also working with Red Hat on a potential Gstreamer plugin.
> We would be happy to work with Debian or anyone else on other wrappers
> for projects that want to download some wrapper format beyond the raw
> library.
>
> It would be ideal to have a single binary (per platform) that works for
> all applications, without many different wrappers. That was the goal of
> the raw library, but apparently this is not sufficient for most projects.
> Until we reach an acceptable common wrapper (with verifiable builds),
> we¹re happy to have folks contribute their desired wrapper for hosting.
> Mozilla contributed the Firefox Gecko Media Plugin (GMP) wrapper. They
> were first to contribute, so they were hosted first, not due to any
> special privilege.
>
> Mo
>
> On 11/6/14, 1:29 PM, Ron <ron@debian.org> wrote:
> On Wed, Nov 05, 2014 at 09:14:27PM -0800, Eric Rescorla wrote:
>> On Wed, Nov 5, 2014 at 2:39 PM, tim panton <tim@phonefromhere.com> wrote:
>>> Agreed, the worst aspect of any adoption of H264 is that it makes it
>>> significantly more difficult to
>>> produce a custom ¹secure¹ build of firefox that has been independently
>>> reviewed for special use-cases
>>> (press, humanitarian workers etc).
>> Why is this true? We currently build OpenH264 and then send the binary to
>> Cisco but keep a hash for comparison. Why is it more difficult to review
>> this?
> Is Cisco offering to ship such binaries for anyone who wants to build
> them, or is this a special privilege they offered to you to win your
> support for their scheme?
>    Ron
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb