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 |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
|
|
|---|---|---|---|
| Author | Marc Blanchet | ||
| Last updated | 2013-06-05 | ||
| Replaced by | draft-ietf-weirds-bootstrap, RFC 7484 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-blanchet-weirds-bootstrap-ianaregistries-00
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
address is located in the corresponding "RDAP URL" column for that
entry, which could be http://rdap.example.org/rdap.
3. Internet Numbers Registry
3.1. IPv4 Address Space
The IPv4 address space authoritative registration data service is
found by doing a longest match of the target address with the values
of the Prefix column in the IANA IPv4 address space
registry[ipv4reg]. The value of the "RDAP URL" column is the base
RDAP url as described in [I-D.ietf-weirds-rdap-query].
For example, a query for "192.0.2.0/24" matches the "192/8" entry in
the Prefix column of the registry. The RDAP server URL for this
address is located in the corresponding "RDAP URL" column for that
entry, which could be http://rdap.example.org/rdap.
3.2. IPv6 Address Space
The IPv6 address space authoritative registration data service is
found by doing a longest match of the target address with the values
of the Prefix column in the IANA IPv6 address space
registry[ipv6reg]. The value of the "RDAP URL" column is the base
RDAP url as described in [I-D.ietf-weirds-rdap-query].
For example, a query for "2001:db8::/32" matches the "2001/16" entry
in the Prefix column of the registry. The RDAP server URL for this
address is located in the corresponding "RDAP URL" column for that
entry, which could be http://rdap.example.org/rdap.
3.3. Autonomous Systems
The Autonomous Systems (AS) authoritative registration data service
is found by identifying the range in which the target Autonomous
System is with the values of the Number column in the IANA Autonomous
Systems (AS) Numbers registry[asreg]. The value of the "RDAP URL"
column is the base RDAP url as described in
[I-D.ietf-weirds-rdap-query].
For example, a query for AS 65411 matches the "64512-65534" entry in
the Number column of the registry. The RDAP server URL for this
address is located in the corresponding "RDAP URL" column for that
entry, which could be http://rdap.example.org/rdap.
Blanchet Expires December 07, 2013 [Page 3]
Internet-Draft Finding Authoritative RDAP service June 2013
4. Nameserver
TBD
5. Entity
TBD
6. Non-existent Entries or RDAP URL Values
The registries may not contain the requested value or the RDAP URL
value may be empty. In these cases, there is no known RDAP server
for that requested value and the client should provide an appropriate
error message to the user.
7. Deployment Considerations
This method relies on the fact that RDAP clients are fetching the
IANA XML registries. Clients SHOULD not fetch every time the XML
files. Clients should rely on HTTP headers to verify if the registry
has changed since last time it was fetched.
IANA should make sure that the service of those registries is able to
cope with a larger demand and should take appropriate measures such
as caching and load balancing.
This specification makes no assumption on how the authorities of
registration data may work together on sharing their information for
a common service.
8. Security Considerations
TBD
9. IANA Considerations
IANA is requested to do the following:
o Add the "RDAP URL" column to the IPv4 Address Space, IPv6 Address
Space and Autonomous Systems Numbers registries. The same
entities who are registrants for these spaces are entitled to
provide the RDAP URL value for their respective space.
o Create a new registry of domain names with the following columns:
Domain and RDAP URL. The content should be initially populated by
an extract of the Root zone database. A change happens in the
database may trigger a change in that new registry. The same
entities who are registrants for the root zone database entries
Blanchet Expires December 07, 2013 [Page 4]
Internet-Draft Finding Authoritative RDAP service June 2013
are entitled to provide the RDAP URL value for their domain. IANA
shall update its procedures to include the provisioning of these
values.
o author note: more details needed
10. Acknowledgements
The weirds working group had multiple discussions on this topic,
including a session during IETF 84. All the people involved in these
discussions are herin acknowledged. XXX have provided input and
suggestions to this document.
11. Normative References
[I-D.ietf-weirds-json-response]
Newton, A. and S. Hollenbeck, "JSON Responses for the
Registration Data Access Protocol (RDAP)", draft-ietf-
weirds-json-response-03 (work in progress), April 2013.
[I-D.ietf-weirds-rdap-query]
Newton, A. and S. Hollenbeck, "Registration Data Access
Protocol Lookup Format", draft-ietf-weirds-rdap-query-04
(work in progress), April 2013.
[I-D.ietf-weirds-using-http]
Newton, A., Ellacott, B., and N. Kong, "HTTP usage in the
Registration Data Access Protocol (RDAP)", draft-ietf-
weirds-using-http-05 (work in progress), May 2013.
[asreg] Internet Assigned Numbers Authority(IANA), ., "Autonomous
System (AS) Numbers", , <http://www.iana.org/assignments/
as-numbers/as-numbers.xml>.
[domainreg]
Internet Assigned Numbers Authority(IANA), ., "TBD", ,
<http://www.iana.org/assignments/tbd/tbd.xml>.
[ipv4reg] Internet Assigned Numbers Authority(IANA), ., "IPv4
Address Space", , <http://www.iana.org/assignments/ipv4
-address-space/ipv4-address-space.xml>.
[ipv6reg] Internet Assigned Numbers Authority(IANA), ., "IPv6 Global
Unicast Address Assignments", , <http://www.iana.org/
assignments/ipv6-unicast-address-assignments/ipv6-unicast-
address-assignments.xml>.
Blanchet Expires December 07, 2013 [Page 5]
Internet-Draft Finding Authoritative RDAP service June 2013
Author's Address
Marc Blanchet
Viagenie
246 Aberdeen
Quebec, QC G1R 2E1
Canada
Email: Marc.Blanchet@viagenie.ca
URI: http://www.viagenie.ca
Blanchet Expires December 07, 2013 [Page 6]