LACNIC's Redirection Service for Number Resource RESTful WHOIS Queries
draft-ietf-weirds-redirects-00

The information below is for an old version of the document
Document Type Active Internet-Draft (weirds WG)
Last updated 2012-10-15
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 None
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                                            A. Servin, Ed.
Intended status: Informational                                  D. Gomez
Expires: April 18, 2013                                          G. Rada
                                                                  LACNIC
                                                        October 15, 2012

 LACNIC's Redirection Service for Number Resource RESTful WHOIS Queries
                     draft-ietf-weirds-redirects-00

Abstract

   The traditional WHOIS protocol has several important shortcomings,
   and over the past few years several approaches to a better WHOIS have
   been discussed and proposed.

   Among these shortcomings, different registries operate different
   WHOIS services.  For users this implies that several WHOIS queries to
   different registries may be necessary in order to obtain data for a
   given resource.

   This document describes a proof-of-concept redirection service for
   RESTful WHOIS queries as implemented by LACNIC.  This service allows
   users to query a single WHOIS service and be redirected to the
   authoritative registry.

   The main goal of this document is to encourage discussion on the
   topics of Joint WHOIS services and query redirection in a RESTful
   WHOIS world.

   The solution implemented by LACNIC proposed here applies to numbering
   resources (IPv4, IPv6 and autonomous system numbers).

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
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Martinez, et al.         Expires April 18, 2013                 [Page 1]
Internet-Draft   LACNIC's RESTWhois Redirection Service     October 2012

   This Internet-Draft will expire on April 18, 2013.

Copyright Notice

   Copyright (c) 2012 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 April 18, 2013                 [Page 2]
Internet-Draft   LACNIC's RESTWhois Redirection Service     October 2012

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 RESTful WHOIS queries  . . . . . . .  5
     2.3.  A global Joint WHOIS trough HTTP redirection . . . . . . .  5
     2.4.  Loops in redirection . . . . . . . . . . . . . . . . . . .  9
   3.  LACNIC RESTful WHOIS redirector implementation . . . . . . . . 12
     3.1.  Accessing the redirector . . . . . . . . . . . . . . . . . 12
       3.1.1.  Redirection URI  . . . . . . . . . . . . . . . . . . . 12
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13
   5.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     5.1.  Normative References . . . . . . . . . . . . . . . . . . . 13
     5.2.  Informative References . . . . . . . . . . . . . . . . . . 13
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14

Martinez, et al.         Expires April 18, 2013                 [Page 3]
Internet-Draft   LACNIC's RESTWhois Redirection Service     October 2012

1.  Introduction

   A user interested in obtaining registration information for a given
   number resource normally uses the WHOIS service provided by the RIRs
   (AfriNIC, APNIC, ARIN, LACNIC and RIPE-NCC).

   In order 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.
   However, among other shortcomings, Joint WHOIS is implemented using
Show full document text