GTLD domain name registries RDAP architecture
Provided is a method for providing Registration Data Access Protocol (“RDAP”) responses. The method includes obtaining, at a RDAP client over a network, a RDAP query for RDAP data from a user; providing, by the RDAP client, the RDAP query and a cryptographic credential to a RDAP server, wherein the RDAP server communicates with one or more thick RDAP servers to provide respective thick RDAP answers to the RDAP query, wherein at least one the respective thick RDAP answers are encrypted using a symmetric or asymmetric cryptographic key associated with the cryptographic credential of the RDAP client; obtaining a consolidated thick RDAP answer to the RDAP query from the RDAP server; decrypting the consolidated thick RDAP answer using a symmetric or asymmetric cryptographic key associated with the cryptographic credential; and providing the thick RDAP answer that is decrypted to the user.
1. A method for providing a registration data response, the method comprising:
obtaining, at a registration data client over a network, a registration data query for registration data from a user;
providing, by the registration data client, the registration data query to a registration data service, wherein the registration data service queries a database of the registration data service and determines an other registration data service to respond to the registration data query;
receiving, at the registration data client, a registration data response including a referral URL to the other registration data service determined to respond to the registration data query;
providing a registration data response to the user, the registration data response comprising a hyperlink based on the referral URL; and
receiving, at the registration data client over the network, a second registration data query for registration data from the user, wherein, based on receiving the second registration data query, an access token is provided to the other registration data service.
2. The method of claim 1 , wherein the other registration data service includes a thick registration data service and/or an IANA registry of gTLD registries.
3. The method of claim 2 , wherein the second registration data query for registration data from the user comprises a search initiated by the user using the registration data results based on the hyperlink.
4. The method of claim 3 , further comprising utilizing the hyperlink to send the second registration data query from the registration data client to the other registration data service specified in the hyperlink.
5. The method of claim 1 , further comprising providing, by the registration data client, the access token to the registration data service, wherein the access token is provided by an authentication provider.
6. The method of claim 5 , further comprising sending the access token to the other registration data service.
7. The method of claim 6 , further comprising receiving, at the registration data client, a response to the second registration data query from the other registration data service.
8. The method of claim 1 , wherein the hyperlink includes the access token.
9. The method of claim 1 , wherein the registration data service is Registration Data Access Protocol (RDAP).
10. A system for providing a registration data response, the system comprising:
one or more processors; and
a memory system comprising one or more computer-readable media, wherein the one or more computer-readable media contain instructions that cause the one or more processors to cause:
obtaining, at a registration data client over a network, a registration data query for registration data from a user;
providing, by the registration data client, the registration data query to a registration data service, wherein the registration data service queries a database of the registration data service and determines an other registration data service to respond to the registration data query;
receiving, at the registration data client, a registration data response including a referral URL to the other registration data service determined to respond to the registration data query;
providing a registration data response to the user, the registration data response comprising a hyperlink based on the referral URL; and
receiving, at the registration data client over the network, a second registration data query for registration data from the user, wherein, based on receiving the second registration data query, an access token is provided to the other registration data service.
11. The system of claim 10 , wherein the other registration data service includes a thick registration data service and/or an IANA registry of gTLD registries.
12. The system of claim 11 , wherein the second registration data query for registration data from the user comprises a search initiated by the user using the registration data results based on the hyperlink.
13. The system of claim 12 , wherein the one or more processors are further operable to perform operations comprising utilizing the hyperlink to send the second registration data query from the registration data client to the other registration data service specified in the hyperlink.
14. The system of claim 10 , wherein the one or more processors are further operable to perform operations comprising providing, by the registration data client, the access token to the registration data service, wherein the access token is provided by an authentication provider.
15. The system of claim 14 , wherein the hyperlink includes the access token.
16. The system of claim 14 , wherein the one or more processors are further operable to perform operations comprising sending the access token to the other registration data service.
17. The system of claim 16 , wherein the one or more processors are further operable to perform operations comprising receiving, at the registration data client, a response to the second registration data query from the other registration data service.
18. The system of claim 10 , wherein the registration data service is Registration Data Access Protocol (RDAP).