RFC 8117: Current Hostname Practice Considered Harmful
In plain English — editorial summary, not part of the RFC
Giving a hostname to your computer and publishing it as you roam from one network to another is the Internet's equivalent of walking around with a name tag affixed to your lapel. This current practice can significantly compromise your privacy, and something should change in order to mitigate these privacy threats. There are several possible remedies, such as fixing a variety of protocols or avoiding disclosing a hostname at all. This document describes some of the protocols that reveal hostnames today and sketches another possible remedy, which is to replace static hostnames by frequently changing randomized values.
Document record
- Document ID
- RFC8117
- Published
- March 2017
- Authors
- C. Huitema; D. Thaler; R. Winter
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 12
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8115DHCPv6 Option for IPv4-Embedded Multicast and Unicast IPv6 PrefixesCurrent
March 2017
- RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent
March 2017
- RFC 8127Mobile Access Gateway Configuration Parameters Controlled by the Local Mobility AnchorCurrent
August 2017
- RFC 8106IPv6 Router Advertisement Options for DNS ConfigurationCurrent
March 2017
- RFC 8105Transmission of IPv6 Packets over Digital Enhanced Cordless Telecommunications (DECT) Ultra Low Energy (ULE)Current
May 2017
- RFC 8096The IPv6-Specific MIB Modules Are ObsoleteCurrent
April 2017
- RFC 8094DNS over Datagram Transport Layer Security (DTLS)Current
February 2017
- RFC 8156DHCPv6 Failover ProtocolCurrent
June 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?