Re: [rtcweb] RTCWEB needs an Internet Codec

Ron <ron@debian.org> Sat, 01 September 2012 03:32 UTC

Return-Path: <ron@debian.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 0548621F84B9 for <rtcweb@ietfa.amsl.com>; Fri, 31 Aug 2012 20:32:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.423
X-Spam-Level:
X-Spam-Status: No, score=-1.423 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HOST_MISMATCH_NET=0.311, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gv7fhH2gqlDP for <rtcweb@ietfa.amsl.com>; Fri, 31 Aug 2012 20:32:05 -0700 (PDT)
Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:6:5]) by ietfa.amsl.com (Postfix) with ESMTP id 3049821F84B8 for <rtcweb@ietf.org>; Fri, 31 Aug 2012 20:32:04 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAKWAQVB5LWvi/2dsb2JhbABEuyCBCIIgAQEFOg0PMwsYLhQYDYhDq3COdYsJg2WCPGADiE2FKIdiAZAagnM
Received: from ppp121-45-107-226.lns20.adl6.internode.on.net (HELO audi.shelbyville.oz) ([121.45.107.226]) by ipmail05.adl6.internode.on.net with ESMTP; 01 Sep 2012 13:02:02 +0930
Received: from localhost (localhost [127.0.0.1]) by audi.shelbyville.oz (Postfix) with ESMTP id 8AF154F8F3 for <rtcweb@ietf.org>; Sat, 1 Sep 2012 12:49:56 +0930 (CST)
X-Virus-Scanned: Debian amavisd-new at audi.shelbyville.oz
Received: from audi.shelbyville.oz ([127.0.0.1]) by localhost (audi.shelbyville.oz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id J3ScTxp2jvae for <rtcweb@ietf.org>; Sat, 1 Sep 2012 12:49:55 +0930 (CST)
Received: by audi.shelbyville.oz (Postfix, from userid 1000) id BDB814F902; Sat, 1 Sep 2012 12:49:55 +0930 (CST)
Date: Sat, 01 Sep 2012 12:49:55 +0930
From: Ron <ron@debian.org>
To: rtcweb@ietf.org
Message-ID: <20120901031955.GF23434@audi.shelbyville.oz>
References: <EDC0A1AE77C57744B664A310A0B23AE240CBCCD8@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <503F61CC.1010709@alvestrand.no> <CAC8DBE4E9704C41BCB290C2F3CC921A162D278D@nasanexd01h.na.qualcomm.com> <503FC1BF.5020004@alvestrand.no> <CAC8DBE4E9704C41BCB290C2F3CC921A162D2B0F@nasanexd01h.na.qualcomm.com> <5040541C.5020008@alvestrand.no> <20120831133845.GW72831@verdi> <5040CE32.5050003@jesup.org> <20120831151247.GY72831@verdi> <CAD6AjGToznJtNdSzyFbxKhhXQTLTuOWnPutOYDCQCVH_8mRZ5w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAD6AjGToznJtNdSzyFbxKhhXQTLTuOWnPutOYDCQCVH_8mRZ5w@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [rtcweb] RTCWEB needs an Internet Codec
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: Sat, 01 Sep 2012 03:32:06 -0000

On Fri, Aug 31, 2012 at 08:40:43AM -0700, Cameron Byrne wrote:
> Agree with the above. G.711 for mti only.
> 
> I want to push Opus and promote its use, but MTI is not the right method
> for that.

I haven't got the impression from this discussion that anybody thinks it
is about "pushing Opus" at all.  The question is what is best for rtcweb.

Since the charter of this group is to produce a standard that facilitates
"direct interactive rich communication", using things that already exist
as much as possible - I thought it was clear that the only important point
is that all this engineering work to produce rtcweb should not be a complete
waste of time for the people actually implementing it, and produce something
that gives such a poor experience in its baseline configuration that nobody
would ever actually want to use it for any of its intended purposes.

That Opus is a very obvious choice of existing technology, which no other
single codec comes anywhere close to matching for this purpose, stands out
like an elephant in the room.  Blind men might argue about whether it is a
pillar or a brush, or whether enough double blinded men have yet touched it
to be sure of this, but no amount of "pushing" is going to realistically
move it from that position one way or the other.

Pretending that other much-poorer codecs could fill this role is abandoning
the "rich communication" part of the charter, and condemning this group to
an embarrassing failure to achieve its goals in any meaningful way.

Let's not do that shall we.  It seems quite clear that many people have an
intense interest in its success.  Delaying this indefinitely, or selecting
poorer options than are already available today do not seem like the choices
that rational people who actually do want this to succeed would make.

Interoperability requires an adequate MTI codec.  Nobody has proposed an
alternative codec that is not clearly inadequate by comparison to Opus.
In a room full of clever engineers who want rtcweb to excel as a best of
breed specification, this decision should be a total no-brainer.

This time would be much better spent on the Actually Hard questions that
still remain for rtcweb.

 Best,
 Ron