draft-ietf-dhc-dhcpv6-solmaxrt-update-03.txt   draft-ietf-dhc-dhcpv6-solmaxrt-update-04.txt 
dhc R. Droms dhc R. Droms
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Updates: 3315 (if approved) August 20, 2013 Updates: 3315 (if approved) September 13, 2013
Intended status: Standards Track Intended status: Standards Track
Expires: February 21, 2014 Expires: March 17, 2014
Modification to Default Values of SOL_MAX_RT and INF_MAX_RT Modification to Default Values of SOL_MAX_RT and INF_MAX_RT
draft-ietf-dhc-dhcpv6-solmaxrt-update-03 draft-ietf-dhc-dhcpv6-solmaxrt-update-04
Abstract Abstract
This document updates RFC 3315 by redefining the default values for This document updates RFC 3315 by redefining the default values for
SOL_MAX_RT and INF_MAX_RT, and defining options through which a SOL_MAX_RT and INF_MAX_RT, and defining options through which a
DHCPv6 server can override the client's default value for SOL_MAX_RT DHCPv6 server can override the client's default value for SOL_MAX_RT
and INF_MAX_RT with a new value. and INF_MAX_RT with new values.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 21, 2014. This Internet-Draft will expire on March 17, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2
3. Updates to SOL_MAX_RT and INF_MAX_RT in RFC 3315 . . . . . . 2
4. SOL_MAX_RT option . . . . . . . . . . . . . . . . . . . . . . 3
5. INF_MAX_RT option . . . . . . . . . . . . . . . . . . . . . . 4
6. Updates for SOL_MAX_RT and INF_MAX_RT options to RFC 3315 . . 5
7. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . . . 6
8. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . 6
9. DHCPv6 Relay Agent Behavior Text . . . . . . . . . . . . . . 7
10. Security Considerations . . . . . . . . . . . . . . . . . . . 7
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
13.1. Normative References . . . . . . . . . . . . . . . . . . 8
13.2. Informative References . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
Section 5.5 of the DHCPv6 specification [RFC3315] defines the default Section 5.5 of the DHCPv6 specification [RFC3315] defines the default
values of SOL_MAX_RT and INF_MAX_RT to be 120 seconds. In some values of SOL_MAX_RT and INF_MAX_RT to be 120 seconds. In some
circumstances, these defaults will lead to an unacceptably high circumstances, these defaults will lead to an unacceptably high
volume of aggregated traffic at a DHCPv6 server. volume of aggregated traffic at a DHCPv6 server.
The change to SOL_MAX_RT is in response to DHCPv6 message rates The change to SOL_MAX_RT is in response to DHCPv6 message rates
observed at a DHCPv6 server in a deployment in which many DHCPv6 observed at a DHCPv6 server in a deployment in which many DHCPv6
clients are sending Solicit messages but the DHCPv6 server has been clients are sending Solicit messages but the DHCPv6 server has been
skipping to change at page 3, line 32 skipping to change at page 4, line 21
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code OPTION_SOL_MAX_RT (TBD). option-code OPTION_SOL_MAX_RT (TBD).
option-len 4. option-len 4.
SOL_MAX_RT value Overriding value for SOL_MAX_RT SOL_MAX_RT value Overriding value for SOL_MAX_RT
in seconds; MUST be in range: in seconds; MUST be in range:
60 <= "value" <= 86400 (1 day) 60 <= "value" <= 86400 (1 day)
Figure 1 Figure 1: SOL_MAX_RT option format
5. INF_MAX_RT option 5. INF_MAX_RT option
A DHCPv6 server sends the INF_MAX_RT option to a client to override A DHCPv6 server sends the INF_MAX_RT option to a client to override
the default value of INF_MAX_RT. The value of INF_MAX_RT in the the default value of INF_MAX_RT. The value of INF_MAX_RT in the
option replaces the default value defined in Section 3. One use for option replaces the default value defined in Section 3. One use for
the INF_MAX_RT option is to set a longer value for INF_MAX_RT, which the INF_MAX_RT option is to set a longer value for INF_MAX_RT, which
reduces the Information-Request traffic from a client that has not reduces the Information-Request traffic from a client that has not
received a response to its Information-Request messages. received a response to its Information-Request messages.
skipping to change at page 4, line 33 skipping to change at page 5, line 22
The client MUST ignore any Advertise message that includes a Status The client MUST ignore any Advertise message that includes a Status
Code option containing the value NoAddrsAvail, with the exception Code option containing the value NoAddrsAvail, with the exception
that the client MAY display the associated status message to the that the client MAY display the associated status message to the
user. user.
NEW: NEW:
The client MUST ignore any Advertise message that includes a Status The client MUST ignore any Advertise message that includes a Status
Code option containing the value NoAddrsAvail, with the exception Code option containing the value NoAddrsAvail, with the exception
that the client MUST process an included SOL_MAX_RT option and/or an that the client MUST process an included SOL_MAX_RT option and MUST
included INF_MAX_RT option and MAY display the associated status process an included INF_MAX_RT option and MAY display the associated
message to the user. status message to the user.
Update to RFC 3315 [RFC3315], section 17.2.2: Update to RFC 3315 [RFC3315], section 17.2.2:
OLD: OLD:
If the server will not assign any addresses to any IAs in a If the server will not assign any addresses to any IAs in a
subsequent Request from the client, the server MUST send an subsequent Request from the client, the server MUST send an
Advertise message to the client that includes only a Status Code Advertise message to the client that includes only a Status Code
option with code NoAddrsAvail and a status message for the user, a option with code NoAddrsAvail and a status message for the user, a
Server Identifier option with the server's DUID, and a Client Server Identifier option with the server's DUID, and a Client
skipping to change at page 5, line 31 skipping to change at page 6, line 17
waiting for a response from a server: waiting for a response from a server:
NEW: NEW:
A client is not expected to listen for a response during the entire A client is not expected to listen for a response during the entire
period between transmission of Solicit or Information-Request period between transmission of Solicit or Information-Request
messages. messages.
7. DHCPv6 Client Behavior 7. DHCPv6 Client Behavior
A DHCPv6 client MUST include the SOL_MAX_RT option code in an Option A DHCPv6 client MUST include the SOL_MAX_RT option code in any Option
Request option [RFC3315] in any message it sends. Request option [RFC3315] it sends as required by RC 3315.
A DHCPv6 client MUST include the INF_MAX_RT option code in an Option A DHCPv6 client MUST include the INF_MAX_RT option code in any Option
Request option [RFC3315] in any message it sends. Request option [RFC3315] it sends as required by RFC 3315.
a DHCPv6 client MUST silently ignore any SOL_MAX_RT or INF_MAX_RT A DHCPv6 client MUST silently ignore any SOL_MAX_RT or INF_MAX_RT
values that are less than 60 or more than 86400. option values that are less than 60 or more than 86400.
If a DHCPv6 client receives a message containing a SOL_MAX_RT option If a DHCPv6 client receives a message containing a SOL_MAX_RT option
containing a valid value for SOL_MAX_RT, the client MUST set its containing a valid value for SOL_MAX_RT, the client MUST set its
internal SOL_MAX_RT parameter to the value contained in the internal SOL_MAX_RT parameter to the value contained in the
SOL_MAX_RT option. This value of SOL_MAX_RT is then used by the SOL_MAX_RT option. This value of SOL_MAX_RT is then used by the
retransmission mechanism defined in sections 17.1.2 and 14 of RFC retransmission mechanism defined in sections 17.1.2 and 14 of RFC
3315 [RFC3315]. 3315 [RFC3315].
If a DHCPv6 client receives a message containing a INF_MAX_RT option If a DHCPv6 client receives a message containing a INF_MAX_RT option
containing a valid value for INF_MAX_RT, the client MUST set its containing a valid value for INF_MAX_RT, the client MUST set its
skipping to change at page 6, line 43 skipping to change at page 7, line 29
9. DHCPv6 Relay Agent Behavior Text 9. DHCPv6 Relay Agent Behavior Text
There are no additional requirements for relays. There are no additional requirements for relays.
10. Security Considerations 10. Security Considerations
This document introduces one security consideration beyond those This document introduces one security consideration beyond those
described in RFC 3315 [RFC3315]. A malicious DHCPv6 server might described in RFC 3315 [RFC3315]. A malicious DHCPv6 server might
cause a client to set its SOL_MAX_RT and INF_MAX_RT parameters to an cause a client to set its SOL_MAX_RT and INF_MAX_RT parameters to an
arbitrarily high value with the SOL_MAX_RT and INF_MAX_RT options. arbitrarily high value with the SOL_MAX_RT and INF_MAX_RT options,
Assuming the client also receives a response from a valid DHCPv6 which may cause an undue delay in a client completing its DHCPv6
server, large values for SOL_MAX_RT and INF_MAX_RT will not have any protocol transaction in the case no other valid response is
effect. received.. Assuming the client also receives a response from a valid
DHCPv6 server, large values for SOL_MAX_RT and INF_MAX_RT will not
have any effect.
11. Acknowledgments 11. Acknowledgments
Tomek Mrugalski edited the text for compliance with draft-ietf-dhc- Tomek Mrugalski edited the text for compliance with draft-ietf-dhc-
option-guidelines [I-D.ietf-dhc-option-guidelines] and added option-guidelines [I-D.ietf-dhc-option-guidelines] and added
important detail to the Security Considerations section. important details to the Security Considerations section.
12. IANA Considerations 12. IANA Considerations
IANA is requested to assign one option code each for IANA is requested to assign one option code each for
OPTION_SOL_MAX_RT and OPTION_INF_MAX_RT from the "DHCP Option Codes" OPTION_SOL_MAX_RT and OPTION_INF_MAX_RT from the "DHCP Option Codes"
table of the Dynamic Host Configuration Protocol for IPv6 (DHCPv6) table of the Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
Registry. Registry.
13. References 13. References
13.1. Normative References 13.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
13.2. Informative References 13.2. Informative References
 End of changes. 15 change blocks. 
21 lines changed or deleted 42 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/