Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in the API?

Cullen Jennings <fluffy@iii.ca> Wed, 27 February 2013 18:33 UTC

Return-Path: <fluffy@iii.ca>
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 17C9C21F8A05 for <rtcweb@ietfa.amsl.com>; Wed, 27 Feb 2013 10:33:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 R2wDJwsKFejB for <rtcweb@ietfa.amsl.com>; Wed, 27 Feb 2013 10:33:10 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 7DA9721F89FD for <rtcweb@ietf.org>; Wed, 27 Feb 2013 10:33:10 -0800 (PST)
Received: from dhcp-171-68-20-36.cisco.com (unknown [171.68.20.36]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 0431A509B6; Wed, 27 Feb 2013 13:33:08 -0500 (EST)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <512E4F87.5000308@jitsi.org>
Date: Wed, 27 Feb 2013 10:33:11 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <7B19F4B6-08F1-4BC4-9D6C-8C559D573818@iii.ca>
References: <51273815.20000@ericsson.com> <C5E08FE080ACFD4DAE31E4BDBF944EB113406438@xmb-aln-x02.cisco.com> <512E4F87.5000308@jitsi.org>
To: Emil Ivov <emcho@jitsi.org>
X-Mailer: Apple Mail (2.1499)
Cc: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in the API?
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: Wed, 27 Feb 2013 18:33:11 -0000

On Feb 27, 2013, at 10:25 AM, Emil Ivov <emcho@jitsi.org> wrote:

> It would also if such an API would also the possibility to
> retrieve audio levels from the RTP (Magnus already mentioned RFC6465)
> so that applications can render such information.
> 
> (Like this for example: http://goo.gl/QTaqy )

+1 on that too