Open
Bug 881982
Opened 12 years ago
Updated 3 years ago
ICE: handle dynamic network interface change
Categories
(Core :: WebRTC: Networking, defect, P4)
Core
WebRTC: Networking
Tracking
()
NEW
| backlog | webrtc/webaudio+ |
People
(Reporter: swu, Unassigned)
References
Details
(Whiteboard: [WebRTC][b2g-webrtc+])
There are chances that the network interface been added/removed dynamically, or IP address of network interface been changed. Especially on device accessing through 3G or Wifi network.
There is an IETF draft talking about the mobility of ICE (draft-wing-mmusic-ice-mobility-03). It defines new STUN/TURN attributes, which requires change on STUN/TURN server. So it can be considered as a long term solution after the draft becomes RFC.
For short term solution, we need a way to notify ICE on these changes and re-negotiate new candidates pairs.
|
Reporter | |
Updated•12 years ago
|
Blocks: b2g-webrtc
Whiteboard: [WebRTC]
|
||
Updated•12 years ago
|
Whiteboard: [WebRTC] → [WebRTC][b2g-webrtc+]
|
||
Updated•10 years ago
|
backlog: --- → webRTC+
Rank: 38
Priority: -- → P3
|
||
Comment 1•8 years ago
|
||
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•