The selected successor operator for the .org registry will be required to provide all ICANN-accredited registrars having registry-registrar agreements in effect with equivalent access to registry services through a shared registry system, under which those registrars will provide services (either directly or through resellers) to registrants. This section of the .org Proposal covers the applicant's proposed arrangements for interacting with registrars in a manner that provides equivalent access.
Organic Names will ensure that:
RRP will be supported as given in RFC2832. If there are instances where the VeriSign implementation of RRP is non compliant then in consultation with ICANN Organic Names will seek to emulate that non-compliance in the interests of a seamless transition. The imminent adoption of EPP will probably make a change to a compliant version an unnecessary operation.
An email automaton will be provided for use by those registrars who do not wish to implement RRP or EPP. This will queue requests and process them on a first-come first-served basis.
A web-based registrar console will be provided for registrars to register domain names, create, modify and delete objects, and carry out basic account management.
Public information that is available via Whois will also be available via RRP - this is not addressed in the current VeriSign system.
Describe in detail your proposed methods of providing registry services on an equivalent basis to all accredited registrars having registry-registrar agreements in effect. Your description should include any measures intended to make registration, technical assistance, and other services available to ICANN-accredited registrars in different time zones and relevant languages. In addition, describe the Registry Code of Conduct and other commitments you propose to make to ensure that all such registrars receive equivalent access to registry services. In preparing your response to this item, you may wish to refer to Appendices H and I of the registry agreements ICANN has entered for unsponsored TLDs (e.g., .biz, .com, .info, .name, and .org).
Registry operations will be automatically carried out 24 hours a day, 7 days a week, without human intervention.
Organic Names will provide 24-hour registrar support via telephone, ticketing system and email in the following languages:
It should be noted that CentralNic already provides user support in these languages.
Organic Names will adhere to the following Registry Code of Conduct:
VeriSign, Inc., the current operator of the .org registry uses a registry-registrar protocol (RRP) documented in RFC 2832. At the time of the transition, the selected successor operator will be required to continue to support the RRP (unless a migration of registrars in .org to another protocol has already been completed by that time). In addition, the selected successor operator will be required to implement support for the IETF provreg working group's protocol specification for an Extensible Provisioning Protocol (EPP) no later than 135 days after it is adopted as a Proposed Standard (RFC 2026, section 4.1.1). Provide a detailed description of your plan for supporting RRP at the time of transition, for supporting EPP within the required time frame, and for providing registrars with a smooth, low-cost migration path from RRP to EPP.
Organic Names is committed to the new EPP standard, as well as supporting the existing RRP standard for all registrars, and the system software currently supports the prototype EPP system - this is given in more detail in section C17.2.
Organic Names will develop and publish a Registrar Toolkit in order to assist registrar integration through the EPP protocol. The toolkit will be made available in the public domain, using a variety of diverse languages and programmer interfaces reflecting on the diversity of Internet systems. These methods of access will include, but not be restricted to:
The company will provide a server to enable registrars to test transactions with the new EPP system, which will mimic the live registry system. This will be available from milestone 5 onwards as described in section C18.1.
|C23 & C24 (Intentionally omitted.)|