The sponsor organization behind the restricted .jobs domain is soliciting comment on a plan to substantially liberalize the TLD, allowing generic and two-letter registrations.
The Society For Human Resource Management has published a very brief survey, asking HR folk what they think the pros and cons to the plan might be.
The .jobs domain is run by Employ Media. It’s currently restricted to companyname.jobs registrations, and as such has been predictably unsuccessful.
Now Employ Media wants to branch out into geographical and generic domains. As I reported last month, it looks like it’s trying to remove essentially all of its significant registration restrictions.
The attempt at a policy shift follows a deal made with DirectEmployers Association to monetize geographic domains that raised eyebrows at ICANN late last year.
ERE.net has more here.
Many domains ending in .de, Germany’s country-code TLD, have seen downtime today, after something went wrong at Denic, the registry manager.
Details are sketchy at the moment, but it appears from chatter on the DNS-Ops mailing list that several instances of the .de zone stopped serving addresses this morning.
It appears that the affected servers were responsible for .de domains beginning with F through Z, so facebook.de would have worked, but heise.de would not.
This is obviously a huge headache if you’re German or do business in Germany — I hate to think how many transactions could have been disrupted by the downtime — and I expect Denic will take a lot of flack at home over the coming days and weeks.
The problem, however, does appear to have been fixed. SANS estimates the outage as a little over an hour.
One of the directors of porn industry organization the Free Speech Coalition has suggested the .xxx top-level domain could be approved as an unrestricted gTLD.
But Hymes went on to say: “If that scenario is unacceptable to the Board for one reason or another, I would then encourage it to explore a gTLD option for ICM.”
He noted that he was writing in a personal capacity, not as a representative of the FSC.
ICM’s application was filed under the 2005 round of “sponsored” TLDs, which meant it had to show backing from a sponsorship organization and some measure of ownership restriction.
For example, the Society for Human Resource Management is the sponsor for .jobs and the Universal Postal Union backed .post.
ICM, which has never been part of the adult entertainment industry, created a policy-making body called the International Foundation For Online Responsibility, IFFOR, to act as its sponsor.
In my view, IFFOR was basically a
crude hack to get around the fact that in 2005 ICANN was not looking for any new gTLDs.
The FSC doesn’t like IFFOR, because a) it will make policy on what can be hosted under .xxx domains and b) the adult industry will not control its board or see any of its money.
Hymes, in his personal capacity, seems to be saying that an unrestricted .xxx gTLD would be okay. It’s the first ground I’ve seen anyone in the porn industry give in this debate. He says:
To its credit, the Board is striving to solve the dot xxx imbroglio by dangling a gTLD in front of ICM, a solution ICM thus far has refused to consider. But that sort of suspicious recalcitrance can no longer be tolerated. Instead of threatening to bring a costly lawsuit against ICANN in order to secure control of a policy making regime for which it does not have the required support, ICM should cut its losses, save everyone a lot of money and take the gTLD while it has the opportunity.
I happen to agree, mostly: .xxx would make a heck of a lot more sense, and would be a whole lot less controversial (Christians notwithstanding), as a gTLD.
Unfortunately, I can’t see it happening. Not easily, anyway.
There’s no ICANN process in place for approving gTLDs today, and if ICANN were to choose to kick ICM into the next new gTLD round, there’s a pretty good chance that ICM would find itself fighting a contested string battle with other applications.
From a process point of view, sponsored TLDs are a failed experiment.
The registry behind one of the new Arabic-script ccTLDs has sharply criticised ICANN for the way it introduced internationalized domain names to the root this week.
Adrian Kinderis, CEO of AusRegistry, accused ICANN, specifically those responsible for the IANA function, of “embarrassing incompetency” and cultural insensitivity.
Kinderis’ beef is that IANA added the three new Arabic IDNs to the root without giving their local managers so much as a headsup.
AusRegistry is the back-end provider for امارات. the United Arab Emirates’ new IDN ccTLD, as well as its ASCII original.
“I was alarmed to discover that the relevant ccTLD Managers were only notified many hours after the fact, long after the same IANA staff member had broadcast the news on a personal Twitter account,” he blogged.
“This was an inappropriate manner in which to announce an event of this importance,” Kinderis wrote. “It displays a disturbing lack of understanding and a complete disregard of the cultural and political significance of this event within the Arabic world.”
He goes on to point out that the announcement was made during Saudi Arabia’s weekend, leaving ccTLD managers scrambling to get their marketing in place on their day off.
I could keep quoting. It’s a fairly extraordinary attack on aspects of ICANN’s culture. Go have a read.
Click this: http://وزارة-الأتصالات.مصر/
It’s the Egyptian Ministry of Communications and Information Technology, owner of one of the world’s first fully non-ASCII internet domain names.
If you hover over the link, you might see the Punycode translation appear in your browser’s bottom bar, even though the href itself is in Arabic script.
Thanks to ICANN, from today the Latin script no longer has a stranglehold on the domain name system.
I’m afraid I won’t be able to tell you what the three newly created internationalized domain name ccTLDs are, because none of the software on my machine wants to let me use them in a sentence without switching my cursor to right-to-left editing mid-way through the word or changing the characters entirely, and after ten minutes of beating my head against the keyboard I gave up.
Anyway, the new domains represent Egypt, Saudi Arabia and the United Arab Emirates.
They were all recently approved by ICANN as part of its “fast-track” IDN ccTLD process, which promises to give countries the equivalent of their ASCII ccTLD in their native script.
After 25 years, the English language no longer has exclusive rights on the DNS. Not what I’d call a “fast” track, but we got there eventually.
ICANN has more here.