RFC 5010: The Dynamic Host Configuration Protocol Version 4 (DHCPv4) Relay Agent Flags Suboption
In plain English — editorial summary, not part of the RFC
This memo defines a new suboption of the Dynamic Host Configuration Protocol (DHCP) relay agent information option that allows the DHCP relay to specify flags for the forwarded packet. One flag is defined to indicate whether the DHCP relay received the packet via a unicast or broadcast packet. This information may be used by the DHCP server to better serve clients based on whether their request was originally broadcast or unicast. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5010
- Published
- September 2007
- Authors
- K. Kinnear; M. Normoyle; M. Stapp
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5011Automated Updates of DNS Security (DNSSEC) Trust AnchorsCurrent
September 2007
- RFC 5007DHCPv6 LeasequeryCurrent
September 2007
- RFC 5001DNS Name Server Identifier (NSID) OptionCurrent
August 2007
- RFC 5026Mobile IPv6 Bootstrapping in Split ScenarioUpdated
October 2007
- RFC 4994DHCPv6 Relay Agent Echo Request OptionCurrent
September 2007
- RFC 5030Mobile IPv4 RADIUS RequirementsCurrent
October 2007
- RFC 4988Mobile IPv4 Fast HandoversCurrent
October 2007
- RFC 4986Requirements Related to DNS Security (DNSSEC) Trust Anchor RolloverCurrent
August 2007
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?