RFC 7484
E773538
RFC 7484 is an IETF standards document that specifies how the Registration Data Access Protocol (RDAP) uses HTTP-based bootstrapping to locate authoritative servers for domain, IP address, and autonomous system number registration data.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 7484 canonical | 6 |
How this entity was disambiguated
This entity first appeared as the object of triple T8918659 — 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 7484 Context triple: [RDAP, definedInRFC, RFC 7484]
-
A.
RFC 7684
RFC 7684 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the earlier OSPFv3 specification defined in RFC 5340.
-
B.
RFC 7483
RFC 7483 is the IETF specification that defines the JSON-based data format and usage for the Registration Data Access Protocol (RDAP) used to query domain and network registration information.
-
C.
RFC 7482
RFC 7482 is the IETF specification that defines the HTTP-based query format and usage for the Registration Data Access Protocol (RDAP).
-
D.
RFC 7480
RFC 7480 is an Internet Engineering Task Force (IETF) standard that specifies the HTTP usage and transport considerations for the Registration Data Access Protocol (RDAP).
-
E.
RFC 7481
RFC 7481 is an IETF standards document that specifies the security services and requirements for the Registration Data Access Protocol (RDAP).
- 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 7484 Target entity description: RFC 7484 is an IETF standards document that specifies how the Registration Data Access Protocol (RDAP) uses HTTP-based bootstrapping to locate authoritative servers for domain, IP address, and autonomous system number registration data.
-
A.
RFC 7684
RFC 7684 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the earlier OSPFv3 specification defined in RFC 5340.
-
B.
RFC 7483
RFC 7483 is the IETF specification that defines the JSON-based data format and usage for the Registration Data Access Protocol (RDAP) used to query domain and network registration information.
-
C.
RFC 7482
RFC 7482 is the IETF specification that defines the HTTP-based query format and usage for the Registration Data Access Protocol (RDAP).
-
D.
RFC 7480
RFC 7480 is an Internet Engineering Task Force (IETF) standard that specifies the HTTP usage and transport considerations for the Registration Data Access Protocol (RDAP).
-
E.
RFC 7481
RFC 7481 is an IETF standards document that specifies the security services and requirements for the Registration Data Access Protocol (RDAP).
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet standard ⓘ |
| appliesTo |
Autonomous System Number registration data
ⓘ
IP address registration data ⓘ domain name registration data ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
bootstrapping for Autonomous System Number RDAP queries
ⓘ
bootstrapping for IP address RDAP queries ⓘ bootstrapping for domain name RDAP queries ⓘ |
| definesProtocol | HTTP-based bootstrapping for RDAP ⓘ |
| definesTerm | RDAP bootstrap ⓘ |
| documentType | Standards Track RFC ⓘ |
| focusesOn |
locating authoritative RDAP servers
ⓘ
mapping registration data queries to RDAP base URLs ⓘ |
| format | Text ⓘ |
| hostedAt | https://www.rfc-editor.org/rfc/rfc7484 ⓘ |
| identifier | RFC 7484 ⓘ |
| intendedAudience |
Internet registry operators
ⓘ
RDAP implementers ⓘ |
| language | English ⓘ |
| obsoletedBy | None ⓘ |
| obsoletes | None ⓘ |
| organizationInvolved |
IANA
ⓘ
Internet Assigned Numbers Authority ⓘ |
| protocol | Registration Data Access Protocol ⓘ |
| publicationDate | 2015-03 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| registryDependency | IANA RDAP Bootstrap Registries ⓘ |
| relatedTo |
Autonomous System Number registration data
ⓘ
DNS ⓘ
linked to:
Domain Name System
IP address registration data ⓘ RDAP ⓘ WHOIS ⓘ
linked to:
WHOIS protocol
|
| shortName |
RDAP Bootstrap
ⓘ
linked to:
RDAP
|
| specifies |
bootstrapping mechanism for RDAP based on IANA registries
ⓘ
how RDAP clients discover authoritative RDAP servers ⓘ use of HTTP redirects and bootstrapping data for RDAP ⓘ |
| status | Proposed Standard ⓘ |
| stdStatus | Standards Track ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title | Finding the Authoritative Registration Data (RDAP) Service ⓘ |
| updatedBy | None ⓘ |
| updates | None ⓘ |
| usesTransport | HTTP ⓘ |
| workingGroup | WEIRDS ⓘ |
| year | 2015 ⓘ |
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 7484 Description of subject: RFC 7484 is an IETF standards document that specifies how the Registration Data Access Protocol (RDAP) uses HTTP-based bootstrapping to locate authoritative servers for domain, IP address, and autonomous system number registration data.
Referenced by (6)
Full triples — surface form annotated when it differs from this entity's canonical label.