The document shepherd is Michael Szucs.
Pete Resnick is the responsible Area Director.
The Registration Data Access Protocol (RDAP) provides "RESTful" web services to
retrieve registration metadata from domain name and regional internet
registries. This document specifies a method to find which Registration Data
Access Protocol (RDAP) server is authoritative to answer queries for a
requested scope, such as domain names, IP addresses or Autonomous System
The document is requesting Proposed Standard status as per the definition of a
Technical Specification in RFC2026 Section 3.1.
2. Review and Consensus
This document was discussed at length at recent IETF meetings. Extra
consideration was paid by the working group to the IANA Considerations section.
The document appears to have the support of the WG, and there is at least one
implementation in progress.
There are no known threats of appeals for this document.
I don't believe any particular external review is needed for this document.
3. Intellectual Property
Each author has confirmed conformance with BCP 78/79. Authors have
reconfirmed there are no IPR issues following WGLC.
There are no IPR disclosures on the document.
4. Other Points
The document calls for IANA to setup four RDAP registries.
The WG spent a good deal of time working on the wording of the IANA section.
Attempts were made to clarify the specific data output requirements without
providing instruction to IANA on update frequency, policy, etc., since this
work has the unusual complication that the registry policies actually will
mirror whatever rules ICANN puts in place for updating their name and number
This draft does specify that IANA should implement the required registries in
JSON format, rather than specifying only output format requirements. This was
previously corrected but has reappeared.
The document contains a normative reference to RFC 4627 which is obsoleted by
RFC 7159; these do not currently appear in the downref registry.