"Gateway-Initiated" 6rd
draft-tsou-softwire-gwinit-6rd-05

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-02-03 (latest revision 2011-12-29)
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
RFC Editor RFC Editor state ISR-AUTH
Internet Engineering Task Force                                  T. Tsou
Internet-Draft                                 Huawei Technologies (USA)
Intended status: Informational                                   C. Zhou
Expires: August 5, 2012                                        T. Taylor
                                                     Huawei Technologies
                                                                O. Troan
                                                     Cisco Systems, Inc.
                                                                 Q. Chen
                                                           China Telecom
                                                        February 2, 2012

                        "Gateway-Initiated" 6rd
                   draft-tsou-softwire-gwinit-6rd-05

Abstract

   This document proposes an alternative 6rd deployment model to that of
   RFC 5969.  The basic 6rd model allows IPv6 hosts to gain access to
   IPv6 networks across an IPv4 access network using 6-in-4 tunnels. 6rd
   requires support by a device (the 6rd-CE) on the customer site, which
   must also be assigned an IPv4 address.  The alternative model
   described in this document initiates the 6-in-4 tunnels from an
   operator-owned gateway collocated with the operator's IPv4 network
   edge, rather than from customer equipment.  The advantages of this
   approach are that it requires no modification to customer equipment
   and avoids assignment of IPv4 addresses to customer equipment.  The
   latter point means less pressure on IPv4 addresses in a high-growth
   environment.

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 August 5, 2012.

Copyright Notice

Tsou, et al.             Expires August 5, 2012                 [Page 1]
Internet-Draft           "Gateway-Initiated" 6rd           February 2012

   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
   to this document.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . . . 3
   2.  Problem Statement . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Proposed Solution . . . . . . . . . . . . . . . . . . . . . . . 5
     3.1.  Prefix Delegation . . . . . . . . . . . . . . . . . . . . . 6
     3.2.  Relevant Differences From Basic 6rd . . . . . . . . . . . . 7
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 8
     6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 8
     6.2.  Informative References  . . . . . . . . . . . . . . . . . . 8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 8

Tsou, et al.             Expires August 5, 2012                 [Page 2]
Internet-Draft           "Gateway-Initiated" 6rd           February 2012

1.  Introduction

   6rd ([RFC5969]) provides a transition tool for connecting IPv6
   devices across an IPv4 network to an IPv6 network, at which point the
   packets can be routed natively.  The network topology is shown in
   Figure 1.

      +--------------+     +-----------------+      +---------+
      |              |     |                 |      |         |
   +-----+        +-----+  | Provider   +--------+  |         |
   |IPv6 |        | 6rd |__|   IPv4     | Border |__|  IPv6   |
   |Host |        |  CE |  |  network   | Router |  | network |
   +-----+        +-----+  |            +--------+  |         |
      | Customer LAN |     |                 |      |         |
      +--------------+     +-----------------+      +---------+

                     Figure 1: 6rd Deployment Topology

   In Figure 1, the CE is the customer edge router.  It is provisioned
Show full document text