Hi all,
It's good the see the email lists works
😊
My understanding was we/At-Large supposed to respond to questions addressed with a "focus on registration data accuracy", hence my input to "how can the ICANN Accredited Registrars
improve their process for validation of registration data"?
In my view, it is of importance to have this discussion within the gTLD environment. This view doesn't prevent Registrars to use the same techniques as European ccTLD registrars
use when validating received registration data for a domain name. I have years of experience as Registrar, both gTLD/ICANN and ccTLD, where I used national databases to check registration data. Checking using national databases in an automatic way, can be
costly both in access to the databases and by development of the provision line.
Adding this kind of "database checking" mandatory for the gTLDs will - in my view, create both policy development and time/cost.
What does it mean for registration data to be accurate?
The GNSO-TPR WG discussed this in detail in the Change of Registrant Data (CORD) charter questions. The present policy for a "material change" is not very user friendly.
The GNSO-WG agreed that any "material change" should be validated by the registrar but verification from the domain name holder should not be mandatory.
I agree that the majority of "end-users" may not know the
difference between the gTLDs and the ccTLDs. But we - as representative for the "end-users" should not mix the TLDs
in our responses. Maybe we should add another «tag” to "end-user perspective": "(how
to) educate end-users".
Regards,
Steinar Grøtterød