5 ms·
Am I the only one who believes .tld model is broken? ICANN and IANA overseeing all .tld creation, the current pollution with thousands of .ltds, being just two
by DeathArrow 7y ago
Am I the only one who believes .tld model is broken? ICANN and IANA overseeing all .tld creation, the current pollution with thousands of .ltds, being just two problems.
Maybe even the .tld model is too old to help identify hosts. In the beginning of Internet com, edu, gov, mil, org were enough to group hosts. But now, that we have zillions of hosts, .tld might not be enough.
If IPv6 is a response to IPv4 limits, maybe we need something better than .tld, too.
- markovbot 7y agoWhat are your concerns about TLD "pollution"? opening up TLDs for sale seems like a (somewhat) logical way to expand the available namespace for domains. We have zillions of hosts, why require them to conform to one of a few random categories. Certainly, I have issues with how TLDs are allocated and controlled, but that doesn't mean that the general idea of allowing essentially arbitrary top level domains the same the way we do with second level domains is inherently a bad thing.
- ender341341 7y agoThe main issue is that it breaks expectations. Someone missing a space after a period now potentially typed in a syntactically valid URL (I see this pretty commonly in texts where the messaging app decides its a link), it breaks the UX of searching in browsers URL/Omni-bar and now you have to include a question mark for lots of cases where you haven't for multiple decades.
- labawi 7y agoIt ossifies the namespace. As in, you can't have a name that is both reasonable and can coexist with the current DNS model. Any of .onion, .bit, .coin, .eth, .crypto, .zil, can expect the .dev treatment, or, in time there won't be many nice available one for future developments. Similar issue might be with things like .ipfs, which don't resolve in the usual sense, but could cause confusion if there was an ICANN .ipfs domain. Some domain trader will come and say those aren't "real" names, and you are supposed to rent them from ICANN, but that seems like a protection racket.
- my123 7y ago.onion is reserved, no risk for it at least... (as a special use domain) https://lwn.net/Articles/657056/ https://lwn.net/Articles/657056/
- labawi 7y agoThanks. List for those interested: https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml https://www.iana.org/assignments/special-use-domain-names/sp...
- finnthehuman 7y ago>opening up TLDs for sale seems like a (somewhat) logical way to expand the available namespace for domains. It does the reverse. There is only one root zone. Before the root was a free-for-all there were hundreds of different areas to set up shop in the namespace. Now there are exactly two: 1. have fuckloads of money to piss away on a vanity TLD, or 2. use someone else's TLD. Every TLD has the same possibility space as the root zone, but we only get one root zone. There are no do-overs. Careful creation of TLDs allowed mistakes of previous TLDs models to not be repeated, experimentation with different implementations, business models or namespace allocation strategies. Now there's exactly one. We used to have headroom at the top to sidestep "hope an existing brand isn't squatting the name" and try things like country code TLDs, .arpa, and .int. Or tack resolution experiment onto the side with .local or .onion. If you wanted to do any of those now, it's impossible because the namespace has been reduced. Go back to options 1 and 2.
- michaelt 7y ago> opening up TLDs for sale seems like a (somewhat) logical way to expand the available namespace for domains. Some would say the new gTLDs have failed to increase the supply of useful domain names, because the only people who use the likes of .info and .biz are scammers, and that bad reputation scares users off. It was also well known from the start that the gTLD program was going to extract a lot of rent from domain owners - that the likes of Volvo would end up paying $180k for the .volvo TLD and $300 for volvo.sucks and so on. Some people see the fact gTLDs had none of the benefits and all of the costs, and yet ICANN keeps on issuing them, as a sign that it was never about the benefits to begin with - that it was about shaking people down for rent all along.
- dmm 7y agoThey tlds are basically scams. When they are introduced they claim to have a rollout schedule that allows the general public to register names but the good names are effectively reserved. I tried to buy california.beer on the first day .beer was available to the public. It was always listed as unregistered but if I tried to buy it strange errors occurred. After the time period where they were required to allow registrations for a set price, california.beer was listed for $1000+.
- deleted 7y ago[deleted]
- fastball 7y agoThere are a great many people working on this[1]. The problem is that these solutions have a worse UX for the consumer than the status quo. [1] https://en.wikipedia.org/wiki/Alternative_DNS_root https://en.wikipedia.org/wiki/Alternative_DNS_root
- DeathArrow 7y agoThanks, is interesting to read. I fail to see alternative DNS as much better solution, as that still depends on having tlds. For sure, identifying hosts in a "good for all purposes and all actors" manner it isn't a easy problem to solve, but it something that might makes lives of many easier. And even if you come up with a great solution, how you convince most actors to use it?
- tasuki 7y agoThere's a blockchain project for everything these days, so there's also a blockchain project for TLDs: https://handshake.org/ https://handshake.org/ If we had DNSSEC and DANE support in browsers, it would solve the security problems stemming from certificate authorities being able to issue certificates for any domain they like. Handshake would enable people to actually own their domains and bypass the CAs altogether.
- StavrosK 7y agoNextDNS has native support for Handshake domains, I started using NextDNS (because it's fantastic in its own right) and I can resolve Handshake domains "for free" (with no other configuration).
- tptacek 7y agoIt would solve that problem by allowing governments to directly issue certificates for every domain under their TLD, while not actually preventing CAs from doing anything (see Adam Langley's post for why), all the while allowing this weird blockchain project to monetize its own quirky version of the DNS. I don't understand why this project is taken seriously.
- rasengan 7y ago> It would solve that problem by allowing governments to directly issue certificates for every domain under their TLD, while not actually preventing CAs from doing anything (see Adam Langley's post for why) Definitely a valid point - DNSSEC and DANE are incomplete without Handshake [1]. > quirky version of the DNS It's the same DNS, simply the root was decentralized from ICANN to the commons. > I don't understand why this project is taken seriously. The reason the project is taken so seriously by so many is because the project improves our internet by improving security [2] and gives ownership of the internet back to the people where it originated, and where it belongs [3]. [1] https://github.com/handshake-org/hdns https://github.com/handshake-org/hdns [2] https://handshake.org/files/handshake.txt https://handshake.org/files/handshake.txt '### Proof of Work as a Trust Anchor' [3] https://handshake.org/files/handshake.txt https://handshake.org/files/handshake.txt '# Stakeholders'
- cryptonector 7y ago> If IPv6 is a response to IPv4 limits, maybe we need something better than .tld, too. You get 63 bytes (really, ASCII chars, fewer Unicode codepoints using IDNA) per-label in a DNS domainname, and you can have many labels per-domainname, which means we really can't run out of names the way we have run out of IPv4 addresses. The comparison you drew is just not valid. By "tld" you seem to mean "DNS". DNS is basically irreplaceable at this point. We can replace the UDP port 53 protocol with, e.g., DoT (DNS over TLS) or DoH (DNS over HTTP), maybe nice RESTful APIs -- whatever, but we can't replace the DNS data model because it's too deeply embedded, and not exactly busted and in need of replacement. That is, domainnames are here to stay. DNS Resource Records are here to stay. Access methods and representation on the wire can change, but their semantics can't. Given that, more TLDs, or not, makes no difference whatsoever to availability of domains for all sorts of organizations, as well as individuals.
- colejohnson66 7y agoI’m being facetious, but what’s to stop someone from registering “microsoft “ (note the space at end)? ASCII printables isn’t limited enough.