This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/cooperation-wg@ripe.net/
[cooperation-wg] blocking (top-level) domain names
- Previous message (by thread): [cooperation-wg] blocking (top-level) domain names
- Next message (by thread): [cooperation-wg] blocking (top-level) domain names
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Patrik Fältström
patrik at frobbit.se
Thu Sep 8 13:16:54 CEST 2011
On 8 sep 2011, at 07:10, Jim Reid wrote: > On 8 Sep 2011, at 11:23, Patrik Fältström wrote: > >> And finally, some details about "selection of domain names"... Of course the applicant should be able to choose whatever domain name they want. But, in various countries there are certain words, or set of words, that are prohibited from use, or specific use. >> >> Given that such laws exists, where in the ICANN process should a review be done? > > I think the problem here is one of transparency. If there is to be a list of reserved words which cannot be used as new gTLD strings, this list needs to be visible before the application process starts. No such list exists. In Swedish legislation, there is only words about "you can not claim to be a bank if you are not" (or something like that). > It'll cost upwards of $1M to start a new gTLD -- ICANN's application fee is just the tip of the iceberg -- and if someone's going to spend that sort of money, they would want to know in advance if the name they want is not going to be blacklisted. BTW that fee is likely to go up: ICANN's just issued an RFP to get someone to carry out background checks on gTLD applicants for criminal records, bankruptcy, etc. Whoever does those checks will need to be paid. Let me be devils advocate here. If you want a new TLD, spend $1M on a new name you will use, you better do a darn good due diligence on what legislation exists in the world -- or at least the markets you will do your businesses in. I am not saying blocking the application should happen, that is a fair discussion. I just wanted to point out that some legislation that is absolutely not related to IT do set limitations on what words you can use in your business. And the question is then what responsibility (if any) there is during the application process of ICANN to approve/not approve such names that violate local legislation. > I'm sceptical a list of reserved words could be compiled in a reasonable amount of time. Getting consensus on that will be even harder. Then there are the questions about how that list is maintained and updated and the processes for that. Bingo. > Frankly, I am astonished that ICANN could let the gTLD process get to this point (start next year?) when there's this level of uncertainty about such a fundamental issue. It surprises me too that the people applying for gTLDs don't seem to be bothered about it either. I do not have to comment on this... ;) >> Blocking of domain names is of course not good, extremely bad (see above) and (I claim) do not solve the problem people want to have solved. > > +100 Patrik. But where and how does this argument get made? And will the others listen? There seems to be a very strong mindset amongst IPR types and law enforcement that take down notices against web sites is the only tool they have. Yes, but my point is also that IF they are to take down a website, or block traffic to it, then do that. Do not play around with domain names. Patrik
- Previous message (by thread): [cooperation-wg] blocking (top-level) domain names
- Next message (by thread): [cooperation-wg] blocking (top-level) domain names
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]