Open Bug 884196 Opened 12 years ago Updated 3 years ago

ICE: report error on network interface change

Categories

(Core :: WebRTC: Networking, defect, P4)

defect

Tracking

()

People

(Reporter: swu, Unassigned)

References

Details

(Whiteboard: [WebRTC][b2g-webrtc+])

Prior to bug 881982, we should at least report error when network interface changed.
Blocks: b2g-webrtc
Whiteboard: [WebRTC][b2g-webrtc+]
Hi Shian-Yow, Is there a more detailed plan on error report? 1. Error report mechanism 2. Error handling mechanism 3. Category of error kind, and a high level priotized list.
Flags: needinfo?(swu)
(In reply to C.J. Ku[:CJKu] from comment #1) > Hi Shian-Yow, > Is there a more detailed plan on error report? > 1. Error report mechanism When nICEr detects the error, the report path will be: nICEr -> mtransport -> PeerConnection -> App According to Ekr, nICEr already has mechanisms for this, namely: - call the stream_failed() handler on the stream [ice_handler.h] And ICE_CTX_FAILED will be done in the handler in NrIceCtx. > 2. Error handling mechanism The events could be just a notification, not necessarily to be error. For example, if ICE module received interface change event, it may decide to get network interface list again. > 3. Category of error kind, and a high level priotized list. Example of events: - Interface up/down - IP address change (and/or routing/DNS change?) - ICMP error - Lost of connectivity
Flags: needinfo?(swu)
backlog: --- → webRTC+
Rank: 33
Priority: -- → P3
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.