Hi George, this is a difficult question to answer, especially for registrars operating a reseller channel as their users are usually not the registrants. For us, revenue is based on purchase price, maintenance cost and implementation costs. So I would assume the revenue to be higher for sunrise registration simply based on the fact that most registries have higher sunrise registration fees than standartd registration fees. But this will vary from registrar to registrar. Some registrars charge nothing over the purchase prices and make their money with add-on services. It really depends on the business case. I do agree that domains that are registered but not used are detrimental to the registry if there is someone who wanted to buy and use it but could not. But this is based mainly on my experience that the best advertizement for a new TLD is publicv use cases. The more a TLD is seen in the wild and used by its registrants, the faster it will usually grow, at least in my personal observation (for which I have no studies to back that up). Best, Volker Am 14.08.2017 um 14:26 schrieb George Kirikos:
Hi Volker,
On Mon, Aug 14, 2017 at 8:02 AM, Volker Greimann <vgreimann@key-systems.net> wrote:
Thanks George. Having the list public serves many benefits, least of all to allow registrars that could not offer new TLDs until the claims phases closed to see these domains from day one simply because their systems di not allow for processing of these notices. I agree with you 100%, that there are many benefits that should far exceed the costs. It should have been public from day 1, and this PDP has the opportunity to correct past mistakes, based on the experiences/data/evidence that didn't exist before the policy was created.
One of the things I wanted to ask you (and other registrars and/or ISPs can weigh in too), is whether you have any data on ARPU (average revenue per user) for sunrise registrations, compared with 'normal' registrations (e.g. non-defensive registrations, registered in landrush or GA).
The reason I ask this is that it's an important consideration when looking at the overall costs/benefits of the sunrise period.
My hypothesis is that a TM holder buying a domain for defensive purposes *isn't* going to be buying things like webhosting, SSL, web design services, email hosting and all the other kinds of offerings from registrars and resellers (especially the consumer-oriented registrars like GoDaddy, Tucows, etc., as opposed to the 'brand protection' registrars like Markmonitor, CSC, etc.). In essense, that sunrise-registered domain name is blocking someone else who *would* be buying those high margin value-added services from registrars and their resellers/partners. If my hypothesis is correct, that difference should be reflected in the ARPU of registrars and their resellers/service providers. It should be measurable.
We know that names 'captured' in sunrise have some obvious negative effects on registry operators. For exampled the delayed starts, compliance costs, being forced to spend on monopolistic providers (TMCH etc.) and regulatory burden. There's the "deprivation of oxygen" as defensive sunrise-registered names aren't 'used', and thus not promoted by the end-user which would promote the entire extension (e.g. just like Verisign doesn't have to spend much promoting dot-com, because there's are many end-users already promoting active websites ending in dot-com).
But, does that also hold true for the registrars, via experience/data? I'm sure the registrars would guard the precise *magnitude* of that data (except for public companies like GoDaddy which publish their total ARPU). But perhaps some registrars might share the *relative* ARPUs for the various subsets of registered names.
e.g. if a sunrise-registered domain name has a ARPU indexed to be 1.00 (or $X), is the ARPU for a landrush or GA domain name higher, or lower, and by how much? (e.g. if it's 2.00 or $2X, then that's a real cost of sunrises for registrars/resellers/partners).
This is perhaps data that should be broadly solicited from registrars/hosting providers/web designers, etc., and added by ICANN staff to the sunrise data collection document.
Sincerely,
George Kirikos 416-588-0269 http://www.leap.com/ _______________________________________________ gnso-rpm-wg mailing list gnso-rpm-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rpm-wg
-- Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung. Mit freundlichen Grüßen, Volker A. Greimann - Rechtsabteilung - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen. -------------------------------------------- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.