Skip to main content

Anonymity profile for DHCP clients
draft-huitema-dhc-anonymity-profile-02

Document Type Replaced Internet-Draft (dhc WG)
Expired & archived
Authors Christian Huitema , Tomek Mrugalski , Suresh Krishnan
Last updated 2015-10-14 (Latest revision 2015-04-07)
Replaced by draft-ietf-dhc-anonymity-profile
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-dhc-anonymity-profile
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

Some DHCP options carry unique identifiers. These identifiers can enable device tracking even if the device administrator takes care of randomizing other potential identifications like link-layer addresses or IPv6 addresses. The anonymity profile is designed for clients that wish to remain anonymous to the visited network. The profile provides guidelines on the composition of DHCP or DHCPv6 requests, designed to minimize disclosure of identifying information. This draft updates RFC4361.

Authors

Christian Huitema
Tomek Mrugalski
Suresh Krishnan

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