RE: Proposal and discussion for RtpSender.getCapabilities

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:pthatcher@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 17:38:47 UTC