Side note: Please don’t use such gray and thin fonts. I had to modify the CSS to use black instead of #555 for the text color.
I had to use the "Reader" feature of my browser to read the text, for maybe the first time ever.
Taking control of all .io domains with a targeted registration
101–110 of 258 posts
Re: Taking control of all .io domains with a targeted registration
#102Earlier quoted context omitted.
There are a few ccTLDs that differ from that, though. DENIC and CZNIC are two that are generally very well-run, DENIC even offering better security and safety than many gTLDs (while also being a cooperative, not a commercial NIC, so prices are very low, too)
.me and .ca "seem" competently run. More so for .me, ran by the owners of .org
if .ca was not competently run, I'm pretty sure the federal government would step in and put it into the hands of people with real DNS/network engineering credibility.
Unlike the rarely used .us for the USA, it is used for the vast majority of canadian domestic corporations' web identities.
Re: Taking control of all .io domains with a targeted registration
#103Earlier quoted context omitted.
Why is that an important distinction? Is forcible expulsion and dispropriration more acceptable if the people were brought to the island as slaves and laborers in the mid-1700s?
It doesn't really matter at all. The land didn't come with a .io ccTLD. It's dervived from a name the British chose, so it's not like they stole the domain name from those people, right? Displacing settlers is a different question.
Still, why does the UK need a special TLD for a naval base?
Re: Taking control of all .io domains with a targeted registration
#104Earlier quoted context omitted.
It doesn't really matter at all. The land didn't come with a .io ccTLD. It's dervived from a name the British chose, so it's not like they stole the domain name from those people, right? Displacing settlers is a different question.
Still, why does the UK need a special TLD for a naval base?
Because the domain name system uses ISO-8859, which provides codes for "countries, territories and islands".
The standard provides codes for such places since different law often applies in territories and on islands.
(See also: UM, TW, EH, AQ, SH, SJ, and many others.)
Re: Taking control of all .io domains with a targeted registration
#105Earlier quoted context omitted.
There are a few ccTLDs that differ from that, though. DENIC and CZNIC are two that are generally very well-run, DENIC even offering better security and safety than many gTLDs (while also being a cooperative, not a commercial NIC, so prices are very low, too)
There's probably around a dozen ccTLDs that are really competently run and that are world-class. Beyond that I'd stick with competently run gTLDs. I actually just met a bunch of the denic guys at a conference they hosted a month ago in Frankfurt. They're on point with their Internet stuff.
I think it's more than a dozen. I would expect all wealthy, tech-savvy democracies to have fairly competently run ccTLDs. It's just that there's about 200 countries in the world, and quite a lot of those are a complete mess.
Re: Taking control of all .io domains with a targeted registration
#106Earlier quoted context omitted.
I think the morally questionable problem is this: I am highly doubtful that the original inhabitants of the islands are receiving any revenue whatsoever from the corporation which runs .IO. At least the small pacific island nation states that have hired third parties to run their ccTLD have contracts and agreements in place for a revenue share.
Why should they get any revenue from .io? The .io is an invention of the government and has nothing to do with the original inhabitants. The "original" people were removed well before .io even existed. Might as well demand they get paid for any inventions the military makes while testing stuff out there. And if the British hadn't done this and gave control over to the people living there 50 years ago, they wouldn't g…
When Britain (and thus the US) decide they no longer require the island for a naval base, it will be given to Mauritius.
The .IO domain would eventually be deleted, and that territory represented under the existing .MU (Mauritius) domain.
Judging by https://en.wikipedia.org/wiki/.mu I don't think the Mauritian people have much benefit from the arrangements for .MU.
Re: Taking control of all .io domains with a targeted registration
#107NIC.io are a terrible, terrible registrar. I reported an account takeover security vulnerability to them 6 years ago that they only fixed after 4ish years.
Re: Taking control of all .io domains with a targeted registration
#108Earlier quoted context omitted.
.me and .ca "seem" competently run. More so for .me, ran by the owners of .org
if .ca was not competently run, I'm pretty sure the federal government would step in and put it into the hands of people with real DNS/network engineering credibility. Unlike the rarely used .us for the USA, it is used for the vast majority of canadian domestic corporations' web identities.
And also the Canadian government for that matter
Re: Taking control of all .io domains with a targeted registration
#109Considering there are a grand total of 2500 people in the BIOT, all of whom are British or American military personnel, it might not be a great idea to route a good chunk of the world's tech traffic through them. The disparity between how important the .io TLD is for the Internet and how few resources must go to running it is pretty appalling.
"route"? That's not how DNS works.
Re: Taking control of all .io domains with a targeted registration
#110Just to add some color to this: There was an attack last Friday on a few geo TLDs that ended up hijacking a bunch of traffic for a few hours, including .la, .es, and .jp: https://news.gandi.net/en/2017/07/report-on-july-7-2017-inci...
I'm one of the unlucky few that were affected by this (I own .ch). One of my site user's reported that the website is inaccessible on Friday. I went to check and observed the DNS changing. Then went to check Route 53 status page[2] in which I learn that this is not specific to my site. The behavior is exactly the same as what is described in the SWITCH report[1]. Luckily that I have HSTS on my site, so the damage is…
We were also affected by this on a major e-commerce site. It was a .se domain.
Their post mortem isn't really convincing ( https://news.gandi.net/en/2017/07/report-on-july-7-2017-inci... ) since they do not state what really happened and how it can be prevented again.
I issued a support ticket to aws today to see what measures can be taken, otherwise we might need to change registrar.