W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > June 2017

Re: [webrtc-pc] Section 4.4.4 closed state

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Mon, 26 Jun 2017 10:39:19 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-311024219-1498473557-sysbot+gh@w3.org>
That won't cause the PC to end (`[[isClosed]]` will still be false, you can still do a re-offer that recycles the rejected "m=" sections). But it would cause all transports to enter the "closed" state, in which case you'd get an `RTCIceConnectionState` of `"new"`:

> new: Any of the RTCIceTransport s are in the new state and none of them are in the checking, failed or disconnected state, **or all RTCIceTransport s are in the closed state**.

This was by design, since having a bunch of rejected "m=" sections is equivalent to having none at all, from an application's perspective. +@pthatcherg 

-- 
GitHub Notification of comment by taylor-b
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1257#issuecomment-311024219 using your GitHub account
Received on Monday, 26 June 2017 10:39:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 June 2019 15:32:44 UTC