Skip to main content

Using Multicast DNS to protect privacy when exposing ICE candidates
draft-mdns-ice-candidates-00

Document Type Replaced Internet-Draft (candidate for rtcweb WG)
Expired & archived
Author Youenn Fablet
Last updated 2018-07-27 (Latest revision 2018-06-29)
Replaced by draft-ietf-rtcweb-mdns-ice-candidates
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-rtcweb-mdns-ice-candidates
Consensus boilerplate Unknown
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 rely on ICE candidates to enable peer-to-peer connections between clients in as many network configurations as possible. To maximize the probability to create a direct peer-to- peer connection, client private IP addresses are often exposed without user consent. This is currently used as a way to track users. This document describes a way to share IP addresses with other clients while preserving client privacy. This is achieved by obfuscating IP addresses using dynamically generated names resolvable through Multicast DNS [RFC6763].

Authors

Youenn Fablet

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