Skip to main content

Current Hostname Practice Considered Harmful
RFC 8117

Revision differences

Document history

Date By Action
2022-08-10
(System) Received changes through RFC Editor sync (removed Errata tag)
2022-08-09
(System) Received changes through RFC Editor sync (added Errata tag)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'Giving a hostname to your computer and publishing it as you roam from one network to …
Received changes through RFC Editor sync (changed abstract to '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.')
2017-03-10
(System)
Received changes through RFC Editor sync (created alias RFC 8117, changed abstract to 'Giving a hostname to your computer and publishing it as you …
Received changes through RFC Editor sync (created alias RFC 8117, changed abstract to '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.', changed pages to 12, changed standardization level to Informational, changed state to RFC, added RFC published event at 2017-03-10, changed IESG state to RFC Published)
2017-03-10
(System) RFC published