RFC 6146
E127326
RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 6146 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1077170 — 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 6146 Context triple: [NAT64, definedInRFC, RFC 6146]
-
A.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
-
B.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
C.
RFC 3416
RFC 3416 is an Internet standard that specifies the protocol operations for the Simple Network Management Protocol (SNMP), defining how management data is exchanged between network devices and management systems.
-
D.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
E.
RFC 7143
RFC 7143 is the Internet Engineering Task Force (IETF) standard that defines the updated core specification for the iSCSI (Internet Small Computer Systems Interface) protocol used for block-level storage over IP networks.
- 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 6146 Target entity description: RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
-
A.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
-
B.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
C.
RFC 3416
RFC 3416 is an Internet standard that specifies the protocol operations for the Simple Network Management Protocol (SNMP), defining how management data is exchanged between network devices and management systems.
-
D.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
E.
RFC 7143
RFC 7143 is the Internet Engineering Task Force (IETF) standard that defines the updated core specification for the iSCSI (Internet Small Computer Systems Interface) protocol used for block-level storage over IP networks.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet Standard ⓘ |
| area |
the internet
ⓘ
surface form:
Internet
|
| category | Standards Track ⓘ |
| defines |
NAT64 address pooling behavior
ⓘ
NAT64 endpoint-independent filtering requirements ⓘ NAT64 endpoint-independent mapping requirements ⓘ NAT64 load-balancing considerations ⓘ NAT64 redundancy considerations ⓘ NAT64 timeout behavior ⓘ NAT64 well-known prefix usage ⓘ stateful NAT64 ⓘ translation of IPv4 packets to IPv6 packets ⓘ translation of IPv6 packets to IPv4 packets ⓘ |
| documentType | Technical specification ⓘ |
| enables | communication from IPv6-only clients to IPv4 servers ⓘ |
| focusesOn |
IPv4 server connectivity
ⓘ
IPv6-only client networks ⓘ |
| language | English ⓘ |
| obsoletes | RFC 2766 ⓘ |
| protocolFamily | Internet Protocol ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| relatedTo |
DNS64
ⓘ
IPv4-IPv6 protocol translation ⓘ IPv6 transition mechanisms ⓘ NAT64 ⓘ RFC 6147 ⓘ |
| specifies |
DNS64 interaction considerations
ⓘ
ICMP and ICMPv6 translation behavior ⓘ address mapping behavior for NAT64 ⓘ behavior of NAT64 ⓘ error handling for NAT64 ⓘ hairpinning behavior for NAT64 ⓘ logging requirements for NAT64 ⓘ requirements for NAT64 ⓘ session state maintenance for NAT64 ⓘ |
| standardizes |
stateful IPv4-to-IPv6 translation
ⓘ
stateful IPv6-to-IPv4 translation ⓘ |
| status | Proposed Standard ⓘ |
| title |
NAT64
ⓘ
surface form:
Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers
|
| updates |
RFC 4787
ⓘ
RFC 5382 ⓘ RFC 5508 ⓘ |
| workingGroup | Behave ⓘ |
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 6146 Description of subject: RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.