RFC 6925: The DHCPv4 Relay Agent Identifier Sub-Option
In plain English — editorial summary, not part of the RFC
This document defines a new Relay Agent Identifier sub-option for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Information option. The sub-option carries a value that uniquely identifies the relay agent device within the administrative domain. The value is normally administratively configured in the relay agent. The sub-option allows a DHCP relay agent to include the identifier in the DHCP messages it sends.
Document record
- Document ID
- RFC6925
- Published
- April 2013
- Authors
- B. Joshi; R. Desetti; M. Stapp
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6704Forcerenew Nonce AuthenticationCurrent
August 2012
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 6418Multiple Interfaces and Provisioning Domains Problem StatementCurrent
November 2011
- RFC 7653DHCPv6 Active LeasequeryCurrent
October 2015
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 8415Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Obsoleted
November 2018
- RFC 5071Dynamic Host Configuration Protocol Options Used by PXELINUXCurrent
December 2007
- RFC 8801Discovering Provisioning Domain Names and DataCurrent
July 2020
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?