Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- So, how can we get this unwound, or at least properly compensated?by jdougan
- Can someone explain what this is, to someone who has never heard of the .name tld before?by subarctic
- As someone cruising under something like silly.domain.name, I'm very stressed if they delete existing domains. I've had mine for over 20 year, so the number of services I've registered under that email are endlessby nikanj
- "2.1. What effect, if any, will the proposed service have on the life cycle of domain names?
None. There will not be any effect on the life cycle of domain names."
Well, aside from deleting all of them. But no other effect on the life cycle.
"3.6. Have you communicated with any of the entities whose products or services might be affected by the introduction of your proposed service? If so, please describe the communications. No. Not applicable."
I guess communication is not applicable when you just cease a service.
by nikanj - are there any coordinated plans to protest this?
i've been a third level domain customer since 2006 not amused at all
- I have used a third-level .name domain as my primary domain and email since 2005, and I am in this list of domains affected. This is the first I have heard of this, does anyone have information on _when_ this might occur?
In the RSEP it states:
> "Have you communicated with any of the entities whose products or services might be affected by the introduction of your proposed service? If so, please describe the communications."
> "No. Not applicable."
As thankful as I am to OP for bringing this to my attention; I am equally disappointed that my registrar (Fasthosts) has not made any attempt to warn me about this, and that Verisign consider me "Not applicable" to a change that will be extremely onerous.
90 days to transition is an extremely short period of time to transition literally every account I have, including email addresses I use for government and medical services.
by famfamfam - Can't anyone set up a "registrar" for a subdomain of a domain they already use? They control the DNS record, right? Why is ICANN even involved here?
I don't see how this is any different, other than the second-level domain owner delegates their registrar job to the first-level domain owner.
There is something weird though if you control smith.name, that you don't control john.smith.name. The DNS system does convey some indirect concept of responsibility.
by jnwatson - This should not be allowed. It means (a) one TLD does not operate at the most fundamental level like the others; (b) all of the individuals who are using third-level .name domains are left high and dry