Can we remove DTLS 1.0 from WebRTC
Categories
(Core :: WebRTC: Networking, task, P2)
Tracking
()
People
(Reporter: drno, Unassigned)
References
Details
(Keywords: site-compat)
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Comment 1•6 years ago
|
||
Apparently Google is planing on removing support for 1.0 https://twitter.com/Emad_Omara/status/1092546483222728706
Looking at the Telemetry data it looks like we would kill <=2% of PeerConnection by disabling DTLS 1.0.
Martin do you think that would be reasonable?
Comment 2•6 years ago
|
||
2% is pretty high. It's a lot higher than we'd normally make a move like this. If others are moving, then we might consider 1%. If not, then the number is probably below 0.1%.
If you were to announce this for March 2020 (like we are doing for HTTP), maybe we could reduce the rates enough by then.
It would be good to eliminate DTLS 1.0, especially now that the spec no longer requires it.
Reporter | ||
Comment 3•6 years ago
|
||
Looks like Chrome is getting all kind of bug reports for turning off DTLS 1.0 in 74.
Reporter | ||
Comment 4•5 years ago
|
||
With the intent to unship TLS 1.0 and 1.1 in March 2020 https://groups.google.com/forum/#!topic/mozilla.dev.platform/8EFRYDR3N1c
we decided to also turn off DTLS 1.0 for WebRTC at the same time.
In bug 1583317 we added prefs which enable users to test today with DTLS 1.2 only.
Reporter | ||
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Comment 5•5 years ago
|
||
We should remove this telemetry: https://searchfox.org/mozilla-central/rev/723e61e5f6fe36e69592b7742bc10338392e53e4/toolkit/components/telemetry/Histograms.json#9444 as part of fixing this bug.
Comment 6•3 years ago
|
||
DTLS 1.0 is already disabled. Are there any remaining tasks?
Comment hidden (off-topic) |
Comment hidden (off-topic) |
Updated•2 years ago
|
Description
•