Content deleted Content added
VulcanSphere (talk | contribs) |
→WHOIS replacement: hyphen missing from compound modifier |
||
| (12 intermediate revisions by 3 users not shown) | |||
Line 50:
| date=2015-03-25
| publisher=[[Internet Engineering Task Force|IETF]]
| access-date=2016-11-10
| archive-date=2015-07-11
| archive-url=https://web.archive.org/web/20150711224619/http://www.ietf.org/wg/concluded/weirds
| url-status=live
}}</ref>
The biggest delay in getting RDAP done turned out to be the ''bootstrap'', figuring out where the server is for each top-level ___domain, IP range, or ASN range. [[Internet Assigned Numbers Authority|IANA]] agreed to host the bootstrap information in suitable registries, and publish it at a well-known ___location URLs in JSON format. Those registries started empty and will be gradually populated as registrants of domains and address spaces provide RDAP server information to IANA.<ref>{{cite web
Line 58 ⟶ 62:
| date=2014-09-10
| website=jl.ly
| accessdate=2016-11-10
| archive-date=2022-12-25
| archive-url=https://web.archive.org/web/20221225110924/https://jl.ly/ICANN/weirds14.writeback
| url-status=live
}}</ref><ref>{{cite IETF
| title = Finding the Authoritative Registration Data (RDAP) Service
| rfc = 7484
Line 72 ⟶ 80:
| date=2015-06-22
| publisher=[[American Registry for Internet Numbers|ARIN]]
| accessdate=2016-11-10
| accessdate=2016-11-10}}</ref> For name registries, [[ICANN]] requires RDAP compliance since 2013.<ref name="icann2013">{{cite web▼
| archive-date=2023-08-01
| archive-url=https://web.archive.org/web/20230801120619/https://www.arin.net/resources/rdap.html
| url-status=live
▲
|url = https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en
|title = 2013 Registrar Accreditation Agreement
Line 88 ⟶ 100:
| publisher=[[ICANN]]
| quote=Registry Operator shall implement a new standard supporting access to ___domain name registration data (SAC 051) no later than one hundred thirty-five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry
| accessdate=2016-11-10
| archive-date=2022-09-01
| archive-url=https://web.archive.org/web/20220901042744/https://newgtlds.icann.org/en/applicants/agb/agreement-approved-02jul13-en.pdf
| url-status=live
}}</ref>
==Number resources==
RDAP databases for assigned IP numbers are maintained by five [[Regional Internet registry|
==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 [[General Data Protection Regulation|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]] |access-date=June 8, 2020 |archive-date=May 25, 2023 |archive-url=https://web.archive.org/web/20230525235553/https://www.theregister.com/2019/10/23/icann_kills_whois/ |url-status=live }}</ref> To solve the conflict between GDPR and ICANN policies ICANN published a temporary specification according to which all contact details need to be redacted for privacy reasons if they fall under the GDPR, unless the contact explicitly allows publication. This includes email addresses, however the registrar has to offer an anonymized email address or a web form to allow forwarding of information to contacts. The registry RDAP/WHOIS response has to contain a notice that these options to contact the contacts are only available in the registrar RDAP/WHOIS.<ref name=":0">{{Cite web |title=Temporary Specification for gTLD Registration Data
To keep RDAP information accurate, registrars have to send a yearly Whois Data Reminder Policy (WDRP) notice to the registrant contact. This is commonly done via email containing all the RDAP information the registrar has and asking the registrant to update it immediately if it is incorrect, while at the same time reminding the registrant that incorrect RDAP information can lead to the deletion of the ___domain name.<ref>{{Cite web |title=Whois Data Reminder Policy
== WHOIS replacement ==
On January 19, 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
== Query example ==
To query RDAP, there are several software and web clients
In certain
Below is an example of RDAP data returned for an individual resource holder. This is the result of a RDAP query in raw format (using OpenRDAP client)
> rdap finalfantasyxiv.com
Domain:
Line 173 ⟶ 189:
== Extensions ==
The RDAP protocol allows for extensions and IANA is maintaining a list of known RDAP extensions. Some of these extensions are defined by RFCs, such as
==Related standards==
Line 196 ⟶ 212:
* [[Domain name registry]]
* [[Domain name registrar]]
* [[Extensible Provisioning Protocol]]
==References==
Line 205 ⟶ 221:
* [https://www.iana.org/assignments/rdap-extensions/rdap-extensions.xhtml IANA RDAP Extensions]
* [https://www.iana.org/assignments/rdap-json-values/rdap-json-values.xhtml IANA RDAP JSON Values]
* {{Github|icann/icann-rdap}}
* {{Github|openrdap/rdap}}
* [https://rdap.dev/ rdap.dev]
* [https://about.rdap.org/ rdap.org]
* [https://www.apnic.net/apnic-info/whois_search/about/rdap RDAP page at APNIC]
* [https://www.arin.net/resources/rdap.html RDAP page at ARIN]
| |||