CurrentBEST CURRENT PRACTICEIETF streamBCP221

RFC 8521: Registration Data Access Protocol (RDAP) Object Tagging

In plain English — editorial summary, not part of the RFC

The Registration Data Access Protocol (RDAP) includes a method that can be used to identify the authoritative server for processing domain name, IP address, and autonomous system number queries. The method does not describe how to identify the authoritative server for processing other RDAP query types, such as entity queries. This limitation exists because the identifiers associated with these query types are typically unstructured. This document updates RFC 7484 by describing an operational practice that can be used to add structure to RDAP identifiers and that makes it possible to identify the authoritative server for additional RDAP queries.

Document record

Document ID
RFC8521
Published
November 2018
Authors
S. Hollenbeck; A. Newton
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
ops
Pages
13
Also known as
BCP221
Updates:
RFC 7484

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8521-registration-data-access-protocol-rdap-object-tagging