3 ms·
I work for a registrar as well. You are right, I hadn't considered ccTLD's What I find really insidious about ccTLD registries is the crazy rules they have (an
by robalfonso 10y ago
I work for a registrar as well. You are right, I hadn't considered ccTLD's What I find really insidious about ccTLD registries is the crazy rules they have (and therefore the crazy business rules I must use to support them) this doesn't fix that, but as you pointed out it might help some of those small ones that are otherwise out of luck.
- talideon 10y agoWell, unlike gTLDs, ICANN have no control over what ccTLD registries do. Personally, I much prefer dealing with ccTLD registries who behave like gTLD registries (.me, .co, &c.), but those are few and far between. Smaller ccTLDs are unlikely to use this though: it makes more sense for them to contract out the technical side of things than run their own, with .cm being an example of a registry that shouldn't run their own infrastructure.
- robalfonso 10y agoIncidentally I find that to be a smart business move for them as well. I mean if you behave like a gTLD you integrate much faster than say .es where you have all kinds of offset rules you must apply to their expiration or .nl who give you a one day window to renew!
- talideon 10y agoYou'd think that, but trying to convince registries to go down that route is head wrecking. And then you have the likes of the .ie domain registry (IEDR) who use their own vaguely EPP-like protocol that works nothing like normal registries with a set of needlessly bizarre policies specific to them. Ugh.
- CydeWeys 10y agoThere's one big obvious advantage of open source registries, from the perspective of registrars: You can look at our source code and figure out exactly what we're doing.