Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in the API?
Adam Bergkvist <adam.bergkvist@ericsson.com> Fri, 22 February 2013 11:13 UTC
Return-Path: <adam.bergkvist@ericsson.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 C408121F8E77 for <rtcweb@ietfa.amsl.com>; Fri, 22 Feb 2013 03:13:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 txWzpQnhnVKx for <rtcweb@ietfa.amsl.com>; Fri, 22 Feb 2013 03:13:21 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id BC60B21F8E6C for <rtcweb@ietf.org>; Fri, 22 Feb 2013 03:13:20 -0800 (PST)
X-AuditID: c1b4fb30-b7f0d6d000007e61-ae-512752cfaa6f
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 0B.3F.32353.FC257215; Fri, 22 Feb 2013 12:13:19 +0100 (CET)
Received: from [150.132.141.81] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.279.1; Fri, 22 Feb 2013 12:13:19 +0100
Message-ID: <512752CF.1010700@ericsson.com>
Date: Fri, 22 Feb 2013 12:13:19 +0100
From: Adam Bergkvist <adam.bergkvist@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>
References: <51273815.20000@ericsson.com> <51273DCD.5000003@ericsson.com> <512746DD.3080208@ericsson.com> <5127519F.6050306@alvestrand.no>
In-Reply-To: <5127519F.6050306@alvestrand.no>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjluLIzCtJLcpLzFFi42KZGfG3Rvd8kHqgwc3p5hbH+rrYLHo/LmG0 WPuvnd2B2ePKhCusHkuW/GTyODpvP2sAcxSXTUpqTmZZapG+XQJXxqRrCgWz2CsO7Ohnb2C8 ydrFyMkhIWAisefNQUYIW0ziwr31bF2MXBxCAicZJbas38YCkhASWMMocelSQhcjBwevgLbE 0q2iIGEWAVWJOWuXsYHYbAJGEpOWXAebIyoQJfH+ahMziM0rIChxcuYTsDEiAjoSD/c3MIHM ZxboZ5S48mg2O0hCWMBZ4viqTVCLuxgl1m7qB+vmFNCV6N57FWwDs4CFxOI3B9khbHmJ7W/n MEMcpyGxa/Zf5gmMgrOQLJyFpGUWkpYFjMyrGNlzEzNz0svNNzECw/Tglt8GOxg33Rc7xCjN waIkzhvueiFASCA9sSQ1OzW1ILUovqg0J7X4ECMTB6dUA6NrJatcTm1N+HJ7u+WfGgNy3Bde eWS0+7XsnDvJUYYsPIotzye2bZq9OUSd/X3N3SvlRd+2MHrP6ji5qvXQlK0Zkx71cq9vNL4y Q7L1dOFe10lJxRdEZBMCoy5ss5TQ5mbyZcnnufy65+fmOWYtjMmZ+k4b+6deLrnMpvGilV/+ +ayP8mzb/yuxFGckGmoxFxUnAgDsnzAgIQIAAA==
Cc: "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: Fri, 22 Feb 2013 11:13:21 -0000
On 2013-02-22 12:08, Harald Alvestrand wrote: > On 02/22/2013 11:22 AM, Magnus Westerlund wrote: >> On 2013-02-22 10:43, Adam Bergkvist wrote: >>> Reading CSRC info: >>> Right now, the SSRC(s) of a track is only exposed via the Stats API. I >>> think that's the right level if we were to support reading CSRC info as >>> well. >> I don't see how the Stats API comes in here. The information bit I see >> the CRSC list provides is: These MST(s) was used to produce what you >> get. It is a information about original identity of the media sources. >> Thus I would guess that in the API it might be appropriate to map the >> CSRC list to the MST IDs. > > Can you expand MST, please? > > My googling for "CSRC" and "MST" together only came up with > "Multi-Session Transmission" (from the COP draft), and that doesn't seem > to fit. My interpretation: MST = MediaStreamTrack (in this context) /Adam
- [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in the… Magnus Westerlund
- Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in… Adam Bergkvist
- Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in… Magnus Westerlund
- Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in… Harald Alvestrand
- Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in… Stefan Håkansson LK
- Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in… Adam Bergkvist
- Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in… Adam Bergkvist
- Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in… Magnus Westerlund
- Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in… Cullen Jennings (fluffy)
- Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in… Emil Ivov
- Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in… Cullen Jennings
- Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in… Justin Uberti
- Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in… Emil Ivov