Prefix Assignment in DHCPv6
draft-ietf-dhc-host-gen-id-01

The information below is for an old version of the document
Document Type Active Internet-Draft (dhc WG)
Last updated 2011-11-20 (latest revision 2011-05-16)
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           S. Jiang
Internet-Draft                                                    F. Xia
Intended status: Standards Track                             B. Sarikaya
Expires: May 24, 2012                                Huawei Technologies
                                                       November 21, 2011

                      Prefix Assignment in DHCPv6
                   draft-ietf-dhc-host-gen-id-01.txt

Abstract

   This document describes a procedure for configuring hosts' IPv6
   address which the prefix is assigned from a DHCPv6 server through
   DHCPv6 protocol while the interface identifiers are independently
   generated by the hosts.  The method is applicable to
   Cryptographically Generated Addresses (CGA), and other IPv6 addresses
   with host-generated interface identifiers.

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 May 24, 2012.

Copyright Notice

   Copyright (c) 2011 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
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Jiang, et al.             Expires May 24, 2012                  [Page 1]
Internet-Draft         Prefix Assignment in DHCPv6         November 2011

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Address Auto-configuration . . . . . . . . . . . . . . . . . .  4
   4.  DHCPv6 Operation . . . . . . . . . . . . . . . . . . . . . . .  5
   5.  DHCPv6 IA_PA Option  . . . . . . . . . . . . . . . . . . . . .  6
     5.1.  Identity Association for Prefix Assignment Option  . . . .  6
     5.2.  IA_PA Prefix Option  . . . . . . . . . . . . . . . . . . .  7
   6.  Applicability  . . . . . . . . . . . . . . . . . . . . . . . .  8
   7.  IANA consideration . . . . . . . . . . . . . . . . . . . . . .  8
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  9
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     10.1. Normative References . . . . . . . . . . . . . . . . . . .  9
     10.2. Informative references . . . . . . . . . . . . . . . . . .  9
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10

Jiang, et al.             Expires May 24, 2012                  [Page 2]
Internet-Draft         Prefix Assignment in DHCPv6         November 2011

1.  Introduction

   [RFC3315] describes the operation of address assignment by a DHCPv6
   server.  A client uses a Solicit message to discover DHCPv6 servers
   configured to assign addresses.  A server sends an Advertise message
   in response to announce the availability of the server to the client.
   The client then uses a Request message to request addresses.  The
   server then returns addresses in a Reply message.  The operation
   assumes that the server is responsible for the assignment of an
   integral address which includes prefix and interface identifier parts
   as described in [RFC4291].

   This document introduces a new DHCPv6 procedure to configure hosts'
   IPv6 addresses.  In this new procedure, the prefix is advertised from
   a DHCPv6 server through DHCPv6 protocol while the interface
   identifiers are independently generated by the hosts.

   [RFC3633] defines Prefix Delegation options providing a mechanism for
   automated delegation of IPv6 prefixes using the DHCPv6.  This
   mechanism is intended for delegating a long-lived prefix from a
   delegating router to a requesting router.  This mechanism "is not
   bound to the assignment of IP addresses or other configuration
   information to hosts" [RFC3633].  It delegates prefixes to a routable
Show full document text