Enterprise IPv6 Deployment Guidelines
draft-ietf-v6ops-enterprise-incremental-ipv6-02

The information below is for an old version of the document
Document Type Active Internet-Draft (v6ops WG)
Last updated 2013-02-25
Replaces draft-chkpvc-enterprise-incremental-ipv6
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                    K. Chittimaneni
Internet-Draft                                               Google Inc.
Intended status: Informational                                  T. Chown
Expires: August 29, 2013                       University of Southampton
                                                               L. Howard
                                                       Time Warner Cable
                                                            V. Kuarsingh
                                                   Rogers Communications
                                                             Y. Pouffary
                                                         Hewlett Packard
                                                               E. Vyncke
                                                           Cisco Systems
                                                       February 25, 2013

                 Enterprise IPv6 Deployment Guidelines
            draft-ietf-v6ops-enterprise-incremental-ipv6-02

Abstract

   Enterprise network administrators worldwide are in various stages of
   preparing for or deploying IPv6 into their networks.  The
   administrators face different challenges than operators of Internet
   access providers, and have reasons for different priorities.  The
   overall problem for many administrators will be to offer Internet-
   facing services over IPv6, while continuing to support IPv4, and
   while introducing IPv6 access within the enterprise IT network.  The
   overall transition will take most networks from an IPv4-only
   environment to a dual stack network environment and potentially an
   IPv6-only operating mode.  This document helps provide a framework
   for enterprise network architects or administrators who may be faced
   with many of these challenges as they consider their IPv6 support
   strategies.

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."

Chittimaneni, et al.     Expires August 29, 2013                [Page 1]
Internet-Draft         Enterprise IPv6 Deployment          February 2013

   This Internet-Draft will expire on August 29, 2013.

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
   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.

Chittimaneni, et al.     Expires August 29, 2013                [Page 2]
Internet-Draft         Enterprise IPv6 Deployment          February 2013

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Enterprise Assumptions . . . . . . . . . . . . . . . . . .  4
     1.2.  IPv4-only Considerations . . . . . . . . . . . . . . . . .  5
     1.3.  Reasons for a Phased Approach  . . . . . . . . . . . . . .  5
   2.  Preparation and Assessment Phase . . . . . . . . . . . . . . .  7
     2.1.  Program Planning . . . . . . . . . . . . . . . . . . . . .  7
     2.2.  Inventory Phase  . . . . . . . . . . . . . . . . . . . . .  8
       2.2.1.  Network infrastructure readiness assessment  . . . . .  8
       2.2.2.  Applications readiness assessment  . . . . . . . . . .  9
       2.2.3.  Importance of readiness validation and testing . . . . 10
     2.3.  Training . . . . . . . . . . . . . . . . . . . . . . . . . 10
     2.4.  Security Policy  . . . . . . . . . . . . . . . . . . . . . 10
       2.4.1.  IPv6 is no more secure than IPv4 . . . . . . . . . . . 10
       2.4.2.  Similarities between IPv6 and IPv4 security  . . . . . 11
       2.4.3.  Specific Security Issues for IPv6  . . . . . . . . . . 12
     2.5.  Routing  . . . . . . . . . . . . . . . . . . . . . . . . . 13
Show full document text