Handling Unknown DHCPv6 Messages
RFC 7283
| Document | Type |
RFC - Proposed Standard
(July 2014; No errata)
Obsoleted by RFC 8415
Updates RFC 3315
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaces | draft-csl-dhc-dhcpv6-unknown-msg-3315update | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Sheng Jiang | ||
| Shepherd write-up | Show (last changed 2014-01-07) | ||
| IESG | IESG state | RFC 7283 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Brian Haberman | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | No IANA Actions | ||
Internet Engineering Task Force (IETF) Y. Cui
Request for Comments: 7283 Q. Sun
Updates: 3315 Tsinghua University
Category: Standards Track T. Lemon
ISSN: 2070-1721 Nominum, Inc.
July 2014
Handling Unknown DHCPv6 Messages
Abstract
DHCPv6 is not specific about handling messages with unknown types.
This memo describes the problems associated with receiving DHCPv6
messages with unknown types, and defines how a DHCPv6 server, client,
or relay agent should behave when receiving unknown DHCPv6 messages.
This document also provides advice for authors of future documents
that define new messages to be sent from DHCP servers to DHCP relay
agents. This document updates RFC 3315.
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/rfc7283.
Cui, et al. Standards Track [Page 1]
RFC 7283 Handling Unknown DHCPv6 Messages July 2014
Copyright Notice
Copyright (c) 2014 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.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 3
4. Relay Agent Behavior Update . . . . . . . . . . . . . . . . . 3
4.1. A Valid Message for Constructing a New Relay-forward
Message . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.2. Relaying a Message toward the Server . . . . . . . . . . 5
4.3. Relaying a Message toward the Client . . . . . . . . . . 5
5. Client and Server Behavior Update . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6
8. Normative References . . . . . . . . . . . . . . . . . . . . 6
Cui, et al. Standards Track [Page 2]
RFC 7283 Handling Unknown DHCPv6 Messages July 2014
1. Introduction
DHCPv6 [RFC3315] provides a framework for conveying IPv6
configuration information to hosts on a TCP/IP network. But
[RFC3315] is not specific about how to deal with messages with
unrecognized types. This document describes the problems associated
with receiving DHCPv6 messages with unknown types, and defines the
behavior of a DHCPv6 server, client, or relay agent when handling
unknown DHCPv6 messages.
2. 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 [RFC2119].
3. Problem Statement
When a relay agent receives a message, it sends the message toward
either the server or the client. The relay agent decides on the
Show full document text