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

Magnus Westerlund <magnus.westerlund@ericsson.com> Fri, 22 February 2013 09:19 UTC

Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 329EC21F8E36 for <rtcweb@ietfa.amsl.com>; Fri, 22 Feb 2013 01:19:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.914
X-Spam-Status: No, score=-105.914 tagged_above=-999 required=5 tests=[AWL=0.335, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id YhuABR3iQKa3 for <rtcweb@ietfa.amsl.com>; Fri, 22 Feb 2013 01:19:20 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se []) by ietfa.amsl.com (Postfix) with ESMTP id 8C76021F8C5D for <rtcweb@ietf.org>; Fri, 22 Feb 2013 01:19:19 -0800 (PST)
X-AuditID: c1b4fb30-b7f0d6d000007e61-20-5127381674c0
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain []) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 69.CB.32353.61837215; Fri, 22 Feb 2013 10:19:18 +0100 (CET)
Received: from [] ( by esessmw0197.eemea.ericsson.se ( with Microsoft SMTP Server id; Fri, 22 Feb 2013 10:19:18 +0100
Message-ID: <51273815.20000@ericsson.com>
Date: Fri, 22 Feb 2013 10:19:17 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrOJMWRmVeSWpSXmKPExsUyM+Jvja6YhXqgQdcbeYvej0sYLdb+a2d3 YPJYsuQnk8fReftZA5iiuGxSUnMyy1KL9O0SuDI+b6ko6Oer6G56ydTAeIC7i5GTQ0LAROLb rXNsELaYxIV764FsLg4hgZOMEt+mnmOHcJYzSvQt+s0CUsUroClx/O1PJhCbRUBV4uW8Rewg NpuAhcTNH41gk0QFgiU2HFzFBFEvKHFy5hOwXhEBQ4lXy6+D2cwC6hJ3Fp8D6xUWMJN4eeEm UC8H0BXiEmvecECU6ElMudrCCGHLSzRvnc0MYgsJaEs0NHWwTmAUmIVkwywkLbOQtCxgZF7F yJ6bmJmTXm6+iREYeAe3/DbYwbjpvtghRmkOFiVx3nDXCwFCAumJJanZqakFqUXxRaU5qcWH GJk4OKUaGBk5dybufq4akTp5dZiQnT6/bd5ErawtdcoZiofSxTmZ+j3nrig/yBcWw7vpv0aW +Fcmr5P3822jyzfVF4qWCa5dLfhwe/5xQaXZ+/7mhy/ZUfX2PouZss3ujOxXAU8FOgreBqs8 ls362TLhcMmSXR0THB9LpN17zpcsdU62SvXI12YhyZI7SizFGYmGWsxFxYkAJ/OLqwoCAAA=
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: [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: Fri, 22 Feb 2013 09:19:21 -0000


As editor of the RTP usage specification in RTCWEB WG, we have had a
noted issue in our draft specification
(https://datatracker.ietf.org/doc/draft-ietf-rtcweb-rtp-usage/). In
Section 12.5. of version 05 (Contributing Sources) we had the following:

(tbd: does the API need to provide the ability to add a CSRC list to
   an outgoing packet? this is only useful if the sender is mixing

This is clearly an API question. We intended to remove it. However, I
like to hand it over to you in W3C to consider on the impact on the API
this has.

>From my personal view point this has two aspects:

Exposing when a received MediaStreamTrack is actually the mix (or
switch) of other MediaStreamTracks, a mix performed by a WebRTC endpoint
or RTP middlebox (Mixer). Applications that like to know who are
currently seen or audible needs this information mapping. We also have
specified an optional to support RTP header extension (RFC6465) that
provide energy levels for each contributing source. If that is used,
that information would be something an application would like to render

The other aspect is when an WebRTC endpoint mixes media to produce a new
MediaStreamTrack, for example with the Web Audio API, then one need to
consider if and how the CSRC list is populated.


Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVM
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com