index

V. Proposed Registry Services

C25

Describe each Registry Service (as defined in subsection 1.16 of the model .org Registry Agreement) that you propose to provide for a fee. For an example of a description of this type, see <http://www.icann.org/tlds/agreements/name/registry-agmt-appc-1-03jul01.htm>.

Services Offered for a fee

The following services will be provided, and are described in detail in subsequent paragraphs:

  • Domain Name Initial Registration
  • Domain Name Renewal
  • Domain Name Transfer of Sponsorship
  • Public Registry Subscription Service
  • International Domain Name Registration
  • Monitoring Services
  • Domain Name Lockdown     

Maximum Domain-Name Initial Registration Fee

Organic Names may charge a maximum of US $6 per year for each domain name registered (the "Initial Registration Fee") in .org. The Initial Registration Fee shall be paid in full by the registrar sponsoring the domain name at the time of registration.

Maximum Domain-Name Renewal Fee

Organic Names may charge a maximum of US $6 per year for each domain name registration renewal (the "Renewal Fee") in .org. The Renewal Fee shall be paid in full by the registrar sponsoring the domain name at the time of renewal.

Fees for Transfers of Sponsorship of Domain-Name Registrations

Where the sponsorship of a domain name is transferred from one registrar to another registrar, Organic Names will require the registrar receiving the sponsorship to request a renewal of one year for the name, which will run from the date of transfer. In connection with that extension, Organic Names may charge a Renewal Fee for the requested extension, which shall be charged as above.

For a bulk transfer approved by ICANN, Organic Names may charge the gaining registrar US $1 per domain name (for transfers of 50,000 names or fewer) or US $50,000 (for transfers of more than 50,000 names).

Additional Fee-Based Services

Organic Names may also charge a fee for the following services, charges for which will be determined according to customer demand, though Organic Names will commit to not exceeding those charges levelled by VeriSign Inc during its normal commercial operations.

Public Registry Subscription Service (PRSS)

PRSS (known elsewhere as bulk Whois) is a chargeable subscription-based service that will provide, subject to data protection legislation, intellectual property owners and their agents the facility to effectively police and monitor their marks, and similar terms, without overloading the main Whois system.

Once a day, Organic Names will generate a file containing the entire list of registered domains, in a format which will allow easy extraction and manipulation of the data within. A secure web-based interface will be provided that will allow the subscriber to download this file. Transmission of the file will be through HTTP over SSL. Passphrases will be changed regularly.

Internationalised Domain Registrations

Organic Names is committed to supporting Internationalised Domain Name registrations, at a point soon after IDN becomes a recommended standard. The standard, complexity, and patent situation of doing so is currently unclear, and therefore Organic Names reserves the right to make a small additional charge should these result in adverse cost variances over normal registrations.

Monitoring Services

This is a service for registrars to provide to registrants. Firstly, it allows for changes to domain data of an existing domain to be monitored. Secondly, it allows intellectual property owners to monitor registrations of domain names which may infringe on their trademarks.

Domain Lockdown

In a later development phase, Organic Names proposes to introduce a high security domain protection feature for unusually valuable domains, which will prevent modification of domain data except subject to secondary out-of-band security checks.

Fee Adjustments and Tax

All fees above will be subject to adjustment according to the terms the Registry Agreement, and are also subject to adjustment to account for additional charges that Organic Names may pass through to ICANN-accredited registrars in accordance with the terms of the Registry Agreement.

Organic Names commits to cap its fees at those charged by VeriSign for registrations in .com for equivalent services, under normal business conditions.

All fees are exclusive of any applicable sales taxes.

Co-marketing Rebate

Organic Names will rebate Registrars for co-marketing programmes which promote the .org TLD, based on the number of registrations taken. Co-marketing budgets will be set by Organic Names from time to time.

C26

State the maximum price you propose for each Registry Service identified in item C25.

See C25 above.

C27

Describe each Registry Service (as defined in subsection 1.16 of the model .org Registry Agreement) that you propose to provide without charging a fee.

Basic Name Service

Organic Names will insert the appropriate NS and A resource records in the .org zonefile and maintain them in order to provide a DNS service.

Registrar Console

A subset of the staff console, designed to operate only on a particular registrar's names. Registrars may carry out most of the tasks the staff console can carry out, but they will be restricted to names over which they are tagged as having control. This section is accessed through a web browser. The authentication method is via a standard htaccess operation, and the transaction is carried out over an SSL connection.

Email Automaton

A basic email-based automaton is provided for, enabling domain registration and modification, as well as basic accounting and query operations, to be integrated with a Registrars own systems. The automaton uses PGP and GPG authentication methods where appropriate, and the format is similar to that used by Nominet UK and RIPE-NCC.

The presence of an email automaton makes registration easier and lowers barriers to entry for small, technically simple registrars.

RRP Gateway

Registration will be made as per the current VeriSign RRP method.

EPP Gateway

Registration will be made as per the new EPP mechanism, as detailed in section C17.2.

Whois service

A RFC954-compliant Whois service will be provided for domain name lookups.

C28

Describe the technical performance (including quality-of-service commitments) you propose to make. See <http://www.icann.org/tlds/agreements/name/registry-agmt-appd-29jun01.htm> for an example. The successor operator will be expected to meet the Cross-Network Nameserver Performance Requirements set forth in section 2.1 of the document at the above URL.

Organic Names recognises that Quality-of-Service is affected by Internet performance and therefore cannot be closely controlled. Organic Names will therefore monitor its systems very closely and take a proactive stance towards ensuring high technical performance.

Cross-network nameserver performance measurements will be conducted by ICANN at times of its choosing, in the following manner:

  1. The measurements will be conducted by sending strings of DNS request packets from each of four measuring locations to each of the .org nameservers and observing the responses from the .org nameservers. (These strings of requests and response are referred to as a "CNNP Test".) The measuring locations will be four root nameserver locations (on the US East Coast, US West Coast, Asia, and Europe).
  2. Each string of request packets will consist of 100 UDP packets at 10 second intervals requesting ns records for arbitrarily selected .info second-level domains, preselected to ensure that the names exist in the Registry TLD and are resolvable. The packet loss (i.e. the percentage of response packets not received) and the average Round-trip time for response packets received will be noted.
  3. To meet the packet loss and Round-trip-time requirements for a particular CNNP Test, all three of the following must be true:
    1. The Round-trip time and packet loss from each measurement location to at least one .org nameserver must not exceed the required values.
    2. The Round-trip time to each of 75% of the ..org nameservers from at least one of the measurement locations must not exceed the required value.
    3. The packet loss to each of the .org nameservers from at least one of the measurement locations must not exceed the required value.
  4. Any failing CNNP Test result obtained during an identified Core Internet Service Failure shall not be considered.
  5. To ensure a properly diverse testing sample, ICANN will conduct the CNNP Tests at varying times (i.e. at different time of the day, as well as on different days of the week). Organic Names will be deemed to have failed to meet the cross-network nameserver performance requirement only if the .org nameservers persistently fail the CNNP Tests with no less than three consecutive failed CNNP Tests to be considered to have persistently failed.

Organic Names will use reasonable endeavours to avoid failure, and persistent failure, of ICANNs CNNP tests. However, Organic Names will run more stringent quality of service tests itself, as described below, so that it can responder sooner and more proactively to any problems, and so that it can detect more minor degradations.

Organic Names own quality-of-service tests will be conducted by sending strings of DNS request packets from each nameserver location to each of the .org nameservers and observing the responses from the .org nameservers, to include round-trip times (RTT), packet loss and latency. This will result in a mesh of nameserver response times and tests to exceed ICANN requirements. Organic Names also plans to test other TLD nameservers and build agreements for mutual testing.

Organic Names will monitor the complete network and archive historical bandwidth and service statistics using the Multi-Router Traffic Grapher (MRTG) package. This is a tool to monitor the traffic load on network-links. MRTG generates HTML pages containing GIF images that provide a live visual representation of this traffic. The Registry Operator will use this tool for additional monitoring of services, computers and applications using SNMP.

Organic Names will monitor network incidents using the NetSaint and NOCOL alert management programs. These use a client-server architecture combined with methods, with both push and pull data. Network testing is done by polling all monitored services from a single machine and reporting these results to a central location. Organic Names will use both NOCOL and NetSaint to constantly monitor network, computer and application status.

C29 (Intentionally omitted.)