mirrors/nomulus
1
0
Fork 0
mirror of https://github.com/google/nomulus synced 2026-01-03 11:45:39 +00:00
Code Issues Releases Wiki Activity

Update RDAP response profile + tech impl guide versions (#2778)

Browse Source 
This corresponds to the Feb 2024 response profile section 1.2 and
implementation guide 1.3 respectively, now that we comply (or are, at
least closer to complying), with the Feb 2024 versions.

This should probably depend on https://github.com/google/nomulus/pull/2771
because that includes a small change included in the Feb 2024 version

This also updates the documentation to reference the proper areas of the
specifications.
This commit is contained in:
gbrodman
2025-07-09 17:02:33 -04:00
committed by GitHub
parent f34aec8b56
commit c6868b771b
67 changed files with 195 additions and 349 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/coding-faq.md
View File

@@ -48,23 +48,22 @@ much internally for this reason.
## Do you support RDAP?
We are working on an implementation of the Registry Data Access Protocol (RDAP),
ICANN's proposed successor to WHOIS, which provides similar data to WHOIS, but
in a structured format. The standard is defined in RFCs 7480 through 7484:
We provide an implementation of the Registry Data Access Protocol (RDAP) which provides
similar data to the outdated WHOIS protocol, but in a structured format. The
standard is defined in STD 95 and its RFCs:
* [RFC 7480: HTTP Usage in the Registration Data Access Protocol
(RDAP)](https://tools.ietf.org/html/rfc7480)
* [RFC 7481: Security Services for the Registration Data Access Protocol
(RDAP)](https://tools.ietf.org/html/rfc7481)
* [RFC 7482: Registration Data Access Protocol (RDAP) Query
Format](https://tools.ietf.org/html/rfc7482)
* [RFC 7483: JSON Responses for the Registration Data Access Protocol
(RDAP)](https://tools.ietf.org/html/rfc7483)
* [RFC 7484: Finding the Authoritative Registration Data (RDAP)
Service](https://tools.ietf.org/html/rfc7484)
* [RFC 9082: Registration Data Access Protocol (RDAP) Query
Format](https://tools.ietf.org/html/rfc9082)
* [RFC 9083: JSON Responses for the Registration Data Access Protocol
(RDAP)](https://tools.ietf.org/html/rfc9083)
* [RFC 9224: Finding the Authoritative Registration Data (RDAP)
Service](https://tools.ietf.org/html/rfc9224)
Some gaps in the implementation remain, but most of the functionality is
currently available. If you access this endpoint on a running Nomulus system:
If you access this endpoint on a running Nomulus system:
`https://{PROJECT-ID}.appspot.com/rdap/domains?name=ex*`
@@ -97,5 +96,4 @@ can specify a TLD after the domain name wildcard (e.g. abc*.tld), and you can
specify .domain.tld after the nameserver wildcard (e.g. ns*.domain.tld). But you
can't do anything else, like searching for nameservers with ns*.tld. When using
a wildcard, we currently require a prefix of at least two characters, to avoid
having someone search for *. There are other limitations to the system which we
plan to address in the future.
having someone search for *.