The submitted document is a good summary of the "no strings attached" fraction here in the WG. If I may condense:
But as I said: we are probably past the "discussion stage": we exchanged these same bullet points forth and back for years.
- An unfiltered approach to closed TLDs; were anybody can apply for any string as closed gTLD:
- Generic keywords (".book")
- Brands (Spec 13 would be eliminated in that model, right?)
- Geo terms (e.g. ".shanghai")
- An approach where the public benefit that is suggested in the gTLD operation plan is outweighing the fact that the public can't register domains.
- I am not singling out any concrete policy version.
- Implementation will have to be worked on.
- None of the above is satisfactory - therefore until an appropriate policy advice is being created closed gTLDs remain confined to SPEC 13 brand TLDs.
A word to Spec13 Brand TLDs:
If any string could be operated as closed gTLD: wouldn't then the entire class (and the related policies) of SPEC13 Brand gTLD be superfluous?
If we do not lift all restrictions around closed generic gTLDs (hence keep SPEC13):
How to prevent that closed generics are being introduced as SPEC13 registry? I register a TM "BOOK" (or buy a used one; there are two live TMs "BOOK" at USPTO right now; and there are many more globally) apply for .book as SPEC13 Brand gTLD - then do my "innovative thing"? E.g. give "accounts" (not domains) to clients - and route accountname.book to their presence that is hosted on my servers (similar to a FB page presence; or ebay store)? I don't give them the domain or access to nameservers - they apply for an account name - get an online service of whatever kind (store, social media account, heart tracker app account) - and I as registry route accountname.closedTLD to their account presence on my servers!
Alexander