6977
PROPOSED STANDARD
Triggering DHCPv6 Reconfiguration from Relay Agents
Authors: M. Boucadair, X. Pougnard
Date: July 2013
Area: int
Working Group: dhc
Stream: IETF
Abstract
This document defines two new DHCPv6 messages: Reconfigure-Request and Reconfigure-Reply. The Reconfigure-Request message is sent by a DHCPv6 relay agent to notify a DHCPv6 server about a configuration information change, so that the DHCPv6 server can send a Reconfigure message accordingly. The Reconfigure-Reply message is used by the server to acknowledge the receipt of the Reconfigure-Request message.
RFC 6977
PROPOSED STANDARD
Internet Engineering Task Force (IETF) M. Boucadair
Request for Comments: 6977 X. Pougnard
Category: Standards Track France Telecom
ISSN: 2070-1721 July 2013
<span class="h1">Triggering DHCPv6 Reconfiguration from Relay Agents</span>
Abstract
This document defines two new DHCPv6 messages: Reconfigure-Request
and Reconfigure-Reply. The Reconfigure-Request message is sent by a
DHCPv6 relay agent to notify a DHCPv6 server about a configuration
information change, so that the DHCPv6 server can send a Reconfigure
message accordingly. The Reconfigure-Reply message is used by the
server to acknowledge the receipt of the Reconfigure-Request message.
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 <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc6977">http://www.rfc-editor.org/info/rfc6977</a>.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
<span class="grey">Boucadair & Pougnard Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc6977">RFC 6977</a> DHCPv6 Relay-Triggered Reconfiguration July 2013</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Requirements Language . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. Problem Statement . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4">4</a>. Solution Overview . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-5">5</a>. Link Address Option . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-6">6</a>. Detailed Specification . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-6.1">6.1</a>. Messages Format . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-6.2">6.2</a>. Messages Validation . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-6.2.1">6.2.1</a>. Reconfigure-Request . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-6.2.2">6.2.2</a>. Reconfigure-Reply . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-6.3">6.3</a>. Creation and Transmission of a Reconfigure-Request . . . <a href="#page-7">7</a>
<a href="#section-6.4">6.4</a>. Intermediate Relay Agents Behavior . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-6.5">6.5</a>. Server Behavior . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-6.6">6.6</a>. Receipt of a Reconfigure-Reply . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-7">7</a>. Rate-Limiting Considerations . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-8">8</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-9">9</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-10">10</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-11">11</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-11.1">11.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-11.2">11.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document specifies two new DHCPv6 messages [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>]:
Reconfigure-Request and Reconfigure-Reply.
<a href="#section-3">Section 3</a> describes a typical problem scenario encountered that
triggers the DHCPv6 server to issue a Reconfigure message when the
configuration data is supplied by the relay agent. This problem may
be encountered in other contexts. It is out of scope of this
document to list all these cases.
<a href="#section-4">Section 4</a> describes the proposed solution that relies on the use of
Reconfigure-Request and Reconfigure-Reply messages. The Reconfigure-
Request message is sent by a DHCPv6 relay agent to notify a DHCPv6
server about a configuration-information change, so that the DHCPv6
server can send a Reconfigure message accordingly. The Reconfigure-
Reply message is used by the server to acknowledge the receipt of
Reconfigure-Request.
<a href="#section-5">Section 5</a> specifies the Link Address Option used by the relay agent
to indicate the link on which the client is located to the server.
<a href="#section-6">Section 6</a> provides the detailed specification of the procedure to
trigger Reconfigure messages by DHCPv6 relay agents.
<span class="grey">Boucadair & Pougnard Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc6977">RFC 6977</a> DHCPv6 Relay-Triggered Reconfiguration July 2013</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements Language</span>
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 [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Problem Statement</span>
For cases where the DHCPv6 relay agent possesses some information
that would be useful to the DHCPv6 client, [<a href="./rfc6422" title=""Relay-Supplied DHCP Options"">RFC6422</a>] specifies 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 is achieved by use of RSOO (Relay-Supplied
Options option), which carries configuration data to the DHCPv6
server. The data conveyed in an RSOO is then sent back by the DHCPv6
server to the requesting DHCPv6 client.
An example of RSOO usage is shown in Figure 1; only a subset of
exchanged DHCPv6 and RADIUS messages is represented. Figure 1 shows
a broadband network scenario in which the Network Access Server (NAS)
embeds a DHCPv6 relay agent.
+-------+ +-------+ +-------+
|DHCPv6 | | NAS | |Radius |
|Client | |(DHCPv6| |Server |
| | | Relay)| | |
+-------+ +-------+ +-------+
| | |
|---Solicit---------------->| |
| |---Access-Request---------->|
|<--Access-Accept------------|
| (e.g., DS-Lite-Tunnel-Name)|
....
| +-------+
| |DHCPv6 |
| |Server |
| | |
| +-------+
| |
|---Relay-Forward----------->|
| (RSOO(OPTION_AFTR_NAME)) |
| |
| |<--Relay-Reply--------------|
|<--Advertise---------------| (e.g., OPTION_AFTR_NAME) |
| (e.g., OPTION_AFTR_NAME) |
....
Figure 1: An Example of the RSOO Usage
<span class="grey">Boucadair & Pougnard Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc6977">RFC 6977</a> DHCPv6 Relay-Triggered Reconfiguration July 2013</span>
A configuration change may result in an exchange of CoA (Change-of-
Authorization) [<a href="./rfc5176" title=""Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)"">RFC5176</a>] messages between the NAS/DHCPv6 relay agent
and Dynamic Authorization Client (DAC) server as shown in Figure 2.
In this example, the NAS answers with a CoA-Ack message to notify the
DAC that the CoA-Request has been successfully handled.
Note that the change of the configuration in the DHCPv6 relay agent
can be triggered by any other out-of-band mechanism.
+-------+ +-------+ +-------+
|DHCPv6 | | NAS | |Radius |
|Client | |(DHCPv6| |Server/|
| | | Relay)| | DAC |
+-------+ +-------+ +-------+
| | |
|<-----CoA-Request-----------|
|(e.g., DS-Lite-Tunnel-Name) |
|------CoA-Ack-------------->|
....
Figure 2: Change of Configuration
Whenever the configuration information sent by the DHCPv6 relay agent
to the DHCPv6 server changes, the DHCPv6 server has no means of
detecting the change so that it can send a Reconfigure message
accordingly. A solution is sketched in <a href="#section-4">Section 4</a>.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Solution Overview</span>
To solve the problem described in <a href="#section-3">Section 3</a>, this document proposes a
new DHCP message called Reconfigure-Request. In the example depicted
in Figure 3, a Reconfigure-Request message is sent by the DHCPv6
relay agent to a DHCPv6 server as soon as the configuration data
conveyed in an RSOO has changed. Upon receipt of this message, and
if it is configured to support such a mode, the DHCPv6 server must
build Reconfigure-Reply and Reconfigure messages. Reconfigure-Reply
is used to acknowledge the receipt of Reconfigure-Request. The
Reconfigure message encapsulated in Relay-Reply is sent to the DHCPv6
relay, which in turn will forward the message to the appropriate
DHCPv6 client.
This setup assumes the relay has a record of the client, so that it
has enough information to send the Reconfigure-Request message to the
server. How the state is recorded in the relay is out of scope of
this document. For better resilience of the proposed solution, means
to recover state in the event of failure (e.g., use of stable
storage, DHCPv6 Bulk Leasequery [<a href="./rfc5460" title=""DHCPv6 Bulk Leasequery"">RFC5460</a>]) need to be supported.
These state recovery solutions are not discussed in this document.
<span class="grey">Boucadair & Pougnard Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc6977">RFC 6977</a> DHCPv6 Relay-Triggered Reconfiguration July 2013</span>
+-------+ +-------+ +-------+
|DHCPv6 | | NAS | |Radius |
|Client | |(DHCPv6| |Server/|
| | | Relay)| | DAC |
+-------+ +-------+ +-------+
| | |
|<-----CoA-Request-----------|
|(e.g., DS-Lite-Tunnel-Name) |
| |
|------CoA-Ack-------------->|
....
| +-------+
| |DHCPv6 |
| |Server |
| | |
| +-------+
| |
|---Reconfigure-Request----->|
|<--Reconfigure-Reply--------|
| |
| |<--Relay-Reply -------------|
|<--Reconfigure-------------| (Reconfigure) |
| | |
....
Figure 3: Flow Example with Reconfigure-Request
The support of Reconfigure-Reply messages simplifies the
retransmission procedure of the relay as it provides an explicit
indication from the server (see <a href="#section-6.3">Section 6.3</a> for more details). An
alternative approach is the relay monitors' Reconfigure messages
received from the server to conclude whether or not the Reconfigure-
Request was successfully handled. Nevertheless, this implicit
approach may fail to achieve its goals in some cases: for example,
the server accepts the request but it delays generating the
corresponding Reconfigure messages due to its rate-limiting policies,
the request was partially failed for some clients, etc. To avoid
useless reconfigure cycles (e.g., due to the loss of Reconfigure-
Reply messages), the approach adopted in this document allows the
relay to correct the content of a retransmitted Reconfigure-Request
based on some observed events (e.g., the client has retrieved the
updated configuration). If the relay has no client to be
reconfigured, it stops sending Reconfigure-Request messages.
The Reconfigure-Request message can also be used in scenarios other
than those that assume the use of RSOO. It is out of scope of this
document to describe all these scenarios.
<span class="grey">Boucadair & Pougnard Standards Track [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc6977">RFC 6977</a> DHCPv6 Relay-Triggered Reconfiguration July 2013</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Link Address Option</span>
Figure 4 shows the format of the Link Address Option.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_LINK_ADDRESS | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| link-address (IPv6 address) |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Message Format of Link Address Option
The description of the fields are as follows:
option-code: OPTION_LINK_ADDRESS (80)
option-len: 16 (octets)
link-address: An IPv6 address used by the server to identify the
link on which the client is located.
The Link Address Option is used by the relay agent to indicate to the
server the link on which the client is located. The relay agent MUST
use a link-address value that is equivalent to the value used when
relaying messages from the client to the server. Two link-address
values are said to be equivalent if both values are IPv6 addresses
that are on-link for the network link to which the client is
connected.
To defend against poor implementations that do not correctly evaluate
equivalence, the relay agent SHOULD use the same value that was sent
to the DHCPv6 server when relaying messages from the client to the
server, as in <a href="./rfc3315#section-20.1.1">Section 20.1.1 of [RFC3315]</a>.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Detailed Specification</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Messages Format</span>
Two new message type codes are defined:
o RECONFIGURE-REQUEST (18)
o RECONFIGURE-REPLY (19)
<span class="grey">Boucadair & Pougnard Standards Track [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc6977">RFC 6977</a> DHCPv6 Relay-Triggered Reconfiguration July 2013</span>
Reconfigure-Request and Reconfigure-Reply use the same format as
defined in <a href="./rfc3315#section-6">Section 6 of [RFC3315]</a>.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Messages Validation</span>
<span class="h4"><a class="selflink" id="section-6.2.1" href="#section-6.2.1">6.2.1</a>. Reconfigure-Request</span>
Clients MUST silently discard any received Reconfigure-Request
messages.
Servers MUST discard any received Reconfigure-Request messages that
meet any of the following conditions:
o the message does not include a Client Identifier Option [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>].
o the message does not include a Link Address Option (<a href="#section-5">Section 5</a>).
o the message includes a Server Identifier Option [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>] but the
contents of the Server Identifier Option do not match the server's
identifier.
<span class="h4"><a class="selflink" id="section-6.2.2" href="#section-6.2.2">6.2.2</a>. Reconfigure-Reply</span>
Clients and servers MUST silently discard any received Reconfigure-
Reply messages.
The relay MUST silently discard any received Reconfigure-Reply
messages that meet any of the following conditions:
o the "transaction-id" field in the message does not match the value
used in the original message.
o the message does not include a Server Identifier Option.
o the message does not include a Status Code Option [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>].
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Creation and Transmission of a Reconfigure-Request</span>
For any event (e.g., modification of the configuration information)
that requires the server to issue a Reconfigure message, the relay
agent determines the client(s) affected by the change and then builds
a Reconfigure-Request message: the relay agent sets the "msg-type"
field to RECONFIGURE-REQUEST, generates a transaction ID, and inserts
it in the "transaction-id" field.
The relay agent MUST include one or more Client Identifier Options
[<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>] and a Link Address Option (<a href="#section-5">Section 5</a>) so that the DHCPv6
<span class="grey">Boucadair & Pougnard Standards Track [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc6977">RFC 6977</a> DHCPv6 Relay-Triggered Reconfiguration July 2013</span>
server can identify the corresponding client and the link on which
the client is located.
The relay agent MAY include a Relay Identifier Option [<a href="./rfc5460" title=""DHCPv6 Bulk Leasequery"">RFC5460</a>].
The relay agent MAY supply the updated configuration in the RSOO
[<a href="./rfc6422" title=""Relay-Supplied DHCP Options"">RFC6422</a>]. The relay agent MAY supply a Reconfigure Message Option
to indicate which form of Reconfigure to use. The relay agent MAY
include any option (e.g., Interface Identifier [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>]) that it
might insert when relaying a message received from a client.
When several clients on the same link are affected by a configuration
change, the relay MUST include several Client Identifier Options;
each of these options identifies a specific client. If including the
Client Identifier Options of all impacted clients exceeds the maximum
message size (see <a href="#section-7">Section 7</a>), the relay MUST generate several
Reconfigure-Request messages required to carry all Client Identifier
Options. Rate-limit considerations are discussed in <a href="#section-7">Section 7</a>.
The relay sets the destination address of the Reconfigure-Request
message to the IP address it would have sent a Relay-Forward message
(see <a href="./rfc3315#section-20">Section 20 of [RFC3315]</a>).
In case multiple servers are configured to the relay agent, several
Reconfigure-Request messages are to be built. The behavior of the
relay agent to disambiguate responses when multiple servers are
configured is implementation specific. For example, an
implementation may generate a distinct "transaction-id" per server
while another implementation may use the content of the "transaction-
id" field and the Server Identifier Option to disambiguate the
responses.
The relay transmits Reconfigure-Request messages according to
<a href="./rfc3315#section-14">Section 14 of [RFC3315]</a>, using the following parameters:
IRT (Initial retransmission time): 1 sec
MRT (Maximum retransmission time): 10 secs
MRC (Maximum retransmission count): 5
MRD (Maximum retransmission duration): 0
The relay MAY remove clients from the client identifier list in
subsequent retransmissions, but MUST NOT add clients to the client
identifier list. This decision is local to the relay (e.g., it may
be based on observed events such as one or more clients were
reconfigured on their own).
The relay may receive Reconfigure encapsulated in Relay-Reply before
Reconfigure-Reply. The relay SHOULD NOT interpret it as if the
<span class="grey">Boucadair & Pougnard Standards Track [Page 8]</span><span id="page-9" ></span>
<span class="grey"><a href="./rfc6977">RFC 6977</a> DHCPv6 Relay-Triggered Reconfiguration July 2013</span>
Reconfigure-Request was successfully handled by the server. The
relay SHOULD use Reconfigure-Reply, not the Reconfigure message, to
determine if the request was successful (see the discussion in
<a href="#section-4">Section 4</a>).
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Intermediate Relay Agents Behavior</span>
The relay agent MUST be configurable to accept or reject Reconfigure-
Request messages received from other relay agents. If no indication
is explicitly configured to the relay, the default behavior is to
accept Reconfigure-Request messages.
If the relay is configured not to allow Reconfigure-Request messages,
the relay MUST silently discard any Reconfigure-Request message it
receives. If the relay is configured to accept Reconfigure-Request
messages, these messages are relayed as specified in <a href="./rfc3315#section-20.1.1">Section 20.1.1
of [RFC3315]</a>.
<span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. Server Behavior</span>
The server MUST be configurable to accept or reject Reconfigure-
Request messages. If no indication is explicitly configured to the
server, the default behavior is to reject Reconfigure-Request
messages.
Upon receipt of a valid Reconfigure-Request message from a DHCPv6
relay agent (see <a href="#section-6.2">Section 6.2</a>), the server determines the client(s)
for which a Reconfigure message is to be sent.
The server constructs a Reconfigure-Reply message by setting the
"msg-type" field to RECONFIGURE-REPLY and copying the transaction ID
from the Reconfigure-Request message into the "transaction-id" field.
The server includes its server identifier in a Server Identifier
Option. The server MUST include a Status Code Option [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>]
indicating whether the request has been successfully processed,
failed, or partially failed.
o If the server fails to process the request, the server MUST set
the Status Code Option to the appropriate status code (e.g.,
UnspecFail, NotAllowed, etc.). In particular,
* UnspecFail MUST be returned if the Reconfigure-Request message
is malformed.
* NotAllowed MUST be returned if the server is not configured to
allow Reconfigure-Request.
<span class="grey">Boucadair & Pougnard Standards Track [Page 9]</span><span id="page-10" ></span>
<span class="grey"><a href="./rfc6977">RFC 6977</a> DHCPv6 Relay-Triggered Reconfiguration July 2013</span>
* NotConfigured MUST be returned if the server has no record of
the link [<a href="./rfc5007" title=""DHCPv6 Leasequery"">RFC5007</a>].
o If the Reconfigure-Request is successfully validated, the server
MUST return a Status Code Option indicating "Success". In
addition, the server MUST include a list of all the Client
Identifier Options of the clients to which Reconfigure messages
will not be sent (e.g., the server has no record of the client or
the client did not negotiate for Reconfigure support). Note that
this means that "Success" will be returned even if Reconfigure
messages will not be sent to any of the clients.
If RSOO is supplied, the server might use its content to double check
whether a Reconfigure is required to be sent to the client. This
assumes the server stored the content of RSOO it used to generate the
configuration data sent to requesting clients.
The server might use the content of the Reconfigure Message Option
supplied by the relay agent to determine which form of Reconfigure to
use.
Then, the server MUST follow the procedure defined in <a href="./rfc3315#section-19.1">Section 19.1 of
[RFC3315]</a> to construct a Reconfigure message.
Rate-limit considerations are discussed in <a href="#section-7">Section 7</a>.
<span class="h3"><a class="selflink" id="section-6.6" href="#section-6.6">6.6</a>. Receipt of a Reconfigure-Reply</span>
Depending on the status code enclosed in a received Reconfigure-Reply
message, the relay may decide to terminate the request (e.g.,
NotAllowed, NotConfigured, and Success) or try a different corrected
Reconfigure-Request (e.g., UnspecFail).
When multiple servers are configured, the relay should expect to
receive several Reconfigure-Reply messages. As mentioned in
<a href="#section-6.3">Section 6.3</a>, the relay should be able to disambiguate these responses
and associate them with a given server. The relay agent assumes the
request is successfully handled for a client if there is at least one
Reconfigure-Reply message in which the corresponding Client
Identifier Option does not appear.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Rate-Limiting Considerations</span>
The relay MUST rate-limit Reconfigure-Request messages to be sent to
the server. The relay MUST be configured with required rate-limit
parameters. The maximum Reconfigure-Request packet size SHOULD be
configurable and the default value MUST be 1280 octets.
<span class="grey">Boucadair & Pougnard Standards Track [Page 10]</span><span id="page-11" ></span>
<span class="grey"><a href="./rfc6977">RFC 6977</a> DHCPv6 Relay-Triggered Reconfiguration July 2013</span>
The server MUST rate-limit Reconfigure messages triggered by
Reconfigure-Request messages. The server MUST be configured with
required rate-limit parameters.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
IANA has assigned the following new DHCPv6 Message types in the
registry maintained in
<a href="http://www.iana">http://www.iana</a>.org/assignments/dhcpv6-parameters:
RECONFIGURE-REQUEST
RECONFIGURE-REPLY
IANA has assigned the following new DHCPv6 Option Codes in the
registry maintained in
<a href="http://www.iana">http://www.iana</a>.org/assignments/dhcpv6-parameters:
OPTION_LINK_ADDRESS
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span>
Security considerations elaborated in [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>] (in particular
<a href="#section-21.1">Section 21.1</a>) and [<a href="./rfc6422" title=""Relay-Supplied DHCP Options"">RFC6422</a>] must be taken into account. In addition,
DHCPv6 servers MAY be configured to reject relayed Reconfigure-
Request messages or restrict relay chaining (see [<a href="./rfc5007" title=""DHCPv6 Leasequery"">RFC5007</a>] for more
discussion about the rationale of this recommended behavior).
<a href="#section-6.5">Section 6.5</a> specifies the error code to return when the server is
configured to reject Reconfigure-Request messages.
Relay agents SHOULD implement appropriate means to prevent using
Reconfigure-Request messages as a denial-of-service attack on the
DHCPv6 servers.
Because the Reconfigure-Request message provides a mechanism for
triggering the DHCPv6 Reconfigure message, and the DHCPv6 Reconfigure
message can raise security threats (e.g., to control the timing of a
DHCPv6 renewal), the DHCPv6 server MUST have some mechanism for
determining that the relay agent is a trusted entity. DHCPv6 servers
and relay agents MUST implement relay message authentication as
described in <a href="./rfc3315#section-21.1">Section 21.1 of [RFC3315]</a>. DHCPv6 servers MAY also
implement a control policy based on the content of a received Relay
Identifier Option [<a href="./rfc5460" title=""DHCPv6 Bulk Leasequery"">RFC5460</a>]. Administrators are strongly advised to
configure one of these security mechanisms.
In an environment where the network connecting the relay agent to the
DHCPv6 server is physically secure and does not contain devices not
controlled by the server administrator, it may be sufficient to trust
<span class="grey">Boucadair & Pougnard Standards Track [Page 11]</span><span id="page-12" ></span>
<span class="grey"><a href="./rfc6977">RFC 6977</a> DHCPv6 Relay-Triggered Reconfiguration July 2013</span>
the Relay Agent Identifier provided by the relay agent. In networks
where the security of the machines with access to the data path is
not under the control of the server administrator, IPsec [<a href="./rfc4301" title=""Security Architecture for the Internet Protocol"">RFC4301</a>] is
necessary to prevent spoofing of Reconfigure-Request messages.
DHCPv6 servers MUST silently discard Reconfigure-Request messages
originating from unknown relay agents.
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgements</span>
Many thanks to R. Maglione, A. Kostur, G. Halwasia, C. Jacquenet, B.
Leiba, R. Sparks, A. Farrel, B. Claise, J. Jaeggli, and P. Resnick
for the comments and review.
Special thanks to T. Lemon, B. Volz, and T. Mrugalski who provided a
detailed review.
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC3315">RFC3315</a>] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", <a href="./rfc3315">RFC 3315</a>, July 2003.
[<a id="ref-RFC6422">RFC6422</a>] Lemon, T. and Q. Wu, "Relay-Supplied DHCP Options", <a href="./rfc6422">RFC</a>
<a href="./rfc6422">6422</a>, December 2011.
<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Informative References</span>
[<a id="ref-RFC4301">RFC4301</a>] Kent, S. and K. Seo, "Security Architecture for the
Internet Protocol", <a href="./rfc4301">RFC 4301</a>, December 2005.
[<a id="ref-RFC5007">RFC5007</a>] Brzozowski, J., Kinnear, K., Volz, B., and S. Zeng,
"DHCPv6 Leasequery", <a href="./rfc5007">RFC 5007</a>, September 2007.
[<a id="ref-RFC5176">RFC5176</a>] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B.
Aboba, "Dynamic Authorization Extensions to Remote
Authentication Dial In User Service (RADIUS)", <a href="./rfc5176">RFC 5176</a>,
January 2008.
[<a id="ref-RFC5460">RFC5460</a>] Stapp, M., "DHCPv6 Bulk Leasequery", <a href="./rfc5460">RFC 5460</a>, February
2009.
<span class="grey">Boucadair & Pougnard Standards Track [Page 12]</span><span id="page-13" ></span>
<span class="grey"><a href="./rfc6977">RFC 6977</a> DHCPv6 Relay-Triggered Reconfiguration July 2013</span>
Authors' Addresses
Mohamed Boucadair
France Telecom
Rennes 35000
France
EMail: [email protected]
Xavier Pougnard
France Telecom
Lannion
France
EMail: [email protected]
Boucadair & Pougnard Standards Track [Page 13]
Annotations
Select text to annotate