| Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) | ||||||
![]() |
||||||
|
ISATAP
is the Intra-Site Automatic Tunnel Addressing Protocol; it is used for automatic
deployment of IPv6 in IPv4 sites. ISATAP specifies an IPv6-IPv4 compatibility address
format as well as a means for site border router discovery. ISATAP also specifies the
operation of IPv6 over a specific link layer - that being IPv4 used as a link layer
for IPv6.
As of March 2008, ISATAP has been re-published as an informational-category RFC [RFC5214] which obsoletes the previous experimental-category version [RFC4214]. A development history of RFC4214 is on the ISATAP Issue Tracker Page As of April 2008, ISATAP is implemented in the publicly available Linux operating system kernel, beginning with linux-2.6.25. ISATAP is also implemented in other widely-deployed systems including Microsoft Windows XP, Microsoft Windows Vista, cisco IOS, 6WIND 6WINDGate, and FreeBSD/KAME. A new architecture called Routing and Addressing in Next-Generation EnteRprises (RANGER) is progressing through the RFC publication process as a successor to ISATAP, and in some sense can be considered as ISATAP version 2. RANGER is an architectural framework that extends the basic functions of ISATAP to also include IPv6 autoconfiguration, IPv6 prefix delegation, router-to-router tunneling, adaptation to diverse tunnel MTUs and IPv6 multicast. RANGER combines the functional elements specified in Virtual Enterprise Traversal (VET) and the Subnetwork Adaptation and Encapsulation Layer (SEAL).
|
||||||