Registration Data Access Protocol: Difference between revisions
m MarkWD moved page RDAP to Registration Data Access Protocol over redirect |
|||
(3 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
The '''Registration Data Access Protocol''' (RDAP) is the successor to the [[Whois]] protocol. This [[IETF]]-developed protocol enables users to access current registration data. | The '''Registration Data Access Protocol''' (RDAP) is the successor to the [[Whois]] protocol. This [[IETF]]-developed protocol enables users to access current registration data. The RDAP protocol makes access to data from the WHOIS system more secure. It includes standardized queries, secure access to data, extensibility, differentiated access, support for internationalization of registration data, and enabling search for objects. The scalable technical architecture can accommodate new and future policy-driven functionality requirements. All [[CPH|contracted parties]] have been required to provide RDDS over RDAP for all [[gTLD]] domain names since 26 August 2019.<ref>[https://www.icann.org/en/blogs/details/icann-contracted-parties-set-to-vote-on-rdap-amendments-12-01-2023-en Contracted Parties to Vote on RDAP Amendments, ICANN Blogs]</ref> On April 30, 2023, the [[ICANN Board]] directed the [[ICANN Organization]] to implement the RDAP Global Amendments to the gTLD Registry Agreement ([[RA]]), Specification 13, and 2013 Registrar Accreditation Agreement ([[RAA]]). The global amendments specify operational requirements for providing Registration Data Directory Services ([[RDDS]]) via RDAP and detail the sunset of certain obligations for registries and registrars by 28 January 2025.<ref>[https://www.icann.org/en/blogs/details/icann-board-approves-rdap-amendments-04-05-2023-en Board approves RDAP amendments, ICANN Blogs]</ref> | ||
==Overview== | ==Overview== | ||
Line 67: | Line 67: | ||
For more information, visit [[Gavin Brown]]'s [https://deployment.rdap.org/ dashboard], which is keeping track of [[TLD]]s' deployment of port 43, RDAP, HTTPS, [[DNSSEC]], and [[DANE]]. | For more information, visit [[Gavin Brown]]'s [https://deployment.rdap.org/ dashboard], which is keeping track of [[TLD]]s' deployment of port 43, RDAP, HTTPS, [[DNSSEC]], and [[DANE]]. | ||
==Implementation== | |||
On April 30, 2023, the [[ICANN Board]] directed ICANN Org to implement the RDAP Global Amendments, which specify operational requirements for providing [[RDDS]] via RDAP and sunset obligations for [[registries]] and [[registrars]] to use the [[WHOIS]] protocol by January 28, 2025. This will improve the WHOIS system by updating the underlying technology with the more secure and capable RDAP, which offers standardized queries, secure access to data, extensibility, differentiated access, support for internationalization of registration data, and the ability to search for objects. The ICANN Board carefully reviewed the proposed changes and is confident that the global amendments will lead to a better registration data query experience for contracted parties and the public.<ref>[https://www.icann.org/en/blogs/details/icann-board-approves-rdap-amendments-04-05-2023-en ICANN Board Approves RDAP Amendments, ICANN Blogs]</ref> | |||
==References== | ==References== |