Skip to main content

Redirection Service for Registration Data Access Protocol

Document Type Expired Internet-Draft (weirds WG)
Expired & archived
Authors Carlos M. Martínez , Linlin Zhou , Gerardo Rada
Last updated 2015-01-05 (Latest revision 2014-07-04)
Replaces draft-lacnic-weirds-restwhois-redirects
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state Dead WG Document
Document shepherd Murray Kucherawy
IESG IESG state Expired
Consensus boilerplate Unknown
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:


The traditional WHOIS protocol has several important shortcomings, and over the past few years several approaches to a better Registration Data Access Protocol (RDAP) have been discussed and proposed. It is worth noting that the term WHOIS is sometimes used interchangeably to mean either (a) the registration data itself or (b) the protocol used to access registration data Among these shortcomings, different registries operate different WHOIS services. For users this means that several WHOIS queries to different registries may be necessary in order to obtain data for a given resource. This document describes a redirection service for RDAP queries. This service allows clients to query a single RDAP service and expect either an authoritative answer or a redirection hint pointing to another, possibly authoritative, RDAP server. The solution implemented proposed here applies to Regional Internet Registries(RIRs) and Domain Name Registries(DNRs).


Carlos M. Martínez
Linlin Zhou
Gerardo Rada

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