Registration Data Access Protocol: Difference between revisions

Revision as of 15:18, 6 September 2023

Revision as of 15:57, 6 September 2023

Line 72:

| 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}}</ref>

==Examples==

An example of a RDAP client and server exchange:<ref>{{cite web|title=HTTP Usage in the Registration Data Access Protocol (RDAP)|url=http://www.rfc-editor.org/rfc/rfc7480.html|access-date=27 October 2021}}</ref>

Client:

<TCP connect to rdap.example.com port 80>

GET /rdap/ip/203.0.113.0/24 HTTP/1.1

Host: rdap.example.com

Accept: application/rdap+json

rdap.example.com:

HTTP/1.1 301 Moved Permanently

Location: http://rdap-ip.example.com/rdap/ip/203.0.113.0/24

Content-Length: 0

Content-Type: application/rdap+json

<TCP disconnect>

Client:

<TCP connect to rdap-ip.example.com port 80>

GET /rdap/ip/203.0.113.0/24 HTTP/1.1

Host: rdap-ip.example.com

Accept: application/rdap+json

rdap-ip.example.com:

HTTP/1.1 200 OK

Content-Type: application/rdap+json

Content-Length: 9001

{ ... }

<TCP disconnect>

==Number resources==