4 ms·
> we have to assume that anything could be a TLD Yes. This has been the correct way to handle it for at least a couple of decades and perhaps arguably more. RF
by tialaramex 6y ago
> we have to assume that anything could be a TLD
Yes. This has been the correct way to handle it for at least a couple of decades and perhaps arguably more. RFC 2606 reserves a handful of TLDs (such as .example and .invalid) and it would be sane to treat these specially (e.g. this-is.invalid just isn't a valid DNS name) but otherwise the most you could say for sure about any TLD is that you don't know whether it exists.
There's a lot of bad legacy code out there which will do things like reject email addresses with a TLD longer than three characters, don't do that even if you think .horse was a bad idea.
> At this point, why not just accept any string of characters up to a certain lenght as a TLD?
With the exceptions in RFC 2606 and the practical constraint that some TLDs are "poisoned" by decades of misuse (e.g. .corp) this is the situation today.
However the next question is - who shall operate the registry for each of these TLDs? So that's what the ICANN process is for. It's not a problem for .some-ludicrous-vanity-domain-for-a-corporation as on the one hand, nobody else wanted those names (often even the corporation itself never uses them, it's just burning money) - but it gets trickier for .horse where understandably the people who own a horse's name in .horse don't want to hear about how the company operating it went bankrupt and now they need to pay somebody else or their site stops working.
- labawi 6y ago> the practical constraint that some TLDs are "poisoned" by decades of misuse (e.g. .corp) I would call it poisoned by decades of "misuse". From my POV, squatters rights should apply and ICANN has no business delegating widely used TLDs, even if they are not formally registered (in which case they would be expected to pay $$$$-$$$$$$ / y). TLDs like .onion, .corp, .lan, and other widely used TLDs (say .bit, .dn42, ...) should not be delegated by ICANN, unless it is to the undisputable current users of the TLD. There is no way a hobby project could pay $$$$$$ for registration, and if it does become successful, while not using the root nameserver services, I don't see why it should pay for the privilege.
- tialaramex 6y ago.onion was permanently reserved for Tor (which I imagine is what you'd prefer) in RFC 7686. It makes no sense to do this for say .corp because in fact the existing "squatter" users just arbitrarily assign whatever names they want, so unlike facebookcorewwwi.onion there is no agreed global meaning of headquarters.corp or hplaserjet.corp - the namespace is just poisoned.
- labawi 6y agoOn the contrary, .corp is a widespread totally established internal use domain. Just like .dev was. No, it is not globally resolvable, but it is in the same namespace (no way to add a different namespace while retaining compatibility), is widely used and I don't see why a dozen or so widely used TLDs need to be auctioned off to Donuts co. or whoever. It's not like we have a shortage of words or even operational gTLDs these days. I'm not suggesting any TLD with 3 users should be off-limits (though I don't agree with gTLDs altogether) just the really widely established ones. If a project/group/whatever successfully squats a TLD and gets widely established, then it should be protected as well. If nothing else, then by squatting itself. We do not have another namespace for alternative resolution strategies, so ICANN should not simply rent away all names. Last time I heard, ICANN was corrupt. As far as I am concerned, they have no more right to assign .corp or whatever, than I have a right to reassign and use it for other purposes on my systems. I am not paying 185000$ for gTLD, nor renting a long domain to use for internal purposes, or with my friends.
- CydeWeys 6y ago> From my POV, squatters rights should apply and ICANN has no business delegating widely used TLDs, even if they are not formally registered (in which case they would be expected to pay $$$$-$$$$$$ / y). Who's the "they" in this sentence? ICANN delegating the TLD formally is the mechanism by which you pay money to delegate a TLD. Until said TLD is delegated, it's not a real TLD, and does not resolve on the Internet. You can't use it in a meaningful sense until it is a real TLD, and once it is a real TLD, global collision rules apply. The fake use cases and the real use cases are fundamentally incompatible.
- labawi 6y agoI think I've had this discussion with you. "they" are TLDs I can use tor (.onion), namecoin (.bit), dn42 test net (.dn42) or others. They work and people use them, so not fake, just not registered with ICANN. Most of them work fine along with ICANN DNS. They require alternative forms of DNS resolution, so they don't work with ICANN DNS, but that is actually desirable for many of them. I can also have .lan addresses on my router, .corp addresses on corporate vpn, or whatever in my hosts file and they work. Hosts file works even better than global DNS, so the domains are definitely real, not fake. Just not global, even when globally used.
- rsync 6y ago"... even if you think .horse was a bad idea ..." Which is demonstrably not the case: http://endless.horse/ http://endless.horse/
- koliber 6y agoI really want to get to the bottom of this.
- tialaramex 6y agoWell, surely more to the point, http://my.lovely.horse/ http://my.lovely.horse/ (If you can't guess what that leads to, you might benefit from two pieces of context. The European broadcast region has an organisation for its Public Service Broadcasters, Eurovision, which holds an annual Song Contest that is known for quirky up-beat winning songs. There was a Channel 4 comedy show about the lives of Catholic priests living on a small Irish island and in one episode they enter the song contest...)