--- 1/draft-ietf-regext-rdap-object-tag-00.txt 2018-03-26 07:14:04.267404592 -0700 +++ 2/draft-ietf-regext-rdap-object-tag-01.txt 2018-03-26 07:14:04.343406394 -0700 @@ -1,19 +1,19 @@ Registration Protocols Extensions S. Hollenbeck Internet-Draft Verisign Labs Updates: 7484 (if approved) A. Newton Intended status: Best Current Practice ARIN -Expires: July 20, 2018 January 16, 2018 +Expires: September 27, 2018 March 26, 2018 Registration Data Access Protocol (RDAP) Object Tagging - draft-ietf-regext-rdap-object-tag-00 + draft-ietf-regext-rdap-object-tag-01 Abstract The Registration Data Access Protocol (RDAP) includes a method that can be used to identify the authoritative server for processing domain name, IP address, and autonomous system number queries. The method does not describe how to identify the authoritative server for processing other RDAP query types, such as entity queries. This limitation exists because the identifiers associated with these query types are typically unstructured. This document describes an @@ -29,54 +29,54 @@ 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 July 20, 2018. + This Internet-Draft will expire on September 27, 2018. Copyright Notice Copyright (c) 2018 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 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Object Naming Practice . . . . . . . . . . . . . . . . . . . 3 - 3. Bootstrap Service Registry for RDAP Service Providers . . . . 7 - 3.1. Registration Procedure . . . . . . . . . . . . . . . . . 8 + 3. Bootstrap Service Registry for RDAP Service Providers . . . . 8 + 3.1. Registration Procedure . . . . . . . . . . . . . . . . . 9 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 4.1. Bootstrap Service Registry for RDAP Service Providers . . 9 5. Implementation Status . . . . . . . . . . . . . . . . . . . . 9 - 5.1. Verisign Labs . . . . . . . . . . . . . . . . . . . . . . 9 + 5.1. Verisign Labs . . . . . . . . . . . . . . . . . . . . . . 10 5.2. OpenRDAP . . . . . . . . . . . . . . . . . . . . . . . . 10 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 - 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 - 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 + 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 + 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 8.1. Normative References . . . . . . . . . . . . . . . . . . 11 8.2. Informative References . . . . . . . . . . . . . . . . . 11 - 8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 11 + 8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 1. Introduction The Registration Data Access Protocol (RDAP) includes a method ([RFC7484]) that can be used to identify the authoritative server for processing domain name, IP address, and autonomous system number (ASN) queries. This method works because each of these data elements is structured in a way that facilitates automated parsing of the @@ -321,20 +321,36 @@ character is used for naturally occurring, non-separator purposes in an entity handle. This could lead to a client mistakenly assuming that a TILDE character represents a separator and the text that follows TILDE is a service provider identifier. A client that queries the IANA registry for what they assume is a valid service provider will likely receive an unexpected invalid result. As a consequence, the TILDE character MUST NOT be used in an entity handle for any purpose other than to separate an object identifier from a service provider tag. + The TILDE character was chosen as a separator for two reasons: 1) to + avoid collisions with characters that are commonly found in entity + handles, and 2) to avoid collisons with URI-reserved characters. The + list of unreserved characters specified in Section 2.3 of RFC 3986 + [RFC3986] provided multiple options for consideration as follows: + + unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~" + + ALPHA and DIGIT characters were excluded because they are commonly + used in entity handles. The "-" (HYPHEN MINUS, U+002D) and "_" (LOW + LINE, U+005F) characters were also excluded as a result of being + observed in current operational use. The TILDE character was chosen + over the "." (FULL STOP, U+002E) character due to the authors' + belief that it is less likely to be in use in entity handles as of + the time of this writing. + 3. Bootstrap Service Registry for RDAP Service Providers The bootstrap service registry for the RDAP service provider space is represented using the structure specified in Section 3 of RFC 7484 [RFC7484]. The JSON output of this registry contains alphanumeric identifiers that identify RDAP service providers, grouped by base RDAP URLs, as shown in this example. { "version": "1.0", @@ -527,20 +544,22 @@ example in Section 2 (editorial erratum reported for RFC 7483 by Marcos Sanz). Added acknowledgements. 02: Changed separator character from COMMERCIAL AT to TILDE. Clarity updates and fixed an example handle. Added text to describe the risk of separator characters appearing naturally in entity handles and being misinterpreted as separator characters. 03: Added Implementation Status section (Section 5). 04: Keepalive refresh. 05: Added OpenRDAP implementation information to Section 5. 00: Initial working group version. + 01: Added text to describe why the TILDE character was chosen as the + separator character. Authors' Addresses Scott Hollenbeck Verisign Labs 12061 Bluemont Way Reston, VA 20190 USA Email: shollenbeck@verisign.com