WebRTC-Direct: Chrome may be removing ICE credential munging
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.8k
- Forks
- 320
- Avg merge
- 11d 15h
- Merged PRs (30d)
- 1
Description
ICE credential munging is currently used by webrtc-direct spec.
Chrome appears to be preparing to disable ICE credential munging in a field trial: https://webrtc-review.googlesource.com/c/src/+/385721
I don't know how these work, but there seems to be a date in that patch: Oct. 11, 2025
They may be considering this now because of a side-channel in the webrtc stats api from late last year: https://github.com/w3c/webrtc-stats/issues/789.
I don't know what y'all want to do. I don't use LibP2P, but I do use ICE credential munging. We could try to make some noise and see if we can convince them to keep it.
Or, if you want to write a V2 webrtc-direct I can give some pointers on how to remove the need for ICE munging in unsignalled browser -> server connections.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with webrtc/webrtc-direct.md and the linked Chrome change to identify where ICE credential munging is required, then review the WebRTC Stats issue for the reported motivation. Done would require an agreed migration or specification direction, which this issue does not yet define.
Written by the indexing model from the issue text.
Assessment
- Domain
- audio-video-rtc, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100