ISATAP
E123432
ISATAP (Intra-Site Automatic Tunnel Addressing Protocol) is an IPv6 transition mechanism that enables IPv6 connectivity over an IPv4 intranet by encapsulating IPv6 packets within IPv4.
All labels observed (2)
| Label | Occurrences |
|---|---|
| ISATAP canonical | 2 |
| Intra-Site Automatic Tunnel Addressing Protocol | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1077149 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISATAP Context triple: [Teredo, alternativeTo, ISATAP]
-
A.
Teredo
Teredo is a tunneling protocol that enables IPv6 connectivity for devices on IPv4 networks, particularly those behind NAT.
-
B.
NAT64
NAT64 is a network address translation mechanism that enables IPv6-only clients to communicate with IPv4 servers by translating between the two protocol address spaces and packet formats.
-
C.
IS-IS for IPv6
IS-IS for IPv6 is an extension of the IS-IS interior gateway routing protocol that enables dynamic routing and topology discovery in IPv6 networks.
-
D.
BGP-4+
BGP-4+ is an enhanced version of the Border Gateway Protocol designed to support routing for IPv6 networks.
-
E.
Internet Protocol version 6
Internet Protocol version 6 (IPv6) is the modern Internet addressing and routing protocol designed to replace IPv4 by providing a vastly larger address space and improved network efficiency and security features.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: ISATAP Target entity description: ISATAP (Intra-Site Automatic Tunnel Addressing Protocol) is an IPv6 transition mechanism that enables IPv6 connectivity over an IPv4 intranet by encapsulating IPv6 packets within IPv4.
-
A.
Teredo
Teredo is a tunneling protocol that enables IPv6 connectivity for devices on IPv4 networks, particularly those behind NAT.
-
B.
NAT64
NAT64 is a network address translation mechanism that enables IPv6-only clients to communicate with IPv4 servers by translating between the two protocol address spaces and packet formats.
-
C.
IS-IS for IPv6
IS-IS for IPv6 is an extension of the IS-IS interior gateway routing protocol that enables dynamic routing and topology discovery in IPv6 networks.
-
D.
BGP-4+
BGP-4+ is an enhanced version of the Border Gateway Protocol designed to support routing for IPv6 networks.
-
E.
Internet Protocol version 6
Internet Protocol version 6 (IPv6) is the modern Internet addressing and routing protocol designed to replace IPv4 by providing a vastly larger address space and improved network efficiency and security features.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
IPv6 transition mechanism
ⓘ
tunneling protocol ⓘ |
| abbreviation | ISATAP self-link ⓘ |
| addressingMechanism | IPv6 addresses derived from IPv4 addresses ⓘ |
| canSupport | multicast via IPv4 unicast emulation ⓘ |
| category |
IPv6 transition technology
ⓘ
automatic tunneling mechanism ⓘ |
| definedIn | RFC 5214 ⓘ |
| designGoal |
avoid manual tunnel configuration
ⓘ
enable IPv6 over existing IPv4 infrastructure ⓘ |
| differsFrom |
6to4 by being designed for intra-site use
ⓘ
Teredo by not requiring NAT traversal ⓘ |
| encapsulates | IPv6 packets in IPv4 packets ⓘ |
| fullName |
ISATAP
self-linksurface differs
ⓘ
surface form:
Intra-Site Automatic Tunnel Addressing Protocol
|
| interfaceIdentifierFormat | 0000:5efe:IPv4-address ⓘ |
| limitation |
management and troubleshooting complexity
ⓘ
not recommended for large-scale public Internet deployment ⓘ |
| operatesAtLayer | network layer ⓘ |
| predecessorDocument | Internet-Draft draft-ietf-ngtrans-isatap ⓘ |
| primaryUse | IPv6 connectivity over IPv4 intranets ⓘ |
| publicationYear | 2008 ⓘ |
| requires |
IPv4 unicast connectivity between ISATAP nodes
ⓘ
dual-stack nodes (IPv4 and IPv6) ⓘ |
| runsOverProtocol | IPv4 ⓘ |
| scope | intra-site ⓘ |
| securityConsideration | relies on IPv4 security mechanisms for encapsulated traffic ⓘ |
| similarTo |
6to4
ⓘ
Teredo ⓘ |
| status | Experimental RFC ⓘ |
| supports | unicast IPv6 traffic ⓘ |
| supportsDeploymentModel |
host-to-host
ⓘ
host-to-router ⓘ router-to-router ⓘ |
| supportsProtocol | IPv6 ⓘ |
| transitionType | automatic tunneling ⓘ |
| useCase |
enterprise IPv6 pilot deployments
ⓘ
gradual IPv6 migration within organizations ⓘ |
| usesAddressFormat |
IPv6 global addresses with ISATAP interface identifiers
ⓘ
IPv6 link-local addresses with ISATAP interface identifiers ⓘ |
| usesConcept |
ISATAP host
ⓘ
ISATAP link ⓘ ISATAP router ⓘ |
| usesDiscoveryMechanism |
DNS-based ISATAP router discovery
ⓘ
well-known ISATAP host name (isatap.domain) ⓘ |
| usesEncapsulation | IPv4 protocol number 41 ⓘ |
| wasImplementedBy |
Windows
ⓘ
surface form:
Microsoft Windows operating systems
|
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: ISATAP Description of subject: ISATAP (Intra-Site Automatic Tunnel Addressing Protocol) is an IPv6 transition mechanism that enables IPv6 connectivity over an IPv4 intranet by encapsulating IPv6 packets within IPv4.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
Intra-Site Automatic Tunnel Addressing Protocol