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

Eric Rescorla <ekr@rtfm.com> Thu, 06 November 2014 21:09 UTC

Return-Path: <ekr@rtfm.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 CED7F1A6FE9 for <rtcweb@ietfa.amsl.com>; Thu, 6 Nov 2014 13:09:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 Wev6ob6u6ODB for <rtcweb@ietfa.amsl.com>; Thu, 6 Nov 2014 13:09:04 -0800 (PST)
Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FD481A6F62 for <rtcweb@ietf.org>; Thu, 6 Nov 2014 13:09:04 -0800 (PST)
Received: by mail-wi0-f177.google.com with SMTP id ex7so2760298wid.4 for <rtcweb@ietf.org>; Thu, 06 Nov 2014 13:09:03 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Qr5rWMnIZTZdJv+MClmsDWwzL+9ADNNRqjNLNR5rUjY=; b=LCG0EociM6sQy5xT8SZrItQelNCDLmYDmF7szUMcAa95gf+T2+EX7J5pGrCNYhUuhw uXXG8H+lI5mgU+6mL8344cUyBuZIP3ScvVaZFWe/xYesiWrUusjh7uzTHHmZcKfFtc40 Z3VzgUTDZXhwIbVBwXg1gasdwvl7CNV8wHlNYkVL8wTBPtFKEM1cDpARhPQuMwTwVcb5 dOJ4NFjS0G3FxRPC+r4AqvwqMq0PP1rRkOb69ax7lV6okAdJ48SZxA2ZgxW7r51SJBmg Mb8fxjRdyZgl56MMSjQw0ZM9uhb2Cms6RZ/di19/0pQrQH9QW86xsoQFT64AZq8UHgDr KbCA==
X-Gm-Message-State: ALoCoQlvU8sRdwXCW8lGpjH2NZuRO0anmRwxlha+oDxcb/y7LuHgyWv5deBZVxOzw43qdPazV9Gm
X-Received: by 10.194.79.201 with SMTP id l9mr9482245wjx.59.1415308142976; Thu, 06 Nov 2014 13:09:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.49.198 with HTTP; Thu, 6 Nov 2014 13:08:21 -0800 (PST)
In-Reply-To: <20141106182937.GH8092@hex.shelbyville.oz>
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>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 06 Nov 2014 13:08:21 -0800
Message-ID: <CABcZeBMAba+AdsnekV36nWLpz91pUYsh5uvRVtHzPvnFSHvsUg@mail.gmail.com>
To: Ron <ron@debian.org>
Content-Type: multipart/alternative; boundary="047d7bf0d0f61c2d0d0507371bc3"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/fzv3LT57xmCb1hFTp1De1VHLsck
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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 21:09:06 -0000

On Thu, Nov 6, 2014 at 10:29 AM, 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


I think Mo has answered this.

, or is this a special privilege they offered to you to win your
> support for their scheme?


It certainly wasn't this. When we agreed to do this, the intent was to do
reproducible builds, but then as we got closer to ship engineering
realities intervened and it became clear that it was easier for Mozilla
to do the builds in the interim, but that decision was only made
recently and we would prefer to have reproducible builds, as Mo
says..

-Ekr