Advancing the Registration Data Access Protocol (RDAP) to Internet Standard
The information below is for an old version of the document.
|Document||Proposed status change||Advancing the Registration Data Access Protocol (RDAP) to Internet Standard Snapshot|
|Moves to Internet Standard||RFC7480, RFC7481|
|State||In Last Call|
|Responsible AD||Barry Leiba|
|Send notices email@example.com, firstname.lastname@example.org|
RFCs 7480 ("HTTP Usage in the Registration Data Access Protocol (RDAP)") and 7481 ("Security Services for the Registration Data Access Protocol (RDAP)") were published as Proposed Standards in March, 2015, along with RFCs 7482 ("Registration Data Access Protocol (RDAP) Query Format"), 7483 ("JSON Responses for the Registration Data Access Protocol (RDAP)"), and 7484 ("Finding the Authoritative Registration Data (RDAP) Service"). RFCs 7482 and 7483 have been updated to address known errata and necessary clarifications based on implementation experience, and the 7482bis and 7483bis Internet-Draft documents are on track for approval as Internet Standards. A revision of RFC 7484 is being considered by the REGEXT working group for submission as Internet Standard. RFCs 7480 and 7481 have no verified errata, and no known issues that require that the documents be revised prior to a change in status from Proposed Standard to Internet Standard. The RFC 6410 requirements for "at least two independent interoperating implementations with widespread deployment and successful operational experience" and "no unused features in the specification that greatly increase implementation complexity" have been met. This status change, therefore, requests a change in status for RFCs 7480 and 7481 from Proposed Standard to Internet Standard.