Anonymity profile for DHCP clients
draft-ietf-dhc-anonymity-profile-06
The information below is for an old version of the document | |||||
---|---|---|---|---|---|
Document | Type | None Internet-Draft (dhc WG) | |||
Last updated | 2016-02-15 (latest revision 2016-01-29) | ||||
Replaces | draft-huitema-dhc-anonymity-profile | ||||
Stream | IETF | ||||
Intended RFC status | Proposed Standard | ||||
Formats |
Expired & archived
pdf
htmlized
bibtex
|
||||
Reviews | |||||
Additional URLs |
|
||||
Stream | WG state | (None) | |||
Document shepherd | Bernie Volz | ||||
Shepherd write-up | Show (last changed 2016-01-13) | ||||
IESG | IESG state | Unknown state | |||
Consensus Boilerplate | Unknown | ||||
Telechat date | |||||
Responsible AD | Brian Haberman | ||||
Send notices to | (None) |
https://www.ietf.org/archive/id/draft-ietf-dhc-anonymity-profile-06.txt
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.
Authors
Christian Huitema
(huitema@microsoft.com)
Tomek Mrugalski
(tomasz.mrugalski@gmail.com)
Suresh Krishnan
(suresh.krishnan@ericsson.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)