RFC 6422
Relay-Supplied DHCP Options, December 2011
- File formats:
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 3315
- Authors:
- T. Lemon
Q. Wu - Stream:
- IETF
- Source:
- dhc (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6422
Discuss this RFC: Send questions or comments to the mailing list dhcwg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6422
Abstract
DHCPv6 relay agents cannot communicate with DHCPv6 clients directly. However, in some cases, the relay agent possesses some information that would be useful to the DHCPv6 client. This document describes a mechanism whereby the DHCPv6 relay agent can provide such information to the DHCPv6 server, which can, in turn, pass this information on to the DHCP client.
This document updates RFC 3315 (DHCPv6) by making explicit the implicit requirement that relay agents not modify the content of encapsulation payloads as they are relayed back toward clients. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.