Internet Society Response to the Preliminary Staff Report on Evaluation of the Proposals for the Reassignement of the .ORG Registry
The Internet Society (ISOC) for response to the Preliminary Staff Report on Evaluation of the Proposals: Reassignment of the .ORG Registry.
First, we thank the ICANN staff and the four contributors to the Preliminary Report—Gartner Inc.; the Noncommercial Domain Name Holders Constituency (NCDNHC) team; the international CIO team; and the General Counsel—for their time, energy, and commitment to this important decision. We believe the report reflects a process that has been as fair, thorough, impartial, and transparent as is reasonably possible.
The preliminary report awarded ISOC top tier ratings across the board--the only bidder to achieve this consistently high level and we were pleased to see the evaluation report recommend that "the proposal submitted by the Internet Society (ISOC) be selected." ISOC has also recently posted a statement and additional FAQ's to address several questions that emerged after the report was published.
Second, we'd like to reiterate that ISOC has been a not-for-profit corporation for over 10 years and is operated exclusively for educational, charitable, and scientific purposes. ISOC is a global entity as illustrated by the following:
Should ISOC be selected, we will form a new not-for-profit company—the Public Interest Registry (PIR) -to run the .ORG registry. PIR's board will be appointed by ISOC, but PIR will be a separate legal entity and isolated from ISOC financially and operationally. PIR (not ISOC) will enter into the registry management agreement with ICANN, and PIR will contract with Afilias for all back-end registry services. Our agreement with Afilias provides that Afilias will cover the start-up, transition, and initial operating costs and will then be repaid by PIR for these expenses over the course of the agreement.'Afilias' use of existing capacity will help minimize these costs.
Third, regarding the individual reports, we find the evaluation methodologies to be carefully conceived, the executions objective and impartial, and the resulting conclusion sound. Nevertheless, we would like to draw your attention to several aspects of our bid in response to specific comments in the evaluations. We will address the NCDNHC report first in keeping with its status as the .ORG user representative. Then, we'll comment on the Gartner, CIO and General Counsel reports in that order. We will close with a summary of the strengths of the ISOC proposal.
|Transform Response Time (sec)||0.8 sec||3 sec||3 sec||4 sec||3 sec||3 sec||0.8 sec||3 sec||3 sec||0.8 sec||5 sec|
|Query Response Time (Sec)||0.8 sec||1.5 sec||Data Not Found||4 sec||1.5 sec||3 sec||0.4 sec||3 sec||3 sec||0.4 sec||3 sec|
|Planned Outage / Month (hrs)||8 hrs||8 hrs||8 hrs||8 hrs||8 hrs||8 hrs||2.67 hrs||4 hrs||8 hrs||2.67 hrs||Data Not Found|
|Extended5 Planned Outage / Qtr (hrs)||0 hrs||18 hrs||36 hrs||18 hrs||4.5 hrs||6 hrs||3 hrs||0 hrs||36 hrs||3 hrs||Data Not Found|
|Update Freq. (min)||15 (<5 min actual)||15||Data Not Found||15||5||Data Not Found||5||15||Data Not Found||5||15|
|Cross Network NS Perf. (ms RTT)||300||300||300||Data Not Found||300||300||Data Not Found||300||Data Not Found||300||Data Not Found|
|Response Time (sec)||0.8 sec (0.2 sec actual)||1.5 sec||1.5 sec||1.5 sec||1.5 sec||1.5 sec||0.8sec||1.5 sec||1.5 sec||0.8sec||6 sec|
|Planned Outage / Month (hrs)||8 hrs||8 hrs||8 hrs||8 hrs||8 hrs||8 hrs||2.67 hrs||4 hrs||8 hrs||2.67 hrs||Data Not Found|
|Extended5 Planned Outage / Qtr (hrs)||0 hrs*||18 hrs||36 hrs||18 hrs||4.5 hrs||6 hrs||3 hrs||0 hrs||36 hrs||3 hrs||Data Not Found|
The SRS system for .ORG will be based on the same stable, redundant infrastructure currently in use for .INFO6. A well thought-out, methodical and swift recovery procedure for many different types of SRS events - ranging from slow performance, through the total destruction of all data centers - has been described in our proposal7, and reflects procedures currently in existence for the .INFO registry. This greatly reduces the risk of failure within the SRS, or any other part of the registry system.
In the event of a planned outage of the primary data center, PIR's SRS system would be switched over immediately to the secondary site8. As our proposal states, registrars may notice a brief degradation of service while their SRS clients re-connect to the secondary site. This effect, we believe, would apply to all applicants for the .ORG redelegation.
A major unplanned outage, such as a catastrophic disaster at the primary location, would activate the same SRS failover procedure, as outlined in Section C17.16.1. Since there would not be any advance notice of the outage to registrars, they would need to be contacted immediately to redirect their SRS clients to the secondary site. Our contingency plans ensure that all registrars will be contacted in as timely a fashion as possible in this unlikely event.
It is also important to note that a failure in the SRS system does not impact the ability to resolve existing .ORG domains in any way. In such an instance, PIR will remain able to keep its commitment of providing the highest levels of DNS availability.
The SRS database structure, schema, and procedures in our proposal have been designed to ensure a smooth transition of .ORG from the current registry operator. Afilias, with nearly one million names under management, has clearly demonstrated its ability to manage and maintain a large database in a scalable manner. As of June 18, 2002, the SRS database at Afilias contained over 12 million records, and supported the full range of domain name transactions required by registrars.
The proposed SRS database for .ORG will reside on production grade high-availability Sun Microsystems hardware9, and will be connected to the network in a fully-redundant fashion, with automatic failover in the event of a network component failure.
In order to provide a clearer understanding of the fault-tolerant structure and redundancy of our database services, we have reproduced Figure 3910 from our application. This figure, which shows the system and database architecture of the WHOIS system, is also representative of the design and architecture of the overall SRS system, and was included in the original proposal for this purpose.
In addition to a strong and stable database system, ISOC believes that competent technical leadership in database design and operations is critical in the smooth operation of the SRS database, the heart of any domain registry. Afilias draws upon the skills11 of its experienced management team, including Andrew Sullivan, the company's Senior Database Architect, who brings strong knowledge and experience in database design, development and deployment. Andrew is an active participant in various Open Source database projects, including PostgreSQL, and is an acknowledged expert in both database design and database operation.
The current configuration for the SRS database in the .INFO registry clearly demonstrates that the RDBMS has sufficient capacity12 to handle a 200% growth in the .ORG namespace13, with over 2,000 gigabytes of storage capacity14, and the ability to handle over four times the current .ORG sustained transaction loads15.Figure 39: ORG Database Architecture http://www.icann.org/tlds/org/applications/isoc/section3.html#c17.8-7
A significant portion of the task of transitioning the .ORG domain will be handled by PIR's partner, Afilias. One of the benefits for ISOC of working with Afilias is that it has existing capacity and staff to support the transition and ongoing technical operations of the .ORG registry.
The transition team will be lead by Ram Mohan, Afilias' VP of Business Operations and CTO, who has been involved with building and directing successful multi-functional teams for over 10 years. Ram has built strong Technology, Customer Service and Registrar Relations teams at Afilias. These teams are led by Howard Eland - Senior Technology Architect; Michael Young - Director of Information Technology, and Andrew Sullivan - Senior Database Architect. In addition to this leadership team, we also have over 20 highly qualified, experienced staff. While we anticipate that there may be a need to supplement the core staff with a few additions, we are confident that we have the right team already in place to ensure a successful transition.
With respect to registrar training and education, Afilias is both skilled and experienced. As the registry that pioneered the first implementation of an EPP-based gTLD registry, the success of the .INFO domain was directly tied to Afilias' training and education of registrars in the new technology. In addition, Afilias has led numerous training and planning sessions for registrars, including, most recently for the successfully concluded Land Rush 2 name distribution process. Similar training processes are described within the transition plans in the proposal.
As detailed in our proposal, PIR will have general management and policy responsibility for the registry while Afilias manages the technical aspects under contract to PIR. Beginning with contract negotiations (should the ISOC bid be selected) PIR will provide overall registry leadership. This includes .ORG strategy and priorities, policy implementation, management of the PIR website and its new community input mechanisms; establishment of the .ORG Advisory Council; decisions on the proposed new services such as product definitions and how and when to introduce them; and the management of financials, reporting and other activities ICANN may require.
The international group of CIOs also focused on technical aspects of the bid, but used a different methodology and operated independently of Gartner. The CIO team's report judged ISOC to be a "High Ranking Proposal," one of only two it judged that "could definitely operate the registry successfully." The evaluation team stated that our bid demonstrated:
The General Counsel report addressed policy adherence, competitive impact, and endowment eligibility, and judged ISOC to be in the top tier for all three.
The competitive criterion is especially important, given the magnitude of the .ORG domain and the ICANN core principle of encouraging "...competition in the provision of registration services at both the registry and registrar levels." We believe that it is key for ICANN to select a manager that can successfully build .ORG to its full potential and enable it to compete effectively with .COM and .NET as well as the other TLD's. The ISOC proposal is uniquely attractive because it combines the perspective and experience of the Internet Society with Afilias' demonstrated ability to build and manage a domain in an economically sustainable and stable manner. These attributes will fuel the revitalization of .ORG and enable PIR to foster new levels of competition within the industry overall.
We are happy that the staff and evaluation teams recognized the strength of our proposal. "...the ISOC proposal is the strongest and most balanced proposal overall."
ISOC's proposal brings the best technical capacity to .ORG through its back-end service provider Afilias, who has unmatched experience in running and operating a large-scale, EPP-based, gTLD registry (.INFO). We will modernize .ORG with new technical standards by upgrading the registry system to support the new, faster EPP protocol and by reducing registration to resolution time from hours to minutes.In addition, the proposal includes new registry services such as name locking, site linking, directory, and ID certification designed to deliver tailored, valuable services to meet the unique needs of .ORG registrants.Our proposal ensures that .ORG will remain stable and secure during and after the transition to the new registry operator.
ISOC's proposal also clearly outlines a plan to revitalize .ORG. Based on our own expertise in the Internet and noncommercial communities, we will further .ORG's heritage as the home of noncommercial organizations on the Internet. This plan includes the new services noted above plus a global marketing and public relations program focused on educating noncommercial organizations on the uses of the Internet. It further incorporates new community input mechanisms such as a .ORG Advisory Council and various Web-based tools and features. These will allow .ORG registrants to have a role in the management of .ORG that is absent today.
Overall, we believe ISOC's experience as a not-for-profit, Internet-focused organization, combined with Afilias' expertise as a stable and proven back end provider, enables us to fully meet all the criteria set forth by the ICANN Board.
In summary, we thank the ICANN staff and evaluation teams for their diligence, especially given the tight timetables involved, the complexity of the evaluations, and the importance of this project. We remain committed to our proposal, and look forward to helping make .ORG a stable and secure home for the noncommercial community on the Internet.
Lynn St. Amour
President and CEO
1 Ref. ISOC Application, Sections C12, C13, Contracted Service Providers
2 Ref. ISOC Application, Section C17.13, C17.28
3 Ref. ISOC Application, Sections C28, Figure 54, Figure 55; Appendix N
4 Ref. http://www.icann.org/tlds/org/
5 Planned Outage Time can be used as Extended Planned Outage Time; the total planned outage time per period is the sum of Planned Outage and Extended Planned Outage.
6 Ref. ISOC Application, Section C17.14.2, C17.16.2
7 Ref. ISOC Application, Section 17.16.1 - 17.16.3
8 Ref. ISOC Application, C17.16.1
9 Ref. ISOC Application, C17.3.3
10 Ref. ISOC Application, Section C17.8-7
11 Ref. ISOC Application, Section C15 B
12 This estimate is based on the reports provided by VeriSign, available at http://www.gtldregistries.ORG/reports/2002/apr/index.html/, and referenced in the ISOC application.
13 Ref. ISOC Application, Section C17.3c
14 Ref. ISOC Application, Section C17.3a
15 Ref. ISOC Application, Section C17.10.2 b ii