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

"Mo Zanaty (mzanaty)" <mzanaty@cisco.com> Thu, 06 November 2014 19:11 UTC

Return-Path: <mzanaty@cisco.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 2D31A1A88AC for <rtcweb@ietfa.amsl.com>; Thu, 6 Nov 2014 11:11:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.095
X-Spam-Level:
X-Spam-Status: No, score=-15.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 HMgr0Zxl4-bn for <rtcweb@ietfa.amsl.com>; Thu, 6 Nov 2014 11:11:24 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DEE81A1AD5 for <rtcweb@ietf.org>; Thu, 6 Nov 2014 11:11:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1567; q=dns/txt; s=iport; t=1415301085; x=1416510685; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=LDYxeck9h2pkq2pBkSRw0K1rxUTT4+iExkEtvXAD4jA=; b=DeVq2chOKvj7gfmKjac6Za8qdy5GXGTIigbskK1CGZ4b/uDfIPGWx4oH bCBlWNMMxME2Eoop2NAS2SDVAq9sGMY+ezhePC7hHawGybeHuHegbjKG0 OJ6LDK57cw1nf0x5hTE6jaJbdeModYXAD0HtI//BPUT99puxOVphi6Xcq w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: At8NAOHGW1StJA2K/2dsb2JhbABbgw6BLQTSagECAQECgSEWAQEBAQF9hAMBAQSBCQIBCBguMiUCBAESHogjz1cBAQEBAQEEAQEBAQEdkF46hEsBBIs/hmSLcYEykR2ECoIAHoFabIFIgQMBAQE
X-IronPort-AV: E=Sophos;i="5.07,327,1413244800"; d="scan'208";a="370335300"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-2.cisco.com with ESMTP; 06 Nov 2014 19:11:23 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id sA6JBMBB031216 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 6 Nov 2014 19:11:22 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.140]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0195.001; Thu, 6 Nov 2014 13:11:22 -0600
From: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
To: Ron <ron@debian.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] The MTI Codec Questions (what to ask and how to ask them)
Thread-Index: AQHP+fVz3AJnTv5AGkmz2oVK4GxrFQ==
Date: Thu, 06 Nov 2014 19:11:21 +0000
Message-ID: <D0812C0A.3DDD9%mzanaty@cisco.com>
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>
In-Reply-To: <20141106182937.GH8092@hex.shelbyville.oz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.5.141003
x-originating-ip: [64.100.32.216]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <81F6A05B01D35D44A63306E1E9F3F353@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/7v49hs_YWN8PCM8SjI7-thL_zNU
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 19:11:31 -0000

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