Respond faster to networking errors in ICE

NEW
Unassigned

Status

()

Core
WebRTC: Networking
4 years ago
2 years ago

People

(Reporter: ekr, Unassigned)

Tracking

unspecified
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
The current code doesn't report networking errors upward well,
e.g., when you read. Packets just stop flowing.
Related to bug 929977?

Comment 2

4 years ago
(In reply to Max Jonas Werner from comment #1)
> Related to bug 929977?

The impetus for filing this bug in the first place is informing the application when a TCP connection attempt timeouts (cf. Bug 906968); but the description does sound like EKR has something broader in mind.
Byron -- Do you want to do this sooner than later?
backlog: --- → parking-lot
Flags: needinfo?(docfaraday)

Comment 4

3 years ago
This could make it easier to diagnose certain types of ICE failure, but I'm pretty sure these types of failure are uncommon.
Flags: needinfo?(docfaraday)
After having looked into some of the potential errors around TURN TCP and HTTP proxy connect support I think it might be beneficial to have something like a optional transport error callback. But as Byron pointed out it will mostly help with diagnosing and in some cases we might be able finish gathering ealier then having to wait for timeouts like we do so far.
You need to log in before you can comment on or make changes to this bug.