Registration Data Access Protocol: Difference between revisions
No edit summary |
No edit summary |
||
| 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== | ||