metasystema.org
ObsoletedEXPERIMENTALINDEPENDENT stream

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

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5214.

Current version: 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 IPv6 hosts/routers over IPv4 networks. ISATAP views the IPv4 network as a link layer for IPv6 and views other nodes on the network as potential IPv6 hosts/routers. ISATAP supports an automatic tunneling abstraction similar to the Non-Broadcast Multiple Access (NBMA) model. This memo defines an Experimental Protocol for the Internet community.

Document record

Document ID
RFC4214
Published
October 2005
Authors
F. Templin; T. Gleeson; M. Talwar; D. Thaler
Status
EXPERIMENTAL
Stream
INDEPENDENT
Area
—
Pages
14
Also known as
—
Obsoleted by:
RFC 5214

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

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

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?

canonical URL: /rfc/4214-intra-site-automatic-tunnel-addressing-protocol-isatap