Closed Bug 1123722 Opened 10 years ago Closed 8 years ago

Support for the STUN origin attribute

Categories

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

Product:
Core
Component:
WebRTC: Networking
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX
Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: fippo, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/37.0.2062.120 Chrome/37.0.2062.120 Safari/537.36 Actual results: Firefox does currently not support the STUN origin attribute Expected results: Associating TURN binding requests with the origin of the request (and/or choosing a realm attribute based on that) would be useful. https://tools.ietf.org/html/draft-ietf-tram-stun-origin-03 describes a way to do this by adding an origin attribute Chrome will start doing this soon -- http://code.google.com/p/webrtc/issues/detail?id=4091 and only having this in both major browsers will make this actually usable.
Component: Untriaged → WebRTC: Networking
OS: Linux → All
Product: Firefox → Core
Hardware: x86_64 → All
Byron -- Do you agree with this priority?
Status: UNCONFIRMED → NEW
backlog: --- → webRTC+
Rank: 25
Ever confirmed: true
Flags: needinfo?(docfaraday)
Priority: -- → P2
At a glance, this doesn't look as important compared to the other stuff on our plate.
Rank: 25 → 40
Flags: needinfo?(docfaraday)
Priority: P2 → P4
https://bugs.chromium.org/p/webrtc/issues/detail?id=4091#c10 -- chrome just decided to unship this since it didn't survive in IETF land so it doesn't make sense to implement in Firefox either
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.