gTLD RDAP Architecture with Virtual Thick-Data Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing RDAP systems face challenges in providing efficient and secure access to registration data, particularly in thin registries where domain contact information is not transferred during domain transfers, leading to parsing difficulties and inconsistencies, and there is a lack of mandated registrar WHOIS output.
Innovation Solution
A virtual RDAP service (VRDAP) is introduced to provide thick RDAP capabilities by querying multiple RDAP services, aggregating responses, and supporting batch processing and asynchronous query handling, allowing thin RDAP services to offer transparent thick data retrieval.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If thin registry architecture is used, then device complexity is reduced, but data completeness deteriorates
Solution Approach 1:
The patent introduces an intermediary service layer between thin registries and clients that aggregates contact information from multiple sources. This mediator collects data from various registrars and presents it as complete thick registry data, allowing thin registries to maintain low complexity while providing information completeness through the intermediary's aggregation capability.
2Loss of information
If thick registry is implemented, then data completeness is improved, but device complexity increases
Solution Approach 1:
The patent segments the thick registry functionality into separate modular components: a thin registry core, an intermediary aggregation service, and client interfaces. This segmentation allows the complex data aggregation and presentation logic to be isolated in separate services, enabling thick registry capabilities without requiring the entire system to be complex.
3Ease of operation
If domain transfer is performed in thin registry, then ease of operation is improved, but measurement precision deteriorates
Solution Approach 1:
The intermediary service acts as a mediator during domain transfers by receiving transfer requests from thin registries, aggregating complete contact information from multiple sources, and delivering accurate data to the new registrar. This ensures that even though the transfer process remains simple, the contact information received maintains high precision and completeness.
4Measurement precision
If RDAP query processing is performed synchronously, then measurement precision is improved, but productivity deteriorates
Solution Approach 1:
The patent implements preliminary actions by pre-establishing connections to multiple data sources and pre-organizing contact information databases. When RDAP queries arrive, the system can quickly retrieve and aggregate information from pre-configured sources rather than establishing connections and searching in real-time, maintaining data accuracy while significantly improving query processing throughput.
Data Source
AI summary
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.