RFC 6964: Operational Guidance for IPv6 Deployment in IPv4 Sites Using the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)
In plain English — editorial summary, not part of the RFC
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).
Document record
- Document ID
- RFC6964
- Published
- May 2013
- Authors
- F. Templin
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5579Transmission of IPv4 Packets over Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) InterfacesCurrent
February 2010
- RFC 6139Routing and Addressing in Networks with Global Enterprise Recursion (RANGER) ScenariosCurrent
February 2011
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 6179The Internet Routing Overlay Network (IRON)Current
March 2011
- RFC 7021Assessing the Impact of Carrier-Grade NAT on Network ApplicationsCurrent
September 2013
- RFC 5572IPv6 Tunnel Broker with the Tunnel Setup Protocol (TSP)Current
February 2010
- RFC 5569IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)Current
January 2010
- RFC 5214Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)Current
March 2008
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?