[Int-area] RFC 8117 on Current Hostname Practice Considered Harmful
rfc-editor@rfc-editor.org Fri, 10 March 2017 17:23 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F7151299A7; Fri, 10 Mar 2017 09:23:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tR0ccuNgvQw0; Fri, 10 Mar 2017 09:23:40 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CDCC1299A1; Fri, 10 Mar 2017 09:23:35 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 81BE8B80E56; Fri, 10 Mar 2017 09:23:30 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310172330.81BE8B80E56@rfc-editor.org>
Date: Fri, 10 Mar 2017 09:23:30 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/ZRNPsi1L4YlwGlbgEtZd5yFngjs>
Cc: drafts-update-ref@iana.org, int-area@ietf.org, rfc-editor@rfc-editor.org
Subject: [Int-area] RFC 8117 on Current Hostname Practice Considered Harmful
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Mar 2017 17:23:49 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8117
Title: Current Hostname Practice Considered Harmful
Author: C. Huitema, D. Thaler, R. Winter
Status: Informational
Stream: IETF
Date: March 2017
Mailbox: huitema@huitema.net,
dthaler@microsoft.com,
rolf.winter@hs-augsburg.de
Pages: 12
Characters: 26750
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-intarea-hostname-practice-05.txt
URL: https://www.rfc-editor.org/info/rfc8117
DOI: 10.17487/RFC8117
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.
This document is a product of the Internet Area Working Group Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC