More to the point of the article, when new.net first released its plugin I managed to capture it (it was relatively simple so I don't know why newnetters were complaining they couldn't get a copy to provide for download) and take it apart.|
The way it worked then (I don't know about now) was that it contained all the existing legacy gTLD strings and all existing ccTLD strings. If one typed unregistered-name.travel, or even unregistered-name.foo one was served up with the new.net site. That is, it worked by a system of exclusion along the lines of:
If TLD string = ICANN TLD string
Then goto ICANN root
Else goto new.net
Interestingly the plugin included the then recently okayed but not yet functional .info, .biz etc. I find it hard to believe that if .travel was okayed by ICANN that new.net wouldn't similarily recognize it. Let's look at the possibilities.
1. new.net recognizes only it's own travel. That would make it less useful.
2. new.net recognizes only ICANN .travel. That would make its registrants howl (and perhaps, though I doubt, it even sue).
3. new.net recognizes both and where there is a collision it chooses either itself or ICANN (or even serves up a page which points to both).
It will be interesting to see where they go with this, but I can't see ICANN losing much sleep over it. -g