Operational Guidance for IPv6 Deployment in IPv4 Sites using ISATAP

The information below is for an old version of the document
Document Type None Internet-Draft (individual)
Last updated 2011-10-13 (latest revision 2011-07-27)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
IETF conflict review conflict-review-templin-v6ops-isops
Additional URLs
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Unknown state
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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 continues to provide satisfactory internal routing and addressing services for most applications. As more and more IPv6-only services are deployed in the Internet, however, end user devices within such sites will increasingly require at least basic IPv6 functionality for external access. This document therefore provides operational guidance for deployment of IPv6 within predominantly IPv4 sites using the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP).


Fred Templin (fltemplin@acm.org)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)