RFC 6052
E127875
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 6052 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T1077171 — 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 6052 Context triple: [NAT64, relatedRFC, RFC 6052]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
E.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
- 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 6052 Target entity description: 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.
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
E.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet Standard ⓘ |
| area | Internet Area ⓘ |
| author |
I. van Beijnum
ⓘ
M. Bagnulo ⓘ P. Matthews ⓘ |
| category | Standards Track ⓘ |
| defines |
IPv4-embedded IPv6 addresses
ⓘ
IPv6 address format for representing IPv4 addresses ⓘ Network-Specific Prefix for IPv4-embedded IPv6 addresses ⓘ Well-Known Prefix for IPv4-embedded IPv6 addresses ⓘ address format for IPv4/IPv6 translators ⓘ address format for NAT64 ⓘ address format for stateful IPv4/IPv6 translation ⓘ address format for stateless IPv4/IPv6 translation ⓘ |
| definesFor |
stateful NAT64 translation
ⓘ
stateless IP/ICMP translation ⓘ |
| documentType |
IETF Internet standards process
ⓘ
surface form:
Standards Track RFC
|
| intendedUse | IPv4-IPv6 interoperability ⓘ |
| introduces | Well-Known Prefix 64:ff9b::/96 ⓘ |
| obsoletes |
RFC 2765
ⓘ
RFC 2766 ⓘ |
| publicationDate | October 2010 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
DNS64
ⓘ
IPv4/IPv6 transition mechanisms ⓘ IPv6 transition ⓘ NAT64 ⓘ |
| RFCNumber | 6052 ⓘ |
| specifies |
/32 IPv6 prefix option
ⓘ
/40 IPv6 prefix option ⓘ /48 IPv6 prefix option ⓘ /56 IPv6 prefix option ⓘ /64 IPv6 prefix option ⓘ /96 IPv6 prefix option ⓘ 32-bit IPv4 address embedding in IPv6 ⓘ IPv6 prefix length options for IPv4-embedded addresses ⓘ |
| standardsTrackStatus | Proposed Standard ⓘ |
| status | Active ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title |
NAT64
ⓘ
surface form:
IPv6 Addressing of IPv4/IPv6 Translators
|
| updates |
RFC 4038
ⓘ
RFC 4291 ⓘ |
| uses |
IPv4-embedded IPv6 addresses in DNS64-based translation
ⓘ
IPv4-embedded IPv6 addresses in NAT64 ⓘ |
| workingGroup |
IETF BEHAVE working group
ⓘ
surface form:
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 6052 Description of subject: 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.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.