II.2.6.         Resources Required to Meet Demand (RFP Section D13.2.6)

JVTeam has developed a resource plan that is in keeping with the goal of providing a state-of-the-art, innovative world-class solution that is reliable, scalable and exceeds customer expectation.

The successful development and ongoing operation of a gTLD cannot be accomplished without a comprehensive plan that scopes every facet of the registry business from software development through to the provision of end-user support services. JVTeam recognizes ICANN's need to appoint a highly competent and well-equipped registry provider, and has developed a detailed resource plan that amply meets requirements.

For each of the resource categories   Staffing, Hardware, Software, Facilities and Communications   the JVTeam has analyzed the resources required to design, implement and operate the .geo Domain Name Registry. Factors such as economies of scope and scale, interoperability and feasibility were considered in each of the required operational aspects of the registry as well as for the innovations JVTeam is proposing. We feel our past experience in providing registry services gives us a solid base for generating a resource plan that is realistic and covers all aspects of Registry operation.


Staff resources, further discussed in Registry Operator's Proposal Section II 2.9, includes all those individuals directly involved in the design, implementation, management, integration and ongoing operation of the .geo Domain Name Registry.  The organization is designed to meet our commitment to being a neutral third party registry while at the same time promoting ongoing technological development.

Hardware includes of all hardware components (servers, routers, load balancers, etc.) required for ongoing development and operation. Software includes custom software development to support all registry services described in Registry Operator's Proposal Section II 2.1, as well as third party purchases. The facilities, further detailed in Registry Operator's Proposal Section II 2.7, includes the 2 SRS Data Centers located in Sterling, VA and Chicago, IL, as well as the nameserver sites, geographically positioned across the globe. Communications includes estimates for the bandwidth and Virtual Private Network (VPN) needs of the .geo Domain Name Registry.

The following table is a summation of our resource requirements for the .geo Domain Name Registry. It outlines each resource by category and provides a function and description of the resource as well the factor for calculating the scope of the resource.





Value Driver



       Executive Team

       Management Review

       Fixed component


       System Engineering

       Software development and testing

       IETF, ICANN and other Industry  Relations

       XRP / Fat Registry implementation

       Innovative features

       Registration volume


       Customer Support

       Registrar Integration

       System Testing and Maintenance

       Network Management

       Reporting and Documentation

       XRRP / Fat Registry

       Innovative features

       Number of ICANN-accredited registrars

       Registration volume

Account Management

       Registrar Coordination

       Number of ICANN accredited registrars


       Quality Assurance


       Contract Compliance

       Fixed component (mandatory JVTeam function)


       Finance, Human Resources, Legal

       Fixed component


SRS Data Centers

       Core Registry functions

       Zone root query volume and size

       Registration volume

       Fat Registry design

Nameserver Sites

       DNS management

       Zone root query volume and size

       Registration volume

       Fat Registry design

Requisite Staff H/W

       Workstations, PCs, misc. office 

       Staff size



       Create enhanced functionality and open protocol

       Technological innovations



   Third Party

       Supplement custom software

        Best of Breed  components


Core JVTeam Site


       Staff size

SRS Data Centers

       Provide redundant zones

       Geographic location

       Bandwidth requirements

   Name Server Sites

        Provide redundant zones

       Geographic location

       Bandwidth requirements



       Manage communications at Name Servers

       Zone root query volume and size

       SRS queries


       Manage communications between application servers and nameservers

       Whois queries

       Registration volume


The label of  Fixed' denotes resources that are core to the operation of JVTeam, regardless of factors such as registration volumes. These individuals represent the core management and operational components of a registry of any size. Those staff denoted as variable will increase in terms of full-time equivalents (FTEs) as the volume of registrations increase. The registrar quantity refers to the anticipated growth of ICANN accredited registrars over the course of time.

The Volume driver refers to the increased number of registrations for ..geo over the course of time and captures the implications for the management of the registry. The transaction size and volume and Megabits per second (Mbps) are calculated by evaluating the size of the transactions at each stage of the registration and query process (XRP, Whois, etc) to determine the server capacity and FTEs required to manage the system.

JVTeam found that those items with the greatest variability are those based on the volume of queries, and developed the resource plan accordingly. As these were noted as critical items, they have been given strong consideration in the technical sections of this application and they will be monitored closely through implementation and operation to ensure performance and integrity. 

While JVTeam is striving to offer an innovative and highly reliable service that will not jeopardize the integrity of the Internet, the cost passed onto the Internet community was not overlooked. We feel we have met the highest standards for quality of service at the most economical price. JVTeam has created a resource plan to implement and operate a Registry that will meet the highest quality expectations.

The following enumerates the expected resources required  to operate the .geo registry at the 10, 59 and 90% demand intervals: