GTLD domain name registries RDAP architecture
Provided is a method for providing a response to a user query for domain-related information of a domain. The method can include obtaining, at a client over a network, the user query for the domain-related information, and identifying one or more thick services based on thin data for the domain. The method can also include providing, by the client, the user query to the identified one or more thick services and obtaining a first answer to the user query from the one or more thick services. Furthermore, the method can include providing a second answer to a user based on the first answer.
1 . A method for obtaining registration data by a first registration data service, the method comprising:
obtaining, by the first registration data service, a first query for registration data, wherein the first query is from a client, wherein a thin data is accessible by the first registration data service;
obtaining, by the first registration data service, an access token, wherein the access token is provided to the client by an authorization service;
selecting, by the first registration data service, a second registration data service from a plurality of registration data services based on the thin data;
sending, to the second registration data service, the access token and a second query for registration data, wherein the second query is based on the first query, wherein the second registration data service is configured to trust the access token based on a first relationship between the second registration data service and the authorization service; and
receiving, by the first registration data service, a response to the second query for registration data from the second registration data service.
2 . The method of claim 1 , wherein the first relationship between the second registration data service and the authorization service comprises a first trust relationship.
3 . The method of claim 2 , wherein the first trust relationship comprises an identity of the authorization service being verifiable by the second registration data service.
4 . The method of claim 3 , wherein the identity of the authorization service is verifiable using a public key of the authorization service and the access token, wherein the access token comprises a cryptographic signature of the authorization service.
5 . The method of claim 1 , further comprising: providing to the client, by the first registration data service, the response to the second query for registration data.
6 . The method of claim 1 , wherein the first registration data service is configured to trust the access token based on a second relationship between the first registration data service and the authorization service.
7 . The method of claim 1 , wherein the access token comprises a differentiated level of access.
8 . The method of claim 1 , wherein the access token is obtained at the client based on a request by the first registration data service or the second registration data service.
9 . A system for obtaining registration data by a first registration data service, 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 perform one or more operations, comprising:
obtaining, by the first registration data service, a first query for registration data, wherein the first query is from a client, wherein a thin data is accessible by the first registration data service;
obtaining, by the first registration data service, an access token, wherein the access token is provided to the client by an authorization service;
selecting, by the first registration data service, a second registration data service from a plurality of registration data services based on the thin data;
sending, to the second registration data service, the access token and a second query for registration data, wherein the second query is based on the first query, wherein the second registration data service is configured to trust the access token based on a first relationship between the second registration data service and the authorization service; and
receiving, by the first registration data service, a response to the second query for registration data from the second registration data service.
10 . The system of claim 9 , wherein the first relationship between the second registration data service and the authorization service comprises a first trust relationship.
11 . The system of claim 10 , wherein the first trust relationship comprises an identity of the authorization service being verifiable by the second registration data service.
12 . The system of claim 11 , wherein the identity of the authorization service is verifiable using a public key of the authorization service and the access token, wherein the access token comprises a cryptographic signature of the authorization service.
13 . The system of claim 9 , wherein the one or more processors are further operable to perform operations comprising providing, to the client, by the first registration data service, the response to the second query for registration data.
14 . The system of claim 9 , wherein the first registration data service is configured to trust the access token based on a second relationship between the first registration data service and the authorization service.
15 . The system of claim 9 , wherein the access token comprises a differentiated level of access.
16 . The system of claim 9 , wherein the access token is obtained at the client based on a request provided by the first registration data service or the second registration data service.
17 . A method for obtaining registration data by a first registration data service, the method comprising:
obtaining, by the first registration data service, a first query for registration data, wherein the first query is from a client, wherein a thin data is accessible by the first registration data service;
selecting, by the first registration data service, a second registration data service from a plurality of registration data services based on the thin data;
sending, to the second registration data service, a second query for registration data, wherein the second query is based on the first query, wherein the second registration data service has a first relationship with an authorization service, wherein the second registration data service is configured to respond to the second query based on the first relationship with the authorization service; and
receiving, by the first registration data service, a response to the second query for registration data from the second registration data service.
18 . The method of claim 17 , wherein the first relationship comprises an identity of the authorization service being verifiable by the second registration data service.
19 . The method of claim 18 , wherein the identity of the authorization service is verifiable using a public key of the authorization service and an access token, wherein the access token comprises a cryptographic signature of the authorization service.
20 . The method of claim 1 , further comprising:
selecting, by the first registration data service, a third registration data service from the plurality of registration data services based on the thin data, the third registration data service being different from the second registration data service;
sending, to the third registration data service, the access token and a third query for registration data, wherein the third query is based on the first query, wherein the third registration data service is configured to trust the access token based on a third relationship between the third registration data service and the authorization service; and
receiving, by the first registration data service, a response to the third query for registration data from the third registration data service.
21 . The method of claim 20 , further comprising:
aggregating, by the first registration data service, the response to the second query for registration data from the second registration data service and the response to the third query for registration data from the third registration data service.
22 . The method of claim 1 , wherein the first registration data service comprises a registry.
23 . The method of claim 1 , wherein the first registration data service is unable to respond to the first query based on the thin data accessible by the first registration data service.
24 . The method of claim 1 , wherein the thin data accessible by the first registration data service identifies the second registration data service.
25 . The method of claim 1 , wherein the thin data accessible by the first registration data service identifies the plurality of registration data services.
26 . The method of claim 1 , further comprising:
selecting, by the first registration data service, a third registration data service from the plurality of registration data services based on the thin data;
sending, to the third registration data service, a third query for registration data;
receiving, by the first registration data service, a response to the third query for registration data from the third registration data service, wherein the third query is based on the first query; and
providing to the client, by the first registration data service, an aggregated response to the first query for registration data based on the response received from the second registration data service and the response received from the third registration data service.
27 . The method of claim 1 , wherein the first query is the same as the second query.
28 . The system of claim 9 , wherein the first query is the same as the second query.
29 . The method of claim 17 , wherein the first query is the same as the second query.