Using Multicast DNS to protect privacy when exposing ICE candidates

Document Type Replaced Internet-Draft (individual)
Authors Youenn Fablet  , Jeroen De Borst  , Justin Uberti  , Qingsi Wang 
Last updated 2020-04-18 (latest revision 2019-10-16)
Replaces draft-mdns-ice-candidates
Replaced by draft-ietf-mmusic-mdns-ice-candidates
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-mmusic-mdns-ice-candidates
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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.


Youenn Fablet (
Jeroen De Borst (
Justin Uberti (
Qingsi Wang (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)