From the Report >>1 August 2000 - ICANN to issue a formal call for proposals by those seeking to sponsor or operate one or more new TLDs, >> accompanied by a New TLD Registry Application Form, instructions for filling out the application, and a statement of criteria >> for the Board's eventual decision.
It looks like selecting the different TLD's will be complicated by each of the candidate registrars getting a chance to propose their own rules on how they will deal with trademarks, squatters, and the other issues that come up.
Even $50,000 may not be enough to cover the costs of analysis given the kinds of rules that have been suggested over the years.
It looks like this fall will be entertaining at least.
Code names serve a number of purposes: 1) Buildup that team feeling among the developers 2) Allow the lab to refer to their work without having to commit the company to releasing it. (In some circles 1/2 of the projects to upgrade some product never make it. The marketing folks aren't too happy answering the questions like "Why did you skip Windows 99 to go to Windows 2000?".) 3) To confuse the enemy. Word about what people are working on always leaks out. Best to use some form of code name that's not too descriptive about what it really is.
Slashdot Mirror
>>1 August 2000 - ICANN to issue a formal call for proposals by those seeking to sponsor or operate one or more new TLDs,
>> accompanied by a New TLD Registry Application Form, instructions for filling out the application, and a statement of criteria
>> for the Board's eventual decision.
It looks like selecting the different TLD's will be complicated by each of the candidate registrars getting a chance to propose their own rules on how they will deal with trademarks, squatters, and the other issues that come up.
Even $50,000 may not be enough to cover the costs of analysis given the kinds of rules that have been suggested over the years.
It looks like this fall will be entertaining at least.
Code names serve a number of purposes:
1) Buildup that team feeling among the developers
2) Allow the lab to refer to their work without
having to commit the company to releasing it.
(In some circles 1/2 of the projects to
upgrade some product never make it. The
marketing folks aren't too happy answering
the questions like "Why did you skip Windows
99 to go to Windows 2000?".)
3) To confuse the enemy. Word about what people
are working on always leaks out. Best to use
some form of code name that's not too
descriptive about what it really is.
Good luck.