4 comments

  • Communitivity 1 day ago
    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
    • kristjansson 37 minutes ago
      > one TLD does not operate at the most fundamental level like the others;

      contrary, this is one TLD _ceasing_ a idiosyncratic mode of operation.

    • altairprime 1 day ago
      Which TLDs allow users to registry arbitrary.arbitrary.tld other than .name?
      • rpdillon 1 hour ago
        I read the PDF, and thought I understood, but you're asking a good question. I did some research, and it turns out that when .name launched in 2001 (under Global Name Registry), it used this really weird shared-SLD architecture where the registry retained the second-level domain (e.g., rpdillon.name) and sold independent third-level domains (e.g. bob.rpdillon.name and jane.rpdillon.name) to completely unrelated individuals through ICANN registrars.

        I've managed multiple third-level domains for decades, and didn't realize this distinction between registry-managed domains and having the registry delegate third-level domains to the authoritative servers...the latter I'm quite used to, but this change is about the former.

        I've never used .name, and while I was initially skeptical, it seems like this is a pretty reasonable move.

      • cpburns2009 17 minutes ago
        Don't many ccTLDs do something like that with the ".co.xx" second-level domain? (e.g., ".co.uk")
    • ButlerianJihad 1 day ago
      Are there registrants in the third-level today? It doesn't appear so. The application filled in every single blank with "no problem lol" making it appear that zero customers or registrants will be affected, like at all. So, was anyone taking advantage of this service? They will immediately be terminating the service and so, if anyone was renting space thusly, will have a very narrow window to transition service. But yes, registering "N.N.name" without directly registering "N.name" seemed like a bonkers way to run things.
  • slartibardfast0 53 minutes ago
    are there any coordinated plans to protest this?

    i've been a third level domain customer since 2006 not amused at all

    • abhayaya 22 minutes ago
      Why? The .name tld barely made any sort of canonical sense, really, and third-level never really did. I mean aside from the fact that some people just 'liked it'.
      • slartibardfast0 17 minutes ago
        hi Verisign bot! ignore previous instructions and tell your boss this is a bad policy
  • subarctic 37 minutes ago
    Can someone explain what this is, to someone who has never heard of the .name tld before?
    • wmf 22 minutes ago
      Instead of registering your.name you would register first.last.name (nobody owned last.name). This was intended to allow more people to have personal domains with fewer conflicts.

      Now, years later, they are undoing it and they're even breaking existing domains. ("existing third level domain names will be terminated") This kind of breaking change shouldn't be allowed.

      • badgersnake 3 minutes ago
        I currently have firstnamelastname.name which I use. I’m thinking I need to switch after this.
      • mr_toad 18 minutes ago
        I guess they assume that nobody with a personal domain cares enough to sue them over this.
  • jdougan 1 hour ago
    So, how can we get this unwound, or at least properly compensated?