RFC 5214: Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)

In plain English — editorial summary, not part of the RFC

The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) connects dual-stack (IPv6/IPv4) nodes over IPv4 networks. ISATAP views the IPv4 network as a link layer for IPv6 and supports an automatic tunneling abstraction similar to the Non-Broadcast Multiple Access (NBMA) model. This memo provides information for the Internet community.

Document record

Document ID

RFC5214

Published

March 2008

Authors

F. Templin; T. Gleeson; D. Thaler

Status

INFORMATIONAL

Stream

INDEPENDENT

Area

—

Pages

15

Also known as

—

Obsoletes:

RFC 4214

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC5214

Topics

• ipv6
• ipv4
• non-broadcast multiple access
• nbma
• dual-stack

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 7984Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP NetworkCurrent

  September 2016

• RFC 5569IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)Current

  January 2010

• RFC 5579Transmission of IPv4 Packets over Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) InterfacesCurrent

  February 2010

• RFC 3974SMTP Operational Experience in Mixed IPv4/v6 EnvironmentsCurrent

  January 2005

• RFC 6964Operational Guidance for IPv6 Deployment in IPv4 Sites Using the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)Current

  May 2013

• RFC 7021Assessing the Impact of Carrier-Grade NAT on Network ApplicationsCurrent

  September 2013

• RFC 5549Advertising IPv4 Network Layer Reachability Information with an IPv6 Next HopObsoleted

  May 2009

• RFC 4835Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted

  April 2007

Also filed under

• INFORMATIONAL
• 2008
• INDEPENDENT stream