Very likely the name collision assessment came up clean -- against other domains.
But that's not the issue here.
Is there any requirement for applicants to do due diligence regarding collisions with other common non-DNS computer uses of the applied string?
There are some precedents, notably dot-onion being unavailable to reduce collision with the TOR network (which is certainly out of ICANN's jurisdiction).
But I don't know if, for instance, there would be any inherent ICANN-based opposition to anyone applying for, say, dot-exe or dot-bat (which, like zip, is also a dictionary word).
Perhaps there is room to develop advice to have a mechanism that measures evaluates conflict not just with other domains, but also common computer uses that could if implemented cause pubic confusion or harm.
There are a LOT of file extensions and not all need to be protected, but surely the most common file extensions (and perhaps also command-line utilities) need protections.
I see that dot-run is delegated, which could affect Linux systems (which run a lot of the Internet's infrastructure).
So is dot-mov which is a popular Apple file extension for videos.
Anyway, I leave it with NARALO's ALAC reps to determine if this issue is sufficiently end-user to care about and investigate.
Evan Leibovitch, Toronto Canada
@evanleibovitch / @el56