Q1: In the introduction of new TLDs, what steps should be taken
to coordinate with the Internet Engineering Task Force, the Internet Architecture
Board, and other organizations dealing with Internet protocols and standards?
They should be consulted as to what steps are required.
Q2: What stability concerns are associated with the initial phases of registration
within the TLD?
The purchaise of domain names for speculative
reasons can reduce the usefulness of a new domain, and add an unnessicary cost of
ownership for those that will make actual use of the name.
Q3: What can be done to eliminate or reduce these stability concerns?
If the TLD is to be in high demand, a 2 month bidding period for all names
in that namespace may prevent "domain squatting" and domain ownership speculation.
The bidding process would reveal the true value of the domain, and the extra money
paid for popular domains could subsidise the TLD service instead.
Q4: Would these stability concerns be magnified by introducing a large number
of TLDs at once?
Possibly. I cannot see any benifit
in doing this, so I would advise against it.
Q5: Are there
any practical means of reversing the introduction of a significant new TLD once it
goes into operation?
No. This must not be done.
At best, prevent the introduction of new names in that TLD.
Q6: Is it feasible to introduce a TLD on a "trial basis," giving clear notice that
the TLD might be discontinued after the trial is completed?
No. The "trial" would be unrealistic. Potential users may either avoid
the TLD and miss out, or use the TLD and then discover they have wasted resources.
If the TLD is revoked or not, there will be a cost associated with this label.
Q7: To ensure continued stability, what characteristics should be sought
in a proposed TLD and in the organization(s) proposing to sponsor and/or operate
it?
Domains non-ccTLDs should serve to catagorise thier users
in some meaningful way. For example, the .com and .org TLDs fail this requirement.
Wheras a .xxx TLD would serve to identify content that users could choose to avoid
or block. A ".abc" would fail in this regard.