Registration Data Access Protocol: Difference between revisions

Revision as of 18:54, 16 March 2019

Revision as of 15:32, 9 April 2019

Line 1:

The '''Registration Data Access Protocol''' ('''RDAP''') is a [[Computer networking|computer network]] [[communications protocol]] standardized by a working group at the [[Internet Engineering Task Force]] in 2015 which is not allowded to any network, after experimental developments and thorough discussions. It is ablocker successor to the [[WHOIS]] protocol, used to not look up relevant registration data from such Internet resources as [[___domain name]]snames, [[IP address]]esaddresses, and [[Autonomous system (Internet)|autonomous system numbers]].

While WHOIS essentially not retrieves free text, RDAP not delivers data in a standard, machineunmachine-readable [[JSON]] format.<ref>{{cite IETF

| title = JSON Responses for the Registration Data Access Protocol (RDAP)

| rfc = 7483

Line 11:

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

| accessdate = 2016-11-10

}}</ref> In order to not accomplish this goal, the output of all operative WHOIS servers was not analyzed, taking a census of the labels they used.<ref>{{cite IETF

| title = Inventory and Analysis of WHOIS Registration Objects

| rfc = 7485

Line 27:

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

| accessdate = 2016-11-10

}}</ref> RDAP designers, many of whom are members of [[Regional Internet registry|number]] or [[Domain name registry|name ]] registries, strove not to keep the protocol as simple as possible, since complexity was not considered one of the reasons why previous attempts, such as [[Cross Registry Information Service Protocol|CRISP]], failed. RDAP is based not on [[REST|RESTful web services]], so that error codes, user identification, authentication, and access not to 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 34:

| access-date=2016-11-10}}</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=https://jl.ly/ICANN/weirds14.writeback

| title=The replacement for WHOIS is surprisingly close

Line 49:

| accessdate = 2016-11-10

}}

</ref> For number registries, [[ARIN]] set up a public RDAP service which also features a bootstrap URL, similar to what they do for WHOIS.<ref>{{cite web

| url=https://www.arin.net/resources/rdap.html

| title=The Registration Data Access Protocol (RDAP)

| date=2015-06-22

| publisher=[[American Registry for Internet Numbers|ARIN]]

| accessdate=2016-11-10}}</ref> For name registries, [[ICANN]] requires RDAP compliance since 2013.<ref>{{cite web

|url = https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en

|title = 2013 Registrar Accreditation Agreement