DHCPv4 over IPv6 Transport
draft-ietf-dhc-dhcpv4-over-ipv6-02

The information below is for an old version of the document
Document Type Active Internet-Draft (dhc WG)
Last updated 2012-03-28
Replaces draft-cui-dhc-dhcpv4-over-ipv6
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) 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                                             Y. Cui
Internet-Draft                                                     P. Wu
Intended status: Standards Track                                   J. Wu
Expires: September 30, 2012                          Tsinghua University
                                                                T. Lemon
                                                           Nominum, Inc.
                                                          March 29, 2012

                       DHCPv4 over IPv6 Transport
                   draft-ietf-dhc-dhcpv4-over-ipv6-02

Abstract

   In IPv6 networks, there remains a need to provide IPv4 service for
   some residual devices.  This document describes a mechanism for
   allocating IPv4 addresses to such devices using DHCPv4 with an IPv6
   transport.  It is done by extending DHCP client and server behavior,
   and by adding a new Relay Agent Information option to carry the IPv6
   address of the client.

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 September 30, 2012.

Copyright Notice

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

Cui, et al.            Expires September 30, 2012               [Page 1]
Internet-Draft              DHCPv4 over IPv6                  March 2012

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . . . 3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 4
   4.  Protocol Summary  . . . . . . . . . . . . . . . . . . . . . . . 4
   5.  Client Relay Agent IPv6 Address Sub-option  . . . . . . . . . . 6
   6.  Client Relay Agent Behavior . . . . . . . . . . . . . . . . . . 6
   7.  IPv6-Transport Server Behavior  . . . . . . . . . . . . . . . . 7
   8.  IPv6-Transport Relay Agent Behavior . . . . . . . . . . . . . . 8
   9.  Security Consideration  . . . . . . . . . . . . . . . . . . . . 8
   10. IANA consideration  . . . . . . . . . . . . . . . . . . . . . . 8
   11. Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . 9
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 9
     12.1.  Normative References . . . . . . . . . . . . . . . . . . . 9
     12.2.  Informative References . . . . . . . . . . . . . . . . . . 9

Cui, et al.            Expires September 30, 2012               [Page 2]
Internet-Draft              DHCPv4 over IPv6                  March 2012

1.  Introduction

   DHCPv4 [RFC2131] was not designed with IPv6 in mind: DHCPv4 cannot
   operate on an IPv6 network.  However, as dual-stack networks become a
   reality, the need arises to allocate IPv4 addresses in an IPv6
   environment.  To meet this demand, this document extends DHCPv4 to
   allow the use of an IPv6 network for transport.

   A typical scenario that probably requires this feature is IPv4-over-
   IPv6 hub and spoke tunnel [RFC4925].  In this scenario, IPv4-over-
   IPv6 tunnel is used to provide IPv4 connectivity to end users (hosts
   or end networks) across an IPv6 network.  If the IPv4 addresses of
   the end users are provisioned by the concentrator side, then the
   provisioning process should be able to cross the IPv6 network, too.
   One such tunnel mechanism is demonstrated in
   [I-D.ietf-softwire-public-4over6].  DHCPv4 over IPv6 would be a
   generic solution for this scenario.

   Three main flavours of solutions may be considered:

   o  Use DHCPv6 instead of DHCPv4, to provision IPv4-related
      connectivity.  In DHCPv6, the provisioned IPv4 address can be
      embedded into IPv6 address, or carried within a new option.  Along
      with that, dedicated options are needed to convey IPv4-related
Show full document text