Skip to main content

Registration Data Access Protocol (RDAP) Object Tagging
draft-hollenbeck-regext-rdap-object-tag-05

Document Type Replaced Internet-Draft (individual)
Authors Scott Hollenbeck , Andrew Newton
Last updated 2017-10-24
Replaced by RFC 8521
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-regext-rdap-object-tag
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

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 describes an operational practice that can be used to add structure to RDAP identifiers that makes it possible to identify the authoritative server for additional RDAP queries.

Authors

Scott Hollenbeck
Andrew Newton

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)