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

Iñaki Baz Castillo <ibc@aliax.net> Thu, 06 November 2014 17:14 UTC

Return-Path: <ibc@aliax.net>
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 E3FAD1A87BB for <rtcweb@ietfa.amsl.com>; Thu, 6 Nov 2014 09:14:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Level:
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7] autolearn=no
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 yWqjKCBuMGaT for <rtcweb@ietfa.amsl.com>; Thu, 6 Nov 2014 09:14:08 -0800 (PST)
Received: from mail-qa0-f50.google.com (mail-qa0-f50.google.com [209.85.216.50]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCC8F1A8896 for <rtcweb@ietf.org>; Thu, 6 Nov 2014 09:14:08 -0800 (PST)
Received: by mail-qa0-f50.google.com with SMTP id bm13so1079061qab.9 for <rtcweb@ietf.org>; Thu, 06 Nov 2014 09:14:07 -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:content-transfer-encoding; bh=qRz8KRTJ3xcKB3PnwY/5s0COMwE/LhRmRudeSeIlcns=; b=hRn3vDgLofstZ2rKYmbPrKe5WciEFOOq+562+y4h1DCGPfMX23232dJqDuE2J/vXZ0 dZCNrHGVdfD4xXrXdiBiblWd3NmMNWtqkKEFELaq3RUy572ZJeUDLjIW6AHWlfXrIrKX r+MjCUk+lYa6RPRLuLeSZynLCwHyXQhP057lrRoAbguCyz1Wa+A8+1igIeBsqxmSPuSF LwHETt0ELCkComqDZMkDSH4ayCdvRRRsc7nBqDMsDHE724ZAvl64mK8rGSlkxZthj0rB Mv6xFH62SraZrLkicON+Rfb5gYB/0Wx9vPTDKp0s4vgJ+Tj40SGftT3e4D+3UUl324Fn fdkg==
X-Gm-Message-State: ALoCoQnRJ3cgdyV8Y/XJmDzbBdXKlhv8U5SJb3RAF3zNu/F9OSTKD/dOq6uBWH/Lpo6WsYGEL4Nj
X-Received: by 10.140.39.113 with SMTP id u104mr8275435qgu.86.1415294047517; Thu, 06 Nov 2014 09:14:07 -0800 (PST)
MIME-Version: 1.0
Received: by 10.96.69.200 with HTTP; Thu, 6 Nov 2014 09:13:47 -0800 (PST)
In-Reply-To: <CABcZeBOWyy3hagGpjMzmbPJjCaBdUjUUs5zat-t7h75Xa+Fzkg@mail.gmail.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>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Thu, 06 Nov 2014 18:13:47 +0100
Message-ID: <CALiegfkzfNx-QON5mH5mN411g-P877n9BzdyNtTwJEER=k7+Kw@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/R26ip0LrbCfY3vVfmC27EdBx09Y
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 17:14:10 -0000

2014-11-06 6:14 GMT+01:00 Eric Rescorla <ekr@rtfm.com>:
>> 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?


If somebody expects that teams like Debian will accept such a hack he
is really wrong. I know the Industry does not care about that, but
software packagers (specially Open Source software packagers) will not
trust this hack from Cisco regardless it has been "adopted" by
Mozilla. When I talk to veteran Firefox users (not involved in WebRTC
at all) about the "binary topic" they just cry.

Said that, I'm pretty sure nobody will comment on the previous proposal:

"If the 'Industry' wants to make MTI a codec they control, then they
have to make it completely free and open to everyone."

Is so hard to understand that if the W3C mandates a MTI codec then
such a codec MUST be free and open to everyone (without royalties)?
This is the W3C, not the 3GPP/GSMA. There is no room for binary stuff
or royalties here.




-- 
Iñaki Baz Castillo
<ibc@aliax.net>