datatracker.ietf.org
Sign in
Version 5.12.0.p1, 2015-03-01
Report a bug

Issues and Recommendations with Multiple Stateful DHCPv6 Options
draft-ietf-dhc-dhcpv6-stateful-issues-11

Network Working Group                                           O. Troan
Internet-Draft                                                   B. Volz
Updates: 3315,3633 (if approved)                     Cisco Systems, Inc.
Intended status: Standards Track                            M. Siodelski
Expires: August 16, 2015                                             ISC
                                                       February 12, 2015

    Issues and Recommendations with Multiple Stateful DHCPv6 Options
              draft-ietf-dhc-dhcpv6-stateful-issues-11.txt

Abstract

   The Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
   specification defined two stateful options, IA_NA and IA_TA, but did
   not anticipate the development of additional stateful options.
   DHCPv6 Prefix Delegation added the IA_PD option, which is stateful.
   Applications that use IA_NA and IA_PD together have revealed issues
   that need to be addressed.  This document updates RFC 3315 and RFC
   3633 to address these issues.

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 http://datatracker.ietf.org/drafts/current/.

   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 August 16, 2015.

Copyright Notice

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

Troan, et al.            Expires August 16, 2015                [Page 1]
Internet-Draft          Multiple Stateful Options          February 2015

   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.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Handling of Multiple IA Option Types  . . . . . . . . . . . .   4
     4.1.  Placement of Status Codes in an Advertise Message . . . .   5
     4.2.  Advertise Message Processing by a Client  . . . . . . . .   7
     4.3.  T1/T2 Timers  . . . . . . . . . . . . . . . . . . . . . .   8
     4.4.  Renew and Rebind Messages . . . . . . . . . . . . . . . .   9
       4.4.1.  Renew Message . . . . . . . . . . . . . . . . . . . .   9
       4.4.2.  Rebind Message  . . . . . . . . . . . . . . . . . . .  10
       4.4.3.  Updates to section 18.1.3 of RFC 3315 . . . . . . . .  10
       4.4.4.  Updates to Section 18.1.4 of RFC 3315 . . . . . . . .  12
       4.4.5.  Updates to Section 18.1.8 of RFC 3315 . . . . . . . .  13
       4.4.6.  Updates to Section 18.2.3 of RFC 3315 . . . . . . . .  15
       4.4.7.  Updates to Section 18.2.4 of RFC 3315 . . . . . . . .  16
       4.4.8.  Updates to RFC 3633 . . . . . . . . . . . . . . . . .  18
     4.5.  Confirm Message . . . . . . . . . . . . . . . . . . . . .  19
     4.6.  Decline Should Not Necessarily Trigger a Release  . . . .  20
     4.7.  Multiple Provisioning Domains . . . . . . . . . . . . . .  20
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  21

[include full document text]