Re: [rtcweb] Call for Consensus Regarding Selecting Recommended Audio Codecs

Adam Roach <adam@nostrum.com> Thu, 27 December 2012 18:21 UTC

Return-Path: <adam@nostrum.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 11E1721F8D60 for <rtcweb@ietfa.amsl.com>; Thu, 27 Dec 2012 10:21:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.605
X-Spam-Level:
X-Spam-Status: No, score=-102.605 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, SPF_PASS=-0.001, 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 zKmBfj2TSn5v for <rtcweb@ietfa.amsl.com>; Thu, 27 Dec 2012 10:21:12 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 75F5721F8D5F for <rtcweb@ietf.org>; Thu, 27 Dec 2012 10:21:12 -0800 (PST)
Received: from Orochi.local (99-152-144-32.lightspeed.dllstx.sbcglobal.net [99.152.144.32]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qBRIKt13037212 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 27 Dec 2012 12:20:58 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <50DC9187.6010300@nostrum.com>
Date: Thu, 27 Dec 2012 12:20:55 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Steve Sokol <ssokol@digium.com>
References: <7daabbec-07cc-421e-b6d4-5292b9c063b5@zimbra>
In-Reply-To: <7daabbec-07cc-421e-b6d4-5292b9c063b5@zimbra>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 99.152.144.32 is authenticated by a trusted mechanism)
Cc: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, rtcweb@ietf.org
Subject: Re: [rtcweb] Call for Consensus Regarding Selecting Recommended 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: Thu, 27 Dec 2012 18:21:13 -0000

On 12/27/12 11:05, Steve Sokol wrote:
> I don't see unmediated legacy interoperability as likely to happen

Ugh. I hate repeating this, but there is a radical difference between 
dealing with computationally cheap things like bundling, ICE, SCTP and 
even (from a relative perspective) encryption and dealing with 
re-encoding media.

Transcoding perceptibly increases end-to-end latency. Transcoding 
perceptibly degrades the final audio stream. All other gatewaying 
functions can be done cheaply enough that the user cannot tell a difference.

Which is why I think there is *utility* to listing commonly used codecs 
and explaining where/how they are used. I really do want to see this as 
part of a guidance section for implementors.

However, I don't think any of those reasons rise to the level of an RFC 
2119 "SHOULD" level statement.

/a