How is Whois replacing RDAP currently evaluated?

[janwillemstegink]

For internet.nl, registration of a webdomain may become of additional value. All kinds of new scripts become annoyingly complicated.

On https://rdap.hostingtool.nl/ my modeling should minimize the gap between technical and functional understanding. Its code is on https://github.com/janwillemstegink/rdap_view_model.

1. The role of an entity is unnecessarily hard to read from the JSON format. In my PHP, an initial foreach loop first detects a role's entity key;
2. There are more new and also relevant zone details to display, such as a trade name of the applicable registry. Note: The clear name 'NL Domain Registry' is not (yet) a trade name in the Dutch Business Register;
3. Field names can be more readable by humans;
4. For the .nl zone, wrong display of special characters has been reported. Note: Zone details, such as restrictions, must indeed be read together with domain details in order to work legally.

Think about helping make RDAP a success. As with the DNS discussion about a new authority, the RDAP protocol also requires maintenance by an authority.

[bwbroersma]

Relevant info: ICANN Registration Data Access Protocol Timeline from 2015-2019.

From the ICANN RDAP FAQ:

Will RDAP replace web-based and port 43 WHOIS?

ICANN-accredited registrars currently must provide access to registration data to the public in two ways:

• An interactive web page provided on the registrar's website (web-based WHOIS); and
• WHOIS (port 43) lookup as defined by RFC 3912.

In the short term, RDAP will not replace web-based or port 43 WHOIS. Based on current policies and agreements, contracted parties will be required to implement RDAP in addition to (port 43) WHOIS and web-based WHOIS.

Is there a TLD overview?

[bwbroersma]

I found one: https://deployment.rdap.org/

[mdavids]

I found one: https://deployment.rdap.org/

Seems outdated: https://rdap.sidn.nl/domain/example.nl

[bwbroersma]

RFC 9224 - Finding the Authoritative Registration Data Access Protocol (RDAP) Service / https://www.iana.org/assignments/rdap-dns/rdap-dns.xhtml

So this should be a more official source: https://data.iana.org/rdap/dns.json (also interesting: https://data.iana.org/rdap/). This also does not list nl / SIDN. So maybe the SIDN RDAP it's still in beta, or it's not yet requested to add it.

[janwillemstegink]

5 jun 2024 16:42 CEST: EURid for .eu, .it and .be: For the moment there are no concrete plans to implement RDAP.

Conclusion - A Dutch Ministry of Digital Affairs could take action on these points:

• a next version of the RDAP protocol designed for web id's, optimized for holder types, a communicative fixed field order, clearly specified by role even if duplicate, essential fields mandatory even if empty, and field names optimized for human readability;
• a rate structure almost without discounts and without mutation costs (EU TLD's and gTLD's);
• a country level agreement about storage of entity domain names in order to audit deviations (security officer login);
• approachable such as through GitHub issues.

[janwillemstegink]

Comments from Stegink Hosting & E-mail regarding NIS2

Searching for RDAP leads to potatoes!

1. In my opinion, the RDAP protocol, for domain and IP registration, needs a next version to comply.
   • The expected web IDs in Trade Registers are getting closer.
   • RDAP software does not need to grow as it does now. See also my https://rdap.hostingtool.nl.
   • The European Commission can take steps towards the desired situation;
2. The draft text is about multiple storage of domain registration:
   • A registry of entity-domain name relationships facilitates the audit of deviations from global RDAP data.
   • The Security / Data Protection Officer must be accountable for the relationship between an entity and a domain name.
   • A separate register (from Apeldoorn) can work with the simple interface of the Trade Register;
3. The Trade Register benefits from US English. This includes table definitions, search field names and applications.
   • English is more relevant than Dutch for the Trade Register than for the Land Registry;
4. I saw about thirty specialist vacancies at the Chamber of Commerce.
   • With Logius, the central government can make the expertise of the Kadaster work broadly;
5. The zone holder and the registrar cannot simply arrange identification of an entity between themselves.
   • The costs for customers of mutating are now a revenue model. The EU can focus on period costs.
   • The generic top-level zones seem controllable compared to a country code top-level zone such as .eu;
6. The volume discounts by zone holders are likely to lead to unfair competition.
   • What would be a platform to weigh interests? GitHub is useful for software.

NB: Legal formulation is not my intention. First I think of progressive insight.

Arnhem, Jan Willem Stegink https://janwillemstegink.nl/

[bwbroersma]

The answer to "How to successfully use RDAP protocol instead of WHOIS?" is: there are no way to successfully use RDAP, only, perhaps, to try some experimental implementation... But even experimental, I not know how to try it.

https://stackoverflow.com/a/37835341