RFC 4014: Remote Authentication Dial-In User Service (RADIUS) Attributes Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Information Option
In plain English — editorial summary, not part of the RFC
The RADIUS Attributes suboption enables a network element to pass identification and authorization attributes received during RADIUS authentication to a DHCP server. When the DHCP server receives a message from a relay agent containing a RADIUS Attributes suboption, it extracts the contents of the suboption and uses that information in selecting configuration parameters for the client. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4014
- Published
- February 2005
- Authors
- R. Droms; J. Schnizlein
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 8
- Also known as
- —
- Updated by:
- RFC 9445
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4016Protocol for Carrying Authentication and Network Access (PANA) Threat Analysis and Security RequirementsCurrent
March 2005
- RFC 4007IPv6 Scoped Address ArchitectureUpdated
March 2005
- RFC 4022Management Information Base for the Transmission Control Protocol (TCP)Current
March 2005
- RFC 4030The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent OptionCurrent
April 2005
- RFC 4033DNS Security Introduction and RequirementsUpdated
March 2005
- RFC 4034Resource Records for the DNS Security ExtensionsUpdated
March 2005
- RFC 3993Subscriber-ID Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent OptionCurrent
March 2005
- RFC 4035Protocol Modifications for the DNS Security ExtensionsUpdated
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?