Softwire Provisioning using DHCPv4 Over DHCPv6
draft-ietf-dhc-dhcp4o6-saddr-opt-04

The information below is for an old version of the document
Document Type Active Internet-Draft (dhc WG)
Last updated 2018-09-20 (latest revision 2018-06-14)
Replaces draft-fsc-softwire-dhcp4o6-saddr-opt
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state Submitted to IESG for Publication (wg milestone: Mar 2018 - WGLC draft-ietf-dhc-... )
Document shepherd Bernie Volz
Shepherd write-up Show (last changed 2018-06-21)
IESG IESG state IESG Evaluation
Consensus Boilerplate Yes
Telechat date
Has a DISCUSS. Has enough positions to pass once DISCUSS positions are resolved.
Responsible AD Suresh Krishnan
Send notices to Bernie Volz <volz@cisco.com>
IANA IANA review state IANA OK - Actions Needed
IANA action state None
DHCWG                                                          I. Farrer
Internet-Draft                                       Deutsche Telekom AG
Updates: 7598 (if approved)                                       Q. Sun
Intended status: Standards Track                                  Y. Cui
Expires: December 16, 2018                                        L. Sun
                                                     Tsinghua University
                                                           June 14, 2018

             Softwire Provisioning using DHCPv4 Over DHCPv6
                  draft-ietf-dhc-dhcp4o6-saddr-opt-04

Abstract

   DHCPv4 over DHCPv6 (RFC7341) is a mechanism for dynamically
   configuring IPv4 over an IPv6-only network.  For DHCPv4 over DHCPv6
   to function with some IPv4-over-IPv6 softwire mechanisms and
   deployment scenarios, the operator needs to know the IPv6 address
   that the client will use as the source of IPv4-in-IPv6 softwire
   tunnel.  This address, in conjunction with the client's IPv4 address,
   and (in some deployments) the Port Set ID are used to create a
   binding table entry in the operator's softwire tunnel concentrator.
   This memo defines a DHCPv6 option to convey IPv6 parameters for
   establishing the softwire tunnel and a DHCPv4 option (to be used only
   with DHCP 4o6) to communicate the source tunnel IPv6 address between
   the DHCP 4o6 client and server.  It is designed to work in
   conjunction with the IPv4 address allocation process.

   This document updates "DHCPv6 Options for Configuration of Softwire
   Address and Port-Mapped Clients" (RFC7598), allowing OPTION_S46_BR
   (90) to be enumerated in the DHCPv6 client's ORO request and appear
   directly within subsequent messages sent by the DHCPv6 server.

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 https://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."

Farrer, et al.          Expires December 16, 2018               [Page 1]
Internet-Draft     Softwire Provisioning with DHCP 4o6         June 2018

   This Internet-Draft will expire on December 16, 2018.

Copyright Notice

   Copyright (c) 2018 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
   (https://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.  Applicability . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Requirements Language . . . . . . . . . . . . . . . . . . . .   4
   4.  Solution Overview . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Updating RFC7598 to Permit the Reuse of OPTION_S46_BR(90)   4
   5.  DHCP 4o6 IPv6/IPv4 Binding Message Flow . . . . . . . . . . .   5
   6.  DHCP Options  . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  DHCPv6 Softwire Source Binding Prefix Hint Option . . . .   7
     6.2.  DHCPv4 over DHCPv6 Softwire Source Address Option . . . .   7
   7.  Client Behavior . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Client Initialization . . . . . . . . . . . . . . . . . .   8
     7.2.  Renewing or Rebinding the IPv4 Address Lease and
           Softwire Source Address . . . . . . . . . . . . . . . . .   9
       7.2.1.  Changing the Bound IPv6 Softwire Source Address . . .  10
     7.3.  Releasing the IPv4 Address Lease and Softwire
           Source Address  . . . . . . . . . . . . . . . . . . . . .  10
     7.4.  OPTION_S46_BIND_IPV6_PREFIX Validation Behavior . . . . .  10
     7.5.  Client and Server Softwire Source Address Mismatch  . . .  11
     7.6.  Use With Dynamic, Shared IPv4 Addresses . . . . . . . . .  11
   8.  Server Behavior . . . . . . . . . . . . . . . . . . . . . . .  11
     8.1.  Changing the Bound IPv6 Source Address  . . . . . . . . .  11
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
Show full document text