Finding the Authoritative Registration Data (RDAP) Service
draft-blanchet-weirds-bootstrap-ianaregistries-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-06-05
Replaced by rfc7484, draft-ietf-weirds-bootstrap
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        M. Blanchet
Internet-Draft                                                  Viagenie
Intended status: Informational                             June 05, 2013
Expires: December 07, 2013

       Finding the Authoritative Registration Data (RDAP) Service
         draft-blanchet-weirds-bootstrap-ianaregistries-00.txt

Abstract

   This document specifies a method to find which Registration Data
   Access Protocol (RDAP) server is authoritative to answer queries for
   a requested scope, such as domain names, IP addresses or Autonomous
   System numbers, using data available in IANA registries.

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

   This Internet-Draft will expire on December 07, 2013.

Copyright Notice

   Copyright (c) 2013 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.

Blanchet                Expires December 07, 2013               [Page 1]
Internet-Draft     Finding Authoritative RDAP service          June 2013

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Domain Name Registry  . . . . . . . . . . . . . . . . . . . .   2
   3.  Internet Numbers Registry . . . . . . . . . . . . . . . . . .   3
     3.1.  IPv4 Address Space  . . . . . . . . . . . . . . . . . . .   3
     3.2.  IPv6 Address Space  . . . . . . . . . . . . . . . . . . .   3
     3.3.  Autonomous Systems  . . . . . . . . . . . . . . . . . . .   3
   4.  Nameserver  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Entity  . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Non-existent Entries or RDAP URL Values . . . . . . . . . . .   4
   7.  Deployment Considerations . . . . . . . . . . . . . . . . . .   4
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   11. Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Querying and retrieving registration data from registries are defined
   in the Registration Data Access Protocol(RDAP)[I-D.ietf-weirds-rdap-
   query][I-D.ietf-weirds-using-http][I-D.ietf-weirds-json-response].
   These documents do not specify where to send the queries.  This
   document specifies a method to find which server is authoritative to
   answer queries for the requested scope.

   (author note: should it have some text on various possibilities that
   have been discussed, such as IETF84...?)

   The proposed mechanism is based on that allocation data for domain
   names and IP addresses are maintained by IANA, are publicly available
   and are in a structured format.  The mechanism assumes some data
   structure within these registries and request IANA to modify these
   registries for the specific purpose of RDAP use.  An RDAP client
   fetches the registries, extract the data and then do a match with the
   query data to find the authoritative registration data server and
   appropriate query base URL.

2.  Domain Name Registry

   The domain names authoritative registration data service is found by
   doing the longest match of the target domain name with the values of
   the Domain column in the IANA Domain Name registry[domainreg].  The
   value of the "RDAP URL" column is the base RDAP url as described in
   [I-D.ietf-weirds-rdap-query].

Blanchet                Expires December 07, 2013               [Page 2]
Internet-Draft     Finding Authoritative RDAP service          June 2013

   For example, a RDAP query for example.com matches the .com entry in
   the Domain column of the registry.  The RDAP server URL for this
Show full document text