Operational Guidance for IPv6 Deployment in IPv4 Sites using ISATAP
draft-templin-v6ops-isops-17

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 14
• 15
• 16
• 17
• 18
• 19

Network Working Group                                         F. Templin
Internet-Draft                              Boeing Research & Technology
Intended status: Informational                              May 09, 2012
Expires: November 10, 2012

  Operational Guidance for IPv6 Deployment in IPv4 Sites using ISATAP
                    draft-templin-v6ops-isops-17.txt

Abstract

   Many end user sites in the Internet today still have predominantly
   IPv4 internal infrastructures.  These sites range in size from small
   home/office networks to large corporate enterprise networks, but
   share the commonality that IPv4 provides satisfactory internal
   routing and addressing services for most applications.  As more and
   more IPv6-only services are deployed, however, end user devices
   within such sites will increasingly require at least basic IPv6
   functionality.  This document therefore provides operational guidance
   for deployment of IPv6 within predominantly IPv4 sites using the
   Intra-Site Automatic Tunnel Addressing Protocol (ISATAP).

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 November 10, 2012.

Copyright Notice

   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

Templin                 Expires November 10, 2012               [Page 1]
Internet-Draft         ISATAP Operational Guidance              May 2012

   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.  Enabling IPv6 Services using ISATAP  . . . . . . . . . . . . .  3
   3.  SLAAC Services . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Advertising ISATAP Router Behavior . . . . . . . . . . . .  5
     3.2.  ISATAP Host Behavior . . . . . . . . . . . . . . . . . . .  6
     3.3.  Reference Operational Scenario - Shared Prefix Model . . .  6
     3.4.  Reference Operational Scenario - Individual Prefix
           Model  . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     3.5.  SLAAC Site Administration Guidance . . . . . . . . . . . . 12
     3.6.  Loop Avoidance . . . . . . . . . . . . . . . . . . . . . . 14
     3.7.  Interface Identifier Compatibility Considerations  . . . . 14
   4.  Manual Configuration . . . . . . . . . . . . . . . . . . . . . 15
   5.  Scaling Considerations . . . . . . . . . . . . . . . . . . . . 15
   6.  Site Renumbering Considerations  . . . . . . . . . . . . . . . 16
   7.  Path MTU Considerations  . . . . . . . . . . . . . . . . . . . 16
   8.  Alternative Approaches . . . . . . . . . . . . . . . . . . . . 17
   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 17
   10. Security Considerations  . . . . . . . . . . . . . . . . . . . 17
   11. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 18
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
     12.1. Normative References . . . . . . . . . . . . . . . . . . . 18
     12.2. Informative References . . . . . . . . . . . . . . . . . . 18
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 20

Templin                 Expires November 10, 2012               [Page 2]
Internet-Draft         ISATAP Operational Guidance              May 2012

1.  Introduction

   End user sites in the Internet today currently use IPv4 routing and
   addressing internally for core operating functions such as web
   browsing, filesharing, network printing, e-mail, teleconferencing and
   numerous other site-internal networking services.  Such sites
   typically have an abundance of public or private IPv4 addresses for
   internal networking, and are separated from the public Internet by
   firewalls, packet filtering gateways, proxies, address translators
   and other site border demarcation devices.  To date, such sites have