- From: Florent Castelli via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Dec 2018 13:25:40 +0000
- To: public-webrtc-logs@w3.org
@amithilbuch Implementation for those parameters is on-going. The WebRTC API does map to features specified by the IETF RTCWEB but it isn't meant to have full coverage of features, but answer some use-cases. It is fine to only be able to generate a subset of the possible values. We should be able to accept all values from a remote implementing the full protocol though. @aboba I don't believe that `maxFramerate` or `maxBitrate` would be filled by `max-fs` or `max-br`. I believe they should be enforced at the lower level as hard limits. An application could chose to raise the `maxBitrate` value above `max-br` but the later should be honored (real limit would be the minimum between the two values). It would be similar to `max-height` or `max-width` from SDP which won't map to any `RTCEncodingParameters` entry but should probably still be honored by the sender. -- GitHub Notification of comment by Orphis Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2035#issuecomment-444484032 using your GitHub account
Received on Wednesday, 5 December 2018 13:25:42 UTC