Skip to main content

Registration Data Access Protocol (RDAP) Object Tagging
RFC 8521 also known as BCP 221

Revision differences

Document history

Date By Action
2023-12-12
(System) Imported membership of rfc8521 in bcp221 via sync to the rfc-index
2023-12-12
(System) No history of BCP221 is currently available in the datatracker before this point
2019-11-09
(System) Received changes through RFC Editor sync (added Errata tag)
2018-11-21
(System) IANA registries were updated to include RFC8521
2018-11-19
(System)
Received changes through RFC Editor sync (created alias RFC 8521, changed abstract to 'The Registration Data Access Protocol (RDAP) includes a method that can …
Received changes through RFC Editor sync (created alias RFC 8521, changed abstract to '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.', changed pages to 13, changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2018-11-19, changed IESG state to RFC Published, created updates relation between draft-ietf-regext-rdap-object-tag and RFC 7484, created alias BCP 221)
2018-11-19
(System) RFC published