RFC 8213: Security of Messages Exchanged between Servers and Relay Agents
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8213
- Published
- August 2017
- Authors
- B. Volz; Y. Pal
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 8
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8222Selecting Labels for Use with Conventional DNS and Other Resolution Systems in DNS-Based Service DiscoveryCurrent
September 2017
- RFC 8201Path MTU Discovery for IP version 6Current
July 2017
- RFC 8200Internet Protocol, Version 6 (IPv6) SpecificationUpdated
July 2017
- RFC 8191Home Network Prefix Renumbering in Proxy Mobile IPv6 (PMIPv6)Current
August 2017
- RFC 8180Minimal IPv6 over the TSCH Mode of IEEE 802.15.4e (6TiSCH) ConfigurationCurrent
May 2017
- RFC 8173Precision Time Protocol Version 2 (PTPv2) Management Information BaseCurrent
June 2017
- RFC 8168DHCPv6 Prefix-Length Hint IssuesCurrent
May 2017
- RFC 8163Transmission of IPv6 over Master-Slave/Token-Passing (MS/TP) NetworksCurrent
May 2017
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?