Anonymity Profiles for DHCP Clients

Krishnan, Suresh; Mrugalski, Tomek; Huitema, Christian

doi:10.17487/rfc7844

Cited by 15 publications

(27 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This is, for example, what is attempted for DHCP in [RFC7844]. However, it is unclear that we can identify, revisit, and fix all the protocols that publish hostnames.…”

Section: Randomized Hostnames As a Remedymentioning

confidence: 99%

“…In a way, this is similar to the approach of Media Access Control (MAC) address randomization described in [RFC7844]. Let's assume that the operating system, at the time of connecting to a new network, picks a random hostname and starts publicizing that random name in protocols such as DHCP or mDNS, instead of the static value.…”

Section: Randomized Hostnames As a Remedymentioning

confidence: 99%

See 1 more Smart Citation

Current Hostname Practice Considered Harmful

Huitema¹,

Thaler²

2017

Self Cite

View full text Add to dashboard Cite

show abstract

“…This is, for example, what is attempted for DHCP in [RFC7844]. However, it is unclear that we can identify, revisit, and fix all the protocols that publish hostnames.…”

Section: Randomized Hostnames As a Remedymentioning

confidence: 99%

Section: Randomized Hostnames As a Remedymentioning

confidence: 99%

Current Hostname Practice Considered Harmful

Huitema¹,

Thaler²

2017

Self Cite

View full text Add to dashboard Cite

show abstract

“…Clients may follow the recommendations in [RFC7844] to minimize what information they expose or make use of secure DHCPv6 [SEC-DHCPv6] to secure communication between the client and server.…”

Section: Security Considerationsmentioning

confidence: 99%

Security of Messages Exchanged between Servers and Relay Agents

Pal¹,

Volz²

2017

View full text Add to dashboard Cite

The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has no guidance for how to secure messages exchanged between servers and relay agents. The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) states that IPsec should be used to secure messages exchanged between servers and relay agents but does not require encryption. With recent concerns about pervasive monitoring and other attacks, it is appropriate to require securing relay-to-relay and relay-to-server communication for DHCPv6 and relay-to-server communication for DHCPv4.

show abstract

“…If those mechanisms are available, it is possible to use them to provide tracking; this form of tracking is more secure and reliable than server logs because it operates independently of how addresses are allocated. Finally, tracking address information via DHCPv6 server logs is likely to become decreasingly viable due to ongoing efforts to improve the privacy of DHCPv6 and MAC address randomization [RFC7844].…”

Section: Host Trackingmentioning

confidence: 99%