Redirection Service for Registration Data Access Protocol

The information below is for an old version of the document
Document Type Expired Internet-Draft (weirds WG)
Last updated 2014-01-16 (latest revision 2013-07-15)
Replaces draft-lacnic-weirds-restwhois-redirects
Stream IETF
Intended RFC status (None)
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Sep 2014 - draft-ietf-weirds-re... )
Document shepherd None
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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 Martínez (
Arturo Servin (
Linlin Zhou (
Dario Gomez (
Gerardo Rada (

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