Using Multicast DNS to protect privacy when exposing ICE candidates
draft-ietf-rtcweb-mdns-ice-candidates-03
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-09-26 (latest revision 2019-03-25) | ||
| Replaces | draft-mdns-ice-candidates | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-rtcweb-mdns-ice-candidates-03.txt
Abstract
WebRTC applications collect ICE candidates as part of the process of creating peer-to-peer connections. To maximize the probability of a direct peer-to-peer connection, client private IP addresses are included in this candidate collection. However, disclosure of these addresses has privacy implications. This document describes a way to share local IP addresses with other clients while preserving client privacy. This is achieved by concealing IP addresses with dynamically generated Multicast DNS (mDNS) names.
Authors
Youenn Fablet
(youenn@apple.com)
Jeroen Borst
(jeroendb@google.com)
Justin Uberti
(juberti@google.com)
Qingsi Wang
(qingsi@google.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)