Redirection Service for Registration Data Access Protocol
draft-ietf-weirds-redirects-03

The information below is for an old version of the document
Document Type Active Internet-Draft (weirds WG)
Last updated 2014-02-14
Replaces draft-lacnic-weirds-restwhois-redirects
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Sep 2014 - draft-ietf-weirds-re... )
Document shepherd Murray Kucherawy
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                         C. Martinez, Ed.
Internet-Draft                                                    LACNIC
Intended status: Informational                              L. Zhou, Ed.
Expires: August 18, 2014                                           CNNIC
                                                                 G. Rada
                                                                  LACNIC
                                                       February 14, 2014

       Redirection Service for Registration Data Access Protocol
                     draft-ietf-weirds-redirects-03

Abstract

   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).

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any

Martinez, et al.         Expires August 18, 2014                [Page 1]
Internet-Draft          RDAP Redirection Service           February 2014

   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 18, 2014.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Martinez, et al.         Expires August 18, 2014                [Page 2]
Internet-Draft          RDAP Redirection Service           February 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 4
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . . . 4
   2.  Proposed Approach . . . . . . . . . . . . . . . . . . . . . . . 4
     2.1.  The REST Approach to Web Services . . . . . . . . . . . . . 4
     2.2.  Query Redirection for RDAP Queries  . . . . . . . . . . . . 4
     2.3.  A Joint RDAP Tree through HTTP Redirection  . . . . . . . . 5
     2.4.  The Redirection Table. The Bootstrap Problem. . . . . . . . 7
     2.5.  Loops in Redirection  . . . . . . . . . . . . . . . . . . . 8
     2.6.  Service Discovery . . . . . . . . . . . . . . . . . . . . . 8
     2.7.  Security Considerations . . . . . . . . . . . . . . . . . . 8
   3.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 8
     3.1.  Normative References  . . . . . . . . . . . . . . . . . . . 8
     3.2.  Informative References  . . . . . . . . . . . . . . . . . . 8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 9

Martinez, et al.         Expires August 18, 2014                [Page 3]
Internet-Draft          RDAP Redirection Service           February 2014

1.  Introduction

   A user interested in obtaining registration information for a given
   number or domain resource normally uses the WHOIS service provided by
   the RIRs and DNRs.

   In order to avoid having to query several databases until obtaining
   an answer, some approaches have been discussed and implemented in the
   past, most notably the Joint WHOIS [lacnic-joint-whois] initiative.
Show full document text