ICANN punts on Oman meeting decision
There can be few in the ICANN community feeling confident that the Org’s annual general meeting is going to take place in Oman, as currently planned, but its board has kicked the can on a decision to go ahead or cancel.
The AGM is due to happen in Muscat from October 17, but the US-Israel war on Iran has raised serious question marks about the venue’s suitability to host a large international meeting.
Oman has been one of several allied countries targeted by Iranian retaliatory drone and missile strikes. Three people were killed there by such attacks in March, at the start of the war.
With news about the likely end date of the conflict changing on a daily basis, and seemingly subject to the whims and domestic pressures of Donald Trump, it remains unclear whether Muscat will be a safe or practical destination come October.
ICANN’s board of directors had “October 2026 ICANN Meeting Venue Contracting” on its consent agenda for its meeting last Sunday, but there’s currently no published resolution, if one was passed.
It’s possible that the motion was shunted from the consent agenda to the main agenda, where two “confidential” topics were discussed. But the absence of a public announcement suggests no decision to relocate the meeting has yet been taken.
The likely issue with Oman as a destination likely isn’t so much one of safety — though that is certainly a concern — but one of practicality. Air travel in the region has been seriously complicated by the war.
I recently had a 12-hour layover in Abu Dhabi, another Iranian target, and had to take shelter from drone or missile attacks at the airport on five separate occasions.
While that’s no joke, it was quite chucklesome that the UAE government’s alerts, pushed automatically to every phone in the danger zone, were signed off with “MOI” for Ministry of Interior, which my phone decided to read aloud in an almost flirtatious female voice as “mwah”.
Could .om become the next typo TLD?
Will Oman’s .om domain follow in the footsteps of .co? Or .cm? Or neither?
The country-code top-level domain is set to be transferred to a new manager following an ICANN vote this coming Thursday.
The redelegation is one item on a unusually light agenda for the board’s July 28 telephone meeting. It’s on the consent agenda, so it will likely be rubber-stamped without discussion.
The domain is currently assigned to Oman Telecommunications Company, but the new owner is expected to be the national Telecommunications Regulatory Authority or an affiliated entity.
The Omani TRA was given authority over the nation’s domain names by Royal Decree in 2002.
It has already successfully had the Arabic-script ccTLD .عمان approved by ICANN for use as an internationalized domain name, but the IDN has not yet been delegated.
AusRegistry International this March won a $1.3 million contract with the TRA to provide software and services for the .om and .عمان registries.
At the time, the TRA said it planned to market both Latin and Arabic extensions to increase the number of domain registrations.
The .om ccTLD is of course a .com typo, like .co and .cm, but squatting is not currently possible due to its strict registration policies.
Only Omani entities may register .om domains today, and only third-level domains (such as example.com.om and example.net.om) may be registered. Domains may not be resold.
I have no particular reason to believe this situation will change under new stewardship, but it will certainly be worth keeping an eye on the TLD for possible policy changes.
When Cameroon’s .cm opened up, it implemented a widely vilified blanket wildcard in an attempt to profit from .com typos.
Colombia’s .co of course took the responsible route, disowning wildcards and embracing strong anti-squatting measures, even if its mere existence was still a headache for some trademark owners.
AusRegistry chalks up third Arabic domain win
AusRegistry International has announced it has been picked to provide the back-end registry for عمان., the Arabic-script internationalized domain name for Oman.
It’s the company’s third IDN ccTLD contract in the region, following on from Qatar’s forthcoming قطر. and the United Arab Emirates’ already-live امارات.
The company’s press release suggests to me that it’s a software/support deal, rather than a full-blown hosted back-end registry solution.
AusRegistry said it will “provide Domain Name Registry Software and supporting services for the establishment of a new Domain Name Registry System”.
It has previously announced back-end deals for ASCII ccTLDs including .qa and .ae, and manages Australia’s .au, which recently passed the two million domains milestone.
The deal with Oman, which AusRegistry said was competitively bid, also encompasses .om, the nation’s regular ccTLD.
While ICANN approved Oman’s chosen string under its IDN ccTLD Fast Track program back in October, it has not yet been delegated to the DNS root zone.
With the approval of Ukraine’s Cyrillic ccTLD last week, 25 territories have had their choice of local-script ccTLD given the nod under the program.






Recent Comments