--- 1/draft-ietf-regext-rfc7482bis-01.txt 2020-09-08 08:13:10.656194880 -0700 +++ 2/draft-ietf-regext-rfc7482bis-02.txt 2020-09-08 08:13:10.688195330 -0700 @@ -1,19 +1,19 @@ REGEXT Working Group S. Hollenbeck Internet-Draft Verisign Labs Intended status: Standards Track A. Newton -Expires: December 31, 2020 AWS - June 29, 2020 +Expires: March 12, 2021 AWS + September 8, 2020 Registration Data Access Protocol (RDAP) Query Format - draft-ietf-regext-rfc7482bis-01 + draft-ietf-regext-rfc7482bis-02 Abstract This document describes uniform patterns to construct HTTP URLs that may be used to retrieve registration information from registries (including both Regional Internet Registries (RIRs) and Domain Name Registries (DNRs)) using "RESTful" web access patterns. These uniform patterns define the query syntax for the Registration Data Access Protocol (RDAP). @@ -25,21 +25,21 @@ 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 https://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 31, 2020. + This Internet-Draft will expire on March 12, 2021. Copyright Notice Copyright (c) 2020 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 (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -441,21 +441,21 @@ Detailed results can be retrieved using the HTTP GET method and the path segments specified here. 3.2.1. Domain Search Syntax: domains?name= Syntax: domains?nsLdhName= - Syntax: domains?nsIp= + Syntax: domains?nsIp= Searches for domain information by name are specified using this form: domains?name=XXXX XXXX is a search pattern representing a domain name in "letters, digits, hyphen" (LDH) format [RFC5890]. The following URL would be used to find DNR information for domain names matching the "example*.com" pattern: @@ -478,32 +478,31 @@ search for domains delegated to nameservers matching the "ns1.example*.com" pattern: https://example.com/rdap/domains?nsLdhName=ns1.example*.com Searches for domain information by nameserver IP address are specified using this form: domains?nsIp=ZZZZ - ZZZZ is a search pattern representing an IPv4 [RFC1166] or IPv6 - [RFC5952] address. The following URL would be used to search for - domains that have been delegated to nameservers that resolve to the - "192.0.2.0" address: + ZZZZ is an IPv4 [RFC1166] or IPv6 [RFC5952] address. The following + URL would be used to search for domains that have been delegated to + nameservers that resolve to the "192.0.2.0" address: https://example.com/rdap/domains?nsIp=192.0.2.0 3.2.2. Nameserver Search Syntax: nameservers?name= - Syntax: nameservers?ip= + Syntax: nameservers?ip= Searches for nameserver information by nameserver name are specified using this form: nameservers?name=XXXX XXXX is a search pattern representing a host name in "letters, digits, hyphen" format [RFC5890]. The following URL would be used to find information for nameserver names matching the "ns1.example*.com" pattern: @@ -514,23 +513,23 @@ 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 pattern representing a nameserver name in U-label format [RFC5890]. See Section 6.1 for information on character encoding for the U-label format. Searches for nameserver information by nameserver IP address are specified using this form: nameservers?ip=YYYY - YYYY is a search pattern representing an IPv4 [RFC1166] or IPv6 - [RFC5952] address. The following URL would be used to search for - nameserver names that resolve to the "192.0.2.0" address: + YYYY is an IPv4 [RFC1166] or IPv6 [RFC5952] address. The following + URL would be used to search for nameserver names that resolve to the + "192.0.2.0" address: https://example.com/rdap/nameservers?ip=192.0.2.0 3.2.3. Entity Search Syntax: entities?fn= Syntax: entities?handle= Searches for entity information by name are specified using this @@ -1033,21 +1032,21 @@ (RDAP) Service", RFC 7484, DOI 10.17487/RFC7484, March 2015, . [RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499, January 2019, . [I-D.ietf-regext-rfc7483bis] Hollenbeck, S. and A. Newton, "JSON Responses for the 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] The Unicode Consortium, "Unicode Standard Annex #15: Unicode Normalization Forms", September 2013, . 10.2. Informative References [REST] Fielding, R., "Architectural Styles and the Design of Network-based Software Architectures", Ph.D. @@ -1145,20 +1144,23 @@ [RFC6874] MUST NOT be used, and servers SHOULD ignore it". Changed "Only a single asterisk is allowed for a partial string search" to "A partial string search MUST NOT include more than one asterisk". Changed "Clients should avoid submitting a partial match search of Unicode characters where a Unicode character may be legally combined with another Unicode character or characters" to "Clients SHOULD NOT submit a partial match search of Unicode characters where a Unicode character may be legally combined with 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 Scott Hollenbeck Verisign Labs 12061 Bluemont Way Reston, VA 20190 United States of America Email: shollenbeck@verisign.com URI: https://www.verisignlabs.com/