RFC 2766
E545175
RFC 2766 is an Internet Engineering Task Force (IETF) specification that originally defined Network Address Translation–Protocol Translation (NAT-PT) for IPv6–IPv4 interoperability before being superseded by later standards.
All labels observed (2)
How this entity was disambiguated
This entity first appeared as the object of triple T5770829 — 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: RFC 2766 Context triple: [RFC 6146, obsoletes, RFC 2766]
-
A.
RFC 2866
RFC 2866 is an IETF specification that defines the accounting extensions for the RADIUS (Remote Authentication Dial-In User Service) protocol used in network access and usage tracking.
-
B.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
-
C.
RFC 1666
RFC 1666 is an early Internet standards document that was later superseded by RFC 1901 as the protocol or specification it defined evolved.
-
D.
RFC 1667
RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
E.
RFC 2026
RFC 2026 is an Internet Engineering Task Force (IETF) document that defines the standardization process and procedures for developing and approving Internet Standards.
- 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: RFC 2766 Target entity description: RFC 2766 is an Internet Engineering Task Force (IETF) specification that originally defined Network Address Translation–Protocol Translation (NAT-PT) for IPv6–IPv4 interoperability before being superseded by later standards.
-
A.
RFC 2866
RFC 2866 is an IETF specification that defines the accounting extensions for the RADIUS (Remote Authentication Dial-In User Service) protocol used in network access and usage tracking.
-
B.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
-
C.
RFC 1666
RFC 1666 is an early Internet standards document that was later superseded by RFC 1901 as the protocol or specification it defined evolved.
-
D.
RFC 1667
RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
E.
RFC 2026
RFC 2026 is an Internet Engineering Task Force (IETF) document that defines the standardization process and procedures for developing and approving Internet Standards.
- F. None of above. chosen
Statements (44)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| addressesProblem |
IPv4 to IPv6 communication
ⓘ
IPv6 to IPv4 communication ⓘ IPv6–IPv4 interoperability ⓘ |
| appliesTo |
IPv4
ⓘ
IPv6 ⓘ
linked to:
Internet Protocol version 6
|
| area | Internet Area ⓘ |
| category | Standards Track ⓘ |
| defines |
Network Address Translation - Protocol Translation
ⓘ
linked to:
IP/ICMP Translation Algorithm
|
| definesAbbreviation |
NAT-PT
ⓘ
linked to:
NAT64
|
| definesTerm |
NAT-PT binding
ⓘ
NAT-PT gateway ⓘ NAT-PT prefix ⓘ NAT-PT session ⓘ |
| format |
ASCII
ⓘ
text ⓘ |
| intendedUse | transition from IPv4 to IPv6 ⓘ |
| language | English ⓘ |
| notes | NAT-PT was later deprecated due to architectural and operational issues ⓘ |
| obsoletedBy |
RFC 4966
ⓘ
linked to:
RFC 2766
|
| obsoletes | no earlier RFCs ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| relatedTo |
DNS Application Level Gateway
ⓘ
IPv6 transition mechanisms ⓘ NAT ⓘ Network Address Translation ⓘ protocol translation ⓘ |
| series |
RFC series
ⓘ
linked to:
RFCs
|
| shortTitle |
NAT-PT
ⓘ
linked to:
NAT64
|
| specifies |
DNS-ALG behavior for NAT-PT
ⓘ
mechanisms for translating between IPv4 and IPv6 packet headers ⓘ stateful protocol translation between IPv4 and IPv6 ⓘ stateless protocol translation between IPv4 and IPv6 ⓘ translation of IP addresses between IPv4 and IPv6 ⓘ translation of transport-layer checksums for IPv4–IPv6 translation ⓘ use of a NAT-PT device at the boundary between IPv4 and IPv6 networks ⓘ |
| status | Historic ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| supersededBy | later IPv6–IPv4 translation standards ⓘ |
| title |
Network Address Translation - Protocol Translation (NAT-PT)
ⓘ
linked to:
IP/ICMP Translation Algorithm
|
| workingGroup | NGTRANS ⓘ |
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: RFC 2766 Description of subject: RFC 2766 is an Internet Engineering Task Force (IETF) specification that originally defined Network Address Translation–Protocol Translation (NAT-PT) for IPv6–IPv4 interoperability before being superseded by later standards.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.