Open Bug 860045 Opened 13 years ago Updated 3 years ago

UPnP IGD Implementation for WebRTC NAT Traversal

Categories

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

Product:
Core
Component:
WebRTC: Networking
Type:
enhancement

Tracking

()

Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: abr, Unassigned)

Details

(Whiteboard: [WebRTC] [blocking-webrtc-])

+++ This bug was initially created as a clone of Bug #845007 +++ Implement UPnP IGD (http://upnp.org/specs/gw/igd2/) as a way to program network devices from within WebRTC.
backlog: --- → webRTC+
Rank: 35
Priority: -- → P3
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4

As most WebRTC clients are using IPv4 and behind a NAT or firewall, this feature just makes a lot of good sense! TURN servers are fine, but the need to relay traffic can be eliminated in many cases with a direct P2P connection aided by UPnP IGD.

Syncthing, a popular for synchronization tool written in Go, does something quite similar using UPnP and global discovery servers. It works surprisingly well even without relaying traffic.

Any thoughts on how this could get implemented or added to the WebRTC spec?

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.