Linkable Identifiers
draft-wood-linkable-identifiers-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Christopher A. Wood | ||
| Last updated | 2019-10-26 (Latest revision 2019-04-24) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
Rotating public identifiers is encouraged as best practice as a means of protecting endpoint privacy. For example, regular MAC address randomization helps mitigate device tracking across time and space. Other protocols beyond those in the link layer also have public identifiers or parameters that should rotate over time, in unison with coupled protocol identifiers, and perhaps with application level identifiers. This document surveys such privacy-related identifiers exposed by common Internet protocols at various layers in a network stack. It provides advice for rotating linked identifiers such that privacy violations do not occur from rotating one identifier while neglecting to rotate coupled identifiers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)