Update to latest draft-ietf-rtcweb-ip-handling
Categories
(Core :: WebRTC: Networking, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox70 | --- | fixed |
People
(Reporter: bwc, Assigned: ralderete)
References
Details
Attachments
(2 files)
Updated•6 years ago
|
Assignee | ||
Comment 3•5 years ago
|
||
draft-ietf-rtcweb-ip-handling specifies that the default route is the route
used to reach the origin rather than the one used to reach the internet, so
update the IP routing to reflect this. This addresses issues in which the
wrong IP address is used on machines with multiple network interfaces.
Depends on D36203
Assignee | ||
Comment 4•5 years ago
|
||
Fall back to using Google's DNS server to determine the associated local
addresses for web applications that are not loaded over the network. This
includes the loopback address, which is frequently used in the unit tests.
Provide a separate function for setting the target for the default local
address lookup.
Depends on D36831
Reporter | ||
Comment 5•5 years ago
|
||
I just tried this with the datachannel-only example on webrtc-landing. Depending on how I configured routing to mozilla.github.io, I got different IP addresses on my host candidates, so it seems that this is working. I have not attempted testing a datachannel page loaded from a file, or from localhost.
Reporter | ||
Updated•5 years ago
|
Comment 9•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/45de434a4da1
https://hg.mozilla.org/mozilla-central/rev/ed3ab66482af
Description
•