Registration Data Access Protocol: Difference between revisions

Revision as of 11:57, 10 July 2015

Revision as of 19:16, 12 July 2015

Line 29:

| publisher = [[Internet Engineering Task Force|IETF]]

| accessdate =July 10, 2015

}}</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 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=http://www.ietf.org/wg/concluded/weirds |title=Web Extensible Internet Registration Data Service (weirds) Charter|author=<!--Staff writer(s); no by-line.--> |date=25 March 2015 |publisher=[[Internet Engineering Task Force|IETF]] |access-date=10 Jul 2015}}</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 |url=http://jl.ly/ICANN/weirds14.writeback |title=The replacement for WHOIS is surprisingly close |author=[[John Levine]] |date=10 September 2014 |website=jl.ly |access-date=10 Jul 2015}}</ref><ref>{{cite IETF

| title = Finding the Authoritative Registration Data (RDAP) Service

| rfc = 7484