A. General Description of the Application
  1. TLD String(s) Requested.
  2. Category.
    Special Purpose.

    Internet Events International, Inc. (“IEI”) requests the .event TLD which is targeted at a restricted registrant base and a large end user group. Accordingly, IEI’s TLD request qualifies for the special purpose category.
  3. Sponsor, Registry Operator and Subcontractor.
    a. Sponsor. On August 15, 2000, Brian Burnett founded IEI, an S Corporation organized under the laws of the state of Utah. The company will be located in Spokane, Washington and will offer registration services and associated technical support as the Registry Operator for .event. IEI claims that its management team has a great deal of experience with technology-dependent companies and general business management. IEI lists its President and CEO as bringing business experience to the management team, its Vice President of Policy and Vice President of Registration as having a combined total of over 50 years of experience in engineering, technical operations and Web-based business and its Executive Vice President as having extensive administrative, security and technological experience.
    b. Registry Operator. Also IEI.
    c. Subcontractor. None listed.
  4. Registry-Registrar Model.
    IEI intends to operate as the sponsor, the registry operator and the registrar.

B. Technical Review
  1. Summary Description of Proposal.
    The applicant suggests a .events TLD to organize information about events. The proposer will set up reserved SLDs for common types of events, but will generally allow registrations of both SLDs and third level domains.
  2. Support of the Business Plan by the Technical Plan.
    a. Total Capacity. The design for the system asserts that IEI can support a huge capacity. A quick examination of the design does not uncover a specific flaw, however, the design has never been built. As with most new, large scale development projects, surprises should be expected. Given that they predict 2 million registered names within one quarter of the start of the TLD, they will have little time to correct any problems.
    b. Projected Growth Rate. The applicant asserts that the tremendous projected growth rate can be handled by the addition of hardware. Given the novel nature of the system it is difficult to assess the ability of the system to hand the projected load.
    c. Startup Period. There will be a startup period solely for handling trademark and other legal issues. They will immediately open for business after that period. No specific technical means are involved.
    d. Fault Tolerance. The design is acceptable.
    e. Security. Many of the security tools proposed by the applicant seem irrelevant or poorly chosen for their purpose. For example, it is hard to see what useful role Kerberos would play in running a registry.
  3. Summary of Relevant Experience.
    IEI has no relevant experience, as best as can be determined from the proposal. No evidence was found that technical personnel associated with the proposal have any experience running a registry, registrar, DNS server, fault tolerant system, or large-scale data management system. Some members of the team have done work in systems administration and web design.
  4. Apparent Implementation Risks.
    The application does not demonstrate the experience or facilities to run a registry.

    The application does not describe the unique characteristics of a TLD meant to handle events. Thus, they provide few special features that are suitable for that domain. Users may find the absence of such features (such as a mechanism to automatically expire a name at a particular time) annoying, resulting in limited success for the TLD.

    The application does not demonstrate that IEI understands the security risks and appropriate countermeasures for running a registry. While it might hire someone who does, there is no guarantee it will. The resulting possible insecurities could seriously compromise the system.
  5. Available of Human, Operational and Technical Resources to Cope with Unexpected Events.
    IEI has little experience and no technical team to fall back on.
  6. Advancing the State of the Art.
    The applicant suggests no new services related to this TLD.
  7. Other Comments.

C. Business Review
  1. Applicant’s Representations.
    IEI is both the sponsor and registry operator. This company was created for the purpose of applying for the .events TLD. Its mission is “to imbue the global community with comfort and familiarity towards the many uses the Internet provides.” IEI has no financial results and has no capital commitments at this point.

    The subscription-based revenue model includes a $50 annual fee for a SLD registration, and a $35 annual fee for a third-level-domain registration with multi-year and multi-level discounts. The application defines the target market as the 29 million current DNS registration holders and the 55 million non-Internet businesses.
  2. ICANN’s Evaluation.
    IEI weaknesses are (i) no firm financing, (ii) a business plan that does not fully address the necessary specifics and (iii) management that lacks sufficient experience in registry/registrar operations. Overall, this application is not as strong as other applications in its category.

D. Summary of Public Comments
  1. Number of Comments.
  2. Support for the Application.
    “The .event TLD is surely the most versatile of all those proposed.”

    One comment termed the application “an excellent way to categorize the Internet.”

    “This proposal shows that this TLD transcends all forms of events from weddings, family, personal events, expos, community, music, meetings, conferences, and other activities across the world. This proposal expands the web in a positive manner.
  3. Opposition to Application.
    “The .event TLD is owned by the Quasar and resolves to the ORSC rootzone.”