draft-ietf-regext-rfc7482bis-01.txt   draft-ietf-regext-rfc7482bis-02.txt 
REGEXT Working Group S. Hollenbeck REGEXT Working Group S. Hollenbeck
Internet-Draft Verisign Labs Internet-Draft Verisign Labs
Intended status: Standards Track A. Newton Intended status: Standards Track A. Newton
Expires: December 31, 2020 AWS Expires: March 12, 2021 AWS
June 29, 2020 September 8, 2020
Registration Data Access Protocol (RDAP) Query Format Registration Data Access Protocol (RDAP) Query Format
draft-ietf-regext-rfc7482bis-01 draft-ietf-regext-rfc7482bis-02
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. These Registries (DNRs)) using "RESTful" web access patterns. These
uniform patterns define the query syntax for the Registration Data uniform patterns define the query syntax for the Registration Data
Access Protocol (RDAP). Access Protocol (RDAP).
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 December 31, 2020. This Internet-Draft will expire on March 12, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 10, line 25 skipping to change at page 10, line 25
Detailed results can be retrieved using the HTTP GET method and the Detailed results can be retrieved using the HTTP GET method and the
path segments specified here. path segments specified here.
3.2.1. Domain Search 3.2.1. Domain Search
Syntax: domains?name=<domain search pattern> Syntax: domains?name=<domain search pattern>
Syntax: domains?nsLdhName=<nameserver search pattern> Syntax: domains?nsLdhName=<nameserver search pattern>
Syntax: domains?nsIp=<IP address search pattern> Syntax: domains?nsIp=<nameserver IP address>
Searches for domain information by name are specified using this Searches for domain information by name are specified using this
form: form:
domains?name=XXXX domains?name=XXXX
XXXX is a search pattern representing a domain name in "letters, XXXX is a search pattern representing a domain name in "letters,
digits, hyphen" (LDH) format [RFC5890]. The following URL would be digits, hyphen" (LDH) format [RFC5890]. The following URL would be
used to find DNR information for domain names matching the used to find DNR information for domain names matching the
"example*.com" pattern: "example*.com" pattern:
skipping to change at page 11, line 14 skipping to change at page 11, line 14
search for domains delegated to nameservers matching the search for domains delegated to nameservers matching the
"ns1.example*.com" pattern: "ns1.example*.com" pattern:
https://example.com/rdap/domains?nsLdhName=ns1.example*.com https://example.com/rdap/domains?nsLdhName=ns1.example*.com
Searches for domain information by nameserver IP address are Searches for domain information by nameserver IP address are
specified using this form: specified using this form:
domains?nsIp=ZZZZ domains?nsIp=ZZZZ
ZZZZ is a search pattern representing an IPv4 [RFC1166] or IPv6 ZZZZ is an IPv4 [RFC1166] or IPv6 [RFC5952] address. The following
[RFC5952] address. The following URL would be used to search for URL would be used to search for domains that have been delegated to
domains that have been delegated to nameservers that resolve to the nameservers that resolve to the "192.0.2.0" address:
"192.0.2.0" address:
https://example.com/rdap/domains?nsIp=192.0.2.0 https://example.com/rdap/domains?nsIp=192.0.2.0
3.2.2. Nameserver Search 3.2.2. Nameserver Search
Syntax: nameservers?name=<nameserver search pattern> Syntax: nameservers?name=<nameserver search pattern>
Syntax: nameservers?ip=<IP address search pattern> Syntax: nameservers?ip=<nameserver IP address>
Searches for nameserver information by nameserver name are specified Searches for nameserver information by nameserver name are specified
using this form: using this form:
nameservers?name=XXXX nameservers?name=XXXX
XXXX is a search pattern representing a host name in "letters, XXXX is a search pattern representing a host name in "letters,
digits, hyphen" format [RFC5890]. The following URL would be used to digits, hyphen" format [RFC5890]. The following URL would be used to
find information for nameserver names matching the "ns1.example*.com" find information for nameserver names matching the "ns1.example*.com"
pattern: pattern:
skipping to change at page 12, line 4 skipping to change at page 12, line 4
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 nameserver name in U-label format [RFC5890]. pattern representing a nameserver name in U-label format [RFC5890].
See Section 6.1 for information on character encoding for the U-label See Section 6.1 for information on character encoding for the U-label
format. format.
Searches for nameserver information by nameserver IP address are Searches for nameserver information by nameserver IP address are
specified using this form: specified using this form:
nameservers?ip=YYYY nameservers?ip=YYYY
YYYY is a search pattern representing an IPv4 [RFC1166] or IPv6 YYYY is an IPv4 [RFC1166] or IPv6 [RFC5952] address. The following
[RFC5952] address. The following URL would be used to search for URL would be used to search for nameserver names that resolve to the
nameserver names that resolve to the "192.0.2.0" address: "192.0.2.0" address:
https://example.com/rdap/nameservers?ip=192.0.2.0 https://example.com/rdap/nameservers?ip=192.0.2.0
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>
Searches for entity information by name are specified using this Searches for entity information by name are specified using this
skipping to change at page 23, line 8 skipping to change at page 23, line 8
(RDAP) Service", RFC 7484, DOI 10.17487/RFC7484, March (RDAP) Service", RFC 7484, DOI 10.17487/RFC7484, March
2015, <https://www.rfc-editor.org/info/rfc7484>. 2015, <https://www.rfc-editor.org/info/rfc7484>.
[RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS [RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499, Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499,
January 2019, <https://www.rfc-editor.org/info/rfc8499>. January 2019, <https://www.rfc-editor.org/info/rfc8499>.
[I-D.ietf-regext-rfc7483bis] [I-D.ietf-regext-rfc7483bis]
Hollenbeck, S. and A. Newton, "JSON Responses for the Hollenbeck, S. and A. Newton, "JSON Responses for the
Registration Data Access Protocol (RDAP)", draft-ietf- Registration Data Access Protocol (RDAP)", draft-ietf-
regext-rfc7483bis-00 (work in progress), June 2020. regext-rfc7483bis-01 (work in progress), June 2020.
[Unicode-UAX15] [Unicode-UAX15]
The Unicode Consortium, "Unicode Standard Annex #15: The Unicode Consortium, "Unicode Standard Annex #15:
Unicode Normalization Forms", September 2013, Unicode Normalization Forms", September 2013,
<https://www.unicode.org/reports/tr15/>. <https://www.unicode.org/reports/tr15/>.
10.2. Informative References 10.2. Informative References
[REST] Fielding, R., "Architectural Styles and the Design of [REST] Fielding, R., "Architectural Styles and the Design of
Network-based Software Architectures", Ph.D. Network-based Software Architectures", Ph.D.
skipping to change at page 25, line 24 skipping to change at page 25, line 24
[RFC6874] MUST NOT be used, and servers SHOULD ignore it". [RFC6874] MUST NOT be used, and servers SHOULD ignore it".
Changed "Only a single asterisk is allowed for a partial string Changed "Only a single asterisk is allowed for a partial string
search" to "A partial string search MUST NOT include more than one search" to "A partial string search MUST NOT include more than one
asterisk". Changed "Clients should avoid submitting a partial asterisk". Changed "Clients should avoid submitting a partial
match search of Unicode characters where a Unicode character may match search of Unicode characters where a Unicode character may
be legally combined with another Unicode character or characters" be legally combined with another Unicode character or characters"
to "Clients SHOULD NOT submit a partial match search of Unicode to "Clients SHOULD NOT submit a partial match search of Unicode
characters where a Unicode character may be legally combined with characters where a Unicode character may be legally combined with
another Unicode character or characters". another Unicode character or characters".
02: Changed description of nameserver IP address "search pattern" in
Sections 3.2.1 and 3.2.2.
Authors' Addresses Authors' Addresses
Scott Hollenbeck Scott Hollenbeck
Verisign Labs Verisign Labs
12061 Bluemont Way 12061 Bluemont Way
Reston, VA 20190 Reston, VA 20190
United States of America United States of America
Email: shollenbeck@verisign.com Email: shollenbeck@verisign.com
URI: https://www.verisignlabs.com/ URI: https://www.verisignlabs.com/
 End of changes. 9 change blocks. 
14 lines changed or deleted 16 lines changed or added

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