Relay-Supplied DHCP Options
RFC 6422
| Document | Type |
RFC - Proposed Standard
(December 2011; No errata)
Updates RFC 3315
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6422 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Ralph Droms | ||
| IESG note | John Brzozowski <John_Brzozowski@Cable.Comcast.com> is the document shepherd. | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) T. Lemon
Request for Comments: 6422 Nominum
Updates: 3315 Q. Wu
Category: Standards Track Huawei
ISSN: 2070-1721 December 2011
Relay-Supplied DHCP Options
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6422.
Lemon & Wu Standards Track [Page 1]
RFC 6422 Relay-Supplied DHCP Options December 2011
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................2
1.1. Requirements Language ......................................3
1.2. Terminology ................................................3
2. Protocol Summary ................................................3
3. Encoding ........................................................3
4. RSOO-Enabled Options ............................................4
5. DHCP Relay Agent Behavior .......................................4
6. DHCP Server Behavior ............................................5
7. Security Considerations .........................................6
8. IANA Considerations .............................................7
9. References ......................................................7
9.1. Normative References .......................................7
9.2. Informative References .....................................7
1. Introduction
The DHCPv6 specification [RFC3315] allows DHCP relay agents to
forward DHCPv6 messages between clients and servers that are not on
the same IPv6 link. In some cases, the DHCP relay agent has
information not available to the DHCP server that would be useful to
provide to a DHCP client. For example, the DHCP client may need to
learn the EAP Re-authentication Protocol (ERP) local domain name
[RFC6440] for use in EAP re-authentication [RFC5296], which is known
to the relay agent but not the server.
The DHCPv6 protocol specification does not provide a mechanism
whereby the relay agent can provide options to the client. This
document extends DHCP with a mechanism that allows DHCP relay agents
to propose options for the server to send to DHCP clients.
Lemon & Wu Standards Track [Page 2]
RFC 6422 Relay-Supplied DHCP Options December 2011
This document is not intended to provide a general mechanism for
storing client configuration information in the relay agent. Rather,
it is intended to address specific use cases where only the relay
agent has information needed by the client. This extension is not
applicable to DHCP options in general, but rather provided as a
mechanism for new specifications that require this functionality.
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Show full document text