RFC 7819: Privacy Considerations for DHCP
In plain English — editorial summary, not part of the RFC
DHCP is a protocol that is used to provide addressing and configuration information to IPv4 hosts. This document discusses the various identifiers used by DHCP and the potential privacy issues.
Document record
- Document ID
- RFC7819
- Published
- April 2016
- Authors
- S. Jiang; S. Krishnan; T. Mrugalski
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7821UDP Checksum Complement in the Network Time Protocol (NTP)Updated
March 2016
- RFC 7822Network Time Protocol Version 4 (NTPv4) Extension FieldsUpdated
March 2016
- RFC 7815Minimal Internet Key Exchange Version 2 (IKEv2) Initiator ImplementationCurrent
March 2016
- RFC 7824Privacy Considerations for DHCPv6Current
May 2016
- RFC 7830The EDNS(0) Padding OptionCurrent
May 2016
- RFC 7839Access-Network-Identifier Option in DHCPCurrent
June 2016
- RFC 7843Port Control Protocol (PCP) Third-Party ID OptionCurrent
May 2016
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?