In the current WebRTC specification, there is no way for a peer to inform the other peer that an error has occurred outside of the response to some requests.
Examples:
If a peer has disconnected in the middle of the handshake from the signaling server, the other peer will have to wait for an indefinite period of time before closing its session. With this proposal, the signaling server will be able to notify the connected peer that its counterpart has disconnected and the session can be closed.
If a client sends a connect to a device that does not have sufficient resources to start a new session, the device will now be able to send an error 1001 to inform the client that it cannot continue with this session.
In the current WebRTC specification, there is no way for a peer to inform the other peer that an error has occurred outside of the response to some requests.
Examples:
If a peer has disconnected in the middle of the handshake from the signaling server, the other peer will have to wait for an indefinite period of time before closing its session. With this proposal, the signaling server will be able to notify the connected peer that its counterpart has disconnected and the session can be closed.
If a client sends a connect to a device that does not have sufficient resources to start a new session, the device will now be able to send an error 1001 to inform the client that it cannot continue with this session.