DHCPv4 over DHCPv6 Transport
draft-ietf-dhc-dhcpv4-over-dhcpv6-01

The information below is for an old version of the document
Document Type Active Internet-Draft (dhc WG)
Last updated 2013-07-15
Replaces draft-scskf-dhc-dhcpv4-over-dhcpv6
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
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)
DHC Working Group                                                 Q. Sun
Internet-Draft                                                    Y. Cui
Intended status: Standards Track                     Tsinghua University
Expires: January 16, 2014                                   M. Siodelski
                                                                     ISC
                                                             S. Krishnan
                                                                Ericsson
                                                               I. Farrer
                                                     Deutsche Telekom AG
                                                           July 15, 2013

                      DHCPv4 over DHCPv6 Transport
                  draft-ietf-dhc-dhcpv4-over-dhcpv6-01

Abstract

   This document describes a mechanism for obtaining IPv4 address and
   other parameters in IPv6 networks by carrying DHCPv4 messages over
   DHCPv6 transport.

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 January 16, 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
   (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

Sun, et al.             Expires January 16, 2014                [Page 1]
Internet-Draft             DHCPv4 over DHCPv6                  July 2013

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  New DHCPv6 Messages . . . . . . . . . . . . . . . . . . . . .   3
   5.  Architecture Overview . . . . . . . . . . . . . . . . . . . .   3
   6.  DHCPv6 Options  . . . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  BOOTP Message Option Format . . . . . . . . . . . . . . .   5
     6.2.  DHCPv4-over-DHCPv6 Enable Option Format . . . . . . . . .   5
     6.3.  4o6 Servers Address Option Format . . . . . . . . . . . .   6
   7.  Client Behavior . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  Relay Agent Behavior  . . . . . . . . . . . . . . . . . . . .   8
   9.  Server Behavior . . . . . . . . . . . . . . . . . . . . . . .   8
   10. Security Considerations . . . . . . . . . . . . . . . . . . .   9
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   12. Contributors List . . . . . . . . . . . . . . . . . . . . . .   9
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     13.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     13.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   As the migration towards IPv6 continues, IPv6 only networks will
   become more prevalent.  However, IPv4 connectivity will continue to
   be provided as a service over these IPv6 only networks.  In addition
   to providing IPv4 addresses for clients of this service, other IPv4
   configuration parameters may also need to be provided, (e.g.
   addresses of IPv4-only services).

   By conveying DHCPv4 messages over DHCPv6 transport, this mechanism
   can achieve dynamic provisioning of IPv4 address and other
   configuration parameters.  In addition, it is able to leverage
   existing infrastructure for DHCPv4, e.g. failover, DNS updates,
   leasequery, etc.  This mechanism is suitable for stateful allocation
   and management of IPv4 addresses and configuration parameters across
   IPv6 networks.

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this

Sun, et al.             Expires January 16, 2014                [Page 2]
Show full document text