Re: [rtcweb] Confirmation of consensus on audio codecs

"Richard Shockey" <richard@shockey.us> Sat, 18 August 2012 18:05 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 5109121F8487 for <rtcweb@ietfa.amsl.com>; Sat, 18 Aug 2012 11:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.47
X-Spam-Level:
X-Spam-Status: No, score=-101.47 tagged_above=-999 required=5 tests=[AWL=0.795, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 73m3qp2O9UV2 for <rtcweb@ietfa.amsl.com>; Sat, 18 Aug 2012 11:05:04 -0700 (PDT)
Received: from oproxy5-pub.bluehost.com (oproxy5-pub.bluehost.com [67.222.38.55]) by ietfa.amsl.com (Postfix) with SMTP id 987BD21F846F for <rtcweb@ietf.org>; Sat, 18 Aug 2012 11:04:52 -0700 (PDT)
Received: (qmail 1587 invoked by uid 0); 18 Aug 2012 18:04:30 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by cpoproxy2.bluehost.com with SMTP; 18 Aug 2012 18:04:30 -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=XcBo3mUSLKyCzYozUeKSz7okTFLxrNis+/bKpDSJXY0=; b=Zuq42dmBki2zxLER+z4bvBvGQ+hu7lycd+jHCSKYmV1I6u+6/p7ppD0ZmFfFFH/CRBIOagSclQ42eY8JvxaBwNqPgu7Mlt/+u+cnIE62IoqhR5XijveekL84PM/Az9HN;
Received: from [71.191.243.130] (port=55063 helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.76) (envelope-from <richard@shockey.us>) id 1T2nNu-0007Pb-4h; Sat, 18 Aug 2012 12:04:30 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'Jonathan Rosenberg'" <jdrosen@jdrosen.net>, "'Matthew Kaufman'" <matthew.kaufman@skype.net>
References: <9E2843EA-EBB9-40B3-898C-6B5216FAE7A5@cisco.com> <000801cd7c06$2de34710$89a9d530$@us> <BLU401-EAS85810F1B7E00B95230D7F293B40@phx.gbl> <AE1A6B5FD507DC4FB3C5166F3A05A4840E4DEF42@tk5ex14mbxc272.redmond.corp.microsoft.com> <CA+23+fFLWoMCNgssuuYToXygO5qrtkHd5QidZTiYCaXAZ6smCw@mail.gmail.com>
In-Reply-To: <CA+23+fFLWoMCNgssuuYToXygO5qrtkHd5QidZTiYCaXAZ6smCw@mail.gmail.com>
Date: Sat, 18 Aug 2012 14:04:26 -0400
Message-ID: <001d01cd7d6b$e8d75050$ba85f0f0$@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: Ac18mhYH7FeVglmQSZGsfoxxO/aUzQA0SfFw
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: "'Cullen Jennings \(fluffy\)'" <fluffy@cisco.com>, rtcweb@ietf.org
Subject: Re: [rtcweb] Confirmation of consensus on audio codecs
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, 18 Aug 2012 18:05:06 -0000

Even though 711 quality actually sucks. I only mention 722 ..AMR WB btw
since it's obvious that if you may want to interoperate with the several
billion mobile endpoints that may be deploying VoLTE over the next few
years. It might prove useful, unless this entire exercise is about creating
N squared silos. 

You are still going to have to define a MUST support video codec eventually
so just get on with it ..saying VP8 only is just unrealistic. 

-----Original Message-----
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of
Jonathan Rosenberg
Sent: Friday, August 17, 2012 1:02 PM
To: Matthew Kaufman
Cc: Cullen Jennings (fluffy); rtcweb@ietf.org
Subject: Re: [rtcweb] Confirmation of consensus on audio codecs

I'll chime in here too - it'll surprise no one that I agree Opus should be
MTI. I agree on G.711 as well, as this has realistically been the lingua
franca for voip since the very beginning. Its easy to put in, no IPR and
will help with the many interop scenarios which the market will eventually
want. Even if intermediaries are needed on the media path for other things -
like ICE interop - at least we won't need transcode.

-Jonathan R.

On Fri, Aug 17, 2012 at 12:30 PM, Matthew Kaufman
<matthew.kaufman@skype.net> wrote:
> I agree. OPUS because it will be the IETF standard for wideband audio on
the Internet, G.711 for maximum interoperability. G.722 is a reasonable
thing to put on the "SHOULD" list... there's some other good choices for the
SHOULD list, but they unfortunately come with additional IPR issues.
>
> Matthew Kaufman
>
> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On 
> Behalf Of Bernard Aboba
> Sent: Thursday, August 16, 2012 5:42 PM
> To: rtcweb@ietf.org
> Cc: Cullen Jennings (fluffy); rtcweb@ietf.org
> Subject: Re: [rtcweb] Confirmation of consensus on audio codecs
>
> I also support the selection of OPUS and G.711 as MTI. G.722 can be a
SHOULD; it is widely supported.
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb



--
Jonathan Rosenberg, Ph.D.
GM Product Strategy and Research, Microsoft/Skype
jdrosen@{skype.net,jdrosen.net,microsoft.com}
http://www.jdrosen.net
_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb