RFC 7037: RADIUS Option for the DHCPv6 Relay Agent
In plain English — editorial summary, not part of the RFC
The DHCPv6 RADIUS option provides a mechanism to exchange authorization and identification information between the DHCPv6 relay agent and DHCPv6 server. This architecture assumes that the Network Access Server (NAS) acts as both a DHCPv6 relay agent and RADIUS client. When receiving messages from the DHCPv6 clients, the NAS consults the RADIUS server and adds the RADIUS response when forwarding the DHCPv6 client's messages to the DHCPv6 server. The DHCPv6 server then uses that additional information to generate an appropriate response to the DHCPv6 client's requests.
Document record
- Document ID
- RFC7037
- Published
- October 2013
- Authors
- L. Yeh; M. Boucadair
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7031DHCPv6 Failover RequirementsCurrent
September 2013
- RFC 6853DHCPv6 Redundancy Deployment ConsiderationsCurrent
February 2013
- RFC 7227Guidelines for Creating New DHCPv6 OptionsCurrent
May 2014
- RFC 7283Handling Unknown DHCPv6 MessagesObsoleted
July 2014
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 7598DHCPv6 Options for Configuration of Softwire Address and Port-Mapped ClientsUpdated
July 2015
- RFC 7653DHCPv6 Active LeasequeryCurrent
October 2015
- RFC 7839Access-Network-Identifier Option in DHCPCurrent
June 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?