--- 1/draft-ietf-regext-rdap-object-tag-02.txt 2018-05-21 06:13:17.283789658 -0700 +++ 2/draft-ietf-regext-rdap-object-tag-03.txt 2018-05-21 06:13:17.319790511 -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: October 29, 2018 April 27, 2018 +Expires: November 22, 2018 May 21, 2018 Registration Data Access Protocol (RDAP) Object Tagging - draft-ietf-regext-rdap-object-tag-02 + draft-ietf-regext-rdap-object-tag-03 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 updates RFC 7484 by @@ -29,21 +29,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 October 29, 2018. + This Internet-Draft will expire on November 22, 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 @@ -136,22 +136,24 @@ "YYYY" in an IANA registry, an RDAP client will parse a tagged entity identifier "XXXX-YYYY" into distinct handle ("XXXX") and service provider ("YYYY") identifiers. The service provider identifier "YYYY" is used to query an IANA registry to retrieve the base RDAP URL "https://example.com/rdap/". The base RDAP URL is concatenated to the entity handle to create a complete RDAP query path segment of "https://example.com/rdap/entity/XXXX-YYYY". Implementation of this practice requires tagging of unstructured potential query identifiers in RDAP responses. Consider these elided - examples from Section 5.3 of RFC 7483 [RFC7483] in which the handle - identifiers have been tagged with a service provider tag: + examples ("..." is used to note elided response objects) from + Section 5.3 of RFC 7483 [RFC7483] in which the handle identifiers + have been tagged with service provider tags "RIR", "DNR", and "ABC" + respectively: { "objectClassName" : "domain", "handle" : "XXXX-RIR", "ldhName" : "0.2.192.in-addr.arpa", "nameservers" : [ ... ], "secureDNS": @@ -598,20 +602,22 @@ 05: Added OpenRDAP implementation information to Section 6. 00: Initial working group version. 01: Added text to describe why the TILDE character was chosen as the separator character. 02: Nit fixes. Added rdapConformance text, switched back to HYPHEN MINUS, and added IANA registration instructions per working group last call discussion. Updated suffix syntax reference from the IANA EPP ROID registry to RFC 5730 (which is what the IANA registry references). + 03: Shephered writeup review updates to explain examples in + Section 2. Authors' Addresses Scott Hollenbeck Verisign Labs 12061 Bluemont Way Reston, VA 20190 USA Email: shollenbeck@verisign.com