RFC 4030: The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option
In plain English — editorial summary, not part of the RFC
The Dynamic Host Configuration Protocol (DHCP) Relay Agent Information Option (RFC 3046) conveys information between a DHCP Relay Agent and a DHCP server. This specification defines an authentication suboption for that option, containing a keyed hash in its payload. The suboption supports data integrity and replay protection for relayed DHCP messages. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4030
- Published
- April 2005
- Authors
- M. Stapp; T. Lemon
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 15
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4033DNS Security Introduction and RequirementsUpdated
March 2005
- RFC 4034Resource Records for the DNS Security ExtensionsUpdated
March 2005
- RFC 4035Protocol Modifications for the DNS Security ExtensionsUpdated
March 2005
- RFC 4022Management Information Base for the Transmission Control Protocol (TCP)Current
March 2005
- RFC 4039Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4)Current
March 2005
- RFC 4016Protocol for Carrying Authentication and Network Access (PANA) Threat Analysis and Security RequirementsCurrent
March 2005
- RFC 4014Remote Authentication Dial-In User Service (RADIUS) Attributes Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Information OptionUpdated
February 2005
- RFC 4007IPv6 Scoped Address ArchitectureUpdated
March 2005
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?