b0VIM 6.1Қ@3K rootplata/www/static/icann/docs/tlds/new-stld-rfp/panel.htmU3210#"! Utp:7;tad:ye  : c h  K @ Jv%Q.0b$9r-W connection speed, search capabilities and coordination with other WHOIS
  • Publicly accessible WHOIS service: address software and hardware, and backup plans for data recovery,
  • Data escrow: escrow arrangements, data formats, insurance arrangements procedures for retrieval of data/rebuild of database,
    • systems used, data format, identity of suggested escrow agent(s) and
  • Backup: frequency and procedures for backup of data; hardware and security, accessibility,
  • Billing and collection systems: technical characteristics, system procedures for and means of distributing zone files to them,
  • Zone file distribution and publication: locations of name servers, user authentication, logging and data back-up,
    • registrars and updates. Address frequency, security, process, interface,
  • Zone file generation including procedures for changes, editing by and reporting capabilities,
    • change notifications, registrar transfer procedures, grace period implementation scalability, procedures for object creation, editing, and deletion,
  • Database capabilities including database software, size, throughput, absence of DNSSec.
    • control, DNSSec operations and DNS reliability and scalability in the
  • Implications of scalability, impacts on caches not under registry aspects of a TLD’s operations,
  • The requirement to keep information synchronized across the various
  • Registry-registrar model and protocol,
    • systems, environmental equipment and Internet connectivity, Consideration of, in appropriate detail buildings, hardware, software capacity and interoperability, general availability and level of security. all system locations; the specific types of systems being used; their
  • General description of proposed facilities and systems, including

  • Revenue from other sources including evidence of the stability of and the pricing model, and
  • Operational income amounts, projected sales and penetration estimates,
  • The sources of start-up and follow-on capital,
  • Hardware and systems, along with the adequacy of system capacity,
    • and insurance,
  • Facilities, including locations and all occupancy costs such as leasing
  • Travel required,
  • Outsourced services, potential suppliers or partners,
    • benefits and taxes paid,
  • Salaries must include all salary related expenses such as bonuses, Team: President, General Counsel, or Administration: Finance, Human Resources,
  • Titles and functions of the senior management team, for example, Executive and amounts of estimated costs accompanying the sTLD Business Plan including: of an operational model, judging the validity and soundness of descriptions In particular, the evaluator must be capable of gauging the effectiveness Copies of recently performed external, independent audits.
    • adp`7?d K Y ? F J R  @QE:0(2A:1tR`G8 and coverage amounts, or financial evidence of self-bonding, and< and coverage amounts, or financial evidence of self-bonding, and Evidence of performance bonding, including the provider name and address, bankers or investors, balance sheets, or other certified financial statements, Evidence of financial and economic standing through statements from of the documents listed below:

  • The evaluator should be able to read, understand and adjudge the soundness
  • A resource requirements projection, and risk analysis, a disaster recovery plan and contingency provisions.
  • An appropriate pricing model,
  • A marketing plan including a brief market analysis, reasonable projections and forecast,
  • The availability of capital including sources of start-up and expansion funds,
  • Cost analyses and a revenue model,
  • An outline of anticipated cost and capital requirements,
  • The full description of registry services to be provided,
    • availability of support and language-availability of support. web-based, telephone and other support services to be offered; time users and registrants; technical help systems, personnel accessibility,
  • Technical and other support: support for registrars and for Internet in outages, and
    • on system outages and on potential system problems that could result the system to operation in the event of an outage; documentation kept time for system restoration; procedures for testing the process of restoring and run the system; backup electrical power systems and the projected to operation and the availability of the hardware needed to restore and backup of software and operating systems needed to restore the system training of technical staff who will perform these tasks; the availability and describe the process for recovery from various types of failures; redundant/diverse systems for providing service in the event of an outage operation in the event of a system outage, both expected and unexpected;
  • System recovery procedures: procedures for restoring the system to locations.
    • hardware; the system monitoring, technical maintenance staff and server security; the availability of backup software, operating system and of all systems, backup power supply, facility security and technical
  • System outage prevention: procedures for problem detection, redundancy service.
  • System reliability: define, analyze and quantify quality of planned back-up systems, support systems, escrow systems, maintenance and personnel,
    • demand for registration or load; effects of load on servers, databases,
  • Peak capacities: technical capability for handling a larger-than-projected other disruptions to operations,
    • and procedures to prevent system hacks, break-ins, data tampering and
  • System security and physical security: technical and physical capabilities systems,