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

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

The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) specifies a Non-Broadcast, Multiple Access (NBMA) interface type for the transmission of IPv6 packets over IPv4 networks using automatic IPv6-in-IPv4 encapsulation. The original specifications make no provisions for the encapsulation and transmission of IPv4 packets, however. This document specifies a method for transmitting IPv4 packets over ISATAP interfaces. This document is not an Internet Standards Track specification; it is published for informational purposes.

Document record

Document ID

RFC5579

Published

February 2010

Authors

F. Templin

Status

INFORMATIONAL

Stream

INDEPENDENT

Area

—

Pages

9

Also known as

—

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

Topics

• ISATAP
• Tunnel
• Encapsulation
• Map-and-Encaps
• IPv4
• IPv6

Related documents

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

• RFC 6139Routing and Addressing in Networks with Global Enterprise Recursion (RANGER) ScenariosCurrent

  February 2011

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

  May 2013

• RFC 6179The Internet Routing Overlay Network (IRON)Current

  March 2011

• RFC 4301Security Architecture for the Internet ProtocolUpdated

  December 2005

• RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent

  August 2014

• RFC 2401Security Architecture for the Internet ProtocolObsoleted

  November 1998

• RFC 5572IPv6 Tunnel Broker with the Tunnel Setup Protocol (TSP)Current

  February 2010

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

  January 2010

Also filed under

• INFORMATIONAL
• 2010
• INDEPENDENT stream