RFC 6145
E129973
RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
All labels observed (3)
| Label | Occurrences |
|---|---|
| RFC 6145 canonical | 8 |
| IETF RFC 6145 | 1 |
| RFC 6145 title IP/ICMP Translation Algorithm | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1077172 — 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 6145 Context triple: [NAT64, relatedRFC, RFC 6145]
-
A.
RFC 6146
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.
-
B.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
-
C.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
-
D.
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.
-
E.
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.
- 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 6145 Target entity description: RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
-
A.
RFC 6146
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.
-
B.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
-
C.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
-
D.
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.
-
E.
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.
- F. None of above. chosen
Statements (51)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet Standard ⓘ |
| area | Internet Area ⓘ |
| author |
C. Bao
ⓘ
F. Bagnulo ⓘ
linked to:
M. Bagnulo
F. Baker ⓘ K. Yin ⓘ Xing Li ⓘ |
| category | Standards Track ⓘ |
| defines |
IP/ICMP stateless translation algorithm
ⓘ
checksum adjustment rules for translated packets ⓘ stateless IP/ICMP translation for NAT64 ⓘ stateless translation between IPv4 and IPv6 headers ⓘ translation behavior for ICMP between IPv4 and IPv6 ⓘ translation behavior for ICMPv4 and ICMPv6 error messages ⓘ translation behavior for IPv4 options and IPv6 extension headers ⓘ |
| documentType | Standards Track RFC ⓘ |
| hasRFCEditorURL | https://www.rfc-editor.org/rfc/rfc6145 ⓘ |
| intendedFor |
implementers of NAT64 and translation devices
ⓘ
network operators ⓘ protocol designers ⓘ |
| intendedUse |
IPv4-IPv6 coexistence
ⓘ
IPv4-IPv6 interconnection ⓘ |
| language | English ⓘ |
| number | 6145 ⓘ |
| obsoletes | RFC 2765 ⓘ |
| partOf | IPv6 transition and coexistence specifications ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publishedOn | 2011-04 ⓘ |
| relatedTo |
IPv4
ⓘ
IPv4-IPv6 transition mechanisms ⓘ IPv6 ⓘ
linked to:
Internet Protocol version 6
NAT64 ⓘ |
| securityConsiderations | discusses security implications of IP/ICMP translation ⓘ |
| series |
Request for Comments
ⓘ
linked to:
RFCs
|
| specifies |
handling of DF (Don’t Fragment) bit in IPv4 during translation
ⓘ
handling of Path MTU Discovery during translation ⓘ handling of fragmentation during translation ⓘ mapping of IPv4 addresses to IPv6 addresses using IPv4-embedded IPv6 addresses ⓘ stateless translation mechanism between IPv4 and IPv6 packet headers ⓘ translation of ICMPv4 messages to ICMPv6 messages ⓘ translation of ICMPv6 messages to ICMPv4 messages ⓘ translation of IPv4 headers to IPv6 headers ⓘ translation of IPv6 headers to IPv4 headers ⓘ |
| status | Proposed Standard ⓘ |
| stream | IETF Stream ⓘ |
| title | IP/ICMP Translation Algorithm ⓘ |
| updates | RFC 6052 ⓘ |
| uses | IPv4-embedded IPv6 address format defined in RFC 6052 ⓘ |
| workingGroup |
Behave Working Group
ⓘ
linked to:
IETF BEHAVE working group
|
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 6145 Description of subject: RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
Referenced by (10)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 6145
linked to: RFC 6145