Finding the Authoritative Registration Data (RDAP) Service
RFC 7484
| Document | Type |
RFC - Proposed Standard
(March 2015; Errata)
Updated by RFC 8521
|
|
|---|---|---|---|
| Last updated | 2018-08-16 | ||
| Replaces | draft-blanchet-weirds-bootstrap-ianaregistries | ||
| Stream | IETF | ||
| Formats | plain text pdf htmlized with errata bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Mick Szucs | ||
| Shepherd write-up | Show (last changed 2014-09-30) | ||
| IESG | IESG state | RFC 7484 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Pete Resnick | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) M. Blanchet
Request for Comments: 7484 Viagenie
Category: Standards Track March 2015
ISSN: 2070-1721
Finding the Authoritative Registration Data (RDAP) Service
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 is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7484.
Copyright Notice
Copyright (c) 2015 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 Standards Track [Page 1]
RFC 7484 Finding Authoritative RDAP Service March 2015
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Structure of the RDAP Bootstrap Service Registries . . . . . 3
4. Bootstrap Service Registry for Domain Name Space . . . . . . 5
5. Bootstrap Service Registries for Internet Numbers . . . . . . 6
5.1. Bootstrap Service Registry for IPv4 Address Space . . . . 7
5.2. Bootstrap Service Registry for IPv6 Address Space . . . . 8
5.3. Bootstrap Service Registry for AS Number Space . . . . . 9
6. Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
7. Non-existent Entries or RDAP URL Values . . . . . . . . . . . 10
8. Deployment and Implementation Considerations . . . . . . . . 10
9. Limitations . . . . . . . . . . . . . . . . . . . . . . . . . 11
10. Formal Definition . . . . . . . . . . . . . . . . . . . . . . 11
10.1. Imported JSON Terms . . . . . . . . . . . . . . . . . . 11
10.2. Registry Syntax . . . . . . . . . . . . . . . . . . . . 12
11. Security Considerations . . . . . . . . . . . . . . . . . . . 13
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
12.1. Bootstrap Service Registry for IPv4 Address Space . . . 14
12.2. Bootstrap Service Registry for IPv6 Address Space . . . 14
12.3. Bootstrap Service Registry for AS Number Space . . . . . 14
12.4. Bootstrap Service Registry for Domain Name Space . . . . 15
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
13.1. Normative References . . . . . . . . . . . . . . . . . . 15
13.2. Informative References . . . . . . . . . . . . . . . . . 15
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 17
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction
Querying and retrieving registration data from registries are defined
in Registration Data Access Protocol (RDAP) [RFC7480] [RFC7482]
[RFC7483]. 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.
Top-Level Domains (TLDs), Autonomous System (AS) numbers, and network
blocks are delegated by IANA to Internet registries such as TLD
registries and Regional Internet Registries (RIRs) that then issue
further delegations and maintain information about them. Thus, the
bootstrap information needed by RDAP clients is best generated from
data and processes already maintained by IANA; the relevant
registries already exist at [ipv4reg], [ipv6reg], [asreg], and
[domainreg].
Blanchet Standards Track [Page 2]
RFC 7484 Finding Authoritative RDAP Service March 2015
Per this document, IANA has created new registries based on a JSON
format specified in this document, herein named RDAP Bootstrap
Show full document text