IETF Logo Mail Archive

Re: [rtcweb] RTCWEB needs an Internet Codec

"Richard Shockey" <richard@shockey.us> Mon, 03 September 2012 17:52 UTC

Return-Path: <richard@shockey.us>
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 3900721F8597 for <rtcweb@ietfa.amsl.com>; Mon, 3 Sep 2012 10:52:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.699
X-Spam-Level:
X-Spam-Status: No, score=-99.699 tagged_above=-999 required=5 tests=[AWL=-1.063, BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 QYxYTPGvW52p for <rtcweb@ietfa.amsl.com>; Mon, 3 Sep 2012 10:52:37 -0700 (PDT)
Received: from oproxy12-pub.bluehost.com (unknown [IPv6:2605:dc00:100:2::a4]) by ietfa.amsl.com (Postfix) with SMTP id 8DBA421F8592 for <rtcweb@ietf.org>; Mon, 3 Sep 2012 10:52:37 -0700 (PDT)
Received: (qmail 9031 invoked by uid 0); 3 Sep 2012 17:52:35 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy12.bluehost.com with SMTP; 3 Sep 2012 17:52:35 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From; bh=WOUjl+kk41/QQMPV1P8It1JyYRTcyjq6dMYyWWEdeg4=; b=RZ6XyQ8jY8JDSb5m0jDJJMphC4R3qScq6JBdbw/mhqidyqshonpGXnzUJ4ce7AQbxio5CZNa5jQ1E5rNMTcHUDG5KHm6mTu/GLoGPs15gnWgSvF5FU+JRG33op2zc69K;
Received: from [71.191.243.130] (port=50912 helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.76) (envelope-from <richard@shockey.us>) id 1T8ap8-0007qJ-Su; Mon, 03 Sep 2012 11:52:35 -0600
From: Richard Shockey <richard@shockey.us>
To: 'Randall Gellens' <randy@qualcomm.com>, 'John Leslie' <john@jlc.net>, 'Randell Jesup' <randell-ietf@jesup.org>
References: <p06240603cc63f3f41ca9@[99.111.97.136]> <503F46C5.2090607@alvestrand.no> <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> <p06240608cc66e4862829@[99.111.97.136]>
In-Reply-To: <p06240608cc66e4862829@[99.111.97.136]>
Date: Mon, 03 Sep 2012 13:52:34 -0400
Message-ID: <00a701cd89fc$e681e9d0$b385bd70$@us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
thread-index: Ac2HxqG2c5DJCB41TMOsT9VUjD9raQCNYdFQ
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 71.191.243.130 authed with richard@shockey.us}
Cc: rtcweb@ietf.org
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: Mon, 03 Sep 2012 17:52:38 -0000

So why, pray tell, did the IETF go through the grief of developing OPUS if
its most useful application will not mandate its implementation. 

SHOULD for 722 AMR-WB is very helpful in integration with Enterprise and
Mobile networks.

Its August .. clearly the silly season for technical discussions. 

-----Original Message-----
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of
Randall Gellens
Sent: Friday, August 31, 2012 6:09 PM
To: John Leslie; Randell Jesup
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] RTCWEB needs an Internet Codec

At 11:12 AM -0400 8/31/12, John Leslie wrote:

>  Our issue here is Mandatory-to-Implement. It is very important to  
> have at least one MTI audio codec. I could live with that being G.711,  
> because I trust the market to _actually_ implement others.

Exactly.  The discussion has been going in my view off-track into debates
about which codec is best for which environments.  The real issue is
mandatory versus recommended.

We can pick G.711 as MTI and rely on implementers to support others.

--
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: --------------- One never sits in
hotel lobby chairs, my dear.  One never knows whom has been sitting in them
before one.
    --unknown
_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email