- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 May 2017 17:55:54 +0000
- To: public-webrtc-logs@w3.org
I don't think the browser not implementing "negotiate" is relevant to this issue. The issue is really "what error do you get when the RTCP mux policy is 'require'?". I don't see what "step 3" you're referring to; I see these steps though (2.1.4 and 2.1.5): > If the content of description is not valid SDP syntax, then reject p with an RTCError... > If the content of description is invalid, then reject p with a newly created InvalidAccessError... This error fits more as "invalid content" than "not valid SDP syntax", so I guess it would be an `InvalidAccessError` as specified today. It may make sense to change this to also be an `RTCError` with an SDP line number; @aboba, what do you think? As for `setConfiguration`: I don't think it makes a big difference if you get an `InvalidModificationError` or a `NotSupportedError`. If you'd prefer it being changed, I'm fine with that. -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1235#issuecomment-303802389 using your GitHub account
Received on Wednesday, 24 May 2017 17:56:08 UTC