Re: [rtcweb] RTCWEB needs an Internet Codec
Cameron Byrne <cb.list6@gmail.com> Fri, 31 August 2012 15:40 UTC
Return-Path: <cb.list6@gmail.com>
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 CF03221F8652 for <rtcweb@ietfa.amsl.com>; Fri, 31 Aug 2012 08:40:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.115
X-Spam-Level:
X-Spam-Status: No, score=-3.115 tagged_above=-999 required=5 tests=[AWL=-0.117, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_LOW=-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 bA0rmKk4b4rR for <rtcweb@ietfa.amsl.com>; Fri, 31 Aug 2012 08:40:46 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 123F721F8666 for <rtcweb@ietf.org>; Fri, 31 Aug 2012 08:40:45 -0700 (PDT)
Received: by lbky2 with SMTP id y2so1587833lbk.31 for <rtcweb@ietf.org>; Fri, 31 Aug 2012 08:40:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3HbgXL+Ne4LxM0Hv/Dil3X8vWkdb6Bidvwe9pr3dVsQ=; b=CtXnNd4kOq1ySK+WxagH0xMQVMAcMR/h+9rjTRZ5rR4Wkh8w5C621BWJhCPLave7QJ 3bxzJm90/1U3m2plfySPwYioYJ7Nf2n2bCHyMHK6RvP7K+ho27MfVhXK3Iaopq2OoiJt Yn/r/N7Qo9v0vNA9UhZemMz7Xi2NDeQSI0F/2BhrJREuLwcdxFe0FM4pFOc1Ljr++mYv /I0wQj6Gr+d0fAoBch7wD8oMoXmO8vfy02LCvhIebpgSRsq7rnUjFnfdTWx4xfgqDGGq VnPITH1rS1UNaAWxZ1kPwe8q1FsWOoiAPUkBPCMFn7xaOI9ChJ/IVDyVjFjo/Tk8eXrj dPMg==
MIME-Version: 1.0
Received: by 10.152.112.233 with SMTP id it9mr6819450lab.40.1346427644797; Fri, 31 Aug 2012 08:40:44 -0700 (PDT)
Received: by 10.112.49.66 with HTTP; Fri, 31 Aug 2012 08:40:43 -0700 (PDT)
Received: by 10.112.49.66 with HTTP; Fri, 31 Aug 2012 08:40:43 -0700 (PDT)
In-Reply-To: <20120831151247.GY72831@verdi>
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>
Date: Fri, 31 Aug 2012 08:40:43 -0700
Message-ID: <CAD6AjGToznJtNdSzyFbxKhhXQTLTuOWnPutOYDCQCVH_8mRZ5w@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: John Leslie <john@jlc.net>
Content-Type: multipart/alternative; boundary="f46d040838d37be4b104c8919dcf"
Cc: Randell Jesup <randell-ietf@jesup.org>, 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: Fri, 31 Aug 2012 15:40:47 -0000
On Aug 31, 2012 8:13 AM, "John Leslie" <john@jlc.net> wrote: > > Randell Jesup <randell-ietf@jesup.org> wrote: > > > > If you're talking audio-only calls, I agree - but for audio+video, you > > want a lot of bandwidth available for video. If the user has 128Kbps, I > > don't want 56K of that devoted to audio; I probably want 15-25K for > > audio (which can give good wideband or better performance with Opus), > > and the rest for video. I probably wouldn't open audio up to 56 or 64K > > (using Opus) below 300-500K of total bandwidth, because of diminishing > > rate of improvement over ~25K. > > 128Kbps is marginal for audio+video, yes. > > However, I don't believe it wise for us to try to standardize anything > about the audio-vs-video tradeoff. > > I will state my opinion that good audio plus one frame per second is > better in a conferencing environment than bad audio plus 128Kbps of > video; but I'd never impose that choice on anyone else. > > The point is: G.711 is suboptimal, yes, but not unusable. > > 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. > 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. CB > > Having a *good* low-bitrate (and adaptable) audio codec is *critical* > > to having a good solution for video. > > I'm not sure I agree, though it is certainly _very_ helpful. > > > Without that all the cases that involve video are blown below 100's > > of Kbps; with a good low-bandwidth codec you can do video calls > > with 100Kbps or even less. > > I'm not sure even this will remain true for five years. > > But I am sure that the market will implement Opus or something > like it within five years without our needing to call it MTI. > > > This is why I support Opus (+G.711 for legacy interop and testing) > > for MTI. > > This _is_ a good argument: I don't mean to ridicule it. > > But we need to reach closure on this. If enough people are scared > of the IPR questions of Opus, I'm willing to retreat to a SHOULD > implement Opus. > > -- > John Leslie <john@jlc.net> > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb
- [rtcweb] RTCWEB needs an Internet Codec Alan Johnston
- Re: [rtcweb] RTCWEB needs an Internet Codec Roman Shpount
- Re: [rtcweb] RTCWEB needs an Internet Codec Martin Taylor
- Re: [rtcweb] RTCWEB needs an Internet Codec Harald Alvestrand
- Re: [rtcweb] RTCWEB needs an Internet Codec Randall Gellens
- Re: [rtcweb] RTCWEB needs an Internet Codec Randall Gellens
- Re: [rtcweb] RTCWEB needs an Internet Codec Ralph Giles
- Re: [rtcweb] RTCWEB needs an Internet Codec Harald Alvestrand
- Re: [rtcweb] RTCWEB needs an Internet Codec DRAGE, Keith (Keith)
- Re: [rtcweb] RTCWEB needs an Internet Codec Harald Alvestrand
- Re: [rtcweb] RTCWEB needs an Internet Codec stephane.proust
- Re: [rtcweb] RTCWEB needs an Internet Codec Stefan Hakansson LK
- Re: [rtcweb] RTCWEB needs an Internet Codec Christer Holmberg
- Re: [rtcweb] RTCWEB needs an Internet Codec Martin Taylor
- Re: [rtcweb] RTCWEB needs an Internet Codec Randall Gellens
- Re: [rtcweb] RTCWEB needs an Internet Codec Mandyam, Giridhar
- Re: [rtcweb] RTCWEB needs an Internet Codec Jean-Marc Valin
- Re: [rtcweb] RTCWEB needs an Internet Codec Harald Alvestrand
- Re: [rtcweb] RTCWEB needs an Internet Codec Jean-Marc Valin
- Re: [rtcweb] RTCWEB needs an Internet Codec Gregory Maxwell
- Re: [rtcweb] RTCWEB needs an Internet Codec Mandyam, Giridhar
- Re: [rtcweb] RTCWEB needs an Internet Codec Mandyam, Giridhar
- Re: [rtcweb] RTCWEB needs an Internet Codec Jean-Marc Valin
- Re: [rtcweb] RTCWEB needs an Internet Codec Harald Alvestrand
- Re: [rtcweb] RTCWEB needs an Internet Codec Timothy B. Terriberry
- Re: [rtcweb] RTCWEB needs an Internet Codec John Leslie
- Re: [rtcweb] RTCWEB needs an Internet Codec Randell Jesup
- Re: [rtcweb] RTCWEB needs an Internet Codec Mandyam, Giridhar
- Re: [rtcweb] RTCWEB needs an Internet Codec John Leslie
- Re: [rtcweb] RTCWEB needs an Internet Codec Harald Alvestrand
- Re: [rtcweb] RTCWEB needs an Internet Codec Cameron Byrne
- Re: [rtcweb] RTCWEB needs an Internet Codec Mandyam, Giridhar
- Re: [rtcweb] RTCWEB needs an Internet Codec Jean-Marc Valin
- Re: [rtcweb] RTCWEB needs an Internet Codec Roman Shpount
- Re: [rtcweb] RTCWEB needs an Internet Codec Mandyam, Giridhar
- Re: [rtcweb] RTCWEB needs an Internet Codec Tim Panton
- Re: [rtcweb] RTCWEB needs an Internet Codec Jean-Marc Valin
- Re: [rtcweb] RTCWEB needs an Internet Codec Jean-Marc Valin
- Re: [rtcweb] RTCWEB needs an Internet Codec Randall Gellens
- Re: [rtcweb] RTCWEB needs an Internet Codec Gregory Maxwell
- Re: [rtcweb] RTCWEB needs an Internet Codec Stefan Hacker
- Re: [rtcweb] RTCWEB needs an Internet Codec Ron
- Re: [rtcweb] RTCWEB needs an Internet Codec Basil Mohamed Gohar
- Re: [rtcweb] RTCWEB needs an Internet Codec Cameron Byrne
- Re: [rtcweb] RTCWEB needs an Internet Codec Ron
- Re: [rtcweb] RTCWEB needs an Internet Codec Richard Shockey
- Re: [rtcweb] RTCWEB needs an Internet Codec Randall Gellens
- Re: [rtcweb] RTCWEB needs an Internet Codec Richard Shockey
- Re: [rtcweb] RTCWEB needs an Internet Codec Basil Mohamed Gohar
- Re: [rtcweb] RTCWEB needs an Internet Codec Sergio Garcia Murillo
- Re: [rtcweb] RTCWEB needs an Internet Codec Harald Alvestrand
- Re: [rtcweb] RTCWEB needs an Internet Codec Jim Gettys
- Re: [rtcweb] RTCWEB needs an Internet Codec Ron
- Re: [rtcweb] RTCWEB needs an Internet Codec Randall Gellens
- Re: [rtcweb] RTCWEB needs an Internet Codec Ted Hardie
- Re: [rtcweb] RTCWEB needs an Internet Codec Jean-Marc Valin
- Re: [rtcweb] RTCWEB needs an Internet Codec Ron
- Re: [rtcweb] RTCWEB needs an Internet Codec John Leslie
- Re: [rtcweb] RTCWEB needs an Internet Codec Jean-Marc Valin
- Re: [rtcweb] RTCWEB needs an Internet Codec Timothy B. Terriberry