RFC 7480
E766426
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).
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 7480 canonical | 5 |
How this entity was disambiguated
This entity first appeared as the object of triple T8918655 — 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 7480 Context triple: [RDAP, definedInRFC, RFC 7480]
-
A.
RFC 7472
RFC 7472 is an Internet Engineering Task Force (IETF) specification that defines extensions and mechanisms for the Internet Printing Protocol (IPP), enhancing network printing capabilities and interoperability.
-
B.
RFC 7320
RFC 7320 is an Internet Engineering Task Force (IETF) document that provided guidelines and best practices for the use and management of URI registries in Internet protocols.
-
C.
RFC 6840
RFC 6840 is an Internet Engineering Task Force (IETF) standards document that clarifies, updates, and consolidates the core specifications for the DNS Security Extensions (DNSSEC) protocol suite.
-
D.
RFC 3980
RFC 3980 is an Internet Engineering Task Force (IETF) document that previously specified aspects of the iSCSI (Internet Small Computer Systems Interface) protocol before being superseded by RFC 7143.
-
E.
RFC 7720
RFC 7720 is an IETF standards document that specifies the technical and operational requirements for the DNS Root Server System.
- 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 7480 Target entity description: 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).
-
A.
RFC 7472
RFC 7472 is an Internet Engineering Task Force (IETF) specification that defines extensions and mechanisms for the Internet Printing Protocol (IPP), enhancing network printing capabilities and interoperability.
-
B.
RFC 7320
RFC 7320 is an Internet Engineering Task Force (IETF) document that provided guidelines and best practices for the use and management of URI registries in Internet protocols.
-
C.
RFC 6840
RFC 6840 is an Internet Engineering Task Force (IETF) standards document that clarifies, updates, and consolidates the core specifications for the DNS Security Extensions (DNSSEC) protocol suite.
-
D.
RFC 3980
RFC 3980 is an Internet Engineering Task Force (IETF) document that previously specified aspects of the iSCSI (Internet Small Computer Systems Interface) protocol before being superseded by RFC 7143.
-
E.
RFC 7720
RFC 7720 is an IETF standards document that specifies the technical and operational requirements for the DNS Root Server System.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet standard specification ⓘ |
| abbreviation |
RDAP HTTP Usage
ⓘ
linked to:
RDAP
|
| addresses |
internationalization considerations for RDAP over HTTP
ⓘ
operational deployment considerations for RDAP ⓘ privacy considerations for RDAP over HTTP ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
HTTP header field usage for RDAP
ⓘ
HTTP methods allowed for RDAP ⓘ HTTP status code usage for RDAP ⓘ HTTP usage for RDAP ⓘ base URL structure for RDAP ⓘ caching considerations for RDAP ⓘ error handling for RDAP over HTTP ⓘ redirection handling for RDAP ⓘ transport considerations for RDAP ⓘ |
| definesUsageOf |
HTTP
ⓘ
HTTPS ⓘ |
| focusesOn |
operational considerations for RDAP over HTTP
ⓘ
security considerations for RDAP over HTTP ⓘ transport of RDAP over HTTP ⓘ |
| intendedFor |
developers of RDAP clients
ⓘ
operators of RDAP services ⓘ registry operators ⓘ |
| language | English ⓘ |
| number | 7480 ⓘ |
| obsoletedBy | none ⓘ |
| obsoletes | none ⓘ |
| partOf |
RDAP specification suite
ⓘ
linked to:
RDAP
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 7481
ⓘ
RFC 7482 ⓘ RFC 7483 ⓘ RFC 7484 ⓘ Registration Data Access Protocol ⓘ |
| specifies |
use of HTTP over TLS for RDAP
ⓘ
use of HTTPS as the RECOMMENDED transport for RDAP ⓘ |
| specifiesProtocol | Registration Data Access Protocol ⓘ |
| standardizes | transport layer behavior for RDAP ⓘ |
| status | Proposed Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title |
HTTP Usage in the Registration Data Access Protocol (RDAP)
ⓘ
linked to:
Registration Data Access Protocol
|
| updatedBy | none ⓘ |
| updates | none ⓘ |
| 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 7480 Description of subject: 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).
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.