IMS/ISC: .Org Proposal Form
Total Page:16
File Type:pdf, Size:1020Kb
TOP THE .ORG TLD IS A PUBLIC TRUST » « A Joint Effort of the INTERNET MULTICASTING SERVICE and eorg INTERNET SOFTWARE CONSORTIUM » TRANSMITTAL » FITNESS DISCLOSURE » « VOICE YOUR SUPPORT » PROPOSAL » SUPPLEMENTARY MATERIALS » « SPREAD THE DOT » CONFIDENTIAL INFORMATION » SUPPLEMENTAL QUESTIONS » .org Proposal Form Executive Summary This is a joint bid between the Internet Multicasting Service (IMS) and the Internet Software Consortium (ISC). We are both public benefit corporations with a long history of operating public works and creating freely available software for key infrastructure services on the Internet. The .org Top Level Domain (TLD) is the home for the noncommercial organizations of the world, and we would operate the .org registry service as a public trust: ● We have designed a rock-solid service in strategic exchange points throughout the world. We will build this service on our existing infrastructure and operate a stable, high-performance, high-availability registry service for the .org TLD. ● We will operate this service with strong support for registrars, the registrants in the .org TLD, the general Internet community, ICANN, and our other constituencies. ● We will build on our deep familiarity with the subject area and our extensive experience in provisioning complex Internet services. We will provide a smooth transition with no break in service. ● The .org TLD registry service will support all IETF recommended protocols. Our software, including packages for registry servers, registrar clients, Whois, namespace management, and secure DNS solutions will be freely available with no restrictions in source and binary form. ● We will work with our extensive network of partners throughout the world to provide substantial input to the standards process and advances in core technologies. ● We will work with our extensive network of partners around the world to differentiate .org and make this TLD a home for the noncommercial organizations of the world. IMS and ISC have provided important contributions to Internet infrastructure and have worked together closely for years. Our team is in place and builds on substantial past experience: ● We produce BIND, the software used to provide DNS service on the vast majority of key Internet servers. ● We operate the "F" root server and serve DNS for 22 TLDs. ● We have extensive experience with large, complex databases and were responsible for implementing and operating Internet databases from the ITU, the U.S. Patent and Trademark Office, and the U.S. Securities and Exchange Commission. ● We have built large global communities, such as the Internet 1996 World Exposition, a yearlong event that deployed over US$100m in in-kind contributions to enhance global Internet connectivity and stability. The Exposition included the participation of people from 85 countries and received over 5 million visitors from 130 countries. ● Our team is well known for advancing the state of the art in Internet services and applications, including tpc.int, HTCP, the DNS, and BEEP. Revenue generated from the operation of the registry will first cover core operations, then service debt, and then fund public works projects for the benefit of .org registrants and core Internet infrastructure. No funds will be used for unrelated programs and we have no shareholders. An experienced board of directors, a public process, and extensive reporting will provide full accountability and transparency for the operation of this registry. We will provide ICANN with tools that will spur greater competition in the marketplace for registry services and support innovation in related areas. Table of Contents 1. General Information About the Applicant 2. Statement of Capabilities of the Applicant and Contracted Service Providers 2.1 Outsourcing C12 2.2 Services and Facilities C13 2.3 Scope and Terms of Contracts C14 2.4 Abilities of the Applicant C15 3. Technical Plan (Including Transition Plan) 3.1 Summary 3.2 General Description of Proposed Facilities and Systems C17.1 3.2.1 Functional Specification 3.2.1.1 Provision of Services 3.2.1.2 Transaction Security 3.2.1.3 Active Service Monitoring 3.2.1.4 Event Monitoring 3.3 Registry-Registrar Model and Protocol C17.2 3.3.1 General Approach 3.3.2 RRP Implementation 3.3.3 EPP Implementation 3.3.4 Message Passing to Registrars 3.3.5 Registrar Portal 3.4 Database Capabilities C17.3 3.5 Zone File Generation C17.4 3.5.1 A Note on TSIG and DNSSEC 3.6 Zone File Distribution and Publication C17.5 3.7 Billing and Collection Systems C17.6 3.8 Data Escrow and Backup C17.7 3.8.1 Requirements 3.8.2 Data Escrow Schedule, Content, Format and Procedure 3.8.2.1 Schedule 3.8.2.2 File Naming 3.8.2.3 Escrow Deposit Specification 3.8.2.4 Dump Format 3.8.2.5 Deposit and Transfer 3.8.2.6 Verification Procedures 3.8.3 Backup Provisions 3.9 Whois Services C17.8 3.10 System Security C17.9 3.10.1 Types of Services 3.10.1.1 Public Services 3.10.1.2 Restricted services 3.10.1.3 Private services 3.10.2 Types of Attacks 3.10.2.1 Denial of Service 3.10.2.2 Intrusion 3.10.2.3 General and Physical 3.11 Peak Capacities C17.10 3.12 Customer Support C17.11 3.12.1 Incident Handling 3.12.2 Notifications 3.12.3 Maintenance 3.12.4 Change Control 3.12.5 Questions/Help 3.12.6 Staffing 3.13 Compliance with Specifications C17.12 3.14 System Reliability C17.13 3.14.1 Definitions 3.14.2 Notification 3.14.3 Performance Metrics 3.14.4 Nameserver Availability and Performance Measurements 3.14.5 Update Frequency 3.14.6 Performance Specification Summary 3.15 System Outage Prevention C17.14 3.16 System Recovery Procedures C17.15 3.16.1 Recovery From Hardware Failure 3.16.2 Recovery From Software Failure 3.16.3 Recovery From Operational Failure 3.16.4 Customer Service 3.17 Registry Failure Provisions C17.16 3.17.1 Operational Failure 3.17.2 Business Failure 3.17.3 Regulatory Failure 3.18 Transition Plan C18 3.18.1 Steps of Proposed Transition C18.1 3.18.1.1 August/September 2002 3.18.1.2 September/November 2002 3.18.1.2.1 Implementation of RRP and EPP 3.18.1.2.2 Whois Service 3.18.1.2.3 Zone File Generation 3.18.1.2.4 Operational Planning 3.18.1.3 Final Cutover Preparation 3.18.1.4 Live Cutover Acceptance Criteria 3.18.1.5 RRP/EPP and Thin/Thick Transition 3.18.1.6 Phase I - Stable Transition 3.18.1.7 Phase I - Transfers 3.18.1.8 Phase I - Deleted Domains 3.18.1.9 Phase II - Dual Protocol Support (RRP and EPP) 3.18.1.10 Phase II - Transfers 3.18.1.11 Phase III - From Thin to Thick 3.18.1.12 Phase IV - Complete Thick/Thin Transition 3.18.2 DNS Server Service Assimilation 3.18.3 IDN Transmigration 3.18.4 Whois Redirection from VeriSign 3.18.5 IP Version 6 Support 3.18.6 Community Notification and Outreach 3.19 Interruption of the Registry Function C18.2 3.20 Contingency Plans C18.3 3.21 Effect on .org Registrants and Internet Users C18.4 3.22 Specific Cooperation Required from VeriSign C18.5 3.23 Relevant Prior Transition Experience C18.6 3.24 Proposed Criteria for the Evaluation of Transition C18.7 4. Compliance with ICANN-Developed Policies and the Registry Agreement C19 5. Provisions for Equivalent Access by Accredited Registrars C20 5.1 Equivalent Access Policies C21 5.1.1 Equivalent Access Policy 5.1.2 Registry Code of Conduct 5.2 EPP Support C22 5.2.1 EPP Transition 6. Proposed Registry Services 6.1 Registry Services for Fee C25 6.2 Maximum Price C26 6.3 Registry Services Without Fee C27 6.4 Technical Performance Specifications C28 6.4.1 Performance Specifications 6.4.2 Update Frequency 6.4.3 Cross-Network Nameserver Performance Requirements 7. Enhancement of Competition C30 8. Responsiveness to the Noncommercial Internet User Community 9. Support for Proposal C36 10. Differentiation of the .org TLD C38 11. The VeriSign Endowment C40 12. Supporting Documentation C50 13. Signature and Certification § Normative References § Select RFCs By Team Members § Current Internet-Drafts by Team Members § Books by Team Members § Web Sites by Team Members § Authors' Addresses A. Escrow Data Format A.1 Domain Format A.2 Name Server Format A.3 Registrar Format A.4 Contact Format A.5 Escrow Format Example B. Registry/Registrar E-Mail Templates B.1 Receipt of Transfer Request B.2 Completion of Transfer Request B.3 Auto-Acknowledgement of Transfer Request B.4 Non-Completion of Transfer Request C. Initial Whois Output Format D. Thick Record Whois Output Format E. Biographies of Key Personnel E.1 Program Managers E.1.1 Carl Malamud E.1.2 Rebecca Malamud E.1.3 Paul Vixie E.1.4 Suzanne Woolf E.2 Additional Personnel E.2.1 Joe Abley E.2.2 Luther Brown E.2.3 Brad Burdick E.2.4 Michael Graff E.2.5 Lynda McGinley E.2.6 Rick H. Wesson E.3 Board Members E.3.1 Rick Adams E.3.2 Dave Farber E.3.3 Teus Hagen E.3.4 Daniel Karrenberg E.3.5 Carl Malamud E.3.6 Rebecca Malamud E.3.7 Evi Nemeth E.3.8 Marshall T. Rose E.3.9 Paul Vixie E.3.10 Stephen Wolff E.3.11 Pindar Wong F. Document Formats DOC 1. General Information About the Applicant TOC ? C1. The first section of the .org Proposal (after the signed copy of this document) covers general information about the applicant.