Using Multicast DNS to protect privacy when exposing ICE candidates
draft-ietf-rtcweb-mdns-ice-candidates-03
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | Youenn Fablet , Jeroen De Borst , Justin Uberti , Qingsi Wang | ||
Last updated | 2019-09-26 (Latest revision 2019-03-25) | ||
Replaces | draft-mdns-ice-candidates | ||
Replaced by | draft-ietf-mmusic-mdns-ice-candidates | ||
RFC stream | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
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.)