Hi Steve,
Sorry, I missed this on Monday as I am travelling this week.
Are you able to share the Interisle report?
As a Registry, I know we are contractually required to provide:
- Registry Agreement – Specification 3 – 1. Fields 1 & 2 on Monthly reports:
01 registrar-name
02 iana-id
…
- Registry Agreement – Specification 4 – 1.4.6 (2) on Whois Domain Name response format:
….
Registrar: EXAMPLE REGISTRAR LLC
Registrar IANA ID: 5555555
Registrar Abuse Contact Email: email@registrar.tld
Registrar Abuse Contact Phone: +1.123551234
….
- Registry Agreement – Specification 4 – 1.4.7 (2) on Whois Registrar Information response format:
Registrar: Example Registrar, Inc.
Street: 1234 Admiralty Way
City: Marina del Rey
State/Province: CA
Postal Code: 90292
Country: US
Phone Number: +1.3105551212
Fax Number: +1.3105551213
Email: registrar@example.tld
Registrar WHOIS Server: whois.example-registrar.tld
Registrar URL: http://www.example-registrar.tld
Admin Contact: Joe Registrar
Phone Number: +1.3105551213
Fax Number: +1.3105551213
Email: joeregistrar@example-registrar.tld
Admin Contact: Jane Registrar
Phone Number: +1.3105551214
Fax Number: +1.3105551213
Email: janeregistrar@example-registrar.tld
Technical Contact: John Geek
Phone Number: +1.3105551215
Fax Number: +1.3105551216
Email: johngeek@example-registrar.tld
>>> Last update of WHOIS database: 2009-05-29T20:15:00Z <<<
Both whois format requirements translate to RDAP requirements.
Pre-2012 Registries may still be running under slightly different requirement, but are being folded in as they renew their contracts.
----------
I can’t think of a configuration where a Domain Name would be registered without an IANA-ID.
I don’t read that you are suggesting that.
In practical terms, while there is a public list of IANA-IDs and Registrar Names (https://www.iana.org/assignments/registrar-ids/registrar-ids.xhtml),
there is no authoritative list of Abuse Contact Email and Phone, or the rest of the information in 1.4.7.
Different Registry BackEnds have adopted different strategies to keep the Registrar information up to date, some take the Registrar name from the IANA list and provide some form to collect the other data, other offer allow/require their Registrars to manage
their information on their own including the Registrar Name, some have more manual processes.
As a user of the Monthly Reports as per Spec 3, I know that a same IANA-ID might have slightly different variants of Registrar names depending on the TLD reporting, but there is
always some name.
I know that whois/rdap went through some teething when the Abuse Contact requirements were added, but that Compliance added checking that information is provided to their regular
TLD audits. I can’t think of a reason where this might be a significant problem flying under the radar.
Looking forward to your webinars.
Kindly,
From:
Steve Crocker via Gnso-rdrs-sc <gnso-rdrs-sc@icann.org>
Date: Monday, 13 January 2025 at 12:30 pm
To: Steve DelBianco <sdelbianco@netchoice.org>, gnso-rdrs-sc@icann.org <gnso-rdrs-sc@icann.org>
Cc: GNSO-Secs <gnso-secs@icann.org>
Subject: [Gnso-rdrs-sc] Two items for today's RDRS meeting
1. Registrar info A report from Interisle shows a fairly large number of instances where queries about a registered domain name did not yield the name of the registrar.
What is the official policy regarding disclosure of the name of the registrar?
This Message Is From an External Sender
This message came from outside your organization.
A report from Interisle shows a fairly large number of instances where queries about a registered domain name did not yield the name of the registrar.
What is the official policy regarding disclosure of the name of the registrar?
2. Two upcoming Edgemoor Research Institute webinars
We (Edgemoor Research Institute) will be giving a pair of webinars on Project Jake describing a comprehensive framework for a registration data directory service
that includes disclosure policies and other attributes for a more complete, effective and efficient service.
The first will be on 6 Feb and will give an overview and feature inputs from representatives from several constituencies. The second webinar on 27 Feb will go
into further detail.