W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2014

Re: Proposal and discussion for RtpSender.getCapabilities

From: Peter Thatcher <pthatcher@google.com>
Date: Mon, 24 Nov 2014 18:38:37 +0000
Message-ID: <CAJrXDUH+dzH1G-vZvj8Fng+Q1=7f3V7qsNjwpvqAG2gtcNSw_A@mail.gmail.com>
To: Bernard Aboba <Bernard.Aboba@microsoft.com>, Singh Varun <varun.singh@aalto.fi>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
For what "kind" means, Bernard wrote it better than I could have.

As for which "streams" this applies to, it indicates what header extensions
the browser is capable of sending, for all tracks and RtpSenders of the
corresponding kind.  Translating into "streams", it basically means "all
the streams".

On Mon Nov 24 2014 at 9:38:21 AM Bernard Aboba <Bernard.Aboba@microsoft.com>
wrote:

> RtpSender.getCapabilities(kind) would be used to return the capabilities
> for a given kind.  So if kind === "audio" then this would return the audio
> capabilities.  Having RTCRtpHdrExtCapability.kind would enable
> getCapabilities(kind) to filter the header extensions.
> There are some header extensions that have a clear kind (e.g. "audio" for
> client-mixer and mixer-client extensions) and some that may not (e.g.
> abs-send-time, described at http://www.webrtc.org/
> experiments/rtp-hdrext/abs-send-time).  In the latter case, it is
> necessary to define what RTCRtpHdrExtCapability.kind would be (e.g. return
> the value of kind passed as an argument in getCapabilities(kind)).
>
>
> ======================================
> From: Singh Varun [varun.singh@aalto.fi]
> Sent: Monday, November 24, 2014 6:19 AM
> To: Peter Thatcher
> Cc: public-webrtc@w3.org
> Subject: Re: Proposal and discussion for RtpSender.getCapabilities
>
> Hi Peter
>
> On 03 Nov 2014, at 22:59, Peter Thatcher <pthatcher@google.com<mailto:p
> thatcher@google.com>> wrote:
>
> At TPAC (2014), we reached consensus that we want some form or
> RtpSender.getCapabilities.  But we wanted to make sure we have the right
> "minimal starting set".    Additionally, there was an idea of having audio-
> and video-specific types for audio and video codecs.
>
>
> dictionary RTCRtpHdrExtCapability {
>     DOMString kind;
>     DOMString uri;
> };
>
>
> URIs are based on http://www.iana.org/assignments/rtp-parameters/
> rtp-parameters.xml and may apply to particular stream or to all the media
> streams?
> What does the “kind" correspond to in the case of hdr extensions? Is it
> supposed to point to the codec.kind?
>
Received on Monday, 24 November 2014 18:39:10 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:42 UTC