draft-ietf-dhc-dhcpv6-solmaxrt-update-01.txt   draft-ietf-dhc-dhcpv6-solmaxrt-update-02.txt 
Network Working Group R. Droms dhc R. Droms
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Updates: 3315 (if approved) June 03, 2013 Updates: 3315 (if approved) July 15, 2013
Intended status: Standards Track Intended status: Standards Track
Expires: December 05, 2013 Expires: January 16, 2014
Modification to Default Value of SOL_MAX_RT Modification to Default Values of SOL_MAX_RT and INF_MAX_RT
draft-ietf-dhc-dhcpv6-solmaxrt-update-01 draft-ietf-dhc-dhcpv6-solmaxrt-update-02
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 a new value.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 December 05, 2013. This Internet-Draft will expire on January 16, 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
skipping to change at page 3, line 29 skipping to change at page 3, line 29
| option-code | option-len | | option-code | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SOL_MAX_RT value | | SOL_MAX_RT value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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. in seconds; MUST be in range:
60 <= "value" <= 86400 (1 day)
Figure 1 Figure 1
A DHCPv6 client MUST include the SOL_MAX_RT option code in an Option
Request option [RFC3315] in any message it sends.
The DHCPv6 server MAY include the SOL_MAX_RT option in any response
it sends to a client that has included the SOL_MAX_RT option code in
an Option Request option. The SOL_MAX_RT option is sent in the main
body of the message to client, not as a sub-option in, e.g., an
IA_NA, IA_TA [RFC3315] or IA_PD [RFC3633] option.
If a DHCPv6 client receives a message containing a SOL_MAX_RT option,
the client MUST set its internal SOL_MAX_RT parameter to the value
contained in the SOL_MAX_RT option. As a result of receiving this
option, the DHCPv6 client MUST NOT send any Solicit messages more
frequently than allowed by the retransmission mechanism defined in
sections 17.1.2 and 14 of RFC 3315 [RFC3315].
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 Solicit traffic from a client that has not received a reduces the Information-Request traffic from a client that has not
response to its Solicit messages. received a response to its Information-Request messages.
The format of the INF_MAX_RT option is: The format of the INF_MAX_RT option is:
0 1 2 3 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 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-code | option-len | | option-code | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| INF_MAX_RT value | | INF_MAX_RT value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code OPTION_INF_MAX_RT (TBD). option-code OPTION_INF_MAX_RT (TBD).
option-len 4. option-len 4.
INF_MAX_RT value Overriding value for INF_MAX_RT INF_MAX_RT value Overriding value for INF_MAX_RT
in seconds. in seconds; MUST be in range:
60 <= "value" <= 86400 (1 day)
Figure 2: INF_MAX_RT option format Figure 2: INF_MAX_RT option format
A DHCPv6 client MUST include the INF_MAX_RT option code in an Option
Request option [RFC3315] in any message it sends.
The DHCPv6 server MAY include the INF_MAX_RT option in any response
it sends to a client that has included the INF_MAX_RT option code in
an Option Request option. The INF_MAX_RT option is sent in the main
body of the message to client, not as a sub-option in, e.g., an
IA_NA, IA_TA [RFC3315] or IA_PD [RFC3633] option.
If a DHCPv6 client receives a message containing a INF_MAX_RT option,
the client MUST set its internal INF_MAX_RT parameter to the value
contained in the INF_MAX_RT option. As a result of receiving this
option, the DHCPv6 client MUST NOT send any Information-request
messages more frequently than allowed by the retransmission mechanism
defined in sections 18.1.5 and 14 of RFC 3315 [RFC3315].
6. Updates for SOL_MAX_RT and INF_MAX_RT options to RFC 3315 6. Updates for SOL_MAX_RT and INF_MAX_RT options to RFC 3315
Update to RFC 3315 [RFC3315], section 17.1.3: Update to RFC 3315 [RFC3315], section 17.1.3:
OLD: OLD:
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.
skipping to change at page 6, line 14 skipping to change at page 5, line 29
Add text to the end of section 14, clarifying client behavior while Add text to the end of section 14, clarifying client behavior while
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. Security Considerations 7. DHCPv6 Client Behavior
A DHCPv6 client MUST include the SOL_MAX_RT option code in an Option
Request option [RFC3315] in any message it sends.
Client also MAY include option SOL_MAX_RT in its SOLICIT, REQUEST,
RENEW, REBIND and INFORMATION-REQUEST messages as a hint for the
server regarding preferred option values.
If a DHCPv6 client receives a message containing a SOL_MAX_RT option,
the client MUST set its 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 retransmission mechanism defined in sections 17.1.2 and
14 of RFC 3315 [RFC3315].
A DHCPv6 client MUST include the INF_MAX_RT option code in an Option
Request option [RFC3315] in any message it sends.
Client also MAY include option SOL_MAX_RT in its SOLICIT, REQUEST,
RENEW, REBIND and INFORMATION-REQUEST messages as a hint for the
server regarding preferred option values.
If a DHCPv6 client receives a message containing a INF_MAX_RT option,
the client MUST set its internal INF_MAX_RT parameter to the value
contained in the INF_MAX_RT option. This value of INF_MAX_RT is then
used by the retransmission mechanism defined in sections 18.1.5 and
14 of RFC 3315 [RFC3315].
8. DHCPv6 Server Behavior
Sections 17.2.2 and 18.2 of [RFC3315] govern server operation in
regards to option assignment. As a convenience to the reader, we
mention here that the server will send option SOL_MAX_RT and
INF_MAX_RT only if configured with specific values for them and the
client requested those options using Option Request Option.
The DHCPv6 server MAY include the SOL_MAX_RT option in any response
it sends to a client that has included the SOL_MAX_RT option code in
an Option Request option. The SOL_MAX_RT option is sent in the main
body of the message to client, not as a encapsulated option in, e.g.,
an IA_NA, IA_TA [RFC3315] or IA_PD [RFC3633] option.
The DHCPv6 server MAY include the INF_MAX_RT option in any response
it sends to a client that has included the INF_MAX_RT option code in
an Option Request option. The INF_MAX_RT option is sent in the main
body of the message to client, not as a encapsulated option in, e.g.,
an IA_NA, IA_TA [RFC3315] or IA_PD [RFC3633] option.
9. DHCPv6 Relay Agent Behavior Text
There are no additional requirements for relays.
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 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 server, large values for SOL_MAX_RT and INF_MAX_RT will not have any
effect. effect.
8. IANA Considerations 11. Acknowledgments
IANA is requested to assign an option code from the "DHCP Option Tomek Mrugalski edited the text for compliance with draft-ietf-dhc-
Codes" Registry for OPTION_SOL_MAX_RT. option-guidelines [I-D.ietf-dhc-option-guidelines].
9. Normative References 12. IANA Considerations
IANA is requested to assign option codes from the "DHCP Option Codes"
Registry for OPTION_SOL_MAX_RT and OPTION_INF_MAX_RT.
13. 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
[I-D.ietf-dhc-option-guidelines]
Hankins, D., Mrugalski, T., Siodelski, M., Jiang, S., and
S. Krishnan, "Guidelines for Creating New DHCPv6 Options",
draft-ietf-dhc-option-guidelines-12 (work in progress),
June 2013.
[RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
Host Configuration Protocol (DHCP) version 6", RFC 3633, Host Configuration Protocol (DHCP) version 6", RFC 3633,
December 2003. December 2003.
Author's Address Author's Address
Ralph Droms Ralph Droms
Cisco Systems Cisco Systems
1414 Massachusetts Avenue 1414 Massachusetts Avenue
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
Phone: +1 978 936 1674 Phone: +1 978 936 1674
Email: rdroms@cisco.com Email: rdroms@cisco.com
 End of changes. 16 change blocks. 
47 lines changed or deleted 85 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/