RFC 8056
E766427
RFC 8056 is an IETF specification that extends the Registration Data Access Protocol (RDAP) with support for RDAP object tags and other features to improve registration data management and retrieval.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 8056 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T8918660 — 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 8056 Context triple: [RDAP, definedInRFC, RFC 8056]
-
A.
RFC 8536
RFC 8536 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier specifications to define the modern format and handling of time zone data in the Internet ecosystem.
-
B.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
C.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
-
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 8552
RFC 8552 is an Internet Engineering Task Force (IETF) standards document that specifies technical protocols and procedures used in Internet communications.
- 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 8056 Target entity description: RFC 8056 is an IETF specification that extends the Registration Data Access Protocol (RDAP) with support for RDAP object tags and other features to improve registration data management and retrieval.
-
A.
RFC 8536
RFC 8536 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier specifications to define the modern format and handling of time zone data in the Internet ecosystem.
-
B.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
C.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
-
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 8552
RFC 8552 is an Internet Engineering Task Force (IETF) standards document that specifies technical protocols and procedures used in Internet communications.
- F. None of above. chosen
Statements (43)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| aimsTo |
enhance RDAP search and filtering capabilities
ⓘ
support better categorization of RDAP objects ⓘ |
| appliesTo |
RDAP IP network objects
ⓘ
RDAP autnum objects ⓘ RDAP domain objects ⓘ RDAP entity objects ⓘ RDAP nameserver objects ⓘ |
| area | Applications and Real-Time ⓘ |
| category | Standards Track ⓘ |
| defines |
RDAP object tags
ⓘ
semantics for RDAP object tags ⓘ |
| documentType | Internet Standards Track RFC ⓘ |
| extends | Registration Data Access Protocol ⓘ |
| focusesOn |
data tagging in RDAP
ⓘ
registration data ⓘ |
| format | text ⓘ |
| intendedFor |
RDAP service operators
ⓘ
domain name registrars ⓘ domain name registries ⓘ |
| language | English ⓘ |
| objective |
to improve registration data management
ⓘ
to improve registration data retrieval ⓘ |
| publicationYear | 2017 ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 7480
ⓘ
RFC 7481 ⓘ RFC 7482 ⓘ RFC 7483 ⓘ RFC 7484 ⓘ RFC 7485 ⓘ |
| rfcNumber | 8056 ⓘ |
| specifies |
JSON data structures for RDAP object tags
ⓘ
client behavior for RDAP object tags ⓘ processing rules for RDAP object tags ⓘ server behavior for RDAP object tags ⓘ |
| standardizes | representation of tags in RDAP responses ⓘ |
| status | Proposed Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title |
Extending the Registration Data Access Protocol (RDAP) with Object Tags
ⓘ
linked to:
RDAP
|
| updatesProtocol | RDAP ⓘ |
| workingGroup | WEIRDS ⓘ |
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 8056 Description of subject: RFC 8056 is an IETF specification that extends the Registration Data Access Protocol (RDAP) with support for RDAP object tags and other features to improve registration data management and retrieval.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.