}}</ref> RDAP designers, many of whom are members of [[Regional Internet registry|number]] or [[Domain name registry|name]] registries, strove to keep the protocol as simple as possible, since complexity was considered one of the reasons why previous attempts, such as [[Cross Registry Information Service Protocol|CRISP]], failed. RDAP is based on [[REST|RESTful web services]], so that error codes, user identification, authentication, and access control can be delivered through [[HTTP]].<ref>{{cite web
| url=https://www.ietf.org/wg/concluded/weirds
| title=Web Extensible Internet Registration Data Service (weirds)
Line 82:
== WHOIS Replacement ==
On January 19th19, 2023 ICANN opened voting on a global amendment to all its registry and registrar agreements. In it they defined a RDAP Ramp-Up Period of 180 days starting with the effectiveness of this amendment. 360 days after this period is defined as the WHOIS Services Sunset Date, after which it is not a requirement for registries and registrars to offer a WHOIS service and instead only a RDAP service is required. All voting thresholds were met within the 60 day voting period and the amendment will be submitted to the ICANN Board for approval and implementation.<ref>{{Cite web |title=2023 Global Amendments to the Base gTLD Registry Agreement (RA), Specification 13, and 2013 Registrar Accreditation Agreement (RAA) - ICANN |url=https://www.icann.org/resources/pages/global-amendment-2023-en |access-date=2023-04-07 |website=www.icann.org}}</ref>
