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

Emil Ivov <emcho@jitsi.org> Thu, 28 February 2013 08:15 UTC

Return-Path: <emil@sip-communicator.org>
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 5161C21F86D5 for <rtcweb@ietfa.amsl.com>; Thu, 28 Feb 2013 00:15:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 RBPUxaF6uEGG for <rtcweb@ietfa.amsl.com>; Thu, 28 Feb 2013 00:15:28 -0800 (PST)
Received: from mail-ee0-f42.google.com (mail-ee0-f42.google.com [74.125.83.42]) by ietfa.amsl.com (Postfix) with ESMTP id 3846821F869C for <rtcweb@ietf.org>; Thu, 28 Feb 2013 00:15:27 -0800 (PST)
Received: by mail-ee0-f42.google.com with SMTP id b47so1168331eek.1 for <rtcweb@ietf.org>; Thu, 28 Feb 2013 00:15:27 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=fiRObXWn/97TOQNEpQqkRasT5zv+jD14GStzLDzadVY=; b=QqLZeoKMyio00xlMwBvyyMKqd/eegny/XW82mVDyPT/1IVSzaBGTswrFeGMQzUyI8L RBSl0OX4PetJjM/fZgl73VZ0Dm8J3m9sLSaBCuhAwGl86p6DV+KQo44XMh067V+y/Bd/ KvXMXGWNIhLDf6X9aXys92KuCSN0nX8r4OYRKT2vq2YG3Y/dHp3vMrIoJRFFWJ8B2Cxp nI6LGsIMlBG8AoIj2KmLuekfGEwOraIPly4ptZgR3sm8kZU1+BcQESdiPddyU6EMoeE/ B0SYqsK3fbUSmNhwSaRhgSWoRB5sKDIYdQmYFQ2ZrNjQDGlQPkiAo5HmM7aW6neLm84m mOBA==
X-Received: by 10.14.3.70 with SMTP id 46mr14686529eeg.2.1362039326882; Thu, 28 Feb 2013 00:15:26 -0800 (PST)
Received: from [10.1.1.28] (damencho.com. [78.90.89.119]) by mx.google.com with ESMTPS id 46sm10515625eea.3.2013.02.28.00.15.25 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Feb 2013 00:15:26 -0800 (PST)
Message-ID: <512F121D.6010408@jitsi.org>
Date: Thu, 28 Feb 2013 10:15:25 +0200
From: Emil Ivov <emcho@jitsi.org>
Organization: Jitsi
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
References: <51273815.20000@ericsson.com> <C5E08FE080ACFD4DAE31E4BDBF944EB113406438@xmb-aln-x02.cisco.com> <512E4F87.5000308@jitsi.org>
In-Reply-To: <512E4F87.5000308@jitsi.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlKXo9dFxw1sGsgINrSU6l1O3EIRwvUyZ7ygfcFmkpmUfmRyRLmGXq1rbVDWUXa7vb5l4Xj
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: Thu, 28 Feb 2013 08:15:29 -0000

On 27.02.13, 20:25, Emil Ivov wrote:
> +1 again. It would also if such an API would also the possibility to

Awfully sorry! This was supposed to say:

"It would also *be great* if such an API would also *provide* the
possibility to retrieve audio levels.

(Coffee deficiency!)

Emil

> 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 )
> 
> Cheers,
> Emil
>>
>>
>> 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 mailing list 
>> rtcweb@ietf.org https://www.ietf.org/mailman/listinfo/rtcweb
>>
> 

-- 
https://jitsi.org