> -----Original Message----- > From: I-D-Announce [mailto:[email protected]] On Behalf Of > [email protected] > Sent: Wednesday, April 05, 2017 10:40 AM > To: [email protected] > Subject: [EXTERNAL] I-D Action: draft-hollenbeck-regext-rdap-object-tag- > 02.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : Registration Data Access Protocol (RDAP) Object > Tagging > Authors : Scott Hollenbeck > Andrew Lee Newton > Filename : draft-hollenbeck-regext-rdap-object-tag-02.txt > Pages : 11 > Date : 2017-04-05 > > 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 > operational practice that can be used to add structure to RDAP > identifiers that makes it possible to identify the authoritative > server for additional RDAP queries. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-hollenbeck-regext-rdap-object-tag/
FYI - this version changes the separator character from "@" (a reserved URI character) to "~" (an unreserved URI character) with accompanying text updates. Does anyone see any issues to address before I ask the chairs to see if the WG is interested in adopting the document? Scott _______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
