Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in the API?
"Cullen Jennings (fluffy)" <fluffy@cisco.com> Wed, 27 February 2013 18:16 UTC
Return-Path: <fluffy@cisco.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 30C0021F8889 for <rtcweb@ietfa.amsl.com>; Wed, 27 Feb 2013 10:16:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 xhj66637mv5S for <rtcweb@ietfa.amsl.com>; Wed, 27 Feb 2013 10:16:36 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 3D1CC21F886B for <rtcweb@ietf.org>; Wed, 27 Feb 2013 10:16:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2498; q=dns/txt; s=iport; t=1361988996; x=1363198596; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=mfuP8qHW78xaAe+QgUJIvkpMEWZiFO69SNPKA5srl+g=; b=MGBosiCQtcqL5rkjzat/zH6AAzZrG67XDTcsp7s+g7GTr/JP/5xIs39B ULwr3HPosRJ0gegJU/oqdqKHWOW8tuPNhj5mlWVxJAYnjPZqgIL91UI9/ YzwV3FCcQ8rFesDYGbtDl98m6p4Brj6OA/jD6xJQyVyeGoo7R82eGpCZA M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAMFMLlGtJV2b/2dsb2JhbABFwiV8FnOCHwEBAQMBAQEBCVwGCwUJAgIBCCIdBxsMCxQRAgQOBQiIBQUBDMEUBASOXQIxB4JfYQOINJ53gwiCJw
X-IronPort-AV: E=Sophos;i="4.84,749,1355097600"; d="scan'208";a="181863068"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-5.cisco.com with ESMTP; 27 Feb 2013 18:16:35 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r1RIGZfa012483 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 27 Feb 2013 18:16:35 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.155]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.02.0318.004; Wed, 27 Feb 2013 12:16:35 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in the API?
Thread-Index: AQHOFRaTX7Fxoo94/UigtEaER5qR6A==
Date: Wed, 27 Feb 2013 18:16:35 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB113406438@xmb-aln-x02.cisco.com>
References: <51273815.20000@ericsson.com>
In-Reply-To: <51273815.20000@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [171.68.20.36]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <36EA574D12D64F40AC78F7ACAE201232@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Wed, 27 Feb 2013 18:16:37 -0000
I think this is very useful for a bunch of things in conferences. I'd like to see an API so the CSRC list for outgoing RTP can be set on a per track basis, and the API allows the JS to get the CSRC of most recently received RTP packets for a given PC-Track and also be nice to have a callback any time the received CSRC changes. On Feb 22, 2013, at 1:19 AM, Magnus Westerlund <magnus.westerlund@ericsson.com> wrote: > WebRTC WG, > > 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 > content) > > 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 > somehow. > > 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. > > Cheers > > 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 > ---------------------------------------------------------------------- > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb
- [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