Content deleted Content added
m Undid revision 1088486025 by Jonathan92630 (talk) |
add related RFCs section |
||
Line 106:
==Name resources==
RDAP databases for registered names are maintained after ICANN agreement.<ref name="icann2013"/> Name resources are much slower, as the number of registries under ICANN is huge. In addition, as the [[GDPR]] became enforceable, in May 2018, the problem of personal data divulged via WHOIS or RDAP slowed adoption further.<ref>{{cite web |title=Haunted by Europe's GDPR, ICANN sharpens wooden stake to finally slay the Whois vampire |author=Kieren McCarthy |date=October 23, 2019 |url=https://www.theregister.com/2019/10/23/icann_kills_whois/ |work=[[The Register]]}}</ref>
==Related RFCs==
* [https://www.rfc-editor.org/info/std95 STD 95]
* {{IETF RFC|7480|link=no}}, ''HTTP Usage in the Registration Data Access Protocol (RDAP)''
* {{IETF RFC|7481|link=no}}, ''Security Services for the Registration Data Access Protocol (RDAP)''
* {{IETF RFC|8056|link=no}}, ''Extensible Provisioning Protocol (EPP) and Registration Data Access Protocol (RDAP) Status Mapping''
* {{IETF RFC|9082|link=no}}, ''Registration Data Access Protocol (RDAP) Query Format''
* {{IETF RFC|9083|link=no}}, ''JSON Responses for the Registration Data Access Protocol (RDAP)''
* {{IETF RFC|9224|link=no}}, ''Finding the Authoritative Registration Data Access Protocol (RDAP) Service''
==References==
| |||