Modification to Default Values of SOL_MAX_RT and INF_MAX_RT

The information below is for an old version of the document
Document Type Active Internet-Draft (dhc WG)
Last updated 2013-09-13 (latest revision 2013-08-20)
Replaces draft-droms-dhc-dhcpv6-solmaxrt-update
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Yes
Document shepherd Tomek Mrugalski
Shepherd write-up Show (last changed 2013-07-22)
IESG IESG state Waiting for AD Go-Ahead::Revised I-D Needed
Telechat date
Responsible AD Ted Lemon
Send notices to,
IANA IANA review state IANA - Not OK
IANA action state None
dhc                                                             R. Droms
Internet-Draft                                             Cisco Systems
Updates: 3315 (if approved)                              August 20, 2013
Intended status: Standards Track
Expires: February 21, 2014

      Modification to Default Values of SOL_MAX_RT and INF_MAX_RT


   This document updates RFC 3315 by redefining the default values for
   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
   and INF_MAX_RT with a new value.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 21, 2014.

Copyright Notice

   Copyright (c) 2013 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
   ( 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.

Droms                   Expires February 21, 2014               [Page 1]
Internet-Draft          DHCPv6 SOL_MAX_RT Option             August 2013

1.  Introduction

   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
   circumstances, these defaults will lead to an unacceptably high
   volume of aggregated traffic at a DHCPv6 server.

   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
   clients are sending Solicit messages but the DHCPv6 server has been
   configured not to respond to those Solicit messages.  While no
   explicit observations of traffic due to INF_MAX_RT have been
   conducted, this document updates INF_MAX_RT for consistency with

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   document are to be interpreted as described in RFC 2119 [RFC2119].

3.  Updates to SOL_MAX_RT and INF_MAX_RT in RFC 3315

   This document changes section 5.5 of RFC 3315 [RFC3315] as follows:

      SOL_MAX_RT      120 secs  Max Solicit timeout value

      SOL_MAX_RT     3600 secs  Max Solicit timeout value

      INF_MAX_RT      120 secs  Max Information-request timeout value

      SOL_MAX_RT     3600 secs  Max Information-request timeout value

   With this change, a DHCPv6 client that does not receive a
   satisfactory response will send Solicit or Information-request
   messages with the same initial frequency and exponential backoff as
   specified in sections 17.1.2 and 18.1.5 of RFC 3315 [RFC3315].
   However, the long term behavior of these DHCPv6 clients will be to
   send a Solicit or Information-request message every 3600 seconds
   rather than every 120 seconds, significantly reducing the aggregated
   traffic at the DHCPv6 server.

Droms                   Expires February 21, 2014               [Page 2]
Internet-Draft          DHCPv6 SOL_MAX_RT Option             August 2013

4.  SOL_MAX_RT option

   A DHCPv6 server sends the SOL_MAX_RT option to a client to override
   the default value of SOL_MAX_RT.  The value of SOL_MAX_RT in the
   option replaces the default value defined in Section 3.  One use for
   the SOL_MAX_RT option is to set a longer value for SOL_MAX_RT, which
   reduces the Solicit traffic from a client that has not received a
Show full document text