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

The information below is for an old version of the document
Document Type Active Internet-Draft (dhc WG)
Last updated 2013-09-21
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: Informational                                     J. Wu
Expires: March 25, 2014                              Tsinghua University
                                                                T. Lemon
                                                           Nominum, Inc.
                                                      September 21, 2013

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

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 putting a special relay agent function
   (Client Relay Agent) on the client side, as well as extending the
   behavior of the server; in the case where DHCP server only supports
   IPv4 transport, a relay agent is extended to support IPv6 transport
   (IPv6-Transport Relay Agent) and relay DHCP traffic for the server,
   with a new Relay Agent Information sub-option added to carry the IPv6
   address of the Client Relay Agent.

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 March 25, 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

Cui, et al.              Expires March 25, 2014                 [Page 1]
Internet-Draft              DHCPv4 over IPv6              September 2013

   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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Protocol Summary . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Client Relay Agent IPv6 Address Sub-option . . . . . . . . . .  5
   5.  Client Relay Agent Behavior  . . . . . . . . . . . . . . . . .  6
   6.  IPv6-Transport Server Behavior . . . . . . . . . . . . . . . .  7
   7.  IPv6-Transport Relay Agent Behavior  . . . . . . . . . . . . .  8
   8.  Security Consideration . . . . . . . . . . . . . . . . . . . .  8
   9.  IANA Consideration . . . . . . . . . . . . . . . . . . . . . .  9
   10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . .  9
   11. References . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     11.1.  Normative References  . . . . . . . . . . . . . . . . . .  9
     11.2.  Informative References  . . . . . . . . . . . . . . . . . 10
   Appendix A.  Motivation for selecting this particular solution . . 10
     A.1.   Configuring IPv4 with DHCPv6  . . . . . . . . . . . . . . 10
     A.2.   Tunnel DHCPv4 over IPv6 . . . . . . . . . . . . . . . . . 11
     A.3.   DHCPv4 relayed over IPv6  . . . . . . . . . . . . . . . . 11
   Appendix B.  Discussion on One Host Retrieving Multiple
                Addresses through One CRA . . . . . . . . . . . . . . 12
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12

Cui, et al.              Expires March 25, 2014                 [Page 2]
Internet-Draft              DHCPv4 over IPv6              September 2013

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 the DHCPv4
   protocol 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-
Show full document text