As the WG has deliberated on the below Charter Questions, We may be constraining our thinking by deliberating on existing WHOIS data elements, assuming today’s (often implicit) definitions, without clearly-stated expectations of the entities identified and/or contacted using registration data
- Who should have access to gTLD registration data and for what purposes?
- What data should be collected, stored, and disclosed for those purposes?

...

To address these concerns and enable more effective deliberation, purpose drafting teams were asked to re-convene to answer the following questions:

...

Today, each drafting team will present its answers for consideration by the full WG
Results from today’s session will be input to deliberation on possible purposes and associated data

4. Review DT answers on entities to be identified or contacted for each possible purpose for processing gTLD registration data

Domain Name Purchase/Sale

...

Registrars do not want to be the first point of contact for Tech Issue Resolution – go to the hosting provider (or the Registrant/contact) first. All the Registrar can do is take the DN down. The web host is in a much better position to disable access to the hostname (not the DN)
There are registrars whose business model includes serving as Tech Contact (value add)
Is the entity you want to reach for tech issue resolution sometimes or always the account holder? Probably not since several different entities are enumerated in the DT’s answer, but this deserves further discussion

DNS OARC meeting example – DNSSEC validation – need to contact operators of the DN, to help resolve issue, not take the entire DN down
What is the role of the Reseller in this purpose?
It is not necessary that Registrants understand the technical issue – the “mechanics of the Internet” need to understand/resolve the issue being reported
You only need the help of a domain contact when the IP isn’t resolving
Nameservers will not always lead to the hosting provider
Hosting is not regulated by ICANN – that other part of the Internet community cannot be addressed by RDS policy
Contacting the domain holder can also be useful if the site is partially pirated, to warn the owner. no need for the host to shut down the site, but for the domain holder to clean its database

...

Versions Compared

Key