Section 8.4: RTCRtpFeatures #65

Closed
aboba opened this Issue Apr 22, 2014 · 1 comment

Projects

None yet

2 participants

@aboba
Contributor
aboba commented Apr 22, 2014

Currently, RTCRtpFeatures is defined as follows:

enum RTCRtpFeatures {
"nack"
};

Two questions:

  1. Should it be defined as a DOMString instead?
  2. What is the complete list of RTP features that goes here?
@robin-raymond
Contributor

Discussion:
http://lists.w3.org/Archives/Public/public-ortc/2014Apr/0097.html

And discussion here:
http://lists.w3.org/Archives/Public/public-ortc/2014Apr/0114.html

Going to use GUM style Capabilities / Settings as suggest.

@robin-raymond robin-raymond added the 1.1 label Apr 29, 2014
@robin-raymond robin-raymond pushed a commit to robin-raymond/ortc that referenced this issue Apr 29, 2014
Robin Raymond - Fixes for error handling, as described in w3c#26
- Support for contributing sources removed (re-classified as a 1.2 feature), as described in w3c#27
- Cleanup of DataChannel construction, as described in w3c#60
- Separate proposal on simulcast/layering, as described in w3c#61
- Separate proposal on quality, as described in w3c#62
- Fix for TCP candidate type, as described in w3c#63
- Fix to the fingerprint attribute, as described in w3c#64
- Fix to RTCRtpFeatures, as described in w3c#65
- Support for retrieval of remote certificates, as described in w3c#67
- Support for ICE error handling, described in w3c#68
- Support for Data Channel send rate control, as described in w3c#69
- Support for capabilities and settings, as described in w3c#70
- Removal of duplicate RTCRtpListener functionality, as described in w3c#71
- ICE gathering state added, as described in w3c#72
- Removed ICE role from the ICE transport constructor, as described in w3c#73
3571fd1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment