Finding the Authoritative Registration Data (RDAP) Service
draft-ietf-weirds-bootstrap-03

The information below is for an old version of the document
Document Type Active Internet-Draft (weirds WG)
Last updated 2014-06-28
Replaces draft-blanchet-weirds-bootstrap-ianaregistries
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Sep 2014 - Draft describing boo... )
Document shepherd Olaf Kolkman
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        M. Blanchet
Internet-Draft                                              G. Guillaume
Intended status: Standards Track                                Viagenie
Expires: December 30, 2014                                 June 28, 2014

       Finding the Authoritative Registration Data (RDAP) Service
                   draft-ietf-weirds-bootstrap-03.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.

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 30, 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.

Blanchet & Guillaume    Expires December 30, 2014               [Page 1]
Internet-Draft     Finding Authoritative RDAP service          June 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used In This Document . . . . . . . . . . . . . .   2
   3.  Structure of RDAP Bootstrap Registries  . . . . . . . . . . .   3
   4.  Domain Name RDAP Bootstrap Registry . . . . . . . . . . . . .   3
   5.  Internet Numbers RDAP Bootstrap Registries  . . . . . . . . .   4
     5.1.  IPv4 Address Space RDAP Bootstrap Registry  . . . . . . .   5
     5.2.  IPv6 Address Space RDAP Registry  . . . . . . . . . . . .   6
     5.3.  Autonomous Systems RDAP Bootstrap Registry  . . . . . . .   6
   6.  Entity  . . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Non-existent Entries or RDAP URL Values . . . . . . . . . . .   7
   8.  Deployment and Implementation Considerations  . . . . . . . .   8
   9.  Limitations . . . . . . . . . . . . . . . . . . . . . . . . .   8
   10. Security Considerations . . . . . . . . . . . . . . . . . . .   9
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   12. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     13.2.  Non-Normative References . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Querying and retrieving registration data from registries are defined
   in the Registration Data Access Protocol(RDAP)[I-D.ietf-weirds-rdap-q
   uery][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.

   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 create these
   registries for the specific purpose of RDAP use, herein named RDAP
   Bootstrap registries.  An RDAP client fetches the RDAP bootstrap
   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.  Conventions Used In This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

Blanchet & Guillaume    Expires December 30, 2014               [Page 2]
Internet-Draft     Finding Authoritative RDAP service          June 2014
Show full document text