draft-ietf-weirds-rdap-query-09.txt   draft-ietf-weirds-rdap-query-10.txt 
Network Working Group A. Newton Network Working Group A. Newton
Internet-Draft ARIN Internet-Draft ARIN
Intended status: Standards Track S. Hollenbeck Intended status: Standards Track S. Hollenbeck
Expires: June 22, 2014 Verisign Labs Expires: August 8, 2014 Verisign Labs
December 19, 2013 February 4, 2014
Registration Data Access Protocol Query Format Registration Data Access Protocol Query Format
draft-ietf-weirds-rdap-query-09 draft-ietf-weirds-rdap-query-10
Abstract Abstract
This document describes uniform patterns to construct HTTP URLs that This document describes uniform patterns to construct HTTP URLs that
may be used to retrieve registration information from registries may be used to retrieve registration information from registries
(including both Regional Internet Registries (RIRs) and Domain Name (including both Regional Internet Registries (RIRs) and Domain Name
Registries (DNRs)) using "RESTful" web access patterns. Registries (DNRs)) using "RESTful" web access patterns.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 22, 2014. This Internet-Draft will expire on August 8, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 17 skipping to change at page 2, line 17
1. Conventions Used in This Document . . . . . . . . . . . . . . 2 1. Conventions Used in This Document . . . . . . . . . . . . . . 2
1.1. Acronyms and Abbreviations . . . . . . . . . . . . . . . 2 1.1. Acronyms and Abbreviations . . . . . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Path Segment Specification . . . . . . . . . . . . . . . . . 4 3. Path Segment Specification . . . . . . . . . . . . . . . . . 4
3.1. Lookup Path Segment Specification . . . . . . . . . . . . 4 3.1. Lookup Path Segment Specification . . . . . . . . . . . . 4
3.1.1. IP Network Path Segment Specification . . . . . . . . 5 3.1.1. IP Network Path Segment Specification . . . . . . . . 5
3.1.2. Autonomous System Path Segment Specification . . . . 5 3.1.2. Autonomous System Path Segment Specification . . . . 5
3.1.3. Domain Path Segment Specification . . . . . . . . . . 6 3.1.3. Domain Path Segment Specification . . . . . . . . . . 6
3.1.4. Name Server Path Segment Specification . . . . . . . 7 3.1.4. Name Server Path Segment Specification . . . . . . . 7
3.1.5. Entity Path Segment Specification . . . . . . . . . . 7 3.1.5. Entity Path Segment Specification . . . . . . . . . . 7
3.1.6. Help Path Segment Specification . . . . . . . . . . . 7 3.1.6. Help Path Segment Specification . . . . . . . . . . . 8
3.2. Search Path Segment Specification . . . . . . . . . . . . 8 3.2. Search Path Segment Specification . . . . . . . . . . . . 8
3.2.1. Domain Search . . . . . . . . . . . . . . . . . . . . 8 3.2.1. Domain Search . . . . . . . . . . . . . . . . . . . . 8
3.2.2. Name Server Search . . . . . . . . . . . . . . . . . 9 3.2.2. Name Server Search . . . . . . . . . . . . . . . . . 9
3.2.3. Entity Search . . . . . . . . . . . . . . . . . . . . 9 3.2.3. Entity Search . . . . . . . . . . . . . . . . . . . . 9
4. Search Processing . . . . . . . . . . . . . . . . . . . . . . 10 4. Search Processing . . . . . . . . . . . . . . . . . . . . . . 10
5. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 12 5. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 12
6. Internationalization Considerations . . . . . . . . . . . . . 12 6. Internationalization Considerations . . . . . . . . . . . . . 12
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
8. Security Considerations . . . . . . . . . . . . . . . . . . . 13 8. Security Considerations . . . . . . . . . . . . . . . . . . . 13
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
10.1. Normative References . . . . . . . . . . . . . . . . . . 14 10.1. Normative References . . . . . . . . . . . . . . . . . . 14
10.2. Informative References . . . . . . . . . . . . . . . . . 15 10.2. Informative References . . . . . . . . . . . . . . . . . 16
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 16 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Conventions Used in This Document 1. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
1.1. Acronyms and Abbreviations 1.1. Acronyms and Abbreviations
skipping to change at page 9, line 4 skipping to change at page 9, line 6
/domains?name=XXXX /domains?name=XXXX
where XXXX is a search pattern representing a domain name in where XXXX is a search pattern representing a domain name in
"letters, digits, hyphen" format [RFC5890] in a zone administered by "letters, digits, hyphen" format [RFC5890] in a zone administered by
the server operator of a DNR. The following URL would be used to the server operator of a DNR. The following URL would be used to
find DNR information for domain names matching the "example*.com" find DNR information for domain names matching the "example*.com"
pattern: pattern:
http://example.com/.well-known/rdap/domains?name=example*.com http://example.com/.well-known/rdap/domains?name=example*.com
Internationalized Domain Names (IDNs) in U-label format [RFC5890] can Internationalized Domain Names (IDNs) in U-label format [RFC5890] can
also be used as search patterns (see Section 4). Searches for these also be used as search patterns (see Section 4). Searches for these
names are of the form /domains?name=XXXX, where XXXX is a search names are of the form /domains?name=XXXX, where XXXX is a search
pattern representing a domain name in U-label format [RFC5890]. pattern representing a domain name in U-label format [RFC5890].
3.2.2. Name Server Search 3.2.2. Name Server Search
Syntax: nameservers?name=<nameserver search pattern> Syntax: nameservers?name=<nameserver search pattern>
Searches for name server information are of the form Searches for name server information can take one of two forms:
/nameservers?name=XXXX /nameservers?name=XXXX
where XXXX is a search pattern representing a host name in "letters, /nameservers?ip=YYYY
XXXX is a search pattern representing a host name in "letters,
digits, hyphen" format [RFC5890] in a zone administered by the server digits, hyphen" format [RFC5890] in a zone administered by the server
operator of a DNR. The following URL would be used to find DNR operator of a DNR. The following URL would be used to find DNR
information for name server names matching the "ns1.example*.com" information for name server names matching the "ns1.example*.com"
pattern: pattern:
http://example.com/.well-known/rdap/nameservers?name=ns1.example*.com http://example.com/.well-known/rdap/nameservers?name=ns1.example*.com
YYYY is a search pattern representing an IPv4 [RFC1166] or IPv6
[RFC5952] address. The following URL would be used to search for
name server names that resolve to the "192.0.2.0" address:
http://example.com/.well-known/rdap/nameservers?ip=192.0.2.0
Internationalized name server names in U-label format [RFC5890] can Internationalized name server names in U-label format [RFC5890] can
also be used as search patterns (see Section 4). Searches for these also be used as search patterns (see Section 4). Searches for these
names are of the form /nameservers?name=XXXX, where XXXX is a search names are of the form /nameservers?name=XXXX, where XXXX is a search
pattern representing a name server name in U-label format [RFC5890]. pattern representing a name server name in U-label format [RFC5890].
3.2.3. Entity Search 3.2.3. Entity Search
Syntax: entities?fn=<entity name search pattern> Syntax: entities?fn=<entity name search pattern>
Syntax: entities?handle=<entity handle search pattern> Syntax: entities?handle=<entity handle search pattern>
skipping to change at page 17, line 4 skipping to change at page 17, line 19
-06: Added search text and removed or edited old search text. -06: Added search text and removed or edited old search text.
-07: Fixed query parameter typo by replacing "/?" with "?". Changed -07: Fixed query parameter typo by replacing "/?" with "?". Changed
"asplain" to "AS Plain". Added entity search by handle. "asplain" to "AS Plain". Added entity search by handle.
Corrected section references. Updated IDN search text. Corrected section references. Updated IDN search text.
-08: Revised URI formats and added IANA instructions to create a -08: Revised URI formats and added IANA instructions to create a
registry entry for the "rdap" well-known prefix. Revised search registry entry for the "rdap" well-known prefix. Revised search
processing text and added search privacy consideration. processing text and added search privacy consideration.
Synchronized examples with response draft. Synchronized examples with response draft.
-09: More search processing and URI prefix updates. Updated fully- -09: More search processing and URI prefix updates. Updated fully-
qualified domain name reference. qualified domain name reference.
-10: Added name server search by IP address.
Authors' Addresses Authors' Addresses
Andrew Lee Newton Andrew Lee Newton
American Registry for Internet Numbers American Registry for Internet Numbers
3635 Concorde Parkway 3635 Concorde Parkway
Chantilly, VA 20151 Chantilly, VA 20151
US US
Email: andy@arin.net Email: andy@arin.net
 End of changes. 13 change blocks. 
11 lines changed or deleted 21 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/