New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure of ICE consent #171

Closed
aboba opened this Issue Jan 18, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@aboba
Copy link
Contributor

aboba commented Jan 18, 2015

If ICE consent fails, what happens? IceTransport no longer has an onerror event handler (this was moved to the IceGatherer).

@aboba aboba added the 1.1 label Jan 18, 2015

@aboba

This comment has been minimized.

Copy link
Contributor

aboba commented Jan 20, 2015

Proposal is to treat a failure of ICE consent as a transition of the ICE Transport state to 'disconnected':

disconnected
Liveness checks have failed (such as those in [CONSENT]). This may trigger intermittently (and resolve itself without action).

robin-raymond pushed a commit that referenced this issue Jan 22, 2015

Robin Raymond
Updated Section 8.3 to reflect proposed matching rules, reflecting:
#48

Update to the Statistics API, reflecting:
#85

Update on 'automatic' use of scalable video coding, as noted in:
#156

Update to the H.264 parameters, as noted in:
#158

Update to the 'Big Picture', as noted in:
#159

Added support for maxptime, as noted in:
#160

Changed 'RTCIceTransportEvent' to 'RTCIceGathererEvent' as noted in:
#161

Update to RTCRtpUnhandledEvent as noted in:
#163

Added support for RTCIceGatherer.state as noted in:
#164

Revised the text relating to RTCIceTransport.start() as noted in:
#166

Added text relating to DTLS interoperability with WebRTC 1.0, as noted in:
#167

Revised the text relating to RTCDtlsTransport.start() as noted in:
#168

Clarified handling of incoming connectivity checks by the RTCIceGatherer as noted in:
#170

Added a reference to the ICE consent specification, as noted in:
#171
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment