Docstoc

OpenSRS v256 - New User Guide

Document Sample
OpenSRS v256 - New User Guide Powered By Docstoc
					                                        OpenSRS v2.56 – New User Guide
Containing an overview of the OpenSRS system, and information on gTLD (.com, .net, org, .info,
        .biz, .name), ccTLD (.co.uk, .org.uk, .tv, .vc, .ca, .cc and .us), multilingual domain name
                                                                  registrations, and web certificates.




Release Version 2.56

Wednesday, August 07, 2002
Table of Contents – OpenSRS New User Guide
1.0 Purpose.....................................................................................................................8
1.1 General Overview ..............................................................................................................8
1.2 Definition of Terms............................................................................................................9
1.3 Reseller Requirements .....................................................................................................10
2.0 OpenSRS Reseller Entrance and Qualification .......................................................11
2.1 Quick Start Implementation .............................................................................................12
2.2 PERL client-based Full Access Implementation ..................................................................13
2.3 Other Language Implementation ......................................................................................14
3.0 Further Considerations...........................................................................................14
3.1 Quickstart vs. Full Access, in detail ...................................................................................14
3.2 Our Two Environments; Live and Test ..............................................................................14
3.3 The Reseller Web Interface (RWI)....................................................................................15
3.4 The Manage Domain Interface (the MWI) .........................................................................19
3.5 The Domain Year ............................................................................................................20
3.6 Synchronous vs. Asynchronous registries ..........................................................................21
3.7 Renewing a Domain Name...............................................................................................21
3.8. Reseller contact information in the WHOIS ......................................................................21
3.9 Enabling/disabling this feature .........................................................................................22
3.10. Example output of Reseller Contact info in WHOIS .........................................................22
4.0 Payments................................................................................................................23
4.1 Online Credit Card Account Updates .................................................................................25
4.2 Qualifying for Online Account Updates ..............................................................................25
4.3 Cards we accept..............................................................................................................25
4.4 Minimum/Maximum .........................................................................................................25
4.5 Security checks ...............................................................................................................25
4.6 Manual Review................................................................................................................26
4.7 Using the Online Account Update System .........................................................................26
4.8 Reviewing Payments........................................................................................................27
4.9 Payment Manager ...........................................................................................................28
4.10 Pricing ..........................................................................................................................29
4.11 Financial Statements......................................................................................................29
4.11 Financial Statement HTML Results ..................................................................................29
5.0 Rebates/Promotions ..............................................................................................30
6.0 gTLD (.com, .net, .org) Registrations .....................................................................30
6.1 Registration Considerations..............................................................................................31
6.2 Transfers ........................................................................................................................31
6.3 GTLD Qualification...........................................................................................................31
6.4 Quickstart Considerations ................................................................................................32
6.5 Renewals ........................................................................................................................32
6.6 No refunds for renewals ..................................................................................................32
6.7 gTLD Renewal Flow .........................................................................................................32
6.8 gTLD Renewals Features Overview ...................................................................................33
6.9 The Reseller Web Interface and gTLD Renewals................................................................34
6.10 Renewal Functionality from 60, 30, 0 and Passed Due Views............................................35
6.11 Individual gTLD Renewals ..............................................................................................35
6.12 Bulk gTLD Renewals ......................................................................................................35
6.13 Setting gTLDs to auto-renew..........................................................................................37



                     Page 2 of 174 - Release Version 2.56 - support@opensrs.org
6.14 Ability to set gTLDs for NON-renewal..............................................................................37
6.15 gTLD renewals without sufficient funds...........................................................................38
6.16 gTLD Script/Client Considerations for renewals................................................................38
6.17 gTLD Renewal Messaging ..............................................................................................38
6.18 Reseller Renewal Reminders ..........................................................................................38
6.19 Registrant renewal reminders.........................................................................................40
6.20 Reseller Renewal Confirmation .......................................................................................45
6.21 Registrant Renewal Confirmation....................................................................................46
6.22 Bounced renewal messages ...........................................................................................47
6.23 The Manage Domain Interface and gTLD Renewals .........................................................47
6.24 gTLD Renewal Pricing ....................................................................................................47
6.25 Transfer of ownership....................................................................................................47
6.26 Name Transfers for gTLDs (.com, .net, .org) ...................................................................47
6.27 Why Transfer Domains?.................................................................................................47
6.28 Transfer Overview: Transfers To Tucows ........................................................................48
6.29 Transfer Overview: Transfers away from Tucows ............................................................49
6.30 Transfer Overview: Transfers between Tucows Resellers .................................................51
6.31 Domain Transfer Process: Other Registrar to Tucows ......................................................53
6.32 Quick Start Transfers .....................................................................................................56
6.33 Checking the Status of Domain Transfers........................................................................56
6.34 Searching Transfers.......................................................................................................57
6.35 Customizing the Transfer Approval Web Page .................................................................57
6.36 Setting your Transfer Messaging email address ...............................................................58
6.37 Canceling Transfers .......................................................................................................58
6.38 Resubmitting failed transfer orders .................................................................................58
6.39 Verisign NIC Tracking Number........................................................................................59
6.40 Forcing the completion of registrar transfers ...................................................................59
6.41 Transfer Management....................................................................................................59
6.42 RSP Messaging: Transfers to your account ......................................................................60
6.43 RSP Messaging: Transfers away from your account .........................................................60
6.44 End User Messaging: Transfers to your account ..............................................................61
6.45 End User Messaging: Transfers away from your account..................................................63
6.46 Web Page Customization................................................................................................64
6.47 Default Transfer Messages .............................................................................................64
6.48 End User Messages default text......................................................................................64
6.49 Gaining Reseller Messages default text ...........................................................................67
6.50 Losing Reseller Messages default text .............................................................................68
6.51 Pricing ..........................................................................................................................69
6.52 Managing gTLDs............................................................................................................69
6.53 WHOIS Info ..................................................................................................................69
7.0 .co.uk and .org.uk Registrations ............................................................................70
7.1 The .org.uk and .co.uk Opportunity ..................................................................................71
7.2 About ccTLDs..................................................................................................................71
7.3 About Nominet ................................................................................................................71
7.4 .org.uk and .co.uk Registration Considerations ..................................................................71
7.5 Reseller .org.uk and .co.uk Qualification ...........................................................................73
7.6 Quick Start Considerations ...............................................................................................74
7.7 Pricing ............................................................................................................................74
7.8 Managing .org.uk and .co.uk Registrations........................................................................75
7.9 .org.uk and .co.uk Renewals ............................................................................................75
7.10 .org.uk and .co.uk Transfers Of Registration Sponsorship.................................................76
7.11 .org.uk and .co.uk Transfer of Domain Ownership ...........................................................76
7.12 .org.uk and .co.uk Deletion Requests..............................................................................76



                     Page 3 of 174 - Release Version 2.56 - support@opensrs.org
7.13 WHOIS info...................................................................................................................76
7.14 Registration Considerations ............................................................................................77
7.15 Modification Considerations............................................................................................77
7.16 Modification Considerations............................................................................................77
8.0. .ca Registrations....................................................................................................78
8.1 Overview & Feature List...................................................................................................78
8.2 The .ca Opportunity ........................................................................................................78
8.3 .ca Reseller Qualification..................................................................................................79
8.4 About ccTLDs..................................................................................................................79
8.5 About CIRA .....................................................................................................................80
8.6 .ca Registration Considerations ........................................................................................80
8.7 New Registrations ...........................................................................................................80
8.8 .ca Quick Start Considerations..........................................................................................80
8.9 WHOIS info.....................................................................................................................80
8.10 Registration Flow: .ca Registrations ................................................................................82
8.11 The CIRA Username/Password ......................................................................................83
8.12 Modifications to the Reseller Web Interface for .ca ..........................................................84
8.13 Registering Municipal names and other variants of .ca domain names ..............................85
8.14 .ca Registrar Transfers via the RWI ................................................................................86
8.15 .ca registrar transfers through the PERL client code.........................................................86
8.16 .ca Registrar Transfer Process. .......................................................................................87
8.17 Registrar Transfer Status Codes .....................................................................................87
8.18 Resending the CIRA username and password to the Registrant. .......................................88
8.19 Forcing the completion of Registrar transfers ..................................................................88
8.20 .ca transfers Reseller Messaging.....................................................................................89
8.21 .ca transfers End User Messaging ...................................................................................89
8.22 .ca transfers away from your Reseller profile...................................................................89
8.23 CIRA and OpenSRS: other consideration with transfers....................................................89
8.24 .ca Reseller to Reseller Transfers....................................................................................89
8.25 .ca Reseller Transfer Pricing ...........................................................................................90
8.26 .ca Reseller Transfer Status Codes..................................................................................90
8.27 .ca Reseller transfers Reseller Messaging ........................................................................91
8.28 .ca Reseller transfers End User Messaging ......................................................................91
8.29 .ca transfers away from your Reseller profile...................................................................91
8.30 Managing .ca Registrations ............................................................................................91
8.31 .ca Renewals.................................................................................................................92
8.32 .ca renewal considerations .............................................................................................92
8.33 Ability to set .ca names for NON-renewal ........................................................................94
8.34 .ca Renewal Pricing .......................................................................................................94
8.35 .ca Transfer of Domain Ownership, or .ca Registrant Transfers, or .ca Registrant
Organization Name Changes..................................................................................................94
8.36 .ca Deletion Requests ....................................................................................................96
8.37 .ca Pricing .....................................................................................................................96
8.38 GST ..............................................................................................................................96
8.39 Canadian Presence Requirements for Registrants ............................................................96
8.40 What Registrant Name rules apply to the various legal types? ..........................................99
9.0 Multilingual Registrations ....................................................................................109
9.1 Overview & Feature List................................................................................................. 109
9.2 The Multilingual Opportunity .......................................................................................... 109
9.3 Reseller Qualifications....................................................................................................110
9.4 Multilingual Quick Start Considerations ........................................................................... 111
9.5 Multilingual WHOIS Info ................................................................................................ 111
9.6 Modifications to the Reseller Web Interface for multilingual domains ................................ 111



                     Page 4 of 174 - Release Version 2.56 - support@opensrs.org
9.7 Managing Multilingual Domain Names............................................................................. 112
9.8 Multilingual Domain Renewals & Registration Periods ...................................................... 112
9.9 Multilingual Domain Transfers ........................................................................................ 112
9.10 Viewing Multilingual Orders within RWI......................................................................... 112
9.11 RACE Conversions ....................................................................................................... 113
9.12 Multilingual Exhibit A (Registration Agreement) ............................................................. 113
9.13 Multilingual UDRP Considerations ................................................................................. 113
9.14 Multilingual Pricing....................................................................................................... 113
9.15 Process Overview ........................................................................................................ 113
9.16 Entering Data in UTF8 ................................................................................................. 115
9.17 Eight Easy Steps to Creating A Successful Multilingual Flat File ....................................... 116
9.18 Submitting Your Bulk Multilingual Domains.................................................................... 117
9.19 Testing your data for UTF8 compliance ......................................................................... 119
9.20 Resolution Phases........................................................................................................ 120
9.21 RESOLUTION NOTES:.................................................................................................. 121
10 .tv Registrations ....................................................................................................121
10.1 Overview & Feature List............................................................................................... 121
10.2 The .tv Opportunity ..................................................................................................... 121
10.3 .tv Reseller Qualification .............................................................................................. 122
10.4 About dotTV................................................................................................................ 122
10.5 .tv Registration Considerations ..................................................................................... 122
10.6 Standard Registrations................................................................................................. 122
10.7 High Profile Registrations ............................................................................................. 122
10.8 .tv Quick Start Considerations ...................................................................................... 123
10.9 WHOIS info................................................................................................................. 123
10.10 .tv Registration Flow: Standard Registrations............................................................... 123
10.11 .tv Registration Flow: High Profile Registrations........................................................... 123
10.12 Managing .tv Registrations: Contact Changes .............................................................. 123
10.13 .tv Renewals .............................................................................................................124
10.14 .tv Transfer of Domain Ownership .............................................................................. 124
10.15 .tv Deletion Requests ................................................................................................. 124
10.16 .tv Standard Pricing ................................................................................................... 124
10.17.tv high Profile Pricing ................................................................................................. 124
11.0 .vc Registrations.................................................................................................124
11.1 New Version Overview & Feature List ........................................................................... 125
11.2 .vc Reseller Qualification .............................................................................................. 125
11.3 .vc WHOIS info............................................................................................................ 125
11.4 .vc Registration Considerations..................................................................................... 126
11.5 .vc Contact Changes .................................................................................................... 126
11.6 .vc Renewals ............................................................................................................... 126
11.7 .vc Transfer of Domain Ownership................................................................................ 126
11.8 Registrar Transfers ...................................................................................................... 126
11.9 .vc Pricing ................................................................................................................... 126
12.0 Web Certificates .................................................................................................126
12.1 Overview of Web Certificate Offering ............................................................................ 127
12.2 Refund Policy .............................................................................................................. 127
12.3 Web Certificate Purchase Process ................................................................................. 127
12.4 Reseller Web Interface Commands ............................................................................... 129
12.4.1 Place Order for Web Certificates ................................................................................ 130
12.4.2 Search for Web Certificates ....................................................................................... 131
12.4.3 View Pending Orders................................................................................................. 134
12.4.4 Cancel Key Codes ..................................................................................................... 135
12.4.5 Modifying Reseller Certs Preferences.......................................................................... 136



                    Page 5 of 174 - Release Version 2.56 - support@opensrs.org
12.5 General Notes around Certificate Processing ................................................................ 139
12.6 Changes to the Manage Domain Interface for Web Certificates ...................................... 139
12.7 Renewing Certificates .................................................................................................. 139
13.0 .info Registrations ..............................................................................................140
13.1 .info Reseller Qualification............................................................................................ 140
13.2 .info Overview ............................................................................................................. 140
13.3 .info Registration Considerations .................................................................................. 140
13.4 Registering .info names via the RWI ............................................................................. 140
13.5 .info Registrar/Reseller/Registrant Transfers ................................................................. 141
13.6 Reseller Pricing............................................................................................................ 141
13.7 Updates on the Client Code.......................................................................................... 142
13.8 .info Registration Flow ................................................................................................. 142
13.9 .info Deletion Requests ................................................................................................ 142
13.10 .info Renewals...........................................................................................................142
13.11 .info auth_code ......................................................................................................... 142
13.12 .info Manage Considerations....................................................................................... 143
14 .biz Registrations...................................................................................................143
14.1 .biz Reseller qualification.............................................................................................. 143
14.2 biz registration Considerations...................................................................................... 143
14.3 Modifications to the reseller Web interface for .biz......................................................... 144
14.4 The .biz auth_code ...................................................................................................... 144
14.5 .biz registrant/registrar/reseller transfers ...................................................................... 144
14.6 .biz registration flow ....................................................................................................145
14.7 .biz deletion requests................................................................................................... 145
14.8 Reseller pricing for .biz ................................................................................................ 145
14.9 .biz Manage considerations .......................................................................................... 145
14.10 .biz Domain Name Application Reserved Names by NeuLevel........................................ 145
15. .name Registrations .............................................................................................149
15.1 The .name opportunity ................................................................................................ 149
15.2 .name reseller qualification ......................................................................................... 149
15.3 .name registration considerations ................................................................................. 150
15.4 Modifications to the reseller Web interface for .name..................................................... 150
15.5 Reseller pricing for .name ............................................................................................ 151
15.6 .name deletion requests............................................................................................... 151
15.7 .name renewals and transfers ...................................................................................... 151
15.8 Reserved names.......................................................................................................... 151
16 .US Registrations ...................................................................................................154
16.1 .us Reseller qualification .............................................................................................. 154
16.2 us registration Considerations ...................................................................................... 155
16.3 Modifications to the reseller Web interface for .us ......................................................... 156
16.4 The .us auth_code....................................................................................................... 156
16.5 .us registrant/registrar/reseller transfers ....................................................................... 156
16.6 .us registration flow ..................................................................................................... 157
16.7 .us deletion requests ................................................................................................... 157
16.8 Reseller pricing for .us ................................................................................................. 157
16.9 .us Manage considerations ........................................................................................... 157
17. Order Queuing ......................................................................................................158
17.1 Queuing setting in Reseller Web Interface..................................................................... 158
17.2 Queuing Settings ......................................................................................................... 158
17.3 Viewing Queued Requests............................................................................................ 159
18. Technical Support.................................................................................................159
18.1 Technical Support........................................................................................................ 160
18.2 The OpenSRS Web Site................................................................................................ 160



                    Page 6 of 174 - Release Version 2.56 - support@opensrs.org
18.3 Peer based support...................................................................................................... 160
18.4 Other documentation................................................................................................... 160
18.5 Communication methods.............................................................................................. 161
19. Appendix A. Data Constraints ..............................................................................161
20. Appendix B. Detailed .com/net/org Transfer Process .........................................163
Transfer Process Flow Narrative........................................................................................... 167




                   Page 7 of 174 - Release Version 2.56 - support@opensrs.org
 1.0 Purpose
The purpose of this document is to offer a holistic view of OpenSRS, including its business tools
and tactics.

Please send any comments on this document to suggest@opensrs.org

What is a Reseller?

Throughout this document you’ll see reference to Resellers; Resellers are Managed Service
Providers, and the OpenSRS system is the platform through which Tucows provides services to
our Resellers. At the moment, these services are limited strictly to domain names and web
certificates (and associated administrative and management services), but in the near future,
expect the offerings to multiply dramatically.


 1.1 General Overview

With the OpenSRS system, Tucows has introduced an open source, wholesale domain
registration model aimed at resellers in the Internet industry. Tucows provides resellers with the
software required to incorporate domain name registration into their business model.

Options for implementing the OpenSRS system include:

    i)      Quick Start: a web based, OpenSRS hosted registry interface
    ii)     Full Access: a set of fully customizable PERL scripts that resellers can integrate into
            their existing websites
    iii)    Build your own: a complete protocol description which allows resellers to write an
            interface in the language of their choice

All options provide resellers with access to the all TLDs and services that Tucows offers, if you’ve
signed the contract for that particular TLD/service (see specific TLDs and services for instructions
on contract locations)

OpenSRS also provides a public interface that registrants use to ‘manage’ their domain names,
allowing them to make changes to domain ownership, contact and nameserver information.
Again, resellers have the option of either referring their clients to our public Manage Domain
interface, or taking Tucows’ scripts and building a custom Manage interface that matches the
look and feel of their website. Note that the public management interface does not provide some
features, such as domain locking and renewals. These are functions that are modifiable in the
client code.

The Tucows/OpenSRS model allows the reseller to be a ‘one stop shop’ as far as their clients are
concerned; Tucows is, in most marketing respects, transparent to the End User in the process.

Resellers must demonstrate proficiency (by completing a simple test) before they are actually
able to register domain names. The test is not overly complex; we simply want to be sure that
potential Resellers understand how to access the registries using the OpenSRS system before
they attempt to offer these services to their clients.

Currently, Resellers must maintain an account balance with Tucows in order to register domain
names. Prices vary by product; for pricing information, please refer to the specific sections of this



               Page 8 of 174 - Release Version 2.56 - support@opensrs.org
document. For each registration (or renewal/transfer), the appropriate amount of money is
withdrawn from the Resellers account balance. Resellers must remit a payment (prepay) before
they are able to offer name registration to their clients. Insufficient funds will mean a transaction
is not processed (and an appropriate error is generated).

NOTE: Resellers can make payments into their ‘account’ before their account is actually made
active; this allows Resellers who’ve completed their system testing to start registering domain
names as soon as they ‘go live’.


 1.2 Definition of Terms

Generic Top Level Domain (gTLD)

gTLDs are top level domains that are not associated with any country. Currently, the only gTLDs
in existence are .com, .net and .org. Originally, the top level domain designation was meant to
denote whether the domain name was being used for business (.com), charity/non-profit (.org),
or for a network (.net). However, with the explosion of the Internet (and specifically, the world
wide web) as a new business medium, the lines were blurred, and companies and individuals
alike started cross-registering domains (ie. me.com, me.net, me.org) just to protect their
interests. Now, .com, .net, and .org names (the generic Top Level Domains) can be used for any
purpose.

Country Code Top Level Domain (ccTLD)

Every country (and a few territories) in the world has a reserved, two letter country code domain
that is theirs to use as they see fit. Some countries run their own ccTLD registry, others
outsource it to a private company, and still others sell rights to their ccTLD to third parties to run
as they see fit.

Examples of ccTLDs are .ca (Canada), .us (United States), and .to (Tonga). In general, these are
registered by businesses with a coincidental link to the TLD in question.

For example: .to is used more by Torontonians than Tongans and .tv has more American
television content than native Tuvalu culture.

Domain Registrar

A "Registrar" (or "Domain Name Registrar") is an organization like OpenSRS or Network Solutions
that has control over the granting of domains within certain TLDs (top level domains, like the
generic .com/.org/.net or country-specific .ca/.us/.mx etc.).


Domain Registry

The 'Registry' is the system backend that is maintained by the operators of the TLD. Registrar's
write new names to a central registry database, from which the authoritative root (essentially, a
table of all domain names) is built. In the case of .com, .net and .org, the InterNIC runs the
registry, and qualified registrars have shared access to it. In the case of many ccTLDs, the
registry and registrar functions are combined within one entity.


Domain Registrant



               Page 9 of 174 - Release Version 2.56 - support@opensrs.org
A registrant is the person or company who registers a domain name. For example, Jessica Smith
(registrant) registers the name jessicasmith.com through OpenSRS (registrar) who in turn writes
the name to the central database (Registry).

OpenSRS (Open Shared Registration System)

OpenSRS is a wholesale domain name registration service that uses Open Source principles to
ensure equal participation for as many companies and individuals as possible. Sponsored by
Tucows.com, OpenSRS has been accredited as a domain registrar by ICANN and recognized by
the United States Government and Network Solutions.

Registration Service Provider (RSP/Reseller)

Under the OpenSRS model, the Registration Service Provider resells domain names through
OpenSRS and sells them to individuals or businesses. RSPs are generally Internet based service
providers, either running a domain registration business as a 'value add' to their core business, or
in some cases, as their core business. RSPs also provide all technical support to domain
registrants.

Reseller Web Interface (RWI)
The RWI is the web interface for OpenSRS Quickstart RSPs. All registrations, transfers, renewals
and domain administrative settings available to the Quickstart Reseller are offered through the
RWI.

Management Web Interface (MWI)
The MWI is the interface through which registrant actually manage contacts and nameservers
associated with their domain. A customizable version of our manage.cgi is included in our client
software; we also maintain a public manage interface at http://manage.opensrs.net


 1.3 Reseller Requirements

Following are the requirements to offer name registrations through OpenSRS; Resellers must
meet the basic requirements AND either the Quickstart or Full Access requirements:

Basic requirements:

    a) ability to process payments from end-users; essentially collect money from your
       customers, unless you are not planning on charging them, or are registering names for
       internal use only

    b) ability to support your customers; telephone and/or email support options to handle
       inquiries from your end users; documentation for your end users

Quickstart requirements:

    a) Internet access

    b) Name servers, or access to name servers; required if you want the names you register to
       resolve (work) on the Internet

Full Access requirements:

    a) dedicated connection to the Internet with a static IP address


              Page 10 of 174 - Release Version 2.56 - support@opensrs.org
    b) web server which allows CGI execution (e.g. Apache, http://www.apache.org/)
    c) Perl5 (Practical Extraction and Report Language) http://www.perl.org/ if you are
       choosing to use our Based-based client
    d) cryptography PERL modules, downloaded separately from CPAN http://search.cpan.org/ ;
       see the “OpenSRS PERL Client Manual” for details
    e) enough PERL knowledge to customize our PERL client

         OR

    f)   enough expertise in your preferred development language to build your own client using
         our API

 2.0 OpenSRS Reseller Entrance and
Qualification
The process for becoming an OpenSRS RESELLER is relatively simple. We’ve split the process into
two components, an administrative component and a technical component.

A. The Administrative Component

Anyone wanting to become a RESELLER must first fill out our online form at:

https://horizon.opensrs.net/subscribe/

Once the form has been filled out you are given a reference number, and asked to read,
complete and fax the Tucows/OpenSRS Registration Service Provider Agreement (available on
our website at http://resellers.tucows.com/opensrs/) for each registry that you want to register
domains in.

Once we’ve received Registration Service Provider Agreement, it is reviewed for completeness
and correctness, mindful of signatures on the appropriate pages. If all appears in order, staff
activates your profile in the test environment, and an email is sent out with further instructions
and your username and password.

B. The Technical Component

Once active in the test system, you must choose whether you want to go forward with the
Quickstart system, the PERL-based Full Access system, or to write your own Full Access client in
your preferred programming language.

A Quickstart implementation is the faster, simpler option, but it does not offer nearly the degree
of customization, automation, or functionality of a Full Access implementation. Consider
Quickstart as a fast way to get your business going until you have your client installed and
configured.

For a full list of differences between Quick Start and Full Access, please see section 3.1.

Once you have decided which implementation you wish to pursue, please see the relevant
section below:

Section 2.1, Quick Start Implementation
Section 2.2, Full Access Implementation
Section 2.3, Other language implementation


              Page 11 of 174 - Release Version 2.56 - support@opensrs.org
 2.1 Quick Start Implementation

Very little preparation is needed to run a domain registration business using the Quick Start
system. Since you’ll have to process all registrations manually through the RWI (Reseller Web
Interface), you will not need to incorporate our scripts into your site and can start registering
domain names very quickly. Note: for testing purposes, you will have access to all TLDs that
Tucows offers; however, in the Live system you will only be able to register domains in the TLDs
for which we have received a contract.

This section assumes that you have already:
             1) Filled out the online application for at https://horizon.opensrs.net/subscribe/
                      i. You will receive an access number via email after this; quite this number
                         when submitting your contract

            2) Have filled out and submitted one of the OpenSRS Reseller Contracts (for the
               service or TLD(s) that you wish to sell.

            3) Have used the information obtained after step one to connect to our Test
               Environment at https://horizon.opensrs.net/resellers/ (the RWI for the test
               system)

            4) Have at least reviewed the link to the Quickstart test available once you have
               logged in to the RWI on Horizon

You must become familiar with the Reseller Web Interface (RWI); see section 3.2 for a complete
overview.

You must then complete and submit the Quick Start Access test (by selecting this option within
the RWI).

After submitting the test results you will be informed of whether you were successful or not. If
you pass, your account is made active in the live system, and if you’ve already paid, you can
begin registering domains right away. Please note that you will not be able to begin registering
domains until you have established an account balance with Tucows. For information on
payments, please see section 4.0.

If you were unsuccessful in completing the test, we advise you of what was incomplete/incorrect
and you may try again.

Upon gaining access to the “live/production environment”, there are a few last steps to complete:

    a) decide whether to process orders immediately or have orders sit in a queue for review
       before processing

    b) customize the message (if desired) that registrants receive once their domain registration
       is processed

    c) customize the message that you receive (if any) when a domain registration is processed

    d) update default name server information under “Modify Technical Contact Information” in
       the RWI




              Page 12 of 174 - Release Version 2.56 - support@opensrs.org
    e) ensure your contact information is appropriately configured under “Emergency Contact
       Information” in the RWI

 2.2 PERL client-based Full Access Implementation

Implementing the full access client interface is a more lengthy process, requiring installation and
customization of client-side PERL scripts that interface with the OpenSRS server, which in turn
communicates with the root registries. However, the advantages of a customized ‘look and feel’
and an automated ordering and management process make this well worth the effort.

An experienced PERL programmer works to integrate these scripts into the Resellers web site.
The scripts take information entered via the web interface, encrypt it, and pass it along to the
OpenSRS server. The scripts require PERL, and can run in either a Unix or Windows NT
environment, and can be downloaded from the OpenSRS web site.

The definitive guide to implementing the scripts is distributed with the client package (available
on our web site), “OpenSRS PERL Client Manual”.

Once the scripts have been put in place, you must use your newly built interface to perform the
Full Access test. Note: for testing purposes, you will have access to all TLDs that Tucows offers;
however, once in the Live system, you will only be able to register domains in the TLDs for which
we have received a contract.

Once you’ve completed the test and submitted the results, we’ll inform you of whether you were
successful or not. If you complete the test successfully, your account is made active in the live
system. Please note that you will not be able to begin registering domains until you have
established an account balance with Tucows. For information on payments, please see section
4.0.

If you are unsuccessful in completing the test, we will advise you of what was
incomplete/incorrect and you may try again.

Upon gaining access to the “live/production environment”, there are a few last steps to complete:

    a) customize the message (if desired) that registrants receive once their domain registration
       is processed

    b) customize the message that you receive (if any) when a domain registration is processed

    c) update default name server information under “Modify Technical Contact Information” in
       the RWI

    d) ensure your contact information is appropriately configured under “Emergency Contact
       Information” in the RWI

    e) change your configuration so that your scripts are communicating with the Live
       environment by changing a setting in the opensrs.conf file, and generate a new private
       key for encrypted communication between their client and our server. You must also
       contact rite-bc@opensrs.org with the IP address that your client will be contacting our
       server from, so that we allow the traffic through.




              Page 13 of 174 - Release Version 2.56 - support@opensrs.org
 2.3 Other Language Implementation

If you elect to write you own tools in the language of your choice, you will want to refer to our
“OpenSRS Protocol Specification”, which covers this approach completely. This document is
available as part of the client release, and on our web site. Once you’ve built your client,
entrance and qualification is identical to the Based-based implementation described in Section
2.2.

 3.0 Further Considerations
This section will cover important concepts and processes that are important to understand as an
OpenSRS RESELLER.

 3.1 Quickstart vs. Full Access, in detail

It is useful to understand the differences between the Quickstart and Full Access systems. The
Quickstart system is intended as a stepping-stone that Resellers use until their Full Access system
is in place. Tucows wants to encourage Resellers to use the Full Access system because:

    a)   more automation means more domains, increasing your revenue
    b)   Bulk registrations and transfers mean more revenue
    c)   Resellers can build their registration model the way they want to
    d)   Our open relationship with our RSP community provides feedback on client functionality,
         giving us invaluable ideas for new features and enhancements.

The Quickstart system allows for:

    a) manual single domain registration
    b) manual single domain registrar transfer
    c) use of all other features of the RWI (see below)

The Full Access system allows for:

    a) single and batch domain registrations
    b) single and batch domain transfers (for certain TLDs)
    c) Resellers to offer their customers a web interface for registrations, transfers and domain
       administration that preserves the look and feel of the rest of the Reseller’s website
    d) use of all other features of the RWI (see below)


 3.2 Our Two Environments; Live and Test

To facilitate risk free learning and testing of the OpenSRS system, we maintain two
environments, commonly known as Live and Test, or by their host names horizon.opensrs.net
and rr-n1-tor.opensrs.net . The Test environment mirrors the live environment in nearly every
way, and is the ‘proving grounds’ where Resellers must demonstrate proficiency before entering
the Live environment to register actual domain names. Note: All gTLDs and ccTLDs are available
in the Test Environment; once the Reseller goes live, they can only register domains in the TLDs
for which they have qualified.

The test environment can be accessed via shared web interface (Quick Start) or customized
scripts (Full Access). Similarly, there is an end user ‘Manage Domain’ interface for the test
environment can be accessed via shared web interface, or customized scripts.




               Page 14 of 174 - Release Version 2.56 - support@opensrs.org
Registrations submitted in the Test environment are not actually registered.

The following table shows the URLs of our interfaces in the Live and Test environments:

URL for OpenSRS Interfaces
System                    Test                                      Live
Reseller Web Interface    http://resellers-test.opensrs.net/        http://resellers.opensrs.net/
Manage Domain Interface   http://manage-test.opensrs.net/           http://manage.opensrs.net/

 3.3 The Reseller Web Interface (RWI)

The Reseller Web Interface is an OpenSRS hosted web interface that allows Resellers to manage
and review sales, and set some defaults that are important to the way domain registrations are
offered. All Resellers, whether Quickstart or Full Access, must use the RWI to manage many
elements of their domain registration service. The RWI looks like this (there are many more
options than shown):




                                                      Figure 1: The Reseller Web Interface (RWI)


The following section describes the features available to Resellers via the RWI.

Order Management

Place Order Manually:
This is where you can register new domain names. See below for further detail.

Place Transfer Manually:
This is where you can initiate the transfer of a gTLD from another Registry to OpenSRS. See
below for further detail.

Place Multilingual Bulk Order Manually:
This interface allows for the registration of multiple IDN domain names by using a file (upload).

Place Order Manually for .ca:
This is where you register new .ca names.



              Page 15 of 174 - Release Version 2.56 - support@opensrs.org
Place Transfer Manually for .ca:
This allows you to place a transfer for a .ca domain name

View .ca blocked orders:
When a .ca domain name registration is requested that conflicts with an existing .ca domain
name (i.e. order for chuck.on.ca conflicts with chuck.ca) a special process is invoked. This
interface allows you to see the status of these orders.

Place Order Manually for .us:
This is where you can register .us names.

Place Order Manually for .name:
This is where you can register .name domains.

View Pending Orders:
This allows you to view orders you have entered into the system as pending. These orders will
not be registered until you enter this area and approve them. Also, if a registration fails for any
reason, (for example, incorrect registration term) it will be put into this section for you to review.

This function was primarily designed to work with the Full Access implementation of OpenSRS,
where end users would submit orders, you would mark them as pending, and you would approve
them (perhaps after getting payment).

View Orders In Progress:
This allows you to view domain orders/transfers that have been initiated by either yourself or an
end user through your online interface. Orders in process can include domain transfers, and
registrations into any asynchronous registries. Synchronous new name registrations (.com .net
and .org) never appear here, as they are processed in real time.

Transfers views:
        Waiting Owner Approval:
        This shows transfer orders awaiting the Administrative contact approvale/declination
        Waiting OpenSRS Review:
        Transfers in this step are awaiting review by our administrative department
        Waiting Registry Approval:
        Transfers in this view show orders sent to the registry for approval
        Transfers Away:
        Domains in this view show domains that have a request to be transferred to another
        registrar or reseller

View Declined Orders:
Use this view to review and resubmit orders that were declined (for various reasons) by the
registry or cancelled during the transfer process.

View Completed Orders:
If you follow this link, you can view all domain names that you have successfully registered
through OpenSRS.

Search Reg System Orders:
Once you have registered some domain names, you can use this form to search for a specific
registration. You can also search for any of your domains (whether new or transferred) at any
point in process once it has entered the OpenSRS system



               Page 16 of 174 - Release Version 2.56 - support@opensrs.org
Search Batch Transfers:
This function allows Resellers to search through any transfers (either in progress or completed)
that they have processed using the batch transfer command (Full Access only).

Domain Management

View Domain:
Use this feature to drill down to an individual domain record, review expiry information and
domain names, and apply changes to a domains renewal setting.

Search Domains:
This section allows Resellers to specify search criteria view a list of all domains that have
successfully been registered with or transferred to OpenSRS, and their renewal dates.

        Status Definitions

    a) All Active
       All live domains that are currently sponsored by Tucows that reside in your Reseller
       profile

   b) All Deleted
      All domains that were once active in your profile, but have since become inactive, due to
      transfer away, expiry, or explicit deletion request.
           a. Deleted Historical
               The status ‘Deleted Historical’ has been used to flag all domains that were
               rendered inactive due to expiry, transfer away, or deletion request prior to
               version 2.4 of the OpenSRS server software.
           b. Deleted Expired
               The status given to names inactive in your profile because they expired
           c. Deleted Transferred
               The status given to names transferred from your OpenSRS profile either to
               another OpenSRS reseller, or to another Registrar.
           d. Deleted-By Request
               The status given to names deleted by explicit request from the Reseller.
Output to File

Note the new output option present in the preceding screenshot that allows Resellers to output
the results table for any ‘Search Domain’ queries to a comma delimited file.

Renewal Management (LIVE system only)
Use this section to manage your gTLD renewals. For more information, refer to section 6.5 of this
document.

Transfer Management (LIVE system only)
This section allows you to manage messages relating to a variety of Transfer activities

Registry Nameservers
This interface allows you to populate new nameservers at foreign registries (i.e. adding a .com
based nameserver to the .info registry).

Registration Statistics




               Page 17 of 174 - Release Version 2.56 - support@opensrs.org
View Reg System Statistics:
Use this section to view a daily breakdown (by month) of lookups, orders, and complete
registrations done under your Reseller profile.

View Registration Stats:
Use this section to review domains registered and domain years registered in a specified date
range.

Profile Management

Reseller Contact Information:
Use this section to provide contact information for someone in your organization that we could
use in the event of an important update, such as new version releases, or downtime
announcements. You also use this area to specify the email address that should receive
OpenSRS system announcements, low account balance notifications and new payment
notifications. This is also the address to which all paper correspondence is sent.

Tech Contact Information:
This is where you edit your default technical information (sent for all new registrations), and
where you change your reseller password. Also, use this section to configure the message sent to
the registrant upon successful registration of a domain name.

Reseller Whois Information:
This interface allows you to modify settings and variables shown via the whois for domains under
your sponsorship.

Payment Information:
Use this section to specify the threshold for your low account balance warning. You set your limit
in dollars, and when your account is drawn to that limit, you are sent an email at the address of
your choice.

Online Credit Card Payment:
By working with payments@opensrs.org, you can have this interface enabled to allow you to
enter funds into your account with a credit card and not need to fax in payment information.
Note that there are some requirements for this, more information is available here:

http://resellers.tucows.com/opensrs/payment/

Modify Reseller Password:
Here resellers can change their password to access the Tucows registration systems and
administration interfaces.

Submit your completed test results: (test system only)
Once you have completed either the Quick Start of Full Access RITE tests, follow this link to see
whether you were successful or not.

Full Access Test Instructions: (test system only)
Follow this link to obtain the instructions for the Full Access RITE test

Quick Access Test Instructions: (test system only)
Follow this link to obtain the instructions for the Quick Start RITE test

Generate New Private Key:



               Page 18 of 174 - Release Version 2.56 - support@opensrs.org
This is the mechanism used to generate the back-end “private key” that’s used with the client
code (scripts). The key is used for authentication and building a secure socket for client/server
communications.

Logout:
Follow this link to end your session.

 3.4 The Manage Domain Interface (the MWI)

Registrants make changes to their domain name records using the Manage Domain interface.
They can use the interface to:

    -   Modify domain ownership (certain TLDs only)
    -   Modify administrative, technical and billing contact information
    -   Modify nameserver information
    -   Modify other domain attributes (auth code for EPP domains, lock status, email forwarding
        for .name, etc)

Registrants log into the MWI using the username and password that they selected when they
registered the domain.

Resellers may elect to implement their own customized version of the manage interface and build
specific functionality into it (templates are included in the Full Access scripts). OpenSRS also
maintains a shared manage interface (at https://manage.opensrs.net) for Resellers who do not
run their own manage interface.

The shared OpenSRS manage domain interface looks (something) like:




              Page 19 of 174 - Release Version 2.56 - support@opensrs.org
                                                             Figure 2: The Shared Manage Interface
Manage Profile:
This allows you to:

    -   change the username and password that controls a domain name, typically to transfer
        control of the domain to someone else
    -   move this name to another OpenSRS profile, to either transfer control of the name to
        someone else, or to organize name control
    -   assign a sub-user access to manage either parts of, or all information related to this
        name

Organization Contact:
This is where you can view and edit information about the company or entity associated with the
domain you are managing. NOTE: The organization that .co.uk, .org.uk, or .ca names are
registered to cannot be changed using this interface. For details on changing the Organization
contact these TLDs, please refer to the section covering the TLD you are interested in.

Admin Contact:
This is the person or entity named as "authoritative" as related to decisions made for changes to
domain records.

Billing Contact:
This is the contact responsible for billing issues with regard to this domain's registration. In order
to avoid interruption in service, the registration fee must be up to date at all times. This record
should be accurate in order to maintain renewal fees properly.

Technical Contact:
This is the contact considered authoritative for this domain name as related to Web hosting, mail,
and other DNS records. This is typically an ISP or Web Hosting Provider but it can be anyone the
Registrant chooses. By default, this information is initially populated from the Reseller’s Technical
Contact profile, set in the RWI.

Manage Name Servers:
Controls which name servers are designated as authoritative for the domain. Registrants can also
create nameservers based on their domain names here.

Domain Extras:
Shows information that does not apply to other sections, such as AUTHCODE (for
.info/.biz/.us/.name domains).email forwarding options (for .name domains) and .us “Nexus”
information.

Reseller Contact:
This section shows the Registrant who their Reseller is, and allows them to opt-out of showing
this information via WHOIS.

Domain Locking:
This section shows the registrant whether their domain is currently set to ‘Lock’ (which means
that transfers and DNS modification cannot be made until the domain is ‘Unlocked’) or ‘Unlocked’.
Note that Registrants CANNOT change this setting via our Public Manage Interface.

 3.5 The Domain Year

When discussing domain names, it is useful to understand the concept of the domain year.
Because domains can be either registered within the OpenSRS system or transferred to it, and


               Page 20 of 174 - Release Version 2.56 - support@opensrs.org
because registrants have the option of paying for more than one year, domain years often are
the best, most meaningful way to describe what OpenSRS provides to its Resellers. A domain
year is one year paid on a domain name. Whether a domain is registered with us, transferred to
us or renewed for an additional term, domain years can be used to describe the service being
sold.

 3.6 Synchronous vs. Asynchronous registries

Tucows now offers domain registrations into two different types of top-level domain registries,
synchronous and asynchronous. A synchronous registry allows resellers to register and make
changes to domain names in ‘real time’. The server responds to client requests immediately, with
either confirmation of the expected change or an error message explaining why it didn’t work.
Asynchronous registries accept requests from the client, but the requests are reviewed before
any change is made. This requires that a ‘wait state’ exist, wherein resellers/end users are aware
that they’ve made a request, but are waiting for the registry to actually make the change. In
these cases, the system will be updated and notification sent to the RESELLER to confirm the
change has been made. Currently, our domain name offering breaks down into synchronous and
asynchronous as follows:

               Synchronous                                  Asynchronous
.com, .net, .org, .ca*, .biz, .info, .name,   .co.uk, .org.uk, .ca*,
.tv, .vc, .us

Processing time for asynchronous registries varies by registry; *.uk registrations, for example,
completed in under five minutes, however it can take longer based on circumstances beyond the
control of Tucows. As a result of this, it is important to communicate this delay to users when
they place orders with you. You can check the status of a submitted order anytime through the
Reseller Web Interface (RWI).

*There are both synchronous and asynchronous elements to .ca names. Most elements are
synchronous, but certain contact changes are considered ‘critical’ and require confirmation from
the registrant.

 3.7 Renewing a Domain Name

For information on renewing domain names, refer to the TLD specific sections of this document.

 3.8. Reseller contact information in the WHOIS

In a continuing effort to provide registrants with appropriate information on who to contact for
their domain services, we have modified our WHOIS output so that Reseller Contact information
is shown prominently in WHOIS output for .com/.net/.org domains.

This new feature is customizable, and can be enabled/disabled by each Reseller. We have
defaulted the feature to ‘On’ for all reseller. If this feature is enabled, ONE OF THE FOLLOWING
pieces of information must be provided:

    1.   Business Name (Optional)
    2.   Your support email address
    3.   Your support phone number
    4.   Your fax number
    5.   Your support URL

You MUST show at least ONE of options 2-5.



               Page 21 of 174 - Release Version 2.56 - support@opensrs.org
 3.9 Enabling/disabling this feature

To enable/disable this feature for all of your domains, log into the RWI, and click on ‘Reseller
WHOIS Information’ under Profile management. You’ll find:




Whether the feature is enabled for domains in your reseller profile depends on whether you have
the ‘Activate’ setting on ‘Yes’ or ‘No’. If this feature is enabled, then ONE OF the following are
required:

    a)   URL or
    b)   Telephone Number or
    c)   Fax Number or
    d)   Email address

Note: Registrants can disable this feature for their particular domain, even if you
have the feature turned on globally, through Manage Domain interface. This is not
available via the Public Manage Interface, and must be enabled via your own client
scripts.

NOTE: Disabling this feature only disables Reseller Contact output in the WHOIS;
registrants can still see this information in the ‘Reseller Contact’ section of the
Manage domain interface.

 3.10. Example output of Reseller Contact info in WHOIS


The following is an example of the WHOIS output for a domain in a Reseller profile with this
feature enabled:

WHOIS info for, tucows.com:


Registrant:
 Tucows Inc.
 96 Mowat Avenue



              Page 22 of 174 - Release Version 2.56 - support@opensrs.org
 Toronto, Ontario M6K3M1
 CA

 Domain Name: TUCOWS.COM

 Administrative Contact:
    Contact, Administration           dnsadmin@tucows.com
    96 Mowat Avenue
    Toronto, Ontario M6K3M1
    CA
    1- 416-535-0123

 Technical Contact:
    Contact, Technical dnstech@tucows.com
    96 Mowat Avenue
    Toronto, Ontario M6K3M1
    CA
    1-416-535-0123

 Registration Service Provider:
    Tucows.com, dnstech@tucows.com
    416-535-0123
    http://www.opensrs.org

 Registrar of Record: TUCOWS, INC.
 Record last updated on 13-May-2002.
 Record expires on 06-Sep-2006.
 Record Created on 07-Sep-1995.

 Domain servers in listed order:
    DNS1.TUCOWS.COM   216.40.37.11
    DNS2.TUCOWS.COM   216.40.37.12
    DNS3.TUCOWS.COM   207.136.98.110


 4.0 Payments
OpenSRS will accept pre-payment by wire transfer, cheque, international money order, and credit
card only. We will not accept payments remitted in currencies other than US Dollars (USD).
Please note the minimum payment remittance is $250.00 USD.

Your first payment to the Tucows for use within the OpenSRS system can be made anytime after
you’ve been approved in the Test environment. If you pre-pay before you complete your RITE
test, you will be ready to register domains as soon as you pass the test and are made active in
the live environment. The minimum initial payments are:

Full Access: $250 USD
Quickstart: $500 USD

The 7% Goods and Services Tax must be paid by all Canadian Registration Service Providers. For
information on tax rebates, please refer to the Canadian Customs and Revenue Agency web site
at http://www.ccra-adrc.gc.ca/menu/EmenuHDA.html .

Please note that Tucows recommend purchasing at least one month's worth of credits at a time.
Depending on the payment method you choose, and volume, applying your payment to your
account can take up to two business days after payment is received.



              Page 23 of 174 - Release Version 2.56 - support@opensrs.org
1. Wire Transfers
When remitting a payment via wire transfer, please send a confirmation e-mail to
payments@opensrs.org with the your Company name, OpenSRS user name (if you have been
assigned one), date, originating bank, amount of the transfer, and the Account Name in which
the transfer was conducted from. Wire transfer remittances will be applied to your account within
one business day of receipt.

Please ensure that your company name or OpenSRS user name appear in the sender section of
the wire transfer.

Please note that there is a $15 processing charge for remittances by wire transfer for under
$5000.00. Please add this amount to any remittances submitted via this method.

Wire transfers should be submitted to:

MT100
HSBC Bank USA, New York, N.Y.
SWIFT: MRMDUS33
Pay to HSBC Canada- A/C 000-050881
For account: 362 -003 -068-070
Beneficiary: Tucows.com Co.

2. Cheques, International money orders
Cheque Payments and money orders should be made payable to Tucows.com Inc. and delivered
to:

Tucows Inc.
96 Mowat Avenue
Toronto, Ontario
Canada
M6K 3M1

You must include your OpenSRS username with your cheque or money order. Please note that
non-certified cheque remittances will not be processed until the transaction has cleared our bank,
which can take up to 15 business days.

Certified cheques and International Money Orders will be applied to your account within one
business day.

3. Credit Cards
If you are making a credit card remittance, please submit by fax a signed copy of the form found
at:

http://resellers.tucows.com/opensrs/resources/docs/ccpayment.pdf

Credit card remittances will be processed within 24 hours.

Refunds
OpenSRS will refund any unused account balance within two weeks of receiving a written
request. We will not refund any portion of your account balance that has been used for domain
registrations, renewals or transfers.

Balance check


                Page 24 of 174 - Release Version 2.56 - support@opensrs.org
Registration Service Providers will be able to check their current balance anytime by clicking on
“Payment Information” in the RWI.

 4.1 Online Credit Card Account Updates

The following section details the requirements and instructions for enabling and using the online
credit card account update system in the RWI.

 4.2 Qualifying for Online Account Updates

In order to qualify for online account updates via the RWI, a Reseller must have made a
minimum of three payments (each of a minimum of $250 US) using some other means. We feel
this is a reasonable barrier of entry that will deter those with more nefarious interests from
abusing our system. (Note, the first payment for Quickstart Resellers remains at $500 US)

Once you have made a minimum of three payments, click on the Online Credit Card Payment
section under Profile Management in the RWI to enable Online Account Updates. You will be
asked to email payments@opensrs.org to enable online credit card account updates; be sure to
include you Reseller username in the email.

 4.3 Cards we accept

We currently accept Visa, Mastercard, and American Express.

 4.4 Minimum/Maximum

A payment made through the online credit card account update system must be at least $250,
and at most $2000. If this maximum amount is not acceptable to you, please contact
payments@opensrs.org to request a higher limit; please be sure to include a brief explanation of
why you need a higher limit.

 4.5 Security checks

OpenSRS has adopted two widely used credit card security measures to protect ourselves against
credit card fraud.

        AVS

AVS is the Address Verification System. We simply check the address included with your payment
against the address that your credit card company has on record. So, be SURE that the
address you provide is the address that your Credit Card is registered to.

        CVV

CVV is a newer standard in credit card security. All credit cards are now issued with three extra
digits appended to the card number on the BACK of the card, that do not show up anywhere
else, except in the credit card companies database.

These three numbers are used to ensure that the person making the purchase has (or has had)
actual possession of the credit card.

The following image shows an example of a CVV number.




              Page 25 of 174 - Release Version 2.56 - support@opensrs.org
**NOTE: American Express cards actually have a 4 digit CVV number, on the front of the card;
the process works the same way.

If you have problems processing an online credit card transaction using the CVV2 number, (or
your card does not have a CVV2 number), please contact payments@opensrs.org.

 4.6 Manual Review

Occasionally our credit card clearinghouse will manually audit a transaction; we have NO control
over when this happens.

When it does, our system will simply reject the transaction and you may try again using another
card, or using some other means of payment.

 4.7 Using the Online Account Update System

The following screenshot shows the basic payment submission page:




To make a payment, simply fill in all the fields with the appropriate information, and press
‘Continue’.

The following screen follows the initial submission screen.




              Page 26 of 174 - Release Version 2.56 - support@opensrs.org
Once you press include valid Credit Card information (including CVV2 number) and press submit,
you will see a screen resembling the following.




NOTE: Only Canadian Resellers are charged GST.

 4.8 Reviewing Payments

You may review your online credit card account updates via the normal Payment Information
Screen in the RWI. Online credit card payments will show as:

RWI Online Credit Card Payment




             Page 27 of 174 - Release Version 2.56 - support@opensrs.org
Also, on your credit card statement, your OpenSRS payments will show as:

Tucows *OpenSRSrspusername.

So, if your username was ‘acme’, this would be:

Tucows *OpenSRSacme

 4.9 Payment Manager

Tucows provides an online tool called the “Payment Manager” that allows you to see important
information about your account balance.




                                                         Figure 3: The Payment Manager screen

Field                           Description
Current Account                 This is the total amount of money contained within your
      Balance                   account, including all amounts allocated for domain transfers
                                and asynchronous registrations
Amount Allocated for            This figure represents the money required to process any
Pending Transfers               transfers that are currently in progress. If the transfer
                                completes successfully, the appropriate amount is fully removed
                                from your account. If the transfer fails, the money is returned
                                to your account.
Amount Allocated for New        This figure represents the money required to process any
Registrations in Progress       asynchronous registrations that are currently in progress. If the
                                registration completes successfully, the appropriate amount is
                                fully removed from your account. If the registration fails, the
                                money is returned to your account.
Available Account Balance       This is the total amount available in your account for new
                                registrations and transfers, and does not include any amounts
                                already allocated for orders in process.


              Page 28 of 174 - Release Version 2.56 - support@opensrs.org
Low Account Balance                When your account balance drops below this threshold, an
Threshold and Notification         email is sent to the address specified, reminding you to add
Email                              more money to your account.

 4.10 Pricing

For pricing information, please review the TLD/service specific sections of this document.

 4.11 Financial Statements

We are able to provide financial statements showing a detailed transaction listing for your
account on a monthly basis. Note that this feature will not be available until after August 2002,
and ONLY will contact transactions dated July 2002 or later.

There is a new link under “Profile Management” labeled Financial Statements

Clicking this link gives you the following interface:




The HELP link provides a description of the options in the interface, and an explanation of the
results. To summarize:

You can select any month (that’s currently available in the system). If you wish to view a web
page you can opt for 10/20/30 transactions per page (more results are available on subsequent
pages). Optionally you can download the entire transactions for a specific month into CVS
format.

 4.11 Financial Statement HTML Results

This page will give you a summary statement and detailed transactions (note the information
here is an example only and may not necessarily reflect the range of transactions you will see):

                               OpenSRS Monthly Statement
     The following statement summarizes your account activity during the Statement Period

                          Statement Date: 27-JUN-2002

                        Statement Period: 01-MAY-2002          -   01-JUN-2002
                          Company Name: Tucows
                                 Username: qateam


                                        Payment Summary

              Opening Balance:           $7791.00
                                                        Opening Hold Balance:    ($8.00)



               Page 29 of 174 - Release Version 2.56 - support@opensrs.org
                    Total Payments:      $300.00
                        Total Taxes:       $0.00
               Total Handling Fees:        $0.00
            Total Domain Purchases: ($1675.50)
               Total Cert Purchases:       $0.00
            Total Domain Renewals:     ($178.00)
            Total Domain Transfers:    ($221.00)
             Total Domain Refunds:        $49.00
                Total Cert Refunds:        $0.00
                              Other:       $0.00
              Closing Balance:          $6073.50
                                                   Total Hold Transactions:         ($4.00)
                                                    Closing Hold Balance:        ($12.00)
             Available Balance:         $6061.50


                                       Transaction Detail


Date   ID      Transaction                    Description                  Debit Credit Closing
                  Type                                                                  Balance
 01-
MAY- 9703 Domain Purchase new tranbill1.com 1 y                             10.00             7781.00
2002
 01-
MAY- 9706 Hold Transaction Return reserve transfer ludatu7.com 1 y                     8.00   7789.00
2002


                             Pages: 1 2 3 4 5 6 7 8 9 10 of 23 >> >|

If you opt to select a CVS file, it will contact the summary information in the first segment, then a
listing (comma separate values) of all the transaction details (Date, ID, Transaction Type,
Description, Debit, Credit, Closing Balance)

  5.0 Rebates/Promotions
For information on any current rebate programs or promotions, please contact your sales
representative. Please make sure you monitor Live Reseller Updates for updates on promotions.

  6.0 gTLD (.com, .net, .org) Registrations




               Page 30 of 174 - Release Version 2.56 - support@opensrs.org
 6.1 Registration Considerations

There are no special requirements for registering gTLDs. Any organization can get as many
available names as they are willing to pay for. Registration in the gTLDs is ‘real-time’; the
OpenSRS system sends commands to the Verisign Registry, which in turn replies immediately
with either confirmation of the requested change, or the appropriate error message. In either
case, the result of the transaction is displayed for the Reseller (or in some cases the end user)
immediately. The exception to this rule is gTLD registrar transfers, which are explained in
sections 6.26-6.33 of this document.

The following screenshot shows the basic domain contact structure; note that information from
any contact can automatically be filled in to any subsequent contact (ie. The administrative
contact can be marked ‘same as Registrant Contact’ etc.) The only exception to this is the
technical contact, which is either entered independently, or inherited from your defaults in the
Resellers Web Interface.

Shot 1: Contact Information




 6.2 Transfers

The gTLDs (.com, .net and .org) are run by Verisign Global Registry. The registry offers service
to the public through Registrars; Tucows/OpenSRS is one such registrar. Resellers are
encouraged to transfer all existing domain names with other registrars to Tucows/OpenSRS to
gain all the benefits of the OpenSRS system. For information on gTLD transfers please refer to in
sections 6.26 to 6.48 of this document.

 6.3 GTLD Qualification

In order to resell gTLDs to your clients, you will need to:

        i)      Read, sign and fax the gTLD Registration Contract to OpenSRS
        ii)     Post the gTLD Registrant Agreement and ICANN UDRP on your site, and clearly
                bind your clients to them
        iii)    Pass either the Quickstart or Full Access RITE test and have money in your
                account




               Page 31 of 174 - Release Version 2.56 - support@opensrs.org
 6.4 Quickstart Considerations

Using the Quickstart interface you can only register or transfer one domain at a time. To
implement more advanced features like bulk order processing and credit card integrations,
consider a Full Access implementation.

 6.5 Renewals

The following sections of this document explain how to manage, monitor and process gTLD
renewals.

 6.6 No refunds for renewals

A renewal transaction is final, and cannot, under any circumstances, be cancelled. Please be sure
that you fully understand this before you attempt any domain renewals. We have no means of
retrieving money from the registry for domain years purchased through renewals, and so we
cannot refund Resellers who renew names in error.

 6.7 gTLD Renewal Flow

The OpenSRS renewal system was built to meet the requirements identified by our Resellers.
Many features are optional, allowing you to use the elements of the renewal system that best
match your business model.

Assuming all the features of the system are enabled, the typical renewal cycle is as follows:

    a) Reminder emails are sent to the registrant 90, 60, 30, 5, 0 days before the domains
       expiry
    b) Reminder emails are sent to the reseller at 60, 30, 1, -40
    c) The registrant either contacts the Reseller and orders a domain renewal, or requests the
       renewal online through the Resellers renewal scripts
    d) Once the domain is renewed, an email confirmation is sent to both the registrant and the
       Reseller

The following diagram represents this process:
                           D ay 90         D ay 60      D ay 30                             D ay 5        D ay 0          D ay -40




                        E m ail           E m ail       E m ail                                          E m ail
   M SP                 R em inder        R em inder    C onfirm ation                                   C onfirm ation


                                      1                                                         2                  3


              E m ail    E m ail          E m ail        E m ail             E m ail        E m ail      E m ail
R egistrant
              R em inder R em inder       R em inder     C onfirm ation      R em inder     R em inder   C onfirm ation

                                            1   N am e R enew s if A uto-R enew set to on
                                            2   N am e R enew ed (date arbitrary for this diagram )

                                            3   N am e D eleted if not renewed by day -40




                 Page 32 of 174 - Release Version 2.56 - support@opensrs.org
 6.8 gTLD Renewals Features Overview

The following sections of this document explain the additions to the OpenSRS client and server to
facilitate gTLD renewals. NOTE: Most features of this system are available on an ‘opt-in’ basis,
allowing Resellers to use our standard renewal automation functionality, or to build their own
automated renewal processes.

The following features are now available to automate gTLD renewals:

a)   Views for 60, 30, 0, Past Due, Deleted Names
b)   Email Reminders for 60, 30, 1, Past Due to Reseller
c)   Email Reminders for 90, 60, 30, 5, 0, Past Due to Registrant
d)   Email Confirmation to Registrants/Resellers to confirm successful domain renewal
e)   Bulk Renewals
f)   Ability to set names for auto-renewal
g)   Ability to set names for NON-renewal




              Page 33 of 174 - Release Version 2.56 - support@opensrs.org
6.9 The Reseller Web Interface and gTLD Renewals

Nearly all renewal functionality can be found a new section of the RWI, entitled ‘Renewal
Management’. The following screenshot shows the new headings:




                                        Renewal Views

Names expiring in the      Shows a list of domains expiring in the next 60-31 days
next 60-31 days
Names expiring in the      Shows a list of domains expiring in the next 30 days
next 30-0 days
Deactivated names          Shows a list of domains that are passed their expiry date, but not yet
(0-40 days past            deleted. Names are deleted if they reach 40 days passed their
expiration date)           renewal date and have not been renewed.
Expired names              Shows a list of expired domains
(deleted)
                                      Renewal Settings

Configure daily MSP        Allows Resellers to enable and configure an email report of names
renewal reminder           coming up for renewal (details below)
email
Configure daily end        Allows Resellers to enable and configure an email reminders to end



              Page 34 of 174 - Release Version 2.56 - support@opensrs.org
user renewal               users for names coming up for renewal (details below)
reminder email
Configure renewal          Allows Resellers to enable and configure email confirmations of
order processing           processed renewals to both the end user and the Reseller. (details
messages                   below)



 6.10 Renewal Functionality from 60, 30, 0 and Passed Due Views


Resellers may renew domains from any of the tables in the renewals section, except Expired
Names. The tables are presented as follows, with all renewal functionality described beneath



    Domain Name          Expiry Date       Set Auto-Renew        Renew       Renewal Term

    narrator3.net    2000-12-15 16:08:10          d
                                                  e
                                                  f
                                                  g
                                                  c               d
                                                                  e
                                                                  f
                                                                  g
                                                                  c            1 year


    narrator3.com    2001-01-02 16:07:46          c
                                                  d
                                                  e
                                                  f
                                                  g               e
                                                                  f
                                                                  g
                                                                  c
                                                                  d            1 year


                                              [Select All]    [Select All]     [Submit]

Table Headers:

    a) Domain name
       The domain name that is due for renewal
    b) Expiry Date
       The expiry date of the domain up for renewal
    c) Set Auto-Renew
       Check this box to set the domain to ‘auto-renew’ when the ‘Submit’ button is pressed
    d) Renew
       Check this box to renew the corresponding domain name when the ‘Submit’ button is
       pressed
    e) Select All/Deselect All Button(s)
       These buttons either place or remove checkmarks for all domains viewable on the page,
       allowing Resellers to set Auto-Renew flags or Renew domains in bulk.

 6.11 Individual gTLD Renewals

Domain names can be renewed individually using the tabled views described above. Resellers can
also click on the domain name in question from the tabled renewal views (or the View Active
Domains table) and renew the domain using a renewal feature found towards the bottom of the
screen.

 6.12 Bulk gTLD Renewals

Bulk renewals are possible through the Resellers Web Interface using the Bulk Renew Names link
under Renewal Management. Simply enter a list of names in the text box provided, and press the
submit button. You may also set the ‘autorenew’ flag to on while processing renewals in this
manner.




              Page 35 of 174 - Release Version 2.56 - support@opensrs.org
After submitting your Bulk Renewals, you will see, your screen will look similar to the following:




Every successful renewal has a “green/success” status. If the domain appears in the list twice, it
is skipped and given a “yellow/skipped” status. Any failures will give a “red/failed” status.
Possible reasons for failures include (but are not limited to):




              Page 36 of 174 - Release Version 2.56 - support@opensrs.org
    1. Domain is not in your reseller account, or at OpenSRS
    2. Previous renewal order for domain had failed (contact Support)
    3. Insufficient funds

All errors are identical to errors shown for singular renewals.

6.13 Setting gTLDs to auto-renew

The auto-renew feature is an excellent safety net for domains that absolutely must not be
allowed to expire. Any name with the auto-renew flag enabled will renew for one year once it
reaches 30 days prior to its expiry date.

Names can be set for auto-renewal any of the following ways:

    a) by the Reseller or Registrant during registration (client or RWI)
    b) by the Reseller after clicking on the domain name from either the View Active Domains
       view or one of the renewal views
    c) by the Reseller from one of the renewals views
    d) from the Bulk Renewal Tool in the RWI, while processing renewals
    e) they can optionally allow this in manage as well

Generally, domain renewal becomes an issue once a domain name is approaching its expiry date;
however, one new feature that should be considered upon registration or transfer is the ‘auto-
renew’ feature. The registrant (or the Reseller) may now opt to put a name on Auto-renew.

All names with the Auto-Renew feature enabled will be automatically renewed 30 days before the
domain would have otherwise expired.

Names put on Auto-Renew within 30 (meaning, between day 30 and the expiry date) days of
expiry, will renew that day, or the next. (depending on whether they are set to autorenew before
or after 10:00 PM on the day in question). This time may be subject to change; at time of
writing, the process ran at 10:00 PM daily.

Note: Resellers must be sure to maintain an account balance capable of sustaining auto-
renewals; an auto-renewal transaction will not succeed if there are not sufficient funds in your
Reseller account balance.

 6.14 Ability to set gTLDs for NON-renewal

Names can only be set for ‘non-renewal’ individually, while looking at the domain record linked
from the View Active Domains view or one of the renewals views. NOTE: A domain set for
non-renewal will be deleted 40 days after the domains expiration date. A domain can
be taken off ‘non-renewal’ status by clicking on the domain name from the View Active Domains
or Renewals tables, and selecting either:

        a) Normal Notification
        b) Auto-Renew

This feature is useful if you know that your client is not interested in renewing a domain name,
and you want to prevent the system from including them in any automated emails sent to your
clients.




              Page 37 of 174 - Release Version 2.56 - support@opensrs.org
 6.15 gTLD renewals without sufficient funds

If you attempt to process a domain renewal, or a domain that is set to auto-renew reaches the
30 day mark and renews, but you don’t have sufficient funds in your account to complete the
transaction, the transaction will fail.

If you are using the RWI renewal functionality, an appropriate error message will appear on the
screen. If the renew request comes through the client or as the result of the auto-renew flag, an
error message is displayed to the end user, and the following email is sent to the Technical
Contact email address that we have on file for you to remind you to add money to your account:

                An order has been submitted (ORDER #) through the client scripts which cannot
                be processed due to insufficient funds. Your current account balance is
                ACCOUNT_BALANCE. Orders submitted from this point forward may not be
                processed and no further warnings will be sent for 24 hours. For payment
                remittance information please see:

                http://resellers.tucows.com/opensrs/payment/

                For payment related inquiries, please contact payments@opensrs.org

                If you have any questions about this order please contact support@opensrs.org.

Note: This is the only circumstance where a renewal order error will send an email to the
Reseller.

 6.16 gTLD Script/Client Considerations for renewals

Renewals are mostly handled on the server-side of the OpenSRS system; however, there is a
new feature in the client code that extends renewal functionality to the end user through the
scripts. Resellers must enable this feature in the opensrs.conf file; once done, an end user can
visit a URL and request a domain name renewal. NOTE: It is important that you build some kind
of payment processing into your scripts if you enable this feature. For full instructions on
configuring this option, please refer to the OpenSRS PERL Client Manual Version or the OpenSRS
Protocol Specification.

 6.17 gTLD Renewal Messaging

The following section explains how Resellers can configure the various messages that are
involved in the renewal process. These include both renewal reminders and confirmations to both
Resellers and registrants.

6.18 Reseller Renewal Reminders

Resellers may configure the OpenSRS renewal system to send out email reports of names coming
up for renewal. These options can be configured in the Renewal section of the RWI, under
‘Configure daily RSP renewal reminder email’.

The following annotated tables are representations of the RWI; please review them to
understand how this feature can be configured.


        Configuration Options



              Page 38 of 174 - Release Version 2.56 - support@opensrs.org
        a) Configure daily MSP renewal reminder email

             Use this section to enable/disable renewal email reminders to yourself

             Your options here are:

              Send upcoming renewal report email        k
                                                        l
                                                        m
                                                        n Choose this setting if you want to
                                                        j
              messages to yourself daily, even if there
              are no domains expiring within the next receive renewal reminders, even if there
              60 days?                                  are no domains set to expire in the
                                                        following 60 days
              Send upcoming renewal report email              m
                                                              l
                                                              i
                                                              j
                                                              k
                                                              n
              messages to yourself daily, only if there            Choose this setting if you want to
              are domains expiring within the next 60         receive renewal reminders only if there are
              days.                                           domains set to expire in the following 60
                                                              days
              Never send upcoming renewal report              k
                                                              l
                                                              m
                                                              n
                                                              j
              email messages to yourself.                           Choose this setting if you do not want
                                                              to receive renewal reminders




The email reminder message will tell Resellers:

        a)   Status of Daily MSP Reminder Messages (on/off)
        b)   Status of Daily Registrant Reminder Messages (on/off)
        c)   Names to be deleted (> 40 days overdue) on that day
        d)   Names to be deactivated (0 days) on that day
        e)   Names expiring in 60 and 30 days
        f)   Names Auto-renewed on that day

An example of this type of message follows:

        From: support@opensrs.org
        Reply-to: support@opensrs.org
        Subject: OpenSRS Automated Daily Renewal Reminder for 2000-11-06

        <CUSTOMIZABLE INTRODUCTORY TEXT BY ADMINISTRATOR>

        Your renewal reminder messages to end-user are disabled. Please ensure that you
        inform the end-user that their domain is up for renewal

        The following domains were not renewed and have been deleted today:

        Domain Name, Expiry Date, Billing Contact, Owner Contact, Tech Contact, Admin
        Contact
        <DOMAIN>,<EXPIRY_DATE>,<BILLING>,<OWNER>,<TECH>,<ADMIN>
        <DOMAIN>,<EXPIRY_DATE>,<BILLING>,<OWNER>,<TECH>,<ADMIN>
        …
        <DOMAIN>,<EXPIRY_DATE>,<BILLING>,<OWNER>,<TECH>,<ADMIN>


        The following names have been deactivated today and will be deleted in 40 days.

        Domain Name, Expiry Date, Billing Contact, Owner Contact, Tech Contact, Admin
        Contact
        <DOMAIN>,<EXPIRY_DATE>,<BILLING>,<OWNER>,<TECH>,<ADMIN>
        <DOMAIN>,<EXPIRY_DATE>,<BILLING>,<OWNER>,<TECH>,<ADMIN>
        …




               Page 39 of 174 - Release Version 2.56 - support@opensrs.org
        <DOMAIN>,<EXPIRY_DATE>,<BILLING>,<OWNER>,<TECH>,<ADMIN>


        The following names will expire in 30 days:

        Domain Name, Expiry Date, Billing Contact, Owner Contact, Tech Contact, Admin
        Contact
        <DOMAIN>,<EXPIRY_DATE>,<BILLING>,<OWNER>,<TECH>,<ADMIN>
        <DOMAIN>,<EXPIRY_DATE>,<BILLING>,<OWNER>,<TECH>,<ADMIN>
        …
        <DOMAIN>,<EXPIRY_DATE>,<BILLING>,<OWNER>,<TECH>,<ADMIN>


        The following names will expire in 60 days:

        Domain Name, Expiry Date, Billing Contact, Owner Contact, Tech Contact, Admin
        Contact
        <DOMAIN>,<EXPIRY_DATE>,<BILLING>,<OWNER>,<TECH>,<ADMIN>
        <DOMAIN>,<EXPIRY_DATE>,<BILLING>,<OWNER>,<TECH>,<ADMIN>
        …
        <DOMAIN>,<EXPIRY_DATE>,<BILLING>,<OWNER>,<TECH>,<ADMIN>


        The following names are set to 30 day auto-renewal in 60 days:

        Domain Name, Expiry Date, Billing Contact, Owner Contact, Tech Contact, Admin
        Contact
        <DOMAIN>,<EXPIRY_DATE>,<BILLING>,<OWNER>,<TECH>,<ADMIN>
        <DOMAIN>,<EXPIRY_DATE>,<BILLING>,<OWNER>,<TECH>,<ADMIN>
        …
        <DOMAIN>,<EXPIRY_DATE>,<BILLING>,<OWNER>,<TECH>,<ADMIN>



 6.19 Registrant renewal reminders

You can configure the OpenSRS renewal system to send customized messages to your clients
once their names approach their expiration date. The Reseller sets the message body and the
From and Reply–To addresses. Configure these options in the Renewals section of the RWI,
under ‘Configure daily end user renewal reminder email’.

The following annotated tables are representations of the RWI; please review them to
understand how this feature can be configured.

Configure daily end user renewal reminder email

Use this section to enable/disable renewal email reminders to the registrant.

Your options here are:


                                    Configure End-User Messages
                                            c
                                            d
                                            e
                                            f
                                            g 90 Day
                                            b
            Optional messages to be sent to
            end-users at domain renewal     c
                                            d
                                            e
                                            f
                                            g 60 Day
                                            b
            thresholds
            (ie, 60 and 30 days before      d
                                            e
                                            f
                                            g 30 Day
                                            c
                                            b
            domain expiry)
                                            c
                                            d
                                            e
                                            f
                                            g 10 Days After Expiry
                                            b

                                             90 Day Message Customization
                                   From Address:     renew als@opensrs.org




              Page 40 of 174 - Release Version 2.56 - support@opensrs.org
             From Display Name:      Tucow s Inc.

              Reply-To Address:      renew als@opensrs.org

         Reply-To Display Name:

                        Subject:     90 day renew al reminder

                                       Message Body:
                     The follow ing names are set to expire in 90 days -
                     probably a good idea to renew them - reply to this
                     message if that is w hat you like to do.

                     Ola -



                    Preview the 90 Day Renewal Reminder Message
                         Reset this message to default content
                             60 Day Message Customization
                  From Address:      renew als@opensrs.org


             From Display Name:      Tucow s Inc.

              Reply-To Address:      renew als@opensrs.org


         Reply-To Display Name:

                        Subject:     Automated 60 day renew al reminder

                                       Message Body:




Page 41 of 174 - Release Version 2.56 - support@opensrs.org
                     The follow ing names are set to expire in 60 days -
                     probably a good idea to renew them - reply to this
                     message if that is w hat you like to do.

                     Ola -




                    Preview the 60 Day Renewal Reminder Message
                         Reset this message to default content
                             30 Day Message Customization
                  From Address:      renew als@opensrs.org

             From Display Name:      Tucow s Inc.


              Reply-To Address:      renew als@opensrs.org

         Reply-To Display Name:

                        Subject:     Automated 30 day renew al reminder

                                       Message Body:




Page 42 of 174 - Release Version 2.56 - support@opensrs.org
                     The follow ing names are set to expire in 30 days -
                     probably a good idea to renew them - reply to this
                     message if that is w hat you like to do.

                     Ola -




                    Preview the 30 Day Renewal Reminder Message
                         Reset this message to default content
                             5 Day Message Customization
                  From Address:      renew als@opensrs.org

             From Display Name:      Tucow s Inc.


              Reply-To Address:      renew als@opensrs.org

         Reply-To Display Name:

                        Subject:     Automated 5 day deactivation notice

                                       Message Body:




Page 43 of 174 - Release Version 2.56 - support@opensrs.org
                     The follow ing names are set to expire in 5 days - probab
                     a good idea to renew them - reply to this message if tha
                     is w hat you like to do.

                     Ola -




                     Preview the 5 Day Renewal Reminder Message
                         Reset this message to default content
                   10 Days After Expiry Message Customization
                  From Address:      renew als@opensrs.org

             From Display Name:      Tucow s Inc.


              Reply-To Address:      renew als@opensrs.org

         Reply-To Display Name:

                        Subject:     Automated -10 day renew al reminde

                                       Message Body:




Page 44 of 174 - Release Version 2.56 - support@opensrs.org
                                      The follow ing expired names are set to be deleted in 20
                                      days - probably a good idea to renew them - reply to this
                                      message if that is w hat you like to do.

                                      Ola -




                                Preview the 10 Days After Expiry Renewal Reminder Message
                                           Reset this message to default content

                                                  Save Changes      Reset Values




 6.20 Reseller Renewal Confirmation

Resellers may also set the renewal system to automatically email them when domains are
renewed. This feature can be enabled and configured in the Renewals section of the RWI, under
‘Configure renewal order processing messages’.

       The following annotated tables are representations the RWI; please review them to
       understand how this feature can be configured.

       Your options here are:


                                          Confirmation Message to MSP
                                                     Preview
         Send renewal confirmation messages to                  b
                                                                c
                                                                d
                                                                e
                                                                f
                                                                g
         MSP?


             Page 45 of 174 - Release Version 2.56 - support@opensrs.org
          MSP?
                                             From Address:

                                      From Display Name:

                                        Reply-To Address:

                                   Reply-To Display Name:

                                                     Subject:     Renew al Order Processed:

                                                     Message Body:
                                    This message is to confirm the successful renew al of
                                    {{domain_name}} for {{period}} year(s).
                                    The new expiration date is {{expiredate}}.

                                    To change the options for this message, or stop
                                    receiving this message go to
                                    the Renew als section of the Reseller Web Interface
                                    (RWI) at
                                    http://resellers.opensrs.net .




 6.21 Registrant Renewal Confirmation

 Reseller can configure the renewal system to email confirmation of a domain renewal to the
 registrant once the domain has been renewed. This feature can be enabled and configured in the
 Renewals section of the RWI, under ‘Configure renewal order processing messages’.

 The following annotated tables are representations the RWI; please review them to understand
 how this feature can be configured.


                            Confirmation Message to End Users
                                         Preview
Send renewal confirmation messages to              b
                                                   c
                                                   d
                                                   e
                                                   f
                                                   g
end users?
                                 From Address:       renew als@opensrs.org




              Page 46 of 174 - Release Version 2.56 - support@opensrs.org
                             From Display Name:          Tucow s Inc.

                               Reply-To Address:

                        Reply-To Display Name:

                                           Subject:      Renew al Order Processed:

                                           Message Body:
                          This message is to confirm the successful renew al of
                          {{domain_name}} for {{period}} year(s).
                          The new expiration date is {{expiredate}}.




                                      Save Changes      Reset Values




 6.22 Bounced renewal messages

If the renewals system sends an email to an invalid administrative contact email address, the
bounced message is collected by OpenSRS and sent to the technical contact email address
configured in the RWI. Resellers can then act on these bounced messages to ensure that their
clients are aware that their domain is coming up for renewal.

 6.23 The Manage Domain Interface and gTLD Renewals

When a registrant logs in to the Manage Domain they will be informed whether any of the names
in their OpenSRS profile are due to expire within 60 days. The notice will appear at the top of the
screen. Further, the manage.cgi can be configured to allow you to offer renewals to your
customers directly through your Manage Domain interface. For more information on how to do
this, please consult the latest version of our Perl Client Manual and/or API Guide.

 6.24 gTLD Renewal Pricing

Renewals cost the same as new gTLD domain registrations; $10 USD per domain year.

 6.25 Transfer of ownership

To transfer the ownership of a gTLD, advise your registrants to use the basic ‘change profile’
functionality of the Manage Domain interface. This will allow them to assign a new username and
password to the domain, which the new owner can use to update contact information as desired.

 6.26 Name Transfers for gTLDs (.com, .net, .org)

This section describes the process for transferring .com, .net and .org domain names from
another registrar to OpenSRS AND between Tucows resellers.

 6.27 Why Transfer Domains?

Domain transfers represent a significant revenue opportunity for OpenSRS Resellers. We see the
over 18 million .com/.net/.org domain names already registered worldwide as a lucrative market.
Each of those domains are costing their owners $35 USD per year, and we see domain transfers
as an opportunity for our resellers to provide a captive market with better service at a better
price.



              Page 47 of 174 - Release Version 2.56 - support@opensrs.org
 6.28 Transfer Overview: Transfers To Tucows

With this type of transfer, a domain is being moved to an OpenSRS Reseller and away from
another Registrar. In this scenario, the End User requests the change and the Gaining Reseller
initiates the transfer. In terms of initiating the process, Resellers simply initiate a standard
transfer; the OpenSRS system determines whether to deal with it as a registrar or reseller
transfer.

The system confirms that all the preconditions have been met – if not, the appropriate “Transfer
Failed” error message is sent, and the domain notes are updated with an explanation of why the
transfer failed.

If all the preconditions are met, the system places the necessary funds on hold and sends the
domain’s admin contact an e-mail directing them to a Web page, where they can approve or
decline the transfer.

Upon approval, the transfer is processed:
   • the locked funds are released
   • the account is adjusted
   • the domain is “moved”
   • the WHOIS info is updated
   • the system (optionally) notifies all parties involved that the transfer was successful

If the admin contact declines the transfer, the system will cancel the transaction:
     • the locked funds are released
     • the domain notes are updated
     • all involved parties are (optionally) notified that the transfer was not successful

In general, transfers from other registrars to OpenSRS will continue to work as they have in the
past, with the following enhancements:

    a) Option for the Reseller to receive email when an Admin Contact either accepts or rejects
       a transfer to you
    b) Option for the Reseller to receive email when a transfer times out after 7 days
    c) Customizable headers on the Transfer Confirmation Email
    d) Option to send email to Domain Admin Contact once they have confirmed/rejected the
       transfer request

These changes are fully explained in the section on RSP and End-User messaging.




              Page 48 of 174 - Release Version 2.56 - support@opensrs.org
The following diagram represents this process:


                                                Transfser Ordered
      Other Registrar to Tucows                   via RCL/RWI




                                                                                    Process from
                                                Process Orders
                                                                           No       View Pending
                                                 Immediately
                                                                                    (no time limit)
                   Status: Awaiting Owner
                          Approval                                     Yes
                                                      Yes

                                                 Email to Admin
                                                    Contact
                                                Money put on hold

                                                                                                                          Optional
                                                                                                            Admin rejects
                                                     Admin                                                                email to
                                                                                                              transfer.
              Status: Pending                      approves           No        Ignores email         No                  RSP
                                                                                                                Order
             OpenSRS Review                         transfer                                                 Cancelled
                                                                                                           Money returned
                                                                                     Yes


                                                      Yes                    7 Day order timout Optional email to
                                                                              Order Cancelled RSP
                                                                              Money returned



                            Optional email to        Order                   OpenSRS cancels
                            RSP/Admin             Acceptable to       No          order
                            Contact                OpenSRS                    Money returned


                       Status: Pending                Yes
                       Registry Review
                                                 Request sent to
                                                    Registry


                                                                                OpenSRS cancels
                                                     Current
                                                                                      order
                                                    Registrar
                                                                      No         Money returned
                                                    Accepts
                                                                                Error logged with
                                                     request
                                                                                 Transfer order

                                                      Yes

                                                Order Completed     Optional
                                                  Money taken       email to
                                                 Year added to      Admin
                                                    domain          contact




 6.29 Transfer Overview: Transfers away from Tucows

With this type of transfer, a domain is being moved to another Registrar from a Tucows Reseller.
In this scenario, the End User requests the change and the Gaining Registrar initiates the transfer
on their behalf.

The Losing Reseller is notified that the transfer request has been received, and the system will
send the domain’s admin contact an e-mail directing them to a Web page, where they can
approve or decline the transfer.

Upon approval, the transfer is processed:


               Page 49 of 174 - Release Version 2.56 - support@opensrs.org
    •   the registry is informed of the change
    •   all involved parties are notified that the transfer was successful
    •   the domain is “moved”
    •   the WHOIS info is updated
    •   the domain is marked “deleted-transferred” in the Losing Reseller’s database

If the admin contact declines the transfer, the system will cancel the transaction:
     • acknowledgement of the refusal is shown on the web page
     • the domain notes are updated
     • all involved parties are notified that the transfer was declined

If after five days there is no response from the admin contact, Tucows will monitor the domain at
the Registry level until the either the request times out, or the Registry updates their database
with new Registrar information. Once that happens, the domain is marked “deleted-transferred”
in the OpenSRS database.

Many new features were built to facilitate clean transfers away from Tucows. Certainly nobody
wants to lose business, but in cases were loss is unavoidable, it is in everyone’s best interest to
deal with it cleanly. We offer the following enhancements to this end:

    a) Resellers optionally receive email messages when Tucows receives a "transfer-away"
       request
    b) Resellers receive email messages when a Domain Admin Contact either accepts or rejects
       a "transfer-away" request
    c) email sent to the domain admin contact to confirm a transfer away request
    d) Option to send email to the domain admin contact when he/she either accepts or rejects
       a transfer away from your profile
    e) Domains flagged as ‘Deleted’ once they are truly transferred to another registrar




              Page 50 of 174 - Release Version 2.56 - support@opensrs.org
The following diagram represents this process:

          Tucows to Other Registrar



                                      Tucows/OpenSRS
                                      recevies Registry Optional email
                                         request for    to Reseller
                                          Trasnsfer


                                        Email sent to
                                      Admin Contact to
                                       confirm transfer
                                             away
            Status: Awaiting Owner
                   Approval                                                                Admin rejects   Optional
                                                                                              transfer.    email to
                                           Admin                                                           RSP/
                                                                                           Tucows sends
                                         approves          No     Ignores email       No                   Admin
                                                                                                NACK
                                          transfer                                          command to     contact
                                                                                               registry
                                             Yes                         Yes



                                                                     Registry
                                        OpenSRS sends
                                                                 completes transfer
                                        ACK to Registry
                                                                       away



                                                                 OpenSRS marks
                                                                    domain as
                                                                     'Deleted
                                                                   Transferred'



 6.30 Transfer Overview: Transfers between Tucows Resellers

With this type of transfer the Registrar of record does not change, as both the Losing Reseller
and the Gaining Reseller are part of the OpenSRS system. In this scenario, the End User notifies
the Gaining Reseller, who initiates the transfer. In terms of initiating the process, Resellers simply
initiate a standard transfer; the OpenSRS system determines whether to deal with it as a
registrar or reseller transfer.

When the transfer order is placed, the system places the necessary funds on-hold and sends the
domain’s admin contact an e-mail directing them to a Web page, where they can approve or
decline the transfer.

Upon approval, the transfer is processed:
   • the locked funds are released
   • the account is adjusted
   • the domain is “moved”
   • the domain is marked “deleted-transferred” in the Losing Reseller’s database
   • the system notifies all parties involved that the transfer was successful
   • the domain is renewed when the next renewal cron job runs (currently, 4:00
       AM Daily)

If the admin contact declines the transfer, the system will cancel the transaction:
     • the locked funds are released
     • all involved parties are optionally notified that the transfer was not successful


              Page 51 of 174 - Release Version 2.56 - support@opensrs.org
If after seven days there is no response from the admin contact, the transfer will fail and the
system will follow the same steps taken for a declined transfer.

NOTE: Currently, only gTLD Reseller to Reseller transfers are automated; to transfer any other
type of domain from one Tucows Reseller to another, please use the older process described at:

http://resellers.tucows.com/opensrs/faq/support_faq#Live_reseller_domain_move

Rules for Reseller to Reseller transfers

1. In order to transfer a gTLD between OpenSRS reseller profiles, the name must have resided
with the Losing Reseller for at least 60 days. While the Losing Reseller has no power to block the
transfer away, we feel it is imperative that all Reseller have sufficient opportunity to secure
payment for services rendered.

2. Reseller to Reseller transfers add one year to the domains registration; therefore, Resellers
must have a sufficient balance for the renewal in order to complete the transfer request.

3. Names which are expired, but not deleted (so, up to 40 days passed the expiry date) can be
transferred between different Tucows Resellers.




              Page 52 of 174 - Release Version 2.56 - support@opensrs.org
The following diagram represents this process:


 Reseller to Reseller Transfers
                                           Reseller Submits
                                          Reseller to Reseller
                                        transfer order through
                                              RWI/RCL.




                                                                            Process from
                                           Process Orders
                                                                  No        View Pending
                                            Immediately
                                                                            (no time limit)

                                                                 Yes
                                                 Yes


                                            Money put on
                                               hold




                                         Email is sent from
                                        Gaining RSP profileto     Notification email is
                                         Admin Contact for         optionally sent to
                                              approval              Losing Reseller
                                            (Mandetory)




                                           Admin Contact                               Order Fails.
                                                                       No       Both RSPs and Registrant
                                             Approves
                                                                                  optionally messaged.
                                                                                Money returned to Gaining
                                                                                   Reseller's account
         Order Status:                           Yes
          Completed
                                         Order Completes
                                                                               Order Status:
                                       Admin contact and both
                                                                                Cancelled
                                          RSPs optionally
                                            messaged.
                                      Money taken from Gaining
                                         Reseller's Account


 6.31 Domain Transfer Process: Other Registrar to Tucows

Before attempting a Domain Transfer

Because domain transfers require a high degree of coordination between many parties, the
process will take longer than a domain registration. We recommend that you read and
understand this document thoroughly before attempting a transfer; if you have any questions,
please direct them to support@opensrs.org.

When you are ready to start transferring, you should be completely familiar with the steps, as
confusion or a mistake during a live transfer could cause problems. Consider transferring one or


              Page 53 of 174 - Release Version 2.56 - support@opensrs.org
more of your own domains to OpenSRS before offering transfers to your customers so that you
are completely familiar with the system.

Domain Transfers in the Test Environment (Horizon)
It is not currently possible to simulate the transfer of a domain name to OpenSRS using the test
system. Note that you can place transfer orders, but since the test system only contains test
domains (and test contact information) this is not an adequate representation of the full transfer
process.

Parties and Definitions

End-User: party that is requesting the transfer to OpenSRS

Gaining Reseller: the Tucows reseller that is sponsoring the transfer

Losing Reseller: the Tucows reseller that losing the domain in question

Administrative Contact: the current administrative contact of the domain name

Current Registrar: the current ICANN accredited registrar under whom the name is registered
Reseller Web Interface (RWI): the tool provided by OpenSRS for Reseller to manage their clients’
domain registrations and transfers

Preconditions
In order for a Domain Transfer to be successful the following pre-conditions must be met:

    -   the domain name must have been registered for more than 60 days
    -   the current admin contact’s email address must able to confirm the transfer request
    -   the domain must not be “On-Hold” by the current registrar. This condition can exist for
        many reasons, including lack of payment or domain expiry
    -   the “Gaining Reseller’ must have a positive account balance (enough money paid to
        sponsor the transfer)

Note: The a domains’ nameserver cannot be changed during a registrar transfer;
advise your clients that the nameservers will remain the same during the transfer,
and they can be changed once the domain has reached the OpenSRS system.

Domain Transfers: Step by Step

Step 1 End User Requests Transfer

The end-user chooses to have their domain transferred to an OpenSRS Reseller and submits a
request using the OpenSRS Reseller’s online forms.

As part of submitting the request, the End-User either uses an existing OpenSRS profile, or
creates a new profile; if and when the transfer successfully completes, the name will be inserted
into this profile.

If the Reseller has “process orders immediately” set (in the RWI), then once the End-User’s
request is submitted, the request will immediately go to step three.

At this point, the appropriate amount ($10.00 US) from the Reseller’s account balance is placed
“on hold” until the transfer process is completed or cancelled at any later step.



              Page 54 of 174 - Release Version 2.56 - support@opensrs.org
If the Reseller does not have “process orders immediately” set (in the RWI) then once the End-
User’s request is submitted, it will immediately appear in the “View Pending Orders” section of
the RWI
If the Reseller has configured messages to be sent to him upon order placement, these messages
will sent once the End-User submits his order (regardless of whether “process orders
immediately” is set).

If the Reseller has configured messages to be sent to the End-User and “process orders
immediately” is set, this message will be sent when the End-User submits his order.

Step 2 - Reseller Processing or Review

The OpenSRS Reseller will only have to perform this step if “process orders immediately” is not
selected in the RWI.

The Reseller will review the transfer request in the ‘View Pending Orders’ section of the RWI, and
will either accept or cancel it.

If the Reseller accepts, the transfer continues to the next step, and the appropriate amount
($10.00 US) of the Reseller’s account balance is placed “on hold” until the transfer process is
completed or cancelled at any later step.

If the Reseller refuses the transfer, the transfer is cancelled and there is no notification sent out.

Note: Orders can stay in this state indefinitely; the request simply remains in queue until
approved or cancelled by the Reseller.

Once the domain transfer is approved at this stage, the Reseller can check on the transfer status
at any time via the ‘View Transfers in Progress’ in the Reseller Web Interface.

Step 3 – Current Admin Contact Confirms Request
Once the Reseller approves the transfer request, the current domain Admin Contact will receive
an e-mail containing a link that includes a key to the customizable OpenSRS Transfer Approval
Web Page; this email is parsed from the existing WHOIS information for that domain.

NOTE: if the OpenSRS system is unable to pull Admin Contact information from the current
Registrar WHOIS server, OpenSRS staff will review the transfer request manually. If we are able
to find current Admin contact information, we will send notification to that email address; if we
are not able to find current Admin contact information, the transfer request will be cancelled and
the Reseller will be notified of the problem.

The Admin Contact either:
   - Acknowledges the request; and the request moves on to the next step
           o For Reseller to Reseller transfers, the process ends here. Any money on hold is
               taken from the GRSPs account, and the domain is moved into the new Reseller’s
               profile.
   - Refuses the request; in this case the Reseller’s on hold credit is returned to their account
       balance and the Reseller is notified
   - Does not respond to the email (for whatever reason) for 7 days, and the transfer is
       automatically cancelled; in this case the Reseller’s on hold credit is returned to their
       account balance and the Reseller is notified




               Page 55 of 174 - Release Version 2.56 - support@opensrs.org
Step 4 - OpenSRS Review
Once approved by the Admin Contact, the transfer request is queued to the OpenSRS Admin
Review area for review. This process will take OpenSRS approximately 24-48 hours, but has no
time limit.

If the transfer is acceptable, OpenSRS admin approves it, and a request is submitted to the
current Registrar for the domain in question.

If the transfer is unacceptable, OpenSRS admin cancels it, and the Reseller will receive a Transfer
failure notification with a reason for the cancellation.

Step 5 - Registrar Review
The Current Registrar has five (5) days to either approve or decline the request. It is important to
note that should the current registrar take no action the request will be automatically approved
after the fifth day. However, if the current registrar declines the request, we must wait nine (9)
days before officially canceling the transfer.

If the current registrar approves the request (or the fifth day passes with no cancellation), the
registrar information in the root server is updated to reflect an OpenSRS hosted domain and the
order status is updated in the RWI.

In this event, the on hold credit is permanently deducted from the Reseller’s account.

If the registrar declines the request any time within the 5 day period, the order status is updated
once 9 days have passed.

In this event, the Reseller’s on hold credit is returned to their account balance.

The 9 day wait for a cancellation notice is a limitation of the current communications systems
between various registrars. While OpenSRS is supposed to be notified immediately if the losing
registrar declines a transfer, this is not always the case. If we are not notified of a cancellation,
we cannot be sure that the lack of response indicates a successful transfer (after five days
without answer) or a miscommunication. If we haven’t received notification of the cancellation
from the losing registrar, but they actually had cancelled the domain, then we risk notifying the
Reseller that the transfer was approved, when in fact it wasn’t. So, we wait the full nine days
(the registry has never taken longer than 9 days to process an actual approved transfer) before
informing the Reseller that the transfer was cancelled.

 6.32 Quick Start Transfers

The main difference between Quick Start and Full Access Transfers occurs at Step One. This
difference stems from the fact that a Quick Start Reseller does not have a fully integrated
Website that will allow their End-Users to request the transfer information in an automated
fashion. In most cases an RESELLER will manually take the information from their End-User and
manually input the request themselves via the RWI.

 6.33 Checking the Status of Domain Transfers

Once the Reseller has approved the initial request for transfer from an end user, they can use the
RWI or an API command to check the status of the transfer.

Using the RWI




               Page 56 of 174 - Release Version 2.56 - support@opensrs.org
The ‘View Transfers in Process’ link from the RWI presents a view of all transfers in process for a
particular Reseller, each with one of the following status messages:

Using the API

Resellers can now also query the status of a transfer order using a client-side command. This will
be useful for Reseller’s who handle all OpenSRS transactions through a secondary system, as it
can report on the status of a transfer order and log the result in the Resellers proprietary
database.

For complete details on how to use this feature, please consult the OpenSRS Protocol Spec
Version

Status Messages

Pending Owner Approval
At this point, the admin contact for the domain name in question has been contacted, but has
not yet approved the transfer via the online form.

Pending Registry Approval
Here we have submitted the request to the current Registrar, and we are waiting for them to
approve it so that the Registry can make the change to the WHOIS information.

Waiting for OpenSRS Review
This status is used when (for whatever reason) the domain requires manual review by OpenSRS
staff.

Completed
Once a transfer is complete, and the domain is now on the OpenSRS system, it’s status is
completed.

Cancelled
If the domain transfer is cancelled by anyone (Current Domain Admin, OpenSRS, Reseller,
Current Registrar) during the transfer process, the status will show as cancelled in the RWI.

 6.34 Searching Transfers

You may at some point want to review all completed transfers, or all cancelled transfers; to do
this, simply follow the ‘Search Reg System Orders’ link in the RWI. You can then use the search
features to search for all transfers by status.

 6.35 Customizing the Transfer Approval Web Page

The Transfer Approval Web page is where the current Admin Contact for the domain is directed
to approve the domain’s transfer to the OpenSRS system. There is a default message on this
page, instructing the Admin contact on how to proceed. Resellers can also customize this page
with a further message and a logo, if they so desire.

To customize the Transfer Approval Web Page, click on the ‘Customize Transfer Page’ link in the
Transfer Management section of the RWI (Reseller Web Interface) for the Live System
(http://resellers.opensrs.net/)

Note: It is also possible to provide your own URL to accept transfer confirmations at;
however, this is a complex feature requiring development by the Reseller. For



              Page 57 of 174 - Release Version 2.56 - support@opensrs.org
complete details, please refer to the latest version of the OpenSRS Protocol
Specification.

 6.36 Setting your Transfer Messaging email address

Many of the transfer notification features are delivered to Resellers via email to a specified
address. By default, this address is your Technical Contact address as specified in the Reseller
Web Interface.

However, you can change this so that all Transfer Notification emails for Resellers are routed to a
custom address of your choosing. To set this address, please visit the Reseller Contact
Information in the RWI. You can also use this section to specify an email address to receive
bounced transfer messages sent to your clients.

Also note the ‘End User Transfers Bounce-Forwarding E-Mail Address’; use this feature to
capture transfer messages that our system sends to your clients at bad email addresses. This will
help you identify situations where the administrative contact for a given domain needs to be
updated before a transfer will succeed.

 6.37 Canceling Transfers

Resellers can now cancel Transfer Orders to their profile that are Pending Owner Approval.
Simply find the domain from your View Orders In Progress table in the RWI, click on it, and scroll
down to the bottom to find the Cancel button. These feature works for both Registrar and
Reseller transfers

 6.38 Resubmitting failed transfer orders

Resellers can resubmit transfer orders that failed due to:
   a) timeout waiting for admin approval
   b) declined by the losing registrar
   c) order cancelled by reseller awaiting admin approval

The feature will not work to resubmit orders that were cancelled by the administrative contact,
since, in general, the administrative contact can be said to not want to transfer the name if
they’ve already declined it. (NOTE: it is possible that in some circumstances, the admin contact
will want a cancelled order resubmitted; in these cases, the Reseller will have to re-form the
order from that start.

The domains administrative contact will need to approve the ‘resubmitted’ order; this step cannot
be skipped, even if they granted their approval the first time.

To resubmit a Declined Order, simply click on the View Declined Orders link in the main screen of
the RWI, find the domain order you wish to resubmit, and open it by clicking on the domain
name. Once you’ve opened the specific failed order, scroll down to the bottom, select the ‘Re-
process’ option from the drop-down menu and press ‘Submit’.

This feature will work for .com/.net/.org and .ca transfers.

NOTE: In fact, this feature creates a new order with the same order information, after allowing
the reseller an opportunity to correct any of the information (if required). However, resellers
cannot modify registrant usernames or password from the original order using the feature. The
original order is changed to ‘cancelled’ status after this feature is used.




              Page 58 of 174 - Release Version 2.56 - support@opensrs.org
 6.39 Verisign NIC Tracking Number

In our pursuit to assist with the sometimes complicated transfer process, we are now showing an
additional piece of information pertinent to VeriSign transfers which have been declined.

When VeriSign declines a transfer, they send a “NIC Tracking Number” to the registrar who
attempted the transfer. This information is required to follow-up with VeriSign to determine the
cause of the transfer failure.

To obtain this information, locate the declined order via the Reseller’s Interface under “Declined
Orders”. In the NOTES field of that order (bottom of page), the tracking number will be shown
as part of the notes, if it was successfully parsed from any emails sent from VeriSign.




 6.40 Forcing the completion of registrar transfers

It’s possible that you will find that the Registry shows that Tucows is now the registrar for a
particular name you are transferring here, but that our order will still show as ‘Pending Registry
Approval’; Resellers are now able to force the OpenSRS to query the Registry to see whether the
Registrar has been set to Tucows or not. If, because a reseller has initiated such a check, we
find that the registrar is now Tucows, we will complete the order immediately.

To check the status of a transfer order that is ‘Pending Registry Approval’, click on the domain
name from the ‘Waiting Registry Approval’ view, scroll down to the bottom of the page, and click
the ‘Check Transfer’ button.

Note: This feature will work for gTLD and .ca transfers that are ‘Pending Registry Approval’.

 6.41 Transfer Management

The ‘Transfer Management’ section in the Reseller Web Interface (RWI) holds many important
transfer features.

The following is a screenshot of the Transfer Management section:




              Page 59 of 174 - Release Version 2.56 - support@opensrs.org
6.42 RSP Messaging: Transfers to your account




 a) Receive email messages when a Domain Admin Contact either accepts or
    rejects a transfer to you
        a. Enable this feature to receive an email at your specified Transfer Contact email
            address when a domain’s administrative contact either confirms or rejects a
            transfer to your account. This setting works for both Reseller and Registrar
            transfers.

             Default Setting: Off
             Customizable: No

 b) Receive email messages when a transfer times out after 7 days
       a. Enable this feature to receive an email at your specified Transfer Contact email
          address when a transfer order times out. This setting works for both Reseller and
          Registrar transfers.

             Default Setting: On
             Customizable: No


6.43 RSP Messaging: Transfers away from your account




 a) Receive email messages when OpenSRS receives a ‘transfer-away’ request
       a. Enable this feature to receive an email at your specified Transfer Contact email
          address when Tucows receives a request to transfer a domain in your reseller
          profile to another Registrar or to another Tucows Reseller. This setting works for
          both Reseller and Registrar transfers.

             Default Setting: Off



           Page 60 of 174 - Release Version 2.56 - support@opensrs.org
                Customizable: No

    b) Receive email messages when a Domain Admin Contact either accepts or
       rejects a ‘transfer away’ request.

            a. Enable this feature to receive an email at your specified Transfer Contact email
                address when the domains administrative contact either accepts or rejects a
                transfer away from your account. This setting works for both Reseller and
                Registrar transfers.

                Default Setting: Off
                Customizable: No

 6.44 End User Messaging: Transfers to your account

The end user messaging section allows you to customize most of the letters that are sent to a
domain’s administrative contact during both Registrar and Reseller transfers. There are three
different types of emails to customize, and each can be customized to varying degrees:

    1) Transfer Request Email Customization
    2) Transfer Acceptance Message Customization
          a. For Registrar Transfers
          b. For Reseller Transfers
    3) Admin Contact Rejection Acknowledgement Message Customization
    4) Transfer Completed Email**

Note: Many of the messages allow you to include {{fields}} from the domain database; for a list
of which fields are useable in the various emails, please use the ‘Preview’ feature.

1) Transfer Request Email Customization

This is the email sent to a domains administrative contact once the OpenSRS system has
accepted an order to transfer a domain into a given reseller’s profile. The message must be sent;
most of the message cannot be customized; however, Resellers can customize one section of the
email with any text they would like.

Note that the body of the message will differ slightly based on whether the order is a Registrar or
Reseller transfer, but the headers remain the same. The customized body will appear in both
Reseller and Registrar transfer messages.

Please be sure to preview any changes you make so that you fully understand how your text fits
in with ours. You may use any ASCII based characters, plus the following fields in your section of
the email:

{{order_time}} (the time of the order)
{{rsp_orgname}} (the Gaining Reseller’s company name)
{{admin_name}} (the name of the person who entered the order)
{{domain}} (the domain)
{{id}} (the unique id for transfer)


Default Setting: On (no option)
Customizable: Headers, Transfer URL



              Page 61 of 174 - Release Version 2.56 - support@opensrs.org
All new features in this section are self-explanatory as presented on-screen, with the exception
of:

Transfer web URL:

This feature allows Resellers to optionally provide the URL for the Transfer Approval Web Page.

NOTE: Resellers using this option should be very sure that they understand how the
feature works, and should test the feature out thoroughly before processing live
transfers. This is not, by any means, a feature that works as soon as you provide a
URL. Careful programming is required before you enable a custom Transfer URL;
please consult the OpenSRS Protocol Specification for complete instructions.

2) Transfer Acceptance Message Customization

These are the messages sent to administrative contacts when they either accept or reject a
transfer to a Reseller’s account.

            a. For Reseller Transfers

                All new features in this section are self-explanatory as presented on-screen.

                Default Setting: Off
                Customizable: Headers, Body

            b. For Registrar Transfers

                All new features in this section are self-explanatory as presented on-screen.

                Default Setting: Off
                Customizable: Headers, Body

3) Admin Contact Rejection Acknowledgement Message Customization

This section allows Resellers to customize the message sent to Registrants who reject the
transfer of a domain to their Reseller profile.


All new features in this section are self-explanatory as presented on-screen.

This message works for both rejected Reseller and Registrar Transfers.

Default Setting: Off
Customizable: Headers, Body

4) Transfer Completed Email**

(this email differs slightly in how it’s customized from the emails above)

When a registrar or reseller transfer completes (for .com/.net/.org/.ca names) a message will
now be sent to the administrative contact associated with the order to inform them that the
transfer has completed.



              Page 62 of 174 - Release Version 2.56 - support@opensrs.org
Currently, whether your registrants will receive this notification depends on whether you have
enabled the “Email Message to Customer” under: Tech Contact Information/Email Message to
Customer/Configure Message/Send Confirmation By Default. However, the message is
customized in the Transfer Management/End User Messaging/Transfers to Your Account section.

 6.45 End User Messaging: Transfers away from your account

Use this section to customize the messages sent to Registrants attempting to transfer away from
your account. There are two types of messages to customize here, and each is customizable to
varying degrees:

        1) Transfer Away Notice Email Customization
        2) Transfer Away Acknowledgement Message Customization
              a. Acceptance
              b. Rejection

Transfer Away Notice Email Customization

As a matter of policy, this email is sent to all Registrants as soon as Tucows receives a request to
transfer a domain to another Registrar.

NOTE: Due to the possibility of ‘registrant email flooding’, this message is only delivered to
administrative contacts for Registrar transfers. Registrants are NOT contacted by the OpenSRS
system (on behalf of LOSING Resellers) during reseller transfers.
Note that while the message headers are customizable, the body is not.

Transfer web URL:

This feature allows Resellers to optionally provide the URL for the Transfer-Away Approval Web
Page. Resellers using this option should be very sure that they understand how the
feature works, and should test the feature out thoroughly before processing live
transfers.

If the Registrant does not respond to this email, the Transfer Away is processed five days from
when this email was originally sent.

All other new features in this section are self-explanatory as presented on-screen.

Default Setting: On (no option)
Customizable: Headers, Transfer Web URL

Transfer Away Acknowledgement Message Customization
       1) Acceptance

            Use this message to optionally confirm a registrants acceptance of a transfer away
            from your profile (to either another Registrar or Tucows Reseller)

            Default Setting: Off
            Customizable: Headers, Body

        2) Rejection

            Use this message to optionally confirm a registrants acceptance of a transfer away


              Page 63 of 174 - Release Version 2.56 - support@opensrs.org
            from your profile (to either another Registrar or Tucows Reseller):

            Default Setting: Off
            Customizable: Headers, Body

 6.46 Web Page Customization

Use the Customize Transfer Page section to specify a logo and custom text that registrants see
when approving/rejecting transfers if you are NOT using your own URLs for these pages.
If you have specified custom URLs for transfer acceptance/rejection, these logo/text
parameters are ignored.

 6.47 Default Transfer Messages

 All message defaults are included below; each is marked with information about what is
customizable

 6.48 End User Messages default text

    1. Domain Transfer Request to Administrative Contact (Registrar Transfer)

To :
From: OpenSRS Transfers {{transfer_email}}
Reply-To:
Subject: Transfer Request for {{domain}}

A request has been received to transfer the domain {{domain}}
to {{rsp_orgname}}, an authorized reseller of the registrar Tucows. This request was
entered at {{order_time}}
by {{admin_name}}.

This acknowledgement of transfer will be processed by Tucows Inc, an
ICANN accredited registrar on behalf of {{rsp_orgname}}. If
this is a valid request and you wish to approve this transfer, please
visit the following url and follow the instructions:{{transfer_url}}?rid={{rid}}

You will need to enter the following information to complete the
transfer:
Domain Name: {{domain}}
Password: {{id}}

If you do not wish to approve this transfer, you may simply ignore this
message and the request will be cancelled, or you can use the Domain
Name and Password above to cancel the transfer.

Accepting this transfer will change the registrar of record for your
domain from its current registrar, to Tucows/OpenSRS; it may also
change some of the contact information. If you are receiving this
email, you should have initiated, or at least been aware of this
request already. If this is the first time that you've heard of this,
do not accept the transfer until you are satisfied that the request is
legitimate.

Thank you.
Team {{rsp_orgname}} and Team Tucows

    2. Batch transfer request to Administrative Contact (Registrar Transfer)

To :
From: OpenSRS Transfers {{transfer_email}}
Reply-To:
Subject: Batch Transfer Request

A request has been submitted to transfer one or more domains to {{rsp_orgname}}, an




              Page 64 of 174 - Release Version 2.56 - support@opensrs.org
authorized reseller of the registrar Tucows.   This request was entered at {{order_time}}
by {{admin_name}} for the following domains:

{{domains}}

This acknowledgement of transfer will be processed by TUCOWS Inc, an
ICANN accredited registrar on behalf of {{org_name}}. To either approve
or cancel this request, please visit the following URL and follow the
instructions:

{{transfer_url}}?rid={{rid}}&bt=1

You will need to enter the following information to complete the transfer:

Batch Transfer ID: {{bulk_transfer_id}}
Password:         {{id}}

You may also simply ignore this message and the request will be cancelled.

Thank you.
Team {{org_name}} and Team Tucows

   3. Domain Transfer Request to Administrative Contact (Reseller Transfer)

To :
From: OpenSRS Transfers {{transfer_email}}
Reply-To:
Subject: Transfer Request for {{domain}}

A request has been received to transfer the domain(s) listed
below to {{rsp_orgname}}. This request was entered at {{order_time}} by
{{admin_name}}.

If this is a valid request and you wish to approve this transfer,
please visit the following url and follow the instructions:

{{transfer_url}}?rid={{rid}}

You will need to enter the following information to complete the
transfer:

Domain Name: {{domain}}
Password: {{id}}

If you do not wish to approve this transfer, you must visit the
URL above, and use the Domain Name and Password shown to Decline
it.

Accepting this transfer will change your registration service
provider for your domain(s) to {{rsp_orgname}}, an authorized
reseller of the Domain Registrar Tucows. If you are receiving
this email, you should have initiated, or at least been aware of
this request already. If this is the first time that you've heard
of this, do not accept the transfer until you are satisfied that
the request is legitimate.

Thank you.
Team {{rsp_orgname}} and Team Tucows


   4. Domain Transfer Away Request notice to administrative contact

To :
From: OpenSRS Transfers {{transfer_email}}
Reply-To:
Subject: Transfer Request away has been received for the domain {{domain}}

A request has been received to transfer the domain {{domain}}
away from the Registrar Tucows. This request was entered at {{order_time}}
by {{gaining_registrar}}




              Page 65 of 174 - Release Version 2.56 - support@opensrs.org
If this is a valid request and you wish to approve this transfer,
please visit the following url and follow the instructions:{{transfer_url}}?away=1

You will need to enter the following information to complete the
transfer:

Domain Name: {{domain}}
Password: {{id}}

If you do not wish to approve this transfer, you must visit the URL
above, and use the Domain Name and Password shown to Decline it.
Accepting this transfer will change the registrar of record for your
domain from Tucows, to {{gaining_registrar}}.If you are receiving this
email, you should have initiated, or at least been aware of this
request already. If this is the first time that you've heard of this,
do not accept the transfer until you are satisfied that the request is
legitimate.

The transfer request will be automatically completed within 9
business days if you don't either accept or decline the request.

Thank you.
Team {{rsp_orgname}} and Team Tucows

   5. Administrative contact approves outgoing transfer, message to Administrative
      Contact

To :
From: OpenSRS Transfers {{transfer_email}}
Reply-To:
Subject: Confirmation of domain transfer away

This is to notify you that the domain shown below will be transferred to
{{gaining_registrar}}

{{domain}}

   6. Administrative contact rejects outgoing transfer, message to Administrative
      Contact

To :
From: OpenSRS Transfers {{transfer_email}}
Reply-To:
Subject: Transfer of domain rejected by Admin Contact

The administrative contact for the domain listed below
has declined a request to transfer the domain to
{{gaining_registrar}}

{{domain}}


   7. Reseller Transfer acceptance confirmation to Administrative Contact

To :
From: OpenSRS Transfers {{transfer_email}}
Reply-To:
Subject: Domain Transfer Accepted

Hello,
This email comes to confirm your acceptance of the transfer of your domain {{domain}} to
{{GRSP}}.

Thanks you.


   8. Registrar Transfer acceptance confirmation to Administrative Contact




              Page 66 of 174 - Release Version 2.56 - support@opensrs.org
To :
From: OpenSRS Transfers {{transfer_email}}
Reply-To:
Subject: Domain Transfer Request Accepted

Hello,

This email confirms that you have accepted a request to transfer the domain {{domain}} to
{{GRSP}}.

Thank you.


   9. Transfer is declined by Administrative Contact, confirmation message to
      Administrative contact.

To :
From: OpenSRS Transfers {{transfer_email}}
Reply-To:
Subject: Transfer Rejection Notification for {{domain}}

The following domains(s) was/were not transferred to {{rsp_orgname}} because the
administrative contact rejected the transfer request(s)

{{domains}}


 6.49 Gaining Reseller Messages default text

   1. Transfer approved by Administrative Contact, message to GRSP

To :
From: OpenSRS Transfers {{transfer_email}}
Reply-To:
Subject: Transfer for Domain {{domain}} has been accepted by Registrant

Transfer of the domain shown below to your reseller profile has been
accepted by the Administrative Contact.

For Reseller transfers the transfer request and renewal
of the domain will be completed within 24 hours.

For Registrar transfers the transfer request and renewal
of the domain will be completed within 7 days.

{{domains}}

Thank you,
Team Tucows

   2. Transfer rejected by Administrative Contact, message to GRSP

To :
From: OpenSRS Transfers {{transfer_email}}
Reply-To:
Subject: Transfer of {{domain}} failed

The following domains(s) was/were not transferred to your account
because the administrative contact rejected the transfer request(s)

{{domains}}


   3. Transfer timed out after 7 days, message to GRSP

To :
From: OpenSRS Transfers {{transfer_email}}
Reply-To:
Subject: Transfer failure notification for {{domain}}




              Page 67 of 174 - Release Version 2.56 - support@opensrs.org
This is an automated response to alert you that a transfer request for
{{domain}} for reg_system order # {{order_id}} has failed for the
following reason:

        Transfer timed out waiting for owner approval.

If you have any questions, please contact {{transfer_email}}.

Thank you,
Team {{registrar}}


 6.50 Losing Reseller Messages default text

        1. Transfer Away Notice to LRSP

To :
From: OpenSRS Transfers {{transfer_email}}
Reply-To:
Subject: Transfer of the domain {{domain}} away from OpenSRS

A request to transfer the domain shown below to another Registrar/Tucows Reseller has
been received at {{order_time}}.

Gaining Registrar {{gaining_registrar}}

Domain {{domain}}

Thank you,
Team Tucows


        2. Transfer Away Accepted by Administrative Contact, email to LRSP

To :
From: OpenSRS Transfers {{transfer_email}}
Reply-To:
Subject: Domain {{domain}} is being transferred away

Notice:
The administrative contact for the domain shown below has confirmed
their intent to transfer the domain to {{gaining_registrar}}:

{{domain}}


        3. Transfer Away Declined by Administrative Contact, email to LRSP

To :
From: OpenSRS Transfers {{transfer_email}}
Reply-To:
Subject: Domain Transfer away rejected by Admin Contact

The administrative contact for the domain listed below
has declined a request to transfer the domain away from your Reseller profile.

{{domain}}


4) Notification for Reseller if OpenSRS does not approve transfer

This is an automated response to alert you that a transfer request for
$domain for reg_system order # $order# has failed for the
following reason:

Cancelled by OpenSRS Admin: We cannot process this transfer due to
a 552 error from the registry:

This can occur as a result of:




              Page 68 of 174 - Release Version 2.56 - support@opensrs.org
: domain is not yet 60 days old
: existing registrar has the name
  locked for either non-payment or at the
  end users request - requesting party
  needs to contact existing registrar
  to resolve
: domain name is in dispute
: the name has been deleted


If you have any questions, please contact transfers@opensrs.org.

Thank you,

Team OpenSRS

5) Notification to MSP if request times out at the Registry:
This is an automated response to alert you that a transfer request for
$domain for reg_system order # $order has failed for the
following reason:

        Transfer timed out waiting for registry approval.

If you have any questions, please contact transfers@opensrs.org.

Thank you,
Team OpenSRS


 6.51 Pricing

gTLD registration, renewals and transfers cost $10 USD per domain year.

 6.52 Managing gTLDs

To manage gTLDs, Resellers should advise their clients to use Tucows’ Manage Domain interface,
using the username and password they selected when registering or transferring the domain.
NOTE: It is possible for Resellers to offer domain management as a service; Tucows simply
requires Resellers to provide a means for their clients to make changes to their domain name.

 6.53 WHOIS Info

With the new shared registration system model, the nature of the WHOIS server has changed.
Traditionally, the InterNIC/NSI Registry maintained the WHOIS server for .com, .net and .org
domain names, and a single query returned full WHOIS data including, registrant, administrative
contact, billing contact, technical contact, and nameserver information.

The Old Way:




A single query returned full WHOIS data.

The New Way:

In the multi-registrar model, each registrar maintains a WHOIS server containing contact and


               Page 69 of 174 - Release Version 2.56 - support@opensrs.org
nameserver information for domains registered with them. The InterNIC maintains a central,
registry WHOIS server, which simply contains nameserver and registrar information for all .com,
.net and .org domains.




To find out the registrar of record for a domain, consult the registry WHOIS server, at:

http://rs.internic.net/whois.html

The output from the registry WHOIS query will indicate the website address and WHOIS server
address for domain's registrar of record, where full contact information can be found.

Key Points:

    1. Only the WHOIS server of a domains' registrar of record can be considered authoritative

    2. Some Registrar's configure their WHOIS server to perform a 'registry lookup' for other
       Registrar's domain names; some will even go so far as to perform a lookup on another
       registrar's WHOIS server. However, the only sure way to check domain availability or get
       contact and expiry information is to perform a WHOIS query with the domain's registrar of
       record. As a convenience, the OpenSRS WHOIS server is configured to check other
       Registrars' WHOIS databases.

    3. Many WHOIS databases are not updated in real-time, so that you can make a change to
        record, but the change will not appear in the WHOIS output until sometime the next day.
        OpenSRS' WHOIS server is updated in real-time for all domains that we are the registrar
        for.


 7.0 .co.uk and .org.uk Registrations
The following section describes specific details that relate to the registration of .org.uk and .co.uk
domain names.




               Page 70 of 174 - Release Version 2.56 - support@opensrs.org
 7.1 The .org.uk and .co.uk Opportunity

More and more of your customers will soon be embarking on their own online global expansion.
If the latest trends are any indication, the .uk namespace will likely be one of their first stops.

According to Nominet, 150,000 new .co.uk names are registered every month. To date, .co.uk
and .org.uk names account for just over 10 per cent of the total number of domain names
registered on the Internet.

Offering .co.uk and org.uk as part of your portfolio is also a simple way to send a very powerful
message about your business (even to those who do not currently want these domain names).
It lets your customers know that you are anticipating and meeting all their domain name needs
and hints that they can count on you to continue to expand your selection of ccTLDs and,
eventually, new gTLDs.

 7.2 About ccTLDs

The term ccTLD stands for country code Top Level Domain; it is a term used to differentiate
country code name space such as .ca, .uk, .au (Canada, United Kingdom and Australia from
gTLDs (generic top level domains) such as .com, .net, or .org. A complete listing of ccTLDs and
their corresponding countries can be found at:

http://www.iana.org/cctld/cctld-whois.htm

It is important to note that some ccTLDs are closed or chartered, meaning that there are
restrictions placed on registering a domain in that space, while others are less restrictive or open
for everyone to register domains into. The UK registry restricts registrations into their very top
level domain, .uk, to registrants living in the United Kingdom. However, they offer open
registrations in the .org.uk and .co.uk namespaces, meaning that they can be registered by
anyone, regardless of where they live. Other examples of ccTLD restrictions include; residency in
a given country, proof of business operations and licensing etc.

Tucows’ goal is to offer as many TLDs (both ccTLDs and gTLDs) as possible to our Channel
Partners. Where a ccTLD is deemed too restrictive, Tucows will generally opt not to offer it (as in
.uk), but where registration requirements seem reasonable (as in .co.uk, and .org.uk) we will
endeavor to offer it to our channel.

 7.3 About Nominet

Nominet is a United Kingdom based company that has been given administrative rights over the
.uk name space. Nominet acts as the registry for .uk domains. In becoming a Registrar with
Nominet, Tucows/OpenSRS is now able to extend. org.uk and .co.uk domain name registrations
to our Channel Partners in much the same way as we do with .com, .net, and .org gTLDs.

 7.4 .org.uk and .co.uk Registration Considerations

The same registration templates used for .com .net and .org will also be used when
registering.uk domains. Within the new client code, the order templates include support for .uk
registrations. Upon successful registration, .co.uk and .org.uk domains will be seamlessly inserted
into an OpenSRS registrant profile.

When implementing .org.uk and .co.uk registrations, careful consideration should be given to:

    -   the registration period, which is set at a standard 2 years
    -   the nature of asynchronous processing (registration/modifications are NOT real time)


              Page 71 of 174 - Release Version 2.56 - support@opensrs.org
    -   certificate mailing

Registration period (term)
.org.uk and .co.uk registrations are set for two years. The registry does not offer any other
registration periods at this time.

Asynchronous processing
.org.uk and .co.uk registrations are handled at the registry (Nominet) level as an asynchronous
process. This means that registrations submitted are not immediately processed/approved by the
registry server. When an order is submitted, it enters a pending state, subject to registry
approval. Typical registry processing time is under five minutes, however it can take longer based
on circumstances beyond the control of Tucows. As a result of this, it is important to
communicate this delay to users when they place orders with you. You can check the status of a
submitted order anytime through the Reseller Web Interface (RWI).

This delayed processing is very similar to the process of executing a sponsoring registrar transfer
in the .com, .net, and .org namespace.

As with the Transfer process, once a registration for a .uk domain has been submitted the funds
required for each registration (domain) will be put on hold (frozen) immediately from the
Reseller’s account. Should the registration fail for any reason the funds will be refunded
(released) upon notification of failure from Nominet.

NOTE: if a request is made for a domain name that is already registered, or is even in the
OpenSRS queue to be registered, the Reseller will receive an error message immediately.

                                                                                          Order
   Circumstance                 Message from Nominet                       Type           State
                                                                                         in RWI
.co.uk/.org.uk name      Order # processed: Domain registration       Real Time         Sent to
available at time        successfully submitted                                         Registry
order submitted to
Nominet
.co.uk/.org.uk name      Domain 'requesteddomain.co.uk' taken          Real Time        N/A
not available at time
order is submitted to
Nominet
.co.uk/.org.uk name      Order not registered: A request is           Real Time         N/A
ordered when Tucows      currently waiting on this domain
already has another
request in queue for
the same name
.co.uk/.org.uk name      Message received will be specific to the     Not-real time     Varies
fails to register        problem with the registration; the order
                         will remain in Pending Orders with the
                         appropriate error displayed in the Notes
                         field. Domain order must be corrected or
                         cancelled to leave this state.

                                                   Table 1.0 Asynchronous Order States




              Page 72 of 174 - Release Version 2.56 - support@opensrs.org
Certificate Mailing
When a domain has been successfully registered Nominet will mail the following to the registrant
of that domain:

    -   Registration certificate (see figure 4.0 below)
    -   Registrant reply form
    -   Nominet notes for registrants
    -   Nominet terms and conditions

Upon receipt of these items Nominet expects that the registrant will fill out and send back the
“Reply form.”

Failure to do so may result in cancellation with written notification from Nominet of the domain.
Practically, our experience has shown that not completing and returning the forms has not
resulted in names being cancelled, however, if there are any disputes or problems with the
name, the Registrant (end user) will be in a far stronger position if they have returned the
certificate. We recommend advising your end-users to return the “Reply form” to Nominet.




                                             Figure 4.0 Sample Nominet UK Registration Certificate

 7.5 Reseller .org.uk and .co.uk Qualification

In order to offer .org.uk and .co.uk domain names, each Reseller will be required to a .uk specific
Registration Service Provider Agreement. Additionally, Resellers will be required to bind their
clients to the terms and conditions of the .uk registry; this will include posting and/or linking to
the dispute policy specific to .uk names.




              Page 73 of 174 - Release Version 2.56 - support@opensrs.org
Resellers will be able to use our test environment for .uk registrations without qualification, as
this environment simply simulates the behavior of the .uk registry and does not actually register
.uk names.

In order to apply for access to sell .org.uk and .co.uk registrations from our live environment,
you must:

    -   Remit a new Reseller contract to Tucows authorizing you to act as an OpenSRS .co.uk
        and .org.uk domain reseller,
    -   Demonstrate to Tucows how you will bind your clients to the .org.uk and .co.uk terms
        and conditions; send an email to rite-bc@opensrs.org with a URL showing the terms in
        your ordering process and your OpenSRS username

Both the UK contract and UK Terms and Conditions can be found at:

http://resellers.tucows.com/opensrs/contracts


 7.6 Quick Start Considerations

OpenSRS will support the registration of new ccTLDs via the existing “Quick Start” (server side)
access method, otherwise known as the Reseller Web Interface (RWI). However as with previous
versions of OpenSRS, the “Quick Start” method will not offer the full robust range of options
available to resellers as with the “Full Access” client implementation. For example, a Quick Start
implementation will not allow Reseller to process bulk registrations, or to build payment
processing into their domain registration process.

 7.7 Pricing

We will offer two year .co.uk and .org.uk registrations for only $13.00 US including VAT (value
added tax, see below). That is $11.06 + $1.94 VAT.

After an initial request is submitted, the OpenSRS system puts the appropriate amount ($13 for
two domain years) ‘on hold’. Once the domain is registered, that amount is taken off hold and
deducted from the Reseller’s account. If the domain registration fails for any reason, the credit is
taken off hold, and returned to the Reseller’s account (see figure 5.0 below).




              Page 74 of 174 - Release Version 2.56 - support@opensrs.org
                                     Figure 5.0 Order processing with respect to account balances

VAT
VAT refers to "Value Added Tax", a tax levied by the UK government. Depending on where you
operate your business from, there are different implications:

Resellers who are not UK corporations:
- must pay VAT on *.uk registrations
- will be able to re-claim VAT paid; our auditors are preparing an information kit on this process
which we will distribute shortly

Resellers that operate in the UK/EC:
- as the services we provide are considered to be supplied form the UK, Resellers resident in the
UK or EC must pay VAT on *.uk registrations, and deal with re-claiming VAT paid as they
normally would

 7.8 Managing .org.uk and .co.uk Registrations

OpenSRS will support record modification for .org.uk and .co.uk registrations. The standard
manage interface and profile system will be used to execute modifications to registrations.

It should be noted that record modification is not real-time; therefore you can expect a delay
after submitting a modification request before the changes actually take effect. Our testing has
shown that these modifications are normally applied within 60 minutes.

After a change is submitted through the manage interface for a .org.uk or .co.uk name, a
message indicating the delay will be displayed.

Modifying Contact and Nameserver Information

Registrants can make as many simultaneous changes (as in, multiple changes in one transaction)
to their .co.uk/.org.uk contact information as they like; however, once the change(s) have been
submitted, the record is locked until the changes have been reviewed and either accepted or
rejected by the Nominet. Once the changes have been accepted or rejected, the record is
unlocked and further changes can be made.

Once a change has been submitted, the registrant will note that the domain has a new waiting
status; until this Waiting State returns to ‘None’, no other changes can be made. Please consult
the table below for a summary of the various wait states:

                     Activity                         Wait State Message
          Changing any contact              Waiting Request:
          information                       modify_contact_info
          Changing any nameserver           Waiting Request:
          information                       enhanced_update_nameservers

                Table 2.0 - Wait States and Sample Messages from the Manage Domain interface

 7.9 .org.uk and .co.uk Renewals

At this time, we do not support renewal requests for .org.uk or .co.uk through either the
“Quickstart” or “Full Access” interfaces. Please contact support@opensrs.org for manual renewal
requests. We will extend this functionality in future releases.


              Page 75 of 174 - Release Version 2.56 - support@opensrs.org
 7.10 .org.uk and .co.uk Transfers Of Registration Sponsorship

At this time, we do not support transfer requests for .org.uk or .co.uk through either the
“Quickstart” or “Full Access” interfaces. Please contact support@opensrs.org for manual transfer
requests. We will extend this functionality in future releases.

 7.11 .org.uk and .co.uk Transfer of Domain Ownership

Nominet requires that transfers in domain ownership be handled between the registrant and
Nominet directly. The Reseller can assist the registrant in the deletion, but OpenSRS does not get
involved with this process.

The registrant will need to complete the transfer form on the reverse of the Domain Name
Certificate and submit a letter of authorization on company letterhead. Full instructions are given
on the transfer form itself

In addition, the person or business the registrant is transferring the Domain Name to must sign
the form and submit a letter of authorization on their own letterhead. The two signatories of the
letters must be different people.

If the registrant has misplaced their Certificate for the Domain Name, and they want to transfer
the registration to another holder, they may request a transfer form from Nominet by sending in
a signed headed fax on company letterhead to the Registration Department.

 7.12 .org.uk and .co.uk Deletion Requests

Nominet requires that domain deletions be handled between the registrant and Nominet directly.
The Reseller can assist the registrant in the deletion, but OpenSRS does not get involved with
this process.
Surrendering your Domain Name is straightforward. On the reverse of the Domain Name
Certificate, the registrant will find a surrender form. Complete this and return it to Nominet, along
with a letter of authorization on your company letterhead.

On receipt of these documents, Nominet will cancel the Domain Name, removing it completely
from the .uk Register Database. Once this is done, the name will be available for someone else to
register.

If the registrant has misplaced their Domain Name Certificate, they should Nominet formally in
writing - on company letterhead - of their requirement to surrender your Domain Name.
Once an .org.uk or .co.uk name is registered, you cannot “get a refund” for the registration.

 7.13 WHOIS info

The Nominet WHOIS server is authoritative for all .co.uk and .org.uk names. You can search the
.uk WHOIS database at http://www.nic.uk/index.html

Note: Both the Quickstart and Full Access interfaces are equipped with a domain lookup tool to
check domain name availability; the WHOIS interface simply provides more information about the
domain registrar and registrant.

At this time, the OpenSRS WHOIS service will not do recursive lookups for *.uk registrations.




              Page 76 of 174 - Release Version 2.56 - support@opensrs.org
A sample of WHOIS output for a *.uk name follows (Tucows does not currently own their own
version of the .co.uk domain name):

Domain Name: TUCOWS.CO.UK
Registered For: Inca Research Inc
Domain Registered By: INCA
Registered on 15-Jul-1998.

Record last updated on 19-Nov-1998 by webmaster@ukinternic.co.uk.
Domain servers listed in order:

NS1.INTERNIC-BACKBONE.NET                      209.203.226.10
NS2.INTERNIC-BACKBONE.NET                      209.203.226.11

WHOIS database last updated at 04:09:00 26-Jun-200

It is important to note that the information available through WHOIS for *.uk is substantially less
than the information available for gTLDs.

 7.14 Registration Considerations

There are several stages each *.uk domain registration goes through; it is important to
understand these when interpreting registration status codes in the RWI.

In case of a new domain, a reply from .uk registry typically arrives in 5-10 minutes. That means
no one else can reserve this domain at this point; Nominet will reject new registration requests
for the same name. However, the owner cannot use the domain yet, because the root
nameservers are not updated immediately.

Nominet updates the root nameservers twice daily; your clients will be able to use their names as
soon as the root zone is updated. They will be able to view Nominet WHOIS information within
one hour.

 7.15 Modification Considerations

If only the contact info is updated for a *.uk name, then the change is reflected in the WHOIS
database within one hour. If nameservers are updated, the change won’t take effect until the
root nameservers are reloaded, which happens twice daily.

 7.16 Modification Considerations

When a nameserver based on a UK domain is created, it will not be usable by other domains until
it has first been added to the parent domain. For instance, to be able to attach the new
nameserver ns1.parent.co.uk to other.co.uk, the following procedure must be done:

        - create nameserver through the normal means
        - add the new nameserver to parent.co.uk
        - add the new nameserver to other.co.uk

Note that this will require that ns1.parent.co.uk DNS must be setup to return details on both the
parent and the other domains.




              Page 77 of 174 - Release Version 2.56 - support@opensrs.org
 8.0. .ca Registrations
The following section of this document explains .ca registrations.

 8.1 Overview & Feature List


.ca features include:

Client:
          -       .ca registrations, renewals and registrar transfers
          -       autorenewals
Server:
          -       .ca registrations, renewals and registrar transfers
          -       autorenewals
          -       do not renew flag

 8.2 The .ca Opportunity

Until recently the Canadian country code top-level domain (ccTLD) registry has been operated by
a group of volunteers at the University of British Columbia. To date, approximately 90,000
domain names have been registered under ccTLD .ca. In June 2000, the University reached an
agreement to transfer the operation of the registry to CIRA (Canadian Internet Registration
Authority). CIRA is a not-for-profit organization that has been created to operate a modern ccTLD
registry on behalf of Canadians.

The transfer of the registry to CIRA has several implications for registrants.
First, the existing 90,000 .ca domain holders had to ‘re-register’ their already registered domain
names. CIRA began accepting “pre-registrations” from the existing registrants beginning
September 18, 2000.

Before November 1, 2000, domain names were registered at no cost and it was not necessary to
renew .ca registrations. Once operation of the registry is transferred to CIRA, (on or about
November 1, 2000) registrants are required to pay an annual fee for each domain name.
Existing registrants can pre-register their existing .ca domain names starting September 18,
2000. All existing .ca domain name registrants have until January 31, 2001 to ensure their
domain name has been registered in the new system.

Until the operational transfer of the registry to CIRA, registrations of domains directly under .ca
continue to be limited to Canadian organizations that were either federally incorporated or had a
multi-provincial presence.       Consequently, until November 1, individuals and provincial
organizations are prohibited from registering a second level domain name under .ca. Instead,
the rules required that the domain name be registered under the appropriate second or third
level such as .on.ca. As well, until the change to the registry only one domain name could be
registered for each registrant. Therefore, registrants with multiple brands have been unable to
utilize those brand names to their full potential. After the operational transition these limitations
will be significantly altered. Registrants are required to have a Canadian presence (see Exhibit A
for exact requirements), however, they may register an unlimited number of domain names
directly under .ca. Organizations and individuals will be able to utilize, promote or create multiple
brands and tag lines on the Internet under .ca.

Third, the limitation to a single domain name per registrant means that there are still many
useful ‘generic’ domain names available. Under the gTLDs .com, .net and .org most of these




              Page 78 of 174 - Release Version 2.56 - support@opensrs.org
names, such as movie, garden and ‘yourquote’ have already been registered. With only 90,000
domain names registered under .ca, many ‘generic’ domain names are still available for use.
A fourth change to the operation of the .CA registry is the use of registrars. Registrants will not
contact the registry directly, instead, they will work with a service provider (registrar) to register
and manage their domain name.

 8.3 .ca Reseller Qualification

In order to offer .ca domain names, each Reseller will be required to sign and remit to Tucows a
.ca specific Registration Service Provider Agreement. Additionally, Resellers will be required to
bind their clients to the terms and conditions of the .ca registry.

Resellers will be able to use our test environment for .ca registrations without qualification, as
this environment simply simulates the behavior of the .ca registry and does not actually register
names.

In order to apply for access to sell .ca names from our live environment, you must:

    -   Remit a new Reseller contract to Tucows authorizing you to act as an OpenSRS .ca
        domain reseller. The contract can be found at:
        http://resellers.tucows.com/opensrs/resources/docs/contracts/caagreement.pdf

    -   bind your customers to the .ca registration terms, a copy of which can be found at:
        http://resellers.tucows.com/opensrs/ca/ca_exhibita

 8.4 About ccTLDs

The term ccTLD stands for country code Top Level Domain; it is a term used to differentiate
country code name space such as .ca, .uk, .au (Canada, United Kingdom and Australia) from
gTLDs (generic top level domains) such as .com, .net, or .org. A complete listing of ccTLDs and
their corresponding countries can be found at:

http://www.iana.org/cctld/cctld-whois.htm

It is important to note that some ccTLDs are closed or chartered, meaning that there are
restrictions placed on registering a domain in that space, while others are less restrictive or open
for everyone to register domains into. Examples of ccTLD restrictions include; residency in a
given country, proof of business operations and licensing etc…

Tucows’ goal is to offer as many TLDs (both ccTLDs and gTLDs) as possible to our Channel
Partners. Where a ccTLD is deemed too restrictive, Tucows will generally opt not to offer it (as in
.uk), but where registration requirements seem reasonable (as in .co.uk, .org.uk and .ca) we will
endeavor to offer it to our channel.

Historically, the .ca domain space was very ‘closed’. Names were only granted to entities
federally or provincially incorporated, or with points of presence in more than one city or province
in Canada. Also, only one name was allowed per person or company. Under CIRA, the new
Registry, the single domain limit has been removed, and names can be registered to Canadian
individuals and organizations.

Please see “Section 8.19” for the “Canadian Presence Requirements” for .ca registrations.




              Page 79 of 174 - Release Version 2.56 - support@opensrs.org
 8.5 About CIRA

The Canadian Internet Registration Authority (CIRA) is a not-for-profit Canadian corporation that
is responsible for operating the .ca Internet country code Top Level Domain (ccTLD) for all
Canadians in an efficient and professional manner. CIRA may also carry out other Internet
related registration activities for the Canadian community. The current Board of Directors of
CIRA was appointed on an interim basis to initiate the organization. In the future, members of
the Board of Directors will be elected by the holders of domain names registered under the
ccTLD .ca.

.ca domain names had previously been assigned and registered by the .ca Committee, a
volunteer organization headed by Mr. John Demco, the Computing Facilities Manager for the
Department of Computer Science at the University of British Columbia. On a voluntary basis, the
University provided the technical and administrative resources to house and operate the registry.
This organization has agreed to transfer the operation of the registry to CIRA on or about
November 1, 2000.

 8.6 .ca Registration Considerations

Special .ca registration templates will be used when registering .ca domains. Upon successful
registration .ca domains will be seamlessly inserted into an OpenSRS registrant profile.

 8.7 New Registrations

On 11/08/00 CIRA began accepting new registrations in the .ca namespace, under much less
stringent registration restrictions. Under the new rules only individuals and organizations that
meet Canadian presence criteria will be able to register domain names, however registrants will
be able to register as many .ca domain names as they wish to pay for.

New registrations can be both synchronous processes, and asynchronous processes, depending
on whether the name is being registered to a new registrant or an existing registrant. Names
registered to existing registrants are synchronous, and are processed in real-time. Names
registered to new registrants will be processes asynchronously, and will place the appropriate
Reseller funds "on hold" within the OpenSRS system until the registrant either confirms or rejects
CIRA’s terms and conditions.

Tucows will return all funds on hold to the Reseller if a .ca registration should fail or be rejected
by CIRA.

 8.8 .ca Quick Start Considerations

OpenSRS will support the registration of .ca TLDs via the existing “Quick Start” (server side)
access method, otherwise known as the Reseller Web Interface (RWI). However as with previous
versions of OpenSRS, the “Quick Start” method will not offer the full robust range of options
available to resellers as with the “Full Access” client implementation. For example, a Quick Start
implementation will not allow Reseller to build payment processing into their domain registration
process.

NOTE that since CIRA does not require a billing contact, OpenSRS does not require that a billing
contact be submitted with .ca orders.

 8.9 WHOIS info

The current authoritative WHOIS server for .ca domains is:




               Page 80 of 174 - Release Version 2.56 - support@opensrs.org
http://www.cira.ca/en/home.html

Note: Both the Quickstart and Full Access interfaces are equipped with a domain lookup tool to
check domain name availability; the WHOIS interface simply provides more information about the
domain registrar and registrant.

At this time, the OpenSRS WHOIS service will not do recursive lookups for *.ca registrations.

A sample of WHOIS output for a *.ca name follows:
Domain tucows.ca


Organisation   TUCOWS International Inc.
Registrar      Tucows International Corp.
Renewal Date 2002/09/17
Date
               2000/10/20
approved
Last changed 2000/11/02
               TUCOWS International Inc. is an internationally based firm offering web based content services (ie
               www.pilotzone.com, www.tucows.com)to end users on a global scale. TUCOWS currently operates the
Description    largest Canadian owned web site and has mirrors at over 300 locations world wide. Administrative
               operations are based throughout Canada and the United States (British Columbia, Alberta,
               Saskatchewan, Ontario and Michigan).
Registrar
               156
Number
Registrant
               27673
Number
Domain
               27673
Number
DNS1           cns1.idirect.com
DNS2           cns2.idirect.com

        Nom Edward Gray
   Job Title Manager Central Services
     Postal EDWARD GRAY MANAGER CENTRAL SERVICES TUCOWS INTERNATIONAL INC. TUCOWS
    Address INTERNATIONAL INC. 96 MOWAT TORONTO ON M6K 3M1 CAN
       Phone +1 (416) 535-0123
         Fax +1 (416) 531-5584
       Email ace@tucows.com

        Nom Adrian Daminato
   Job Title Network Engineer
     Postal ADRIAN DAMINATO NETWORK ENGINEER TUCOWS INTERNATIONAL CORP. TUCOWS INTERNATIONAL
    Address CORP. 96 MOWAT TORONTO ON M6K 3M1 CAN
       Phone +1 (416) 535-0123
         Fax +1 (416) 531-5584
       Email dnsadmin@idirect.com




                Page 81 of 174 - Release Version 2.56 - support@opensrs.org
 8.10 Registration Flow: .ca Registrations

Some .ca registrations are now processed in ‘real-time’, others are treated as ‘orders in progress’,
and require confirmation from the registrant. If a new .ca name is being added to an existing
CIRA profile, the transaction is completed in real-time. If a new name is being created for a new
registrant, the registrant must agree to CIRA’s terms and conditions after the order is placed,
and the order is treated as an ‘order in progress’ until the registrant agrees to the terms. Once a
new registration to a new registrant is successful, the appropriate amount of money is removed
from the Resellers account.

CIRA is using ‘Registrant Profiles’, much like the OpenSRS profiles, or NSI’s contact handle
system. If, for example, one registrant orders a number of domain names, CIRA specifies that we
process each of the domains with the Registrant ID number, as opposed to including full contact
information with each order.

NOTE: These profiles are not the same as OpenSRS profiles. To add a new .ca name to
an existing CIRA profile (of a .ca name already registered through the OpenSRS
system) you must inherit the order information using the Username/Password from
the existing .ca domain, as follows:

        Enter the .ca domain, username and password in the ‘Retrieve Order
        Information’ section of the order form. Once you have retrieved the
        information, ensure that the same username/password and domain are
        included in the ‘Registrant Profile’ section of the form.

During the registrant profile creation process, the registrant will be required to agree to all of
CIRA’s terms and conditions. However, once done, the registrant can register as many .ca names
to this profile as they wish, and they will not need to go through the lengthy agreement process
for each name. Registrant profiles also allow for the efficient modification of contact information
once domains have been registered.

During the order process, the Reseller (or the end user) must choose whether to register a new
.ca name to an existing OpenSRS profile, or to create a new profile. If an existing .ca name is
provided as the profile ‘anchor’ during the registration process, then the new name will be placed
in the same CIRA profile as the existing .ca name. If a new profile is created, or the anchor name
chosen is not a .ca name (even if there are other .ca names within that OpenSRS profile), or the
existing profile contains no .ca names, then a new CIRA profile is created.

Order States for Registrations

The following are the system status messages and their meaning that will be important during
the Advance Registration Process (you will find all of these associated with your advance .ca
orders under View Orders in Progress in the Reseller Web Interface):


OpenSRS Status         Meaning                                             To Search
Code (in RWI)

Sent to CIRA           The advance registration has been submitted to      Search Reg System
                       CIRA, and accepted as ‘properly formatted’          Orders
                                                                           Status: Processed
Completed*             The domain has been successfully registered         Search Reg System
(not under View                                                            Orders



               Page 82 of 174 - Release Version 2.56 - support@opensrs.org
Orders In Progress,                                                                                  Status: Completed
but under View                                                                                       (or view under View
Active Domains)                                                                                      Active Domains)
Declined              The order was submitted to CIRA, but rejected                                  Search Reg System
                      because it was improperly formatted. To correct                                Orders
                      or cancel the order:                                                           Status: Declined
                          a) Search Reg System orders for the
                              domain in the RWI
                          b) Change the information and resubmit,
                              or cancel as desired
Failed                The order was submitted to CIRA, and rejected.                                 Search Reg System
                      This may be because the name already exists, is                                Orders
                      reserved or ‘illegal’. The appropriate error is                                Status: Cancelled
                      shown in the Order Notes section
                                                     If new CIRA
                                                    Registrant must
                                                        Order
                                                      be created
                                                    submitted to
                                                     OpenSRS
                         ca Registration
                            Process




                                                    Email sent to
                                                  admin contact with
                                                   CIRA username/
                                                      password
                                                                                   If Existing
                                                                                       CIRA
                                                                                Registrant Profile
                                                    Admin contact                     is use
                                                  agrees to all terms
                                                  CIRA Confirmation
                                                    Process Web
                                                        Page




                                                   Tucows/OpenSRS
                                                   Confirmation page




                                           Registrant Profile Created and new
                                                   domain registered




                                              Tucows/OpenSRS Database




 8.11    The CIRA Username/Password

Once the registration is complete, the administrative contact will be sent a UserID/Password from
CIRA. This is NOT the same as the OpenSRS username and password. The CIRA
UserID/Password must be used to:

    a) confirm ‘critical’ updates to the domain
           a. These include changes to Legal Type and Administrative Contact
    b) Confirm Registrar/Registrant Transfers




              Page 83 of 174 - Release Version 2.56 - support@opensrs.org
Please make sure that either you or your clients save this information, as it will be
useful. The CIRA UserID and Password can be resent to the Administrative Contact
through the RWI as follows:

                         1) Enter the domain in question in the View Domain field, click enter
                         2) Scroll down to the bottom of the page
                         3) Click on the ‘Send request to CIRA to resend password to registrant’s
                            admin contact’ button

 8.12 Modifications to the Reseller Web Interface for .ca

This is under “Place Order Manually for .ca”

Retrieve Order Information from Existing .ca Domain:
This feature will query the current CIRA WHOIS database, and populate your order form with
information currently associated with the domain you are pre-registering. NOTE: You may have
to correct the province from full name to two character abbreviation.

This will not necessarily result in the new domain being placed in the same CIRA profile. CIRA
will match incoming registration information against it’s database, and in case of a match, will
add the new domain to the existing Registrant profile. However, if this is the desired outcome,
we recommend using inheriting the information from a .ca name using the OpenSRS profile
username and password.

Retrieve Order Information from a Registrant Profile based on an existing .ca domain.

This will result in the domain being added to the same CIRA Registrant Profile. In order for
this to work as designed, you must include the same domain, username and password in the
‘Registrant Profile’ section when submitting the registration. If you simply use an existing .ca
name to ‘recall’ the order information, but then change the username/password in the ‘Registrant
Profile’ section, then a new registrant profile will be created at CIRA.

NOTE: If the registrant information provided is very similar or identical to a registrant
that already exists at CIRA, CIRA will NOT accept a new registrant and the previous
.ca domain, OpenSRS username and OpenSRS password must be submitted with the
order.

Registration Type drop down menu
Only Select Advance, for new registrations of a new .ca domain name

Do NOT Select ‘Pre-registration’; this feature stopped working as of February 1st, 2001, and will
be removed from the RWI shortly.

Upgrade 3rd or4th level Domain?

Do NOT use this feature; it stopped working on February 1st, 2001, and will removed from the
RWI shortly.

Is this domain a registered trademark

Answer yes if it is, and no if it is not.

Language



                Page 84 of 174 - Release Version 2.56 - support@opensrs.org
Indicate your client’s preferred language for communications from CIRA

 8.13 Registering Municipal names and other variants of .ca domain
names

Municipals Names

CIRA has reserved a domain name for every village and town in Canada. The syntax for these
names is:

Qualifier.name.province.ca

Where, ‘qualifier’ describes the place, be it town, village, etc.

Examples:
city.toronto.on.ca
town.Orangeville.on.ca

Registration orders for these names are submitted normally through the OpenSRS, however,
CIRA has instituted a manual process to complete the registration.

Once the order has been submitted, OpenSRS staff review it for completeness. If it appears likely
to succeed (ie. Appears to be a legitimate registration) then the order is submitted to CIRA.

At this point, the Reseller should fax a letter to CIRA verifying the towns claim to the name; the
letter should:

    a) be written on the city/town’s letterhead
    b) state that the town is the registrant for the domain {{domain}}
    c) officially name someone from the town’s administration to be the administrative contact
       for the domain (include relevant contact information such as job title, relation to the
       town, email address, phone number)
    d) be signed by a person with signing authority for the town; this person CANNOT be the
       person listed as the admin contact

You should send this to CIRA at: 613-237-0534
You should also fax a copy to Tucows at 416-535-5584

.ca Name Variations

Once a .ca name (or it’s provincial variant) has been registered, all other variants of that name
are blocked to other registrants. For example, if the name smith.on.ca was registered to Jessica
Smith, then only Jessica Smith could register smith.qc.ca (or any other provincial variant) or
smith.ca

Jessica Smith can order any and all of the other variants of her name by linking the new
registration request to the existing CIRA profile as explained in section 8.12.

Jessica Smith can also grant permission to any other party that is eligible for .ca names to
register one or some of the other variants of her name.

To place a request for a ‘blocked’ name, simply enter the order as your normally would for a .ca
name. Our systems will determine that the name has other variants, and will engage the blocker
process. The system emails the administrative contacts of all the ‘blocking’ domains to get their


               Page 85 of 174 - Release Version 2.56 - support@opensrs.org
approval. If all blocking parties agree to grant the new name to your Registrant, our system will
send the registration command to CIRA.

NOTE: in our experience, successful registration of blocked domains is quite rare; most
registrants do not seem to be interested in complying with CIRA’s processes, and either ignore or
reject such requests.

 8.14 .ca Registrar Transfers via the RWI

To transfer .ca names from other registrars to Tucows via the Reseller Web Interface, simply
click on the new Place .ca Transfer Manually link in the .CA Orders section of the Reseller Web
Interface (found at http://resellers.opensrs.net). You will notice that the transfer form looks
considerably different than other OpenSRS transfer forms; this is because contact and
nameserver information does not change during the course of a ca registrar transfer. If the
administrative contact approves the transfer request, the name is simply transferred to Tucows
and one year is added to the registration; contact changes may be initiated once the domain
transfer is completed.

The .ca transfer form is shown below:




Notes:

1) The username and password may be completely new, resulting in the domain being inserted
into a new OpenSRS profile, or may be of an existing profile, resulting in the name being added
to an existing domain profile.

2) the order may be processed immediately, or placed in your Pending Orders table, as specified
by your criteria in the ‘Action’ drop down box.

Once the order has been placed, you can review it’s progress in the ‘View Orders in Progress’
section of the RWI, as well as in the appropriate ‘Transfers’ view in the RWI.

 8.15 .ca registrar transfers through the PERL client code.

Please refer to the latest version of the PERL Client Manual for full information on how to place a
.ca registrar transfer order through the PERL Client.




              Page 86 of 174 - Release Version 2.56 - support@opensrs.org
In general, orders placed using the existing Transfer forms will result in a registrar transfer being
initiated; however, NO contact or nameserver information will be taken along with the order
(since contact and nameserver information cannot be changed during a registrar transfer). A
new template has been provided for .ca transfers.

If you download our newest client, you will get this template; if you do not, the registrant will see
the existing Transfer template, which allows them to enter contact and nameserver information
even though it will not be used. Any contact and nameserver information added will be
dropped, and the transfer will proceed.

Once the order has been processed, it can be tracked via the RWI, and by using the ‘Check
Transfer’ command through the API.

 8.16 .ca Registrar Transfer Process.

The following diagram shows the .ca registrar transfer process:


                                                     O penS RS
 M oney is put on hold here                      receives order via     .ca R egistrar Tran sfer P rocess
                                                     RW I/RC L



                                                  E m ail is sent to
                                                        listed                               M oney is taken off hold and
                                                   adm instrative                               returned to Reseller's
                                                 contact to approve                                    account
                                                      transfer




                                                  A pprove witin 7
                                                                        No         O rder C ancelled
                                                       days




                                                        Y es


                                                  Transfer R equest
                                                 sent to C IRA /C IRA
                                                    em ails adm in
                                                  contact a second
                                                   approval notice                           M oney is taken off hold and
                                                                                                returned to Reseller's
                                                                                                       account




                                                  A pprove witin 7
                                                  days with CIRA
                                                                        No         O rder C ancelled
                                                      UserID /
                                                     P assword



                                                        Y es




                  M oney is taken off hold and       O penS RS
                     charged to R eseller's          Com pletes
                            account                   Transfer




8.17 Registrar Transfer Status Codes

The following status codes apply to .ca registrar transfers:




                    Page 87 of 174 - Release Version 2.56 - support@opensrs.org
                  OpenSRS Status Code             Meaning

                  Pending Owner Approval          The OpenSRS email has been
                                                  sent to the listed administrative
                                                  contact for the domain for their
                                                  approval .
                  Pending Registry Approval       The admin contact has
                                                  approved the OpenSRS request,
                                                  and we have sent the transfer
                                                  request on to CIRA; at this
                                                  point, the admin contact must
                                                  approve CIRA’s confirmation
                                                  request using the CIRA
                                                  UserID/Password originally
                                                  provided by CIRA when the
                                                  domain was registered.
                  Completed                       This means that the registrar
                                                  transfer is complete, and that
                                                  the domain has been renewed.
                  Cancelled                       This means that the order
                                                  either:
                                                      a) timed out
                                                      b) was cancelled by the
                                                           admin contact (at the
                                                           OpenSRS level)
                                                      c) was cancelled by the
                                                           admin contact (at the
                                                           CIRA level).
                                                  The precise reason will be
                                                  recorded in the Order Notes.

 8.18 Resending the CIRA username and password to the Registrant.

It’s possible that you or your clients will have misplaced the CIRA user ID and password that is
required to complete the CIRA authorization. If that is the case, you can resend the information
to the administrative contact by:

    a) querying the name (through View Domain feature in the RWI)
    b) Scroll down to the bottom of the record, and find the “Send Request to CIRA to resend a
       password to the registrant's admin contact” link, and click it.

NOTE: In order for your clients to successfully transfer their .ca names to you, they will need
their CIRA username/password to approve CIRA’s authorization request. They will need to obtain
this from their current registrar.

 8.19 Forcing the completion of Registrar transfers

It’s possible that you will find that CIRA shows that Tucows is now the registrar for a particular
name you are transferring here, but that our order will still show as ‘Pending Registry Approval’;
Resellers are now able to force the OpenSRS to query CIRA to see whether the Registrar has
been set to Tucows or not. If, because a reseller has initiated such a check, we find that the
registrar is now Tucows, we will complete the order immediately.




              Page 88 of 174 - Release Version 2.56 - support@opensrs.org
To check the status of a transfer order that is ‘Pending Registry Approval’, click on the domain
name from the ‘Waiting Registry Approval’ view, scroll down to the bottom of the page, and click
the ‘Check Transfer’ button.

Note: This feature will work for gTLD transfers that are ‘Pending Registry Approval’ as well.

 8.20 .ca transfers Reseller Messaging

.ca names are now included in all Reseller Transfers messaging; these features are fully
explained in the latest version of the OpenSRS New User Guide.

 8.21 .ca transfers End User Messaging

Because OpenSRS has no power to stop transfers away from us to other registrars, End User
Messaging is disabled for .ca transfers to other registrars.

The listed administrative contact for the domain will receive all other messages as specified in the
gTLD Renewal Messaging section of the latest OpenSRS New User Guide
 8.22 .ca transfers away from your Reseller profile

Once a .ca domain has been transferred away from your Reseller profile, it will be marked as
‘Deleted-Transferred’ and can be found using the Search Domain feature on ‘All Deleted’ or
‘Deleted Transferred’ domains, in the RWI.

 8.23 CIRA and OpenSRS: other consideration with transfers

    1. OpenSRS treats .ca transfers as individual transfer requests; even transfers submitted in
       bulk will result in individual confirmation requests (both from OpenSRS and from CIRA)
       being sent to the domains administrative contact.

    2. CIRA uses the concept of a Registrant Profile which may contain a number of .ca
       domains. It is possible to for one registrant profile to contain domains hosted at different
       CIRA registrars; each Registrar who sponsors one of these domains may submit changes
       to the main profile, and once those changes are accepted, they apply to ALL domains
       that are contained within that Registrant Profile at CIRA. To break a domain out of a
       CIRA registrant profile (as opposed to an OpenSRS domain profile) a CIRA Registrant
       Transfer is required. To initiate a CIRA Registrant Transfer, please contact
       support@opensrs.org.

 8.24 .ca Reseller to Reseller Transfers

Transferring .ca names between Tucows resellers follows a similar process to .ca registrar
transfers; however, since everything is local to OpenSRS, no CIRA confirmation step is required.

Reseller transfer orders are entered into the RWI and RCL in exactly the same way as Registrar
transfer orders; a domain year is still charged to the Reseller, and the domains registration period
is extended for one domain year.

The following diagram shows the Reseller transfer process for .ca names:




              Page 89 of 174 - Release Version 2.56 - support@opensrs.org
                                                 O penSR S
                                                                      .ca R eseller to R eseller Tran sfer
 M oney is put on hold here                  receives order via
                                                 RW I/R CL                         P rocess


                                              E m ail is sent to
                                                    listed
                                               adm instrative        M oney is taken off hold
                                             contact to approve      returned to Reseller's
                                                  transfer                   account




                                              A pprove witin 7
                                                                      No                O rder C ancelled
                                                   days




                                                    Y es



            M oney is taken off hold and        O penSR S
               charged to Reseller's            Com pletes
                      account                    Transfer



 8.25 .ca Reseller Transfer Pricing

.ca Reseller to Reseller transfers extend the domain for one year, and charge one year to the
Gaining Reseller’s account. One .ca domain year costs $19 US.

In the event that the .ca domain already has the registry maximum of 10 years, the Reseller is
still charged, but no renewal is processed.

 8.26 .ca Reseller Transfer Status Codes

The following status codes apply to .ca reseller transfers:

                       OpenSRS Status Code             Meaning

                       Pending Owner Approval          The OpenSRS email has been
                                                       sent to the listed administrative
                                                       contact for the domain for their
                                                       approval .
                       Pending Registry Approval       In Reseller transfers, this state
                                                       actually means that the
                                                       administrative contact has
                                                       approved the transfer, but that
                                                       OpenSRS has not yet renewed
                                                       the domain. No .ca domain
                                                       undergoing a reseller transfer
                                                       should be in this state for
                                                       longer than five minutes. If you
                                                       find a domain that remains in
                                                       this state, it means that for
                                                       some reason, OpenSRS is
                                                       having trouble renewing the
                                                       domain at CIRA. If this state
                                                       persists, contact
                                                       support@opensrs.org.



                   Page 90 of 174 - Release Version 2.56 - support@opensrs.org
                Completed                       This means that the reseller
                                                transfer is complete, and that
                                                the domain has been renewed.
                Cancelled                       This means that the order
                                                either:
                                                    a) timed out
                                                    b) was cancelled by the
                                                         admin contact (at the
                                                         OpenSRS level)

                                                The precise reason will be
                                                recorded in the Order Notes.

 8.27 .ca Reseller transfers Reseller Messaging

.ca names are now included in all Reseller Transfers messaging; these features are fully
explained in the latest version of the OpenSRS New User Guide.
 8.28 .ca Reseller transfers End User Messaging

The listed administrative contact for the domain will receive all RSP2RSP transfer messages as
specified in the gTLD Renewal Messaging section of the latest OpenSRS New User Guide.
 8.29 .ca transfers away from your Reseller profile

Once a .ca domain has been transferred away from your Reseller profile, it will be marked as
‘Deleted-Transferred’ and can be found using the Search Domain feature on ‘All Deleted’ or
‘Deleted Transferred’ domains, in the RWI.
 8.30 Managing .ca Registrations

We have enabled the Manage domain interface and scripts to work with CIRA and make changes
to .ca domain names. However, there are some important things to keep in mind:

    a) we are not the authoritative source of WHOIS information for .ca domains; CIRA is.
       Because of this, CIRA is the authority for all .ca contact and nameserver information.
       Your clients will be able to change and review all .ca information through the Manage
       Domain interface, but the information is pulled ‘live’ from the CIRA WHOIS database and
       at no time is the OpenSRS database updated to reflect these changes. Again, all
       information for .ca domains that the registrant can see through the Manage Domain
       interface is pulled LIVE from the CIRA database.

        CIRA’s WHOIS server is available at:
        http://www.cira.ca/en/home.html

    b) Certain updates are considered ‘critical’ and require registrant confirmation; these
       include:
       i) Any change to the Administrative Contact
       ii) Changes to Legal Type

        Upon receiving requests to change any of these fields, CIRA will send a confirmation
        email to the Administrative Contact that they will have to act upon to complete the
        modification. Administrative Contacts will be instructed to visit a CIRA web site, and enter
        their Account ID and Secret CIRA password to confirm the changes; these pieces of
        information are provided to the Administrative Contact when they originally registered



              Page 91 of 174 - Release Version 2.56 - support@opensrs.org
         the domain.

    c) Currently changes cannot be applied ‘en masse’ between .ca domains and domains in
       other TLDs, regardless of whether they are in the same OpenSRS profile or not.

    d) CIRA does not support the notion of a billing contact; we have removed this heading
       from the manage interface when a .ca name is being managed.

    e) Many elements of the CIRA WHOIS are CIRA specific, so you will notice new and
       different fields in the Organization, Administrative and Technical contact sections of the
       manage domain interface.

    Non-critical updates are completed in ‘real-time’ and can be viewed through the Manage
    interface and WHOIS as soon as they are made.

    To manage a .ca domain, direct your clients to:
    https://manage.opensrs.net/

    ….or to your implementation of the newest manage.cgi. They will log into the Manage
    interface using the domain name, and their OpenSRS Username and Password. NOTE: They
    do NOT use their CIRA Account ID and Secret Password; these are used to confirm critical
    updates only.

 8.31 .ca Renewals

The following sections explain the .ca renewal processes and systems.

 8.32 .ca renewal considerations

.ca renewal functionality has been added to the existing gTLD renewal systems. .ca renewal
functionality can now be found in all the places that we’ve implemented .com renewal
functionality, including:

    a)   Views for 60, 30, 0, Past Due, Deleted Names
    b)   Email Reminders for 60, 30, 0, Past Due to Reseller
    c)   Email Reminders for 60, 30, 0, Past Due to Registrant
    d)   Email Confirmation to Registrants/Resellers to confirm successful domain renewal
    e)   Bulk Renewals
    f)   Ability to set names for auto-renewal
    g)   Ability to set names for NON-renewal
    h)   .ca renewals through the client/RWI

Assuming all the features of the system are enabled, the typical renewal cycle is as follows:

    e) Reminder emails are sent to the registrant and the Reseller 60, 30, and 0 days before the
       domains expiry
    f) The registrant either contacts the Reseller and orders a domain renewal, or requests the
       renewal online through the Resellers renewal scripts
    g) Once the domain is renewed, an email confirmation is sent to both the registrant and the
       Reseller

The following diagram represents this process:




              Page 92 of 174 - Release Version 2.56 - support@opensrs.org
                                 D ay 60                D ay 30             D ay 0                 D ay -30




                                                                                         Em ail Confirm ation
       M SP        Em ail Rem inder       Em ail Rem inder    Em ail Rem inder



                                      1                                     2        3



   R egistrant     Em ail Rem inder       Em ail Rem inder    Em ail Rem inder            Em ail Confirm ation

                    1   N am e Renews if Auto-Renew set to on
                    2   N am e Renewed (date arbitrary for this diagram )

                    3   N am e Deleted if not renewed by day -30




Note that .ca names are deleted 30 days past their expiry date (in the absence of a renewal
command) and not 40 as with .com/.net/.org names.

Another key difference with .ca names is that CIRA will also email the registrant to remind
them that their name is coming up for renewal. CIRA explanation of their procedure
follows:

                        !   If the registration period has not been renewed 60 days prior to the
                            expiry date of the registration period, CIRA will advise the Registrar of
                            record by email or a web-based report of the expiry date of the
                            Registration. The Registrant will also be sent an email advising it of the
                            expiry date;


                        !   If the registration period has not been renewed 30 days prior to the
                            expiry date of the registration period, CIRA will advise both the
                            Registrant and the Registrar of record that the Registration is due to
                            expire within 30 days;


                        !   If the registration period has not been renewed seven (7) days prior to
                            the expiry date of the registration period, CIRA will send a final advisory
                            email message to the Registrant and the Registrar of record that the
                            Registration is due to expire within seven (7) days; and


                        !   If the Registration has not been renewed by its expiry date, the
                            Registration will be automatically suspended from the expiry date of the
                            registration period for a period of 30 days. Both the Registrant and its
                            Registrar of record will be advised of this suspension by email. The
                            effect of a suspension of a Registration is described in Section 6.10 of
                            the Registrant Agreement. Essentially, the effect is that an Internet user
                            will not be able to send email or access a web page which incorporates
                            the registered domain name until the Registration is reactivated.


                 Page 93 of 174 - Release Version 2.56 - support@opensrs.org
NOTE: In all cases, .ca renewal management is an extension of the gTLD renewal management
features. If, for example, your renewal messaging is enabled for .com/.net/.org, the same
messages will be used for .ca names. PLEASE MAKE SURE to modify your messages to
address your .ca registrants. Specifically, make sure that you note the term post
expiry that a registrant can still renew their name as 30 and not 40 days.

 8.33 Ability to set .ca names for NON-renewal

Names can only be set for ‘non-renewal’ individually, while looking at the domain record linked
from the View Active Domains view or one of the renewals views. NOTE: A .ca domain set for
non-renewal will be deleted 30 days after the domains expiration date. A domain can
be taken off ‘non-renewal’ status by clicking on the domain name from the View Active Domains
or Renewals tables, and selecting either:

        c) Normal Notification
        d) Auto-Renew

This feature is useful if you know that your client is not interested in renewing a domain name,
and you want to prevent the system from including them in any automated emails sent to your
clients.

CIRA, the .ca registry adds a further administrative step to the ‘non-renewal’ process. As always,
they insist on confirming the registrant’s request. Once a .ca name is set to ‘non-renewal’ in the
OpenSRS, CIRA will send the administrative contact an email asking them to confirm their
intention. If the administrative contact does not confirm their request at the CIRA confirmation
site (using the CIRA username and password associated with the domain) the they will continue
to receive CIRA renewal notices (though no OpenSRS notices will go out.)

If a name set to NON renewal at CIRA is, in fact, renewed, the ‘non-renewal’ setting at CIRA is
cleared, and normal renewal messaging will resume once the domain approaches it’s next expiry
date.

 8.34 .ca Renewal Pricing

.ca renewals cost the same as new .ca domain registrations; $18 USD per domain year.

 8.35 .ca Transfer of Domain Ownership, or .ca Registrant
Transfers, or .ca Registrant Organization Name Changes

CIRA’s domain ownership transfer procedure essentially consists of an organization name
change, or more properly, a Registrant change. This cannot be done using manage.opensrs.net,
and must be initiated through a request to our support team.

There are three distinct variations in this are, and the break down as follows:

    a) domain transfer to new registrant, both old and new registrants with Tucows
    b) domain transfer to new registrant, old registrant with Tucows, new with another
       Registrar
    c) domain transfer to new registrant at Tucows, old registrant at another Registrar.

a) domain transfer to new registrant, both old and new registrants with Tucows




              Page 94 of 174 - Release Version 2.56 - support@opensrs.org
During the process a new registrant is created, and the name is transferred between registrants.
At the present, this process has not been built in to the OpenSRS system and must be processed
through Support.

For now, email this type of registrant change request to support@opensrs.org, and include:

    a) Reseller Username
    b) Domain name
    c) Indication that you understand one domain year will be charged for this request, and
       that the domain will be renewed for one year.
    d) Complete information for the NEW registrant (include all information that differs from the
       old registrant)

Once Tucows administrative staff have initiated this request, CIRA will:

    a) email the LOSING registrant to confirm the transaction
    b) email Tucows to confirm the transaction (we monitor this, and complete all outstanding
       transactions that we have initiated.
    c) Email the GAINING registrant to confirm the transaction.

Once steps a through c are completed, Tucows will insert the domain into your Reseller profile
with a random username and password.

b) domain transfer to new registrant, old registrant with Tucows, new with another
Registrar

This will, essentially, result in the domain being transferred away from Tucows, to a different
registrant at another registrar, but Tucows must initiate this process.

Email this type of registrant change request to support@opensrs.org, and include:

        a) Reseller Username
        b) Domain name
        c) Name of New Registrar

Once Tucows administrative staff has initiated this request, CIRA will:

        a) email the LOSING registrant to confirm the transaction
        b) email Tucows to confirm the transaction (we monitor this, and complete all
           outstanding transactions that we have initiated.
        c) Email the GAINING registrant to confirm the transaction.
        d) Email the GAINING Registrar to confirm this transaction.

Once steps a through c are completed, the new Registrar will be sponsoring the domain that was
transferred to their registrant.

c) domain transfer to new registrant at Tucows, from a registrant at another
Registrar.

This type of transfer must be initiated at the OTHER registrar. If you are attempting this type of
transfer, please send an email to OpenSRS Support to inform us that the transaction will be
taking place. Include:




              Page 95 of 174 - Release Version 2.56 - support@opensrs.org
    a) the domain name
    b) Reseller Username
    c) The Date that you ordered the Registrant Transfer from the Other Registrar

NOTE: We realize that this approach to transfers is particularly Reseller ‘unfriendly’; we are
lobbying CIRA to change this process.


 8.36 .ca Deletion Requests

This applies to domains that have been registered and confirmed and show upon the CIRA
WHOIS.

Only a REGISTRANT can have a registration cancelled.

The procedure is as follows:
   1) Please ask the registrant's admin contact to email the cancellation request to
       ecac@cira.ca
   2) CIRA will ECHO this message to the admin contact email address and ask it to re-confirm
       this request.
   3) If the ECHO is acknowledged we will cancel the registration and refund the charges
   4) If the ECHO is not acknowledged nothing will happen.

Tucows will refund the Reseller if the deletion takes place within 5 days of the registration;
otherwise, the transaction is non-refundable.

 8.37 .ca Pricing

Tucows Resellers will be charged $18.00 US per domain year.

After an initial request is submitted, the OpenSRS system will place ‘on hold’ the appropriate
amount. Once the domain is officially registered with CIRA, the cost of the registration is taken
off hold and deducted from the Reseller’s account. If the domain registration fails for any reason,
the cost of registration is returned to the Reseller’s account.

8.38 GST

GST refers to the "Goods and Services Tax” tax levied by the Canadian government. We charge
GST to our Canadian Resellers when they remit payments to us, so the tax is properly collected
at that point.

Resellers outside Canada have no obligation to pay GST to Tucows. We recommend that
Resellers outside of Canada consult a local tax professional for advice on how to handle taxes as
they relate to .ca registrations.

 8.39 Canadian Presence Requirements for Registrants


1.      Overview. After public consultation, CIRA has determined that the .ca domain space
should be developed as a key public resource for the social and economic development of all
Canadians. Accordingly, persons who wish to register a .ca domain name or sub-domain name
on and after the Operational Transfer Date (when the University of British Columbia (“UBC”)
transfers operation of the .ca registry to CIRA) must meet certain Canadian Presence
Requirements.



              Page 96 of 174 - Release Version 2.56 - support@opensrs.org
              While the Canadian Presence Requirements for Registrants set out below still
require a connection to Canada, they will enable a much broader group of persons to register a
.ca domain name than under the existing rules of UBC.

               Existing Registrants under the UBC system will not have to meet these Canadian
presence requirements when they apply to re-register with CIRA a domain name that is the
subject of an existing registration. CIRA hopes this will make it easier for existing registrants of
the registry operated by UBC when they apply to CIRA for a new registration prior to the
Operational Transfer Date.

                CIRA is committed to reviewing these Canadian Presence Requirements from time
to time in order to ensure they remain in the best interests of Canadians and the .ca registry.

2.       Canadian Presence Requirements. On and after the Operational Transfer Date only
the following individuals and entities will be permitted to apply to CIRA (through a CIRA certified
registrar) for the registration of, and to hold and maintain the registration of, a .ca domain name:

Canadian citizen. A Canadian citizen of the age of majority under the laws of the province or
territory in Canada in which he or she resides or last resided;

Permanent resident. A permanent resident as defined in the Immigration Act (Canada) who is
ordinarily resident in Canada (as defined below) and of the age of majority under the laws of the
province or territory in Canada in which he or she resides or last resided;

Legal representative. An executor, administrator or other legal representative of the Persons
listed in paragraph (a) and (b) above;

Corporation. A corporation under the laws of Canada or any province or territory of Canada;

Trust. A trust established and subsisting under the laws of a province or territory of Canada,
more than 66 2/3 % of whose trustees meet one of the conditions set out in paragraphs (a) to
(d) above;

Partnership. A partnership, more than 66 2/3 % of whose partners meet one of the conditions
set out in paragraphs (a) to (e) above, which is registered as a partnership under the laws of any
province or territory of Canada;

Association. An unincorporated organization, association or club:

                  (i)     at least 80% of whose members: (A) are ordinarily resident in Canada
                        (if such members are individuals); or (B) meet one of the conditions set
                        out in paragraphs (a) to (f) above (if such members are not individuals);
                        and

                 (ii)    at least 80% of whose directors, officers, employees, managers,
                        administrators or other representatives are ordinarily resident in Canada;

Trade union. A trade union which is recognized by a labour board under the laws of Canada or
any province or territory of Canada and which has its head office in Canada;

Political party. A political party registered under a relevant electoral law of Canada or any
province or territory of Canada;




              Page 97 of 174 - Release Version 2.56 - support@opensrs.org
Educational institution. Any of the following: (i) a university or college which is located in
Canada and which is authorized or recognized as a university or college under an Act of the
legislature of a province or territory of Canada; (ii) a college, post-secondary school, vocational
school, secondary school, pre-school or other school or educational institution which is located in
Canada and which is recognized by the educational authorities of a province or territory of
Canada or licensed under or maintained by an Act of Parliament of Canada or of the legislature of
a province or territory of Canada;

Library, Archive or Museum. An institution, whether or not incorporated, that (i) is located in
Canada and (ii) is not established or conducted for profit or does not form part of, or is not
administered or directly or indirectly controlled by, a body that is established or conducted for
profit, in which is held and maintained a collection of documents and other materials that is open
to the public or to researchers;

Hospital. A hospital which is located in Canada and which is licensed, authorized or approved to
operate as a hospital under an Act of the legislature of a province or territory of Canada;

Her Majesty the Queen. Her Majesty Queen Elizabeth the Second and her successors;

Indian band. Any Indian band as defined in the Indian Act, R.S.C. 1985, c. I-5, as amended
from time to time, and any group of Indian bands;

Aboriginal Peoples. Any Inuit, First Nation, Metis or other people indigenous to Canada, any
individual belonging to any Inuit, First Nation, Metis or other people indigenous to Canada and
any collectivity of such Aboriginal peoples;

Government. Her Majesty the Queen in right of Canada, a province or a territory; an agent of
Her Majesty the Queen in right of Canada, of a province or of a territory; a federal, provincial or
territorial Crown corporation, government agency or government entity; and a regional, municipal
or local area government;

Trade-mark registered in Canada. A Person which does not meet any of the foregoing
conditions, but which is the owner of a trade-mark which is the subject of a registration under
the Trade-marks Act (Canada), but in this case such permission is limited to an application to
register a .ca domain name consisting of or including the exact word component of that
registered trade-mark; or

Official marks. A Person which does not meet any of the foregoing conditions, but which is a
Person intended to be protected by Subsection 9(1) of the Trade-Marks Act (Canada) at whose
request the Registrar of Trade-marks has published notice of adoption of any badge, crest,
emblem, official mark or other mark pursuant to Subsection 9(1), but in this case such
permission is limited to an application to register a .ca domain name consisting of or including
the exact word component of such badge, crest, emblem, official mark or other mark in respect
of which such Person requested publications.

2.      For the purposes of this policy:

        (a)     “ordinarily resident in Canada” means an individual who resides in Canada
                for more than 183 days in the twelve month period immediately preceding the
                date of the applicable application for registration of the .ca domain name or sub-
                domain name and in each twelve month period thereafter for the duration of the
                domain name registration; and




              Page 98 of 174 - Release Version 2.56 - support@opensrs.org
        (b)     “Person” includes an individual, a corporation, a partnership, a trust, an
                unincorporated organization, association or club, the government of a country or
                any political subdivision thereof, or any agency or department of any such
                government, and the executors, administrators or other legal representatives of
                an individual in such capacity, a “person” as defined in the Trade-marks Act
                (Canada) and a Person intended to be protected by Subsection 9(1) of the
                Trade-marks Act (Canada).

3.               Notwithstanding paragraph 1 above, each registrant of a .ca domain name or
sub-domain name registration which is registered in the .ca registry operated by UBC prior to the
Operational Transfer Date shall be deemed to satisfy the Canadian presence requirements
described in paragraph 1 above with respect only to an application by such registrant to CIRA to
register such .ca domain name or sub-domain name.

 8.40 What Registrant Name rules apply to the various legal types?

CIRA explains that the following rules should be followed with respect to the format of the
Registrant name (Organization name in the OpenSRS system) as it relates to the Legal Type
chosen.

The various allowable legal types follow immediately below, with in depth explanations of
allowable Registrant names for each type.

Corporation (Canada or Canadian province or territory) (CCO)
Canadian citizen (CCT)
Permanent Resident of Canada (RES)
Government or government entity in Canada (GOV)
Canadian Educational Institution (EDU)
Canadian Unincorporated Association (ASS)
Canadian Hospital (HOP)
Partnership Registered in Canada (PRT)
Trade-mark registered in Canada (by a non-Canadian owner) (TDM)
Canadian Trade Union (TRD)
Canadian Political Party (PLT)
Canadian Library, Archive or Museum (LAM)
Trust established in Canada (TRS)
Aboriginal Peoples (individuals) indigenous to Canada (ABO)
Aboriginal Peoples (groups) indigenous to Canada (ABO)
Indian Band recognized by the Indian Act of Canada (INB)
Legal Representative of a Canadian Citizen or Permanent Resident (LGR)
Official mark registered in Canada
Her Majesty the Queen

Descriptions of Registrant Types

It appears that many registrants do not understand the requirements for the Registrant Type
they have chosen. CIRA has provided the following information to help correct this problem. This
text contains the official definition, what is expected by the Registry and examples of acceptable
and unacceptable registrant names for the Type.

Corporation (Canada or Canadian province or territory)

Definition: A corporation under the laws of Canada or any province or territory of Canada



              Page 99 of 174 - Release Version 2.56 - support@opensrs.org
Requirements: Registrant name must be the full legal name of the corporation and must be
followed by the jurisdiction of incorporation (eg. Canada, Ontario, NWT….) unless it is obvious
from the corporation’s name.

Examples of Valid Registrant Names for this Registrant Type:

123745 Canada Inc.
Smith Corp. of Ontario
Smith Ltée. Canada

Examples of Invalid Registrant Names for this Registrant Type:

Smiths
Smiths Consulting
Smiths Kennel
Smiths Corp.
Leatra SP

Canadian citizen:

Definition: A Canadian citizen of the age of majority under the laws of the province or territory in
Canada in which he or she resides or last resided

Requirements: The Registrant’s name must be the full legal name of the Canadian Citizen who
will hold the domain name registration as the name would appear on a passport, driver’s license
or other identification document issued by a government.

The name may be followed by a space and “o/a xxxx” where “o/a” stands for “Operating As”
and “xxxx” can be any alpha-numeric string designated by the applicant and subject to applicable
rules and length restrictions (e.g. “John Doe o/a Doe Consulting Group”) . The name may also be
followed by a space and a degree granted to the registrant by a recognized degree granting
institution or a recognized professional designation which the registrant has the right to use (eg.
PhD, MD, DDS.)

Full legal names of individuals may only consist of alphabetic characters and the special
characters: single quote mark(‘’), hyphen(-), period(.).

Examples of Valid Registrant Names for this Type:

                John Doe
                Fred-Albert Doon PhD
                Bernard St-James o/a St-James Services

Examples of Invalid Registrant Names for this Registrant Type:

John
                J. Doe
        None
        Personal
        (blank)
        Cool Gal
        Domain Administrator
        St-James Services



              Page 100 of 174 - Release Version 2.56 - support@opensrs.org
        Acme Sales Inc.

Permanent Resident of Canada:

Definition: A permanent resident as defined in the Immigration Act (Canada) R.S.C. 1985, c.I-2,
as amended from time to time, who is “ordinarily resident” in Canada and of the age of majority
under the laws of the province or territory in Canada in which he or she resides or last resided.
(“Ordinarily resident in Canada” means an individual who resides in Canada for more than 183
days in the twelve month period immediately preceding the date of the applicable request for
registration of the .ca domain name or sub-domain name and in each twelve month period
thereafter for the duration of the domain name registration.)

Requirements: The Registrant’s name must be the full legal name of the Permanent Resident
who will hold the domain name registration as the name would appear on a driver’s license or
other identification document issued by a government.

The full legal name may be followed by a space and “o/a xxxx” where “o/a” stands for
“Operating As” and “xxxx” can be any alpha-numeric string designated by the applicant and
subject to applicable rules and length restrictions (e.g. “John Doe o/a Doe Consulting Group”).
The name may also be followed by a space and a degree granted to the registrant by a
recognized degree granting institution or a recognized professional designation which the
registrant has the right to use (eg. PhD, MD, DDS.)

Full legal names of individuals may only consist of alphabetic characters and the special
characters: single quote mark(‘’), hyphen(-), period(.).


Examples of Valid Registrant Names for this Type:

                Jessica Smith
                Fred-Albert Doon DDS
                Bernard St-James o/a St-James Services


Examples of Invalid Registrant Names for this Type:

John
John 7
J. Doe
F.A.D
Cool Gal
        St-James Services
        Acme Sales Inc.

Government or government entity in Canada:
Definition: Her Majesty the Queen in right of Canada, a province or a territory; an agent of Her
Majesty the Queen in right of Canada, of a province or of a territory; a federal, provincial or
territorial Crown corporation, government agency or government entity; or a regional, municipal
or local area government.
Requirements: The Registrant’s name must be the complete official name of the entity that will
hold the domain name registration, without any abbreviations. (A common abbreviation may
follow the official name in parentheses). If the Registrant is not a government, the Registrant’s




             Page 101 of 174 - Release Version 2.56 - support@opensrs.org
name must be followed by the name of the jurisdiction (eg. Canada, province, territory,
municipality, etc) to which the Registrant is related.

Examples of Valid Registrant Names for this Type:

Government of Alberta
Export Development Corporation (EDC) (Canada)
Deposit Insurance Corporation of Ontario (DCIO)
The Corporation of the City of Toronto

Examples of Invalid Registrant Names for this Type:

Toronto Sales Are Us Inc.
DCIOPEI
John Doe

Canadian Educational Institution:
       Definition:

(i)      a university or college which is located in Canada and which is authorized or recognized
as a university or college under an Act of the legislature of a province or territory of Canada; or
(ii)     a college, post-secondary school, vocational school, secondary school, pre-school or
other school or educational institution which is located in Canada and which is recognized by the
educational authorities of a province or territory of Canada or licensed under or maintained by an
Act of Parliament of Canada or of the legislature of a province or territory of Canada.
Requirements: The Registrant’s name must be the complete official name of the institution that
will hold the domain name registration, without any abbreviations. A common abbreviation may
follow the official name in parentheses. The Registrant name must be followed by the jurisdiction
(e.g. name of province, municipality) in which the institution is accredited if not obvious from the
Registrant’s name.

Examples of Valid Registrant Names for this Type:

        University of British Columbia (UBC)
        St-John’s Middle School of Ottawa
        Advanced Languages Institute of Ontario (ALI)(Ontario)

Examples of Invalid Registrant Names for this Type:

        Sandhill Secondary School
        Sales Are Us Inc.
        UBC Student Association
        Professional Association of Teaching Professionals of UdeM
        Joe Smith

Canadian Unincorporated Association:
Definition: This Registrant Type is principally intended for religious congregations, social and
sports clubs and community groups which are based and operating in Canada.
An unincorporated organization, association or club:
(i)      at least 80% of whose members: (A) are ordinarily resident in Canada (if such members
are individuals); or (B) meet the requirements of any one of the following Registrant Types:
Corporation (Canada or Canadian province or territory), Canadian citizen, Permanent Resident of




             Page 102 of 174 - Release Version 2.56 - support@opensrs.org
Canada, Partnership Registered in Canada, Trust established in Canada, Legal Representative of
a Canadian Citizen or Permanent Resident; and
(ii)    at least 80% of whose directors, officers, employees, managers, administrators or other
representatives are ordinarily resident in Canada.

Requirements: The Registrant’s name must be the complete name of the association that will
hold the domain name registration, without any abbreviations. (A common abbreviation may
follow the complete name in parentheses).

Examples of Valid Registrant Names for this Type:

St-Alban’s Reformed Church of Victoria
Archdiocese of Montréal
Sun Youth Montréal
Citizens for the Protection of the Red River
Toronto Junior Soccer Association

Examples of Invalid Registrant Names for this Type:

ACDEN
                St-Patrick’s
                Dartmouth Soccer Club Limited
                John Doe

Canadian Hospital:

Definition: A hospital which is located in Canada and which is licensed, authorized or approved to
operate as a hospital under an Act of the legislature of a province or territory of Canada

Requirements: The Registrant’s name must be the complete official name of the hospital that will
hold the domain name registration, without any abbreviations. (A common abbreviation may
follow the complete name in parentheses.) The Registrant’s name must be followed by the
jurisdiction (eg. name of province) which accredited the hospital if not obvious from the
Registrant’s name.

Examples of Valid Registrant Names for this Type:

Royal Victoria Hospital - Québec
Sick Children’s Hospital of Ontario
Veteran’s Hospital Canada, Pointe Claire

Examples of Invalid Registrant Names for this Type:

Dr. John Doe
Jane Doe
John Doe Inc.
SHUL
Nurses Union Local 1455 NHCWA
Manitoba Doctors Against Drugs (MDAD)

Partnership Registered in Canada:




              Page 103 of 174 - Release Version 2.56 - support@opensrs.org
Definition: A partnership, more than 66 2/3 % of whose partners meet the requirements of one
of the following Registrant Types: Corporation (Canada or Canadian province or territory),
Canadian citizen, Permanent Resident of Canada, Trust established in Canada or a Legal
Representative of a Canadian Citizen or Permanent Resident, which is registered as a partnership
under the laws of any province or territory of Canada.

Requirements: The Registrant’s name must be the registered name of the partnership that will
hold the domain name registration. The Registrant name must be followed by the jurisdiction of
registration (eg. Alberta) and the registration number.

Examples of Valid Registrant Names for this Type:

Xenon Partnership (Ontario)
Blake, Cassels and Graydon LLP (Ontario)
John Doe Partnership, British Columbia

Examples of Invalid Registrant Names for this Type:

John Doe Partnership
Mybusiness Inc.
Fred Smith

Trade-mark registered in Canada by non-Canadian owner:

Definition: A Person which does not fall under any other registrant type, but which is the owner
of a trade-mark which is the subject of a registration under the Trade-marks Act (Canada) R.S.C.
1985, c.T-13 as amended from time to time, but in this case such permission is limited to a
request to register a .ca domain name consisting of or including the exact word component of
that registered trade-mark.

This Registrant Type is only intended for Registrants which do not meet the requirements
associated with any other registrant type but which have a trade-mark registered in Canada.
(Trade-marks subject of trade-mark applications and trade-marks registered in other jurisdictions,
such as the United States, do not qualify.)

The domain name to be registered must include the trade-mark. (eg. If the trade-mark is AVEA
this type of registrant can register avea.ca or aveaisus.ca but not xyz.ca).

Requirements: The Registrant’s name must be the complete legal name of the trade-mark owner
(not the trade-mark agent) holding the domain name registration without any abbreviations. (A
common abbreviation may follow the complete name in parentheses.) The applicant must also
insert the Canadian registration number of the trade-mark following the Registrant name.

Examples of Valid Registrant Names for this Type:

Arcuros SPA - TMA1762466

Examples of Invalid Registrant Names for this Type:

Arcuros SPA

Canadian Trade Union:




              Page 104 of 174 - Release Version 2.56 - support@opensrs.org
Definition: A trade union which is recognized by a labour board under the laws of Canada or any
province or territory of Canada and which has its head office in Canada.

Requirements: The Registrant’s name must be the complete official name of the trade union that
will hold the domain name registration, without abbreviations. (A common abbreviation may
follow the official name in parentheses.) The Registrant name must be followed by the
jurisdiction in Canada which recognizes it (if it is not obvious from the Registrant’s name.)

Examples of Valid Registrant Names for this Type:

Confédération des syndicats nationaux (CSN) - Québec
Canadian Union of Postal Workers (CUPW)

Examples of Invalid Registrant Names for this Type:

ZZCEUL local 237
Jean Smith
Sales Are Us Inc.

Canadian Political Party:

Definition: A political party registered under a relevant electoral law of Canada or any province or
territory of Canada

Requirements: The Registrant’s name must be the complete official name of the political party
holding the domain name registration, without abbreviations. (A common abbreviation may
follow the official name in parentheses.) The Registrant name must also by followed by the
jurisdiction in Canada in which it is registered (if it is not obvious from the official name).

Examples of Valid Registrant Names for this Type:

Progressive Conservative Party of Canada (PC)
Union Nationale du Québec
Reform Party - Alberta

Examples of Invalid Registrant Names for this Type:

John Doe
Sales Are Us Inc.
Liberal Party
ACCULD - Ontario
National Liberation Front of Mexico

Canadian Library, Archive or Museum:
Definition: An institution, whether or not incorporated, that:
(i)      is located in Canada; and
(ii)     is not established or conducted for profit or does not form part of, or is not administered
or directly or indirectly controlled by, a body that is established or conducted for profit in which is
held and maintained a collection of documents and other materials that is open to the public or
to researchers.
Requirements: The Registrant’s name must be the complete legal name of the institution which
will hold the domain name registration without abbreviations. (A common abbreviation may
follow the complete name in parentheses.)



              Page 105 of 174 - Release Version 2.56 - support@opensrs.org
Examples of Valid Registrant Names for this Type:

Royal Ontario Museum
Musé des Beaux Arts de Montréal

Examples of Invalid Registrant Names for this Type:

John Doe
Sales Are Us Inc.
My site
Domain Administrator
Biggs Bargain Books

Trust established in Canada:

Definition: A trust established and subsisting under the laws of a province or territory of Canada,
more than 66 2/3 % of whose trustees meet the requirements of one of the following Registrant
Types: Corporation (Canada or Canadian province or territory), Canadian citizen, Permanent
Resident of Canada, or a Legal Representative of a Canadian Citizen or Permanent Resident.

Requirements: The Registrant’s name must be the complete official name of the trust, without
any abbreviations. (A common abbreviation may follow the official name in parentheses.) The
Registrant name must also indicate the total percentage of the trustees that meet one or more of
the following requirements: Canadian citizen, permanent resident, Canadian corporation, legal
representative

Examples of Valid Registrant Names for this Type:

Marie Daigle Trust - (100%)
Arbeit Trust - (70%)

Examples of Invalid Registrant Names for this Type:

John Doe
Sales Are Us Inc.
Arbeit Trust (10%)

Aboriginal Peoples (individuals) indigenous to Canada:

Definition: Any individual belonging to any Inuit, First Nation, Metis or other people indigenous to
Canada.

Requirements: The Registrant’s name must be the full legal name of the Aboriginal Person
applying for the Registration as it would appear on a driver’s license or other identification
document issued by government.

The Registrant may enter its full legal name followed by a space and “o/a xxxx” where “o/a”
stands for “Operating As” and “xxxx” can be any alpha-numeric string designated by the
applicant and subject to applicable rules and length restrictions (e.g. “John Doe o/a Doe
Consulting Group”). The name may also be followed by a space and a degree granted to the
registrant by a recognized degree granting institution or a recognized professional designation
which the registrant has the right to use (eg. PhD, MD, DDS.)



              Page 106 of 174 - Release Version 2.56 - support@opensrs.org
Full legal names of individuals may only consist of alphabetic characters and the special
characters: single quote mark(‘’), hyphen(-), period(.).


Examples of Valid Registrant Names for this Type:

                John Doe
                Fred-Albert Doon DDS
                Bernard St-James o/a St-James Services

Examples of Invalid Registrant Names for this Type:

John
        None
        Personal
        (blank)
        Domain Administrator
        St-James Services Inc.

Aboriginal Peoples (groups) indigenous to Canada:

Definition: Any Inuit, First Nation, Metis or other people indigenous to Canada, and any
collectivity of such Aboriginal peoples.

Requirements: The Registrant’s name must be the complete official name of the indigenous
people a collectivity of Aboriginal Persons or, if there is no official name, the name by which the
collectivity is commonly known.

Examples of Valid Registrant Names for this Type:

        Carrier Sekani Tribal Council

Examples of Invalid Registrant Names for this Type:

        Acme Sales Inc.
Helping Spirit Lodge Society
John Jones

Indian Band recognized by the Indian Act of Canada:

Definition: Any Indian band as defined in the Indian Act, R.S.C. 1985, c. I-5, as amended from
time to time, and any group of Indian bands;

Requirements: The name of Registrant must be the Indian Band Name as registered with the
Department of Indian and Northern Affairs, Canada.

Examples of Valid Registrant Names for this Type:

Lac la Ronge Indian Band

Examples of Invalid Registrant Names for this Type:




              Page 107 of 174 - Release Version 2.56 - support@opensrs.org
                 Mohawk Motors
Sioux Sales Inc.
        Sales Are Us Inc.
                 Jean Gallant

Legal Representative of a Canadian Citizen or Permanent Resident:

Definition: An executor, administrator or other legal representative of a Person listed as a
Canadian Citizen or Permanent Resident of Canada.

Note: This registrant type is only available to a person or entity that has been appointed by legal
process to represent an individual who is not competent to represent him or herself. It is not
available to anyone who represents a Canadian or foreign corporation in any capacity.

Requirements: The Registrant’s name must be the full legal name of the Canadian Citizen or
Permanent Resident of Canada who is being represented as it would appear on a passport,
driver’s license or other government identification document. This must be followed by the full
legal name and capacity of at least one of the official representatives.

Full legal names of individuals may only consist of alphabetic characters and the special
characters: single quote mark(‘’), hyphen(-), period(.).

The representative should be identified as the administrative contact for these registrations.

Examples of Valid Registrant Names for this Type:

John Smith (Jayne Smith, executor)

Examples of Invalid Registrant Names for this Type:

Sales Are Us Inc.
Arlenza SP
Shingle LLP

Official marks registered in Canada:

Definition: A Person which does not meet the requirements for any other Registrant Type, but
which is a Person intended to be protected by Subsection 9(1) of the Trade-Marks Act (Canada)
at whose request the Registrar of Trade-marks has published notice of adoption of any badge,
crest, emblem, official mark or other mark pursuant to Subsection 9(1), but in this case such
permission is limited to a request to register a .ca domain name consisting of or including the
exact word component of such badge, crest, emblem, official mark or other mark in respect of
which such Person requested publications.

Notes: This registrant type is only intended for Registrants which do not meet the requirements
associated with any other registrant type but which have an Official Mark registered in Canada.

The domain name must include the official mark (eg. If the official mark is WIPO, the registrant
can register wipo.ca but not intellectual-property.ca)

Requirements: The Registrant’s name must be the complete official name of the entity holding
the domain name registration without any abbreviations. (A common abbreviation may follow the




              Page 108 of 174 - Release Version 2.56 - support@opensrs.org
complete name in parentheses.) The registration number of the official mark must follow the
Registrant Name.

Examples of Valid Registrant Names for this Type:

The United Nations Educational, Scientific and Cultural Organization (UNESCO) - 0970388

Examples of Invalid Registrant Names for this Type:

John Doe Inc.
Arcuros SPA

Her Majesty the Queen:

Definition: Her Majesty Queen Elizabeth the Second and her successors.

Requirements: The Registrant’s name must be that of Her Majesty the Queen or, after a
succession, the name of her successor.

 9.0 Multilingual Registrations

9.1 Overview & Feature List

For further history and background surrounding Multilingual Domain Registrations, its testbed
and the technologies utilized, please review our Multilingual Domain Name Position Paper
available at our web site. This document is highly recommended to provide customers with a
thorough background surrounding this unique and exciting opportunity.

The OpenSRS client/server package now supports the registration of multilingual domains. This
new feature will support the following languages:

                 Language                            Encoding Scheme
                 All Languages                       UTF-8


New multilingual features in this release include:

Client:
          -       Support for multilingual registrations/management in all supported languages
          -       Bulk registrations of multilingual names.
          -       RACE (Row-Based Character Encoding) conversion tool

Server:
          -       Support for multilingual registrations/management in all supported languages

 9.2 The Multilingual Opportunity

The current Domain Name System (DNS) was developed to facilitate the quick and easy recall of
Internet addresses. This was achieved through the matching of alphabetical names to
complicated and confusing Internet Protocol (IP) numbers. In an effort to simplify standards,
ASCII was adopted as the defacto character-encoding standard for all web and e-mail addresses.
Unfortunately, the ASCII character-encoding scheme does not allow input of non-English




              Page 109 of 174 - Release Version 2.56 - support@opensrs.org
character sets. Therefore, Internet users are required to have some basic knowledge of ASCII
and/or the English language.

This limitation created a knowledge barrier for non-English countries, barring many from the
tremendous opportunities afforded by the Internet for commerce and learning.

One major irony surrounding this subject revolves around the fact that many major software
applications used to navigate the Internet do provide support for virtually every major language,
yet the fact remains that the DNS, a core functionality of the Internet, requires ASCII based input
for navigation. A second irony exists in that the Internet is often hailed as an environment
‘without borders’, but again, its core addressing system was based on English.

In response to the overwhelming demands for Multilingual support, Verisign Global Registry
Services Inc. announced on August 24th 2000 a Test-bed that would allow the registrations of
multilingual Domain names. Tucows expressed its interest to participate shortly thereafter.

This test-bed has been opened to all ICANN accredited registrars who wish to participate, and is
being introduced in a phased approach in order to evaluate the impact of Multilingual Domain
Names on current Internet standards. RACE (Row-based ASCII Capable Encoding) is the schema
chosen to transform non-Roman characters into ASCII type encoding. RACE is based upon an
IETF Internet Draft, which can be found at:

http://www.ietf.org/internet-drafts/draft-ietf-idn-race-03.txt

The Test Bed has been organized into the following phases:

        Phase 1- Registrar Preparation – Aug-Nov 2000

In this phase, the Registry provided specifications for four encoding schemes: GB2312, KSC5601,
BIG5 and Shift-JIS. Tucows has reviewed these specification and conducted research on any
technical areas that remain ambiguous. The OpenSRS product suite has been adapted to accept
and prepare multilingual names for registration. (Note: languages released since the initial four
have been registered using the UTF8 encoding type)

        Phase 2- Multilingual Registrations – Nov 2000-????

This phase involves a certification test for Tucows. We displayed our proficiency in converting
multilingual names to the Race character set for the supported languages. Once this had been
done Tucows was certified to offer Multilingual names. It is important to note that at this point
registrations will not resolve until the next phase.

        Phase 3- Multilingual Domain Name Resolution – ?????

This phase of the test-bed the Registry will take all registrations that were completed in Phase
two and add these new multilingual names to Top Level Domain Zone files in an effort to have
them resolve within the Internet’s DNS infrastructure. At this point, we have no information on
when this phase will begin.

 9.3 Reseller Qualifications

NOTE: To check whether you are currently enabled for multilingual registrations, log into the
reseller interface at: http://resellers.opensrs.net . Once logged in, click on ‘Place Order Manually’.
Once in the manual domain order page, click the language drop down box and find the UTF8



              Page 110 of 174 - Release Version 2.56 - support@opensrs.org
encoding type. If it is not there, please follow the instructions below. There may be other
encoding types as well; this is not a problem.

In order to offer multilingual domain names, each Reseller will be required to notify Tucows at:
rite-bc@opensrs.org

Included in your message should be the following:

        Subject: <include your MSP username> Request for Multilingual Names
--------
Reseller username:

Once received, your profile will be updated to include multilingual support. In our Horizon test
environment all languages are enabled by default to allow you to test the multilingual system,
and your implementation of this client.

These are the only requirements needed to allow you to register these multilingual names. All
existing rules and contracts pertaining to .com .net and .org domains (Schedule A, UDRP etc.)
apply to multilingual names as well.

 9.4 Multilingual Quick Start Considerations

OpenSRS will support the registration of multilingual domains via the existing “Quick Start”
(server side) access method, otherwise known as the Reseller Web Interface (RWI). However as
with previous versions of OpenSRS, the “Quick Start” method will not offer as many options as
the “Full Access” client implementation. For example, a Quick Start implementation will not allow
Reseller to build payment processing into their domain registration process or bulk multilingual
registrations.

 9.5 Multilingual WHOIS Info

Once registered, a multilingual name will be converted to its RACE equivalent. This RACE name is
what will reside within the registrar (OpenSRS) and the registry (Verisign) database.

WHOIS lookups will have to be done in its RACE converted format. Tucows has provided a RACE
conversion tool within the client distribution as well as making a RACE converter available within
our publicly available WHOIS page. (http://whois.opensrs.net/)

Future enhancements will enable registrants to enter native language names for WHOIS lookups.

 9.6 Modifications to the Reseller Web Interface for multilingual
     domains

Note: Unless specified below, all functions of previous versions work as before. The purpose of
this section is to highlight the differences for multilingual names.

Domain input box:

The domain input box allows the Reseller to input a domain in their specific languages and binds
it to the Language specification box (which is now UTF8 for all multilingual registrations)

Language specification box:
This feature occurs throughout the domain registration and management areas of the client.
(Including name servers) Anytime there is a domain name or name server to be inputted, the



             Page 111 of 174 - Release Version 2.56 - support@opensrs.org
language selection field will be displayed. The options within this box our bound to your reseller
profile kept at Tucows. If you have opted not to offer multilingual names then the only available
language in that box will be “Standard English”. The exception to this rule is that of name
servers. A customer could choose to enter a name server name based on one of the available
languages at which point the language specification box again becomes required. Again, all
languages now use the UTF-8 encoding type.

It is important to note that all other input fields (address, administrative and billing contact info)
can accept input of other languages but that the current registry/registrar schema will not
support the correct display of this information, especially within WHOIS searches. Therefore we
encourage resellers to post warning to their multilingual customers not to do so. Otherwise
WHOIS data will be completely incomprehensible.

Reseller must bear in mind that ccTLDs, even if enabled in your profile, are not enabled for
multilingual registrations.

For example attempting to register yourname.co.uk in its Japanese translated version would
cause an error to occur and the registration to fail.

Username and Password:
Another input field that will not accept non-ACSII characters is the username and password
fields. Attempting to do so will result in registration errors.

 9.7 Managing Multilingual Domain Names

We have modified our manage client (and public manage interface) to default to the UTF8
encoding type. This will work by default regardless of whether you are managing a multilingual or
English domain name. Simply enter the domain name in the native language, and manage
normally.

 9.8 Multilingual Domain Renewals & Registration Periods

As with regular .com .net and .org domains, multilingual domains are available for a registration
period ranging from 1 to 10 years. Renewals work exactly the same as non-multilingual names.

It is important to note that during the initial registration period (beginning November 10th 2000
and ending at an unknown future date) all multilingual registration will be placed on registry
hold. This means that multilingual names will not resolve in DNS during the test bed phase. This
means that should someone input the Japanese equivalent of house.com (in Kanji) it will not
resolve to that domains residing IP address. Resolution will be conducted in a controlled phased
approach at an unknown future date. However customers must understand that this has no
bearing on the matter of renewals. The renewal date of a multilingual domain is the actual date
of registration not the date it begins to resolve.

 9.9 Multilingual Domain Transfers

Multilingual Domain Transfers work exactly like .com/.net/.org domain transfers. Simply submit a
properly formatted transfer request (via the Reseller’s Interface, or API as specified in the API
Spec)

 9.10 Viewing Multilingual Orders within RWI

Within all “view domain” areas of the reseller web interface, a new column has been added which
identifies the Encoding Type of each domain. When this field is blank it identifies the name as
being standard ASCII based English domain. Using the either your local RACE.cgi converter


              Page 112 of 174 - Release Version 2.56 - support@opensrs.org
template (located within the client) or using OpenSRS’ publicly available RACE converter
(http://www.opensrs.org/cgi-bin/RACE/index.cgi) a conversion of each domain can be made back
to its native and graphical representation of each domain. (see Section: RACE converter)

It is important to note that when communicating with OpenSRS regarding multilingual domains,
resellers should do so using the RACE converted name (i.e. bq—2kjskjdfkjsf.com). This will help
facilitate any language barriers that may exist and allow proper resolution of any issue regarding
these names.

 9.11 RACE Conversions

The RACE converter allows registrants and resellers to “round trip” their multilingual domain registrations.
Provided are three input areas witch allow input in the following methods;

Original Domain Name:
In this area, the user inputs the multilingual name using either IME of a native language
Operating system and keyboard and specifies the language of the name inputted. The results will
be that of the domains RACE converted equivalent.

RACE Domain Name:
This area allows the input of a RACE converted name and its native language format and
converts it back to its native graphical representation.

Unicode (Space Separated):
If familiar with Unicode points and their hex representations this area allows you to put these
codes and returns the native representation of the domain. (to learn more about Unicode please
visit www.uinicode.org)

 9.12 Multilingual Exhibit A (Registration Agreement)

Multilingual .com .net and .org domains are governed by the exact same registration agreement
as their English equivalents. All customers registering multilingual domains must be bound to the
existing ICANN sanctioned registration terms and conditions.

 9.13 Multilingual UDRP Considerations

As with the Registration Agreement, multilingual domains fall under the same UDRP
consideration as do regular .com .net and .org names. The UDRP protects individuals and
companies with Trade Marks and Copyright protections. Cybersquatting on multilingual names
will prove as fruitless as with regular English domain names. Squatters stand as good a chance of
losing their squatted names in other languages as they do in English.

 9.14 Multilingual Pricing

Tucows has not increased pricing on multilingual gTLDs. However there are certain restrictions
regarding pricing that must be clearly understood.

    1) Multilingual names are priced at the standards $10 per domain year.
    2) Multilingual names are not eligible at this time for any promotional or volume discount
       programs currently offered.

 9.15 Process Overview

The following list outlines the steps that resellers should take to prepare and submit their files for
bulk registrations.




               Page 113 of 174 - Release Version 2.56 - support@opensrs.org
Step 1: Resellers collect domain name registration requests from its customers.

Step 2: Resellers create flat files based on the names collected. (See: Section 9.18, 8 Easy Steps
to Creating a Successful Flat File below)

Step 3: Tucows strongly recommends that resellers visually inspect their files to ensure that the
representation of the domain name in the flat file matches the domain name requested by the
customer. Also, you can verify that the data you want to enter is UTF8 compliant using the steps
provided in Section 9.19 of this document.

Step 4: Resellers submit their requested domain names via the OpenSRS RWI in a flat file as
described. Resellers must ensure that their browser is set to UTF-8 encoding.

Step 5: The RWI will read the batch file and display the information submitted; please ensure
that the displayed information is the same as what you entered (in the native character set.)

 Step 7: Tucows has integrated the multilingual specification defined by the registry into the
server OpenSRS software. Once the requested domain name has been transformed into UTF-8 by
the browser, the OpenSRS system will use RACE to transform the requested domain name into a
representational ASCII character string.

Note: Using the “Place Multilingual Bulk Order” option in the RWI will only work with the
following Unicode code points (an asterisk indicates that the language is supported in Arial
Unicode MS):

Latin 1 *
Latin Extended-A *
Latin Extended-B *
Greek *
Cyrillic *
Armenian *
Georgian *
Korean *
Japanese *
Chinese *

Devanagari *
Bengali *
Gurmukhi *
Gujarati *
Oriya *
Tamil *
Telugu *
Kannada *
Malayalam *
Sinhala
Thai *
Lao *
Tibetan
Myanmar
Kmer

Hebrew *



               Page 114 of 174 - Release Version 2.56 - support@opensrs.org
Arabic *
Syriac
Thaana
Ethiopic
Cherokee
Canadian Aboriginal Symbols
Mongolian

 9.16 Entering Data in UTF8

In order to create the flat file you need to use for bulk multilingual registration (or to create
single domain names to use via the standard RWI ‘Place Order Manually’ feature or the client
code) you will need a method of inputting data in UTF8. There are various methods available to
you; three options follow.

Method 1: Encoding using characters native to your system.

Method 1 assumes that you already have a method of translating from your native encoding type
into UTF8 on your system. If this is the case, simply enter the UTF8 characters into the domain
name field (or in the text file for the bulk loader) and everything will work fine. NOTE: You can
test to see whether your data is, in fact, UTF8 encoded by following the steps in Section 9.19 of
this document.

Method 2: Encoding using Microsoft Word and a Unicode Font

Microsoft Word 2000 (and probably earlier versions) comes equipped with a Unicode font and a
character input tool. Before accessing the tool, first make sure you have a Unicode font installed.
A Unicode font (such as Arial Unicode MS) is required to represent all the various possible
characters. This font is available with Microsoft Office 2000, or from the Microsoft web site.

Once you’ve installed the font, open MS Word and:

    1.   Choose the Symbol option from the Insert pull down menu
    2.   From the Symbol dialogue box, ensure you have the Symbols tab selected
    3.   Select Arial Unicode MS (or your Unicode font) from the Font dropdown menu.
    4.   Select the character set you want from the Subset Window.
    5.   You can now enter the string you want to register as a domain name. Once you have
         built your file in this manner, refer to Section 4 for file saving instructions

Method 3: Obtain a freeware UTF8 Editor

We have done limited testing with SC UniPad for Windows, and have found that it works as a
Unicode character input tool.

(http://www.sharmahd.com/unipad/unipad.en.html)

The tool allows you to input UTF8 encoded characters in many of the languages that Verisign is
releasing. In fact, you can enter all UTF8 characters, however, not all have the glyph that
corresponds to the code. With proper mapping information (available from
http://www.unicode.org) (and in the absence of any easier method) this tool will work for all
supported languages.




              Page 115 of 174 - Release Version 2.56 - support@opensrs.org
 9.17 Eight Easy Steps to Creating A Successful Multilingual Flat
File


Given the feedback from a core group of beta testers, the following procedures describe the
easiest and safest way to create a batch Multilingual Bulk File. This guide describes the steps for
submitting a bulk file using Microsoft 98/2000/ME running MS Office 2000. Additionally, batch
files must be in the following format:

        To submit your Bulk Orders using our RWI, the file should be in a CSV (comma
        delimited) format and must conform to the file format as outlined below:

                            Field List      Max Length         Variable
                         Domain_Name            50               N/A
                          User_Name             100              N/A
                           Password             20               N/A
                          Reg_Period             2               1-10


**the domain_name length presented in the table above is, of necessity, an approximate value.
There is no way to tell the length of the RACE converted name before conversion.

Specific Steps

Step One: Create your flat file in MS Word with the following format:

Domain_Name, User_Name, Password, Reg_Period
etc.

…using one of the UTF8 input method listed in Section 9.16, above.

Where:

Domain Name = the domain in the desired UTF8 encoded characters (found using the
         Input Symbol tool as described above. Note, the TLD (.com, .net, .org)
         must use English Characters.

Username = the username for Registrant control of the name
Password = the password for Registrant control of the name
Term = the registration term

Step Two: Save it as a Web Page file from MS Word (Set Change Title to Blank).

Step Three: Open the HTML file in IE 5.0 or greater.

Step Four: Now go to File and Save As.

Step Five: Change the File name to something in ASCII (i.e., domains).

Step Six: Choose the File type as Text.

Step Seven: Choose the Encoding Type as UTF-8.



             Page 116 of 174 - Release Version 2.56 - support@opensrs.org
Step Eight: Save the File.

You’re ready to upload!

         Useful Steps for Resellers Not Running Office 2000

(This example uses Win98 and Netscape 4.7)
Special Thanks to Homero Alejandro Gonzalez !

Step One: Create your file with wordpad. Save in Unicode.

Step Two: Open the file in Netscape Composer. (V4.7, version 6+ does not work consistently).

Step Three: Choose view > character set > choose Unicode UTF-8. You will receive a warning
that characters will change. (This is acceptable.)

Step Four: Save as .txt with Unicode UTF-8 still selected.

Your file should be ready to upload.

 9.18 Submitting Your Bulk Multilingual Domains

When the Registry launches Multilingual Domains on April 19, 2001 (exact time to be
announced), resellers should log into their Reseller Web Interface (RWI) via:
http://resellers.opensrs.net

A menu item “Place Multilingual Bulk Orders” is available from the Main Menu under the “Order
Management” section. Click this link to go to the “Multilingual Bulk Order Registration Form”.

The new Multilingual Bulk Order form contains all of the same standard elements found in the
“Place Order Manually” form, with the exception of the new “Upload File” section.

Please ensure that all required fields within this form are filled out to your default settings
(Admin., Billing and Technical, and Desired Name Servers) for your placement of batch domains.
You may also choose to submit these names based on an existing domain profile.

Once all of the required fields are filled out, click on the “Browse” button in the “Upload File”
section. This action will invoke a dialogue box which allows you select the path to your desired
batch file. Once the proper path to your file is chosen, click the “Submit” button at the bottom of
the page.

Once the “Submit” button is pressed, the browser will then read your batch file and redirect you
to a display page called “Domain List” (Fig 1.0) which contains all of the domains from the
submitted batch file. At this point, resellers should ensure that all domains appear correctly and
that their browsers are set to UTF-8 Encoding. Corrections or changes to any domains may be
done directly on this page.

Additionally the “Domain List” page has the functionality to submit your batch file from a
numbered position through the “Start registration process at number”. Resellers simply enter
their desired start position. This feature is useful should your registrations be stopped at any
point within the registration process and you need to resubmit part of your batch.




                Page 117 of 174 - Release Version 2.56 - support@opensrs.org
While your batch file is being read, it will be checked for any duplicates and/or invalid domains
before displaying this page. A routine will then be run to discard any duplicates or invalid names.




                                                                                    Start From
                                                                                    Input Box




                                                                                    Checks for
                                                                                    Duplicates
                                                                                    of Invalid
                                                                                    domains




(Fig 1.0 Example Of Display Page Containing Submitted Batch Multilingual Domains)

Once you have visually inspected your domains, press the “Register” button to commence the
bulk lookup and registration process.

The time it takes to register your bulk file varies greatly and depends on the size of your
batch file. It is expected that at launch the Verisign Registry System will be extremely sluggish
due to an expected “Land Rush” of registrations. You will see each name appear on the screen as
it either registers or fails to register because it’s taken. The word ‘Done’ will appear at the bottom
of the domain list once the file is completely done.

As orders are looked up and registered a new page will be displayed showing the status of each.
Please make sure your browser is still set to UTF8 when reviewing the results page! (Note: In
some cases, especially with large files or during times when the registry’s response is slow, your
browser may not display live updates of the registration progress until it has completed your file.
Do not shut down your browser and try again, instead let the browser complete the
process until you see a screen as displayed in Fig 1.1)




              Page 118 of 174 - Release Version 2.56 - support@opensrs.org
                                                                               Registrat
                                                                               ion
                                                                               Results




                                                                       Registrat
                                                                       ion
                                                                       Summaries


(Fig 1.1 Displays The Results Of A Bulk Multilingual Submission)

Fig. 1.1 shows an example where, 12 Russian Domains Names are submitted. Three were not
registered because they were already registered while nine domains within the batch were
successfully registered.

Once your batch is completed and the summary information is displayed, you may save this page
onto your computer as an HTML file for later review and reconciliation.

You may now submit a new file for Multilingual Bulk Registration.

 9.19 Testing your data for UTF8 compliance

All Multilingual domains must now be entered into our system using the UTF8 encoding type. In
our research we found that a preponderance of non-ASCII encodings are actually not distinct
encodings, but rather use what’s known as ‘font overloading’ to override certain characters and
represent them differently. These fonts will NOT work in either the Multilingual bulk loader, the
single domain form in the RWI, or through the PERL client, since the underlying encoding might
still be Western European (or some other encoding type).

The following test will help you determine whether the data you are entering is in UTF8.

    1. Using one of the methods describe in Section 3 above, create a Unicode Domain Name.
    2. Copy the complete domain name, and paste it into the Original Domain Name field at:
       http://www.opensrs.org/RACE
    3. Click on the Encode button.




             Page 119 of 174 - Release Version 2.56 - support@opensrs.org
                   4. You will now be taken to a RACE results page, which should look like the following:




UTF8 encoded
name




                                                               RACE
 Round trip                                                    Name as it
 verifies                                                      will be
 correct                                                       stored in




                   5. If the ROUND TRIP name does resemble your input, then your data is not encoded in
                      UTF8, and cannot be used for multilingual domain name registrations. NOTE: the data
                      may not exactly match your input due to case folding and other syntactical rules of
                      RACE.

                9.20 Resolution Phases

               Verisign is approaching resolution of multilingual domain names in three phases.

               Phase 1 will allow users to verify that a Web site URL entered into their browser using the
               testbed domain name responds with the correct information. Phase 1 began on January 15,
               2001.

               Phase 1 of internationalized domain name resolution will allow users to query a testbed domain
               name in its RACE format (for example, bq--3b7vcv67.mltbd.com) and ensure that the name
               resolves to the correct confirmation page. The confirmation page will be hosted by VeriSign and
               will contain information of use to the owner of the name. Specifically, the page will indicate
               whether or not the resolution was successful, and will display the queried internationalized name.

               Phase 2 will, within a controlled environment, test the resolution of testbed names on the name
               servers to their corresponding Web sites throughout the Internet. Phase 2 is expected to begin in
               April 2001.




                            Page 120 of 174 - Release Version 2.56 - support@opensrs.org
Phase 2 of internationalized domain name resolution will allow internationalized domain names
to be maintained by the owner of the name, who can direct users to his or her own Web site
(rather than the VeriSign confirmation page). This will represent the first opportunity for testbed
name owners to use their internationalized domain name in conjunction with their site.

Phase 3 will introduce the testbed names into the .com, .net, and .org zone files, allowing for
full-featured resolution. Phase 3 is expected to begin in May 2001.

We are currently in Phase 2. In order to test your multilingual name registration during Phase 2,
you must set up the zone file for your domain as follows:

multinlingualname.mltbd.com      IN      A        IP.ADD.RE.SS

bq-qbdfecssd.mltbd.com           IN A 123.321.123.321

 9.21 RESOLUTION NOTES:


1) The file must use either the mltbd.com, mltbd.net or mltbd.org zones, depending on whether
your multilingual name is a .com, .net, or .org.

2) Because Realnames translation is used, the IDNs cannot be called when the normal ‘http://’
protocol identifier is used; this means that these names cannot be hyperlinked; they can only be
typed into browsers without ‘http://’.

10 .tv Registrations

 10.1 Overview & Feature List

OpenSRS .tv features include:

Client:
                -   Registration of .tv domains
                -   Modification of .tv domains
                -   Referrals through server for high profile domains (explained below)

Server:
                -   Registration of .tv domains
                -   Modification of .tv domains
                -   Tracking of high profile referrals (explained below)

 10.2 The .tv Opportunity

.tv is the TLD for the country of Tuvalu, a small Pacific Island. Through an agreement with the
country of Tuvalu, the California company dotTV became the exclusive registry for .tv domain
names.

In October 2000, Tucows Inc reached an agreement with dotTV to offer .tv domain name
registrations to Tucows Resellers.

In October 2000, .tv set a record for the fastest growing Top-Level Domain on the Internet by
registering over 100,000 names in less than 6 months.




             Page 121 of 174 - Release Version 2.56 - support@opensrs.org
.tv is run out of an open registry, which means that anyone can register a .tv domain name, as
long as they’re willing to pay for it.

 10.3 .tv Reseller Qualification

In order to offer .tv domain names, each Reseller will be required to sign and remit to Tucows a
.tv specific Registration Service Provider Agreement. Additionally, Resellers will be required to
bind their clients to the terms and conditions of the .tv registry.

Resellers will be able to use our test environment for .tv registrations without qualification, as
this environment simply simulates the behavior of the .tv registry and does not actually register
names.

In order to apply for access to sell .tv names from our live environment, you must:

    -   Remit a new Reseller contract to Tucows authorizing you to act as an OpenSRS .tv
        domain reseller. The contract can be found at:
        http://resellers.tucows.com/opensrs/resources/docs/contracts/tvagreement.pdf

    -   Bind your customers to the .tv registration terms, a copy of which can be found at:
        http://resellers.tucows.com/opensrs/tv/tv_exhibit_a

    -   Email rite-bc@opensrs.org to formalize your request.


 10.4 About dotTV

DotTV is a California based company with the exclusive right to operate the .tv registry for the
country of Tuvalu. Tuvalu plans to use proceeds from the agreement to increase the quality of
life for its approximately 10,000 citizens. Tuvalu is a significant majority shareholder in dotTV and
has a seat on its board.

 10.5 .tv Registration Considerations

New registration templates - included in the new client code - will be used when registering .tv
domains. Upon successful registration .tv domains will be seamlessly inserted into an OpenSRS
registrant profile.

DotTV Registry has implemented a scaled methodology for registering names that have a higher
potential worth. Most names will be given “standard” pricing, for example: web-weddings.tv and
thewebparty.tv. Other names considered “high-profile” are given much higher values, such as
free.tv, baseball.tv, and nbc.tv. When implementing .tv registrations, careful consideration should
be given to “standard”, and “high-profile” registrations.

 10.6 Standard Registrations

Standard registrations have a fixed base price. Please refer to the 10.16 .tv Standard Pricing
section for the pricing structure. Most domains will fall under this category, and are available in
real time. Domains purchased from this category can be associated with existing OpenSRS
domains and registrant profiles.

 10.7 High Profile Registrations

High Profile registrations vary greatly in price. The pricing for these domains can change over
time (always increasing) based on demand – this price is controlled exclusively by dotTV Registry



              Page 122 of 174 - Release Version 2.56 - support@opensrs.org
-Tucows does not affect this price in any way. Some examples of prices are $100,000 for free.tv,
$25,000 for lawyer.tv and $1,000,000 for casino.tv (yes, that says one million dollars!). Due to
the OpenSRS prepayment model, and the wide range of prices for these high profile names, we
have no choice but to simply refer registrants directly to dotTV Registry for the purchase of these
names. OpenSRS and dotTV registry track referrals of this nature, and rebates are given to the
referring reseller IF a successful registration is completed. More information can be found in the
10.17.tv high Profile Pricing section.

Because registrations in this category are referred to the dotTV Registry, High Profile domains do
not remain part of the OpenSRS system, and cannot be managed or renewed from our systems.

 10.8 .tv Quick Start Considerations

OpenSRS will support the registration of .tv TLDs via the existing “Quick Start” (server side)
access method, otherwise known as the Reseller Web Interface (RWI). However, as with
previous versions of OpenSRS, the “Quick Start” method will not offer the full robust range of
options available to resellers as with the “Full Access” client implementation. For example, a
Quick Start implementation will not allow Reseller to build payment processing into their domain
registration process.

The Quickstart system will support both standard and high profile registrations.

 10.9 WHOIS info

Currently the registry for .tv names limits WHOIS information for dotTV registered names. You
can query a name at http://www.tv. If a domain is taken, an option to perform a WHOIS will
appear – you must login to their site and create and account to do this. Once an account is
created, users can perform up to 10 WHOIS queries per day. Information provided on the
website is brief; however, more extensive information is emailed to the email address associated
with your “account”. The OpenSRS system has the ability to show WHOIS information for
OpenSRS registered .tv domains.

 10.10 .tv Registration Flow: Standard Registrations

Registering .tv names is no different than registering in the gTLDs; each domain year costs $35
USD.

 10.11 .tv Registration Flow: High Profile Registrations

Since the pricing for these domains varies so much and is potentially so high, we refer high
profile registrations directly to the dotTV Registry. If you perform a search for a name that is
beyond the pricing for a standard registration, you are immediately referred to dotTV. This
process is seamless, and we track the referring reseller. The purchase of the domain MUST be
completed during THIS SESSION if you wish to qualify for referrals. Note that any referrals done
via the test (horizon) system will NOT qualify. If the registration is completed and verified, we
will provide the reseller with 25% of the full price of the domain name we referred.

 10.12 Managing .tv Registrations: Contact Changes

We have enabled the Manage domain interface and scripts to work with dotTV Registry and
make changes to .tv domain names. Modifications to .tv names work in exactly the same
manner as gTLDs – you can alter one domain, or multiple domains within the same profile. The
only feature not present is the ability to “create or modify a nameserver which is based on
<domain>”, under the Name Server management area.



             Page 123 of 174 - Release Version 2.56 - support@opensrs.org
Updates are completed in ‘real-time’ and can be viewed through the Manage interface as soon as
they’re made. To manage a .tv domain, direct your clients to:

https://manage.opensrs.net/

….or to your implementation of the newest manage.cgi. They will log into the Manage interface
using the domain name, and their OpenSRS Username and Password.

 10.13 .tv Renewals

.tv renewals work in the same manner as .com/.net/.org renewals, including messaging.

 10.14 .tv Transfer of Domain Ownership

To transfer the ownership of a .tv domain, advise your registrants to use the basic ‘change
profile’ functionality of the Manage Domain interface. This will allow them to assign a new
username and password to the domain, which the new owner can use to update contact
information as desired.

 10.15 .tv Deletion Requests

As a rule, we don't delete domains registered in error. RSPs are responsible for securing payment
and making sure all info is correct before processing.

However, we do offer RSPs one free deletion request for a mistake they have made. Deletions
must be requested within 48 hours of creation. If you wish to use your one free deletion request
at this time, please send in a signed fax on company letterhead including the domain names and
your RSP username.

Fax: 416-531-2516 Attn: OpenSRS Support
Please Email support@opensrs.org so we know to expect your fax.

 10.16 .tv Standard Pricing

Tucows Resellers will be charged as follows:

        Term                                                Reseller Price (USD)
1 Domain Year                                      $35.00

10.17.tv high Profile Pricing

The Registrant will be registering directly on the dotTV site (upon referral from the Reseller’s
site). The Reseller’s account will be credited 25% of the retail price paid for the High Profile
Registration made by the Registrant. Credits will be done at the end of each month, once
verification of a referral is acquired.

 11.0 .vc Registrations

Note: .vc functionality, while described in this document and included in the client
code release, is not yet enabled. We will enable and announce this functionality in the
near future. Any links referred to in this section will not work until .vc functionality is
actually released.


              Page 124 of 174 - Release Version 2.56 - support@opensrs.org
On October 31, 2000 the Government of Saint Vincent and the Grenadines and Tucows Inc.
signed an agreement whereby Tucows Inc. will have the exclusive right to operate the Registry
for .vc. Until now, there has been no Government approved opportunity to purchase .vc names.

We expect .vc registrations to do particularly well in the Venture Capital and Virtual Communities
markets. .vc is also an open registry

Tucows Inc. has been granted exclusive rights to run and operate the registry for the .vc name
space. In the near future, a wholly owned subsidiary of Tucows Inc. will be designated as the
registry operator for the .vc name space.

 11.1 New Version Overview & Feature List

New .vc features in this release include:

Client:
                  -   Registration of .vc domains
                  -   Modification of .vc domains

Server:
                  -   Registration of .vc domains
                  -   Modification of .vc domains


 11.2 .vc Reseller Qualification

In order to offer .vc domain names, each Reseller will be required to sign and remit to Tucows a
.tv specific Registration Service Provider Agreement. Additionally, Resellers will be required to
bind their clients to the terms and conditions of the .vc registry.

Resellers will be able to use our test environment for .vc registrations without qualification, as
this environment simply simulates the behavior of the .vc registry and does not actually register
names.

In order to apply for access to sell .vc names from our live environment, you must:

    -     Remit a new Reseller contract to Tucows authorizing you to act as an OpenSRS .vc
          domain reseller. The contract can be found at:
          http://www.opensrs.org/vc/vcagreement.pdf

    -     Bind your customers to the .vc registration terms, a copy of which can be found at:
          http://www.opensrs.org/vc/vc_exhibit_a.html

    -     Email rite-bc@opensrs.org to formalize your request.

 11.3 .vc WHOIS info

.vc domains will be viewable through http://resellers.tucows.com/opensrs/whois/, or through a
command line interface by querying whois.opensrs.net (port 43). The field requirements and
layout are exactly the same as current gTLD registrations.




               Page 125 of 174 - Release Version 2.56 - support@opensrs.org
 11.4 .vc Registration Considerations

In designing the .vc registration system, we opted to work with a pre-established model. The
flow and functionality of .vc domains work exactly the same as with the current gTLDs (.com,
.net, .org).
 11.5 .vc Contact Changes

We have enabled the Manage domain interface and scripts to work with and make changes to .vc
domain names. Modifications to .vc names work in exactly the same manner as gTLDs – you can
alter one domain, or multiple domains within the same profile. The only feature not present is
the ability to “create or modify a nameserver which is based on <domain>”, under the Name
Server management area.

Updates are completed in ‘real-time’ and can be viewed through the Manage interface as soon as
they’re made. To manage a .vc domain, direct your clients to:

https://manage.opensrs.net/

….or to your implementation of the newest manage.cgi. They will log into the Manage interface
using the domain name, and their OpenSRS Username and Password.


 11.6 .vc Renewals

Renewals for .vc work in the same fashion as gTLD domain renewals. Please refer to latest to
the gTLD renewals section of this document for procedural information.


 11.7 .vc Transfer of Domain Ownership

To transfer the ownership of a .vc domain, advise your registrants to use the basic ‘change
profile’ functionality of the Manage Domain interface. This will allow them to assign a new
username and password to the domain, which the new owner can use to update contact
information as desired.

 11.8 Registrar Transfers

Currently, as Tucows is the sole registry and registrar for .vc names, there are no registrar
transfers. Eventually, .vc will be offered through multiple registrars, at which point registrar
transfers will be possible.

  11.9 .vc Pricing

.vc registrations and renewals cost $35 US per domain year.

 12.0 Web Certificates
The following sections of this document explain how to manage, monitor and process the sale of
Web Certificates. As of July 3rd 2002 Tucows will be provisioning all digital security products
through GeoTrust as the new supplier of choice for Digital Security Products. Currently our
offering includes the Geotrust TrueBusinessID offering. Other product offerings will be available
within the next 6 months. For more information about the TrueBusiness ID product, and related
installation procedures, please visit Geotrust.




              Page 126 of 174 - Release Version 2.56 - support@opensrs.org
 12.1 Overview of Web Certificate Offering


          -       System collects all information necessary to purchase a Certificate Keys
          -       Certificate Key is generated and sent to the requestor
          -       Certificate Key is used to redeem a Web Certificate at
                  www.certificateregistration.com
          -       Reseller is provided with view for managing Certificate Keys
                 o Searching of codes by different variables
                 o Ability to process or cancel any requests
                 o Ability to customize messages sent to end users
                 o Ability to opt in to confirmation emails
                 o Reporting related to volumes for certs sold

 12.2 Refund Policy

The Web Certificate purchase is a two-step process. Upon purchase, the purchaser will get a
Certificate Code that can be used to register for a web certificate on the
www.certificateregistration.com website. Web Certificates, once issued cannot be refunded.

Within 30 days of purchase, unused (certs have not been issued) Certificate Keys may be
returned for a full refund. Once a Certificate Key has been used or 30 days have passed since
purchase, no refunds are available. Certificate Keys expire 1 year after purchase.

Refunds take approximately two weeks from the refund request date.

12.3 Web Certificate Purchase Process

The Web Certificate Purchase Process was designed to minimize the implementation time
required by Resellers. Over time full web certificate registration functionality will be built into
OpenSRS. However, at this phase of development, integration and management of the Web
Certificate Sales process has been minimized.

The typical purchase process will flow as follows:


Step 1:              Ordering a Web Certificate

                     1a) A customer can order a web certificate from an enabled Resellers web-
                         site (using the API) or--
                     1b) A Reseller can purchase web certificates on their own account or on
                         behalf of a customer by purchasing directly through the Reseller Web
                         Interface.



Step 2 and 3:        Certificate Key(s) Issued / Price Deducted from Reseller’s Account

                     Orders can either be processed immediately or put into a “pending” state in
                     which they wait for authorization by the Reseller. Once a Reseller has
                     authorized a certificate purchase, the Certificate Key is issued to the e-mail
                     address given.




              Page 127 of 174 - Release Version 2.56 - support@opensrs.org
Step 4:            Certificate Key(s) and Instructions e-mailed to Customer

                   An e-mail is sent to the customer containing Certificate Key and instructions.
                   The e-mail contains the registration code(s) and instructions on how to use
                   them to register a Web Certificate. The Reseller can brand this e-mail to the
                   end user. The reseller will have the ability to customize the subject line, the
                   header, the footer and the from-address.

Step 5:            Web Certificate Application

                   The customer, or the Reseller on behalf of the customer, then takes the
                   certificate code to the www.certificateregistration.com web site, enters
                   required information and submits the certificate application.
                   Information requested will include:
                        ! Contact Information
                        ! Certificate Signing Request

Step 6:            Applicant is verified

                   The applicant must fax their proof of organization to Geotrust for verification
                   at 1-770-752-1460. Documents that can be used as a proof of organization
                   are:

                   •   DUNS number (Dun and Bradstreet) for more info Click Here.
                   •   Articles of Incorporation
                   •   Business License
                   •   Doing Business As (DBA) registration
                   •   Partnership documentation
                   •   Sole Proprietorship documentation

                   Verification is done by: Comparing the order information, the whois record of
                   the domain, and the Organization information; when all of these match the
                   certificate will be issued.

Step 7:            Web Certificate Distribution
                   Once the verification process is complete the certificate will be emailed to
                   the admin, technical and billing contacts listed on the order. After the cert
                   has been issued, it cannot be refunded.

The diagram on the following page represents this process.




             Page 128 of 174 - Release Version 2.56 - support@opensrs.org
                                               Customer




                 Reseller      RWI Entry        STEP 1          API Entry




                                             Key Issued for
                                             Cert when order
              OpenSRS                                           STEP 2
                                              is processed




                                            Reseller Account
              OpenSRS                      Decremented when     STEP 3
                                           order is processed                STEP 7
                                                                             Cert is sent to
                                                                             Customer

                                             Email issued       STEP 4
              OpenSRS                        to Customer                     Geotrust




                                               Application at
               Geotrust                       www.certificate   STEP 5
                                             registration.com




                                              Applicant is      STEP 6
               Geotrust                         verified




12.4 Reseller Web Interface Commands




Figure1: Within the RWI the following commands are available, each will be explained in detail.

Place Order for Web         Allows Reseller to purchase Web Certificate Registration Codes
Certificate(s)              directly.
Search for Web              Allows Reseller to search all of its Web Certificate orders
Certificates
View Pending Orders         Shows a list of all the orders in “Pending” status. These orders are
for Web Certificates        awaiting Reseller approval such that Registration Codes be issued and
                            the Reseller account billed.
Cancel Key Codes            Shortcut to canceling a Registration Code (a.k.a. Key Code) when the
                            code is known.


             Page 129 of 174 - Release Version 2.56 - support@opensrs.org
                             Profile Management (modifications)
Tech Contact                Allows Reseller to modify their preferences related to the sale of Web
Information                 Certificates. Resellers choose whether or not to accept orders
                            immediately, whether or not to receive a confirmation e-mail and can
                            modify the e-mail that goes to the customer.


 12.4.1 Place Order for Web Certificates

Use this feature to place an order for digital web certificates. Access this form by clicking on
Place Order For Web Certificates in the RWI as shown in Figure 1. The order form is displayed in
Figure 2.




Figure 2: Digital Certificate Purchase screen

The required fields on Certificate Purchase form are:

    !   Contact – The name of the person purchasing the web certificate.
    !   Organization Name – The name of the organization purchasing the web certificate.
    !   Phone Number – The telephone number of the person purchasing the web certificate.
    !   E-mail – The e-mail of the person purchasing the web certificate.
    !   Quantity of Digital Certificates - The number of web certificates requested in the
        order.

Note that the e-mail address provided in this form is the one to which the Key Code is emailed.




              Page 130 of 174 - Release Version 2.56 - support@opensrs.org
There is an option to ‘submit the order immediately’ or ‘save it to the pending orders list’. When
the order is processed immediately, the Reseller’s account will be decremented for the cost of the
web cert(s) and the key code(s) will be e-mailed. If the order is saved, the order will be added to
the Pending Orders table and the Reseller’s account will not be decremented until the order has
been processed by the Reseller.

Prior to an order being submitted, a confirmation screen shows all information captured in the
order form as displayed in Figure 3.




                                         Figure 3: Digital Certificate Purchase confirmation screen

The order will be submitted to the system for processing once confirmed. If declined, the
browser will return to the input form shown in Figure 2.

Each order can have a maximum of 100 certs ordered at once. Once accepted by the reseller and
the account is decremented, the order is then spliced into 100 different coupon numbers and
subsequently, 100 separate orders.

 12.4.2 Search for Web Certificates
To search for a Web Certificate order, click on Search For Web Certificates, in the RWI Certificate
Management section (shown in Figure 1.) This form is to be used to search for orders based on
the criteria displayed in Figure 4.




             Page 131 of 174 - Release Version 2.56 - support@opensrs.org
                                                          Figure 4: Search For Certificates screen

The searchable criteria are:

    !   Organization Name – The organization for which the web certificates were purchased.
    !   Contact Name – The name of the contact in the client organization.
    !   Phone – The telephone number of the contact in the client organization.
    !   E-mail address – The e-mail address to which the certificate key(s) were sent.
    !   Order ID – The order ID for the web certificate.
    !   Certificate Key – The Certificate Key issued to redeem at certificateregistration.com
    !   Current Status – The status of the order
    !   Renewal Date – The date before which renewal of the web certificates will be required.
        The range must have a start date and an end date, i.e., Jan. 1, 2000 to Dec. 1, 2000.
        Note that this is calculated as one year from the date that the Key Code status changes
        to “used”. Note: the status of a Key Code is changed to “Used” when the code is input
        and a certificate is issued as per the process on the www.certificateregistration.com web
        page.
    !   Status Change Date – The date of the most recent status change of the web
        certificate. The range must have a start date and an end date, i.e., Jan 1 2000 to Dec 1
        2000.

The status of the order can be one of:
   ! Issued – The key code has been sent to the e-mail address and is awaiting processing.
   ! Pending - The key code has not yet been purchased, only reserved. The Reseller’s
        account is not decremented until the order is processed.
   ! Used - The key code has been activated.




             Page 132 of 174 - Release Version 2.56 - support@opensrs.org
    !   Cancelled - The key code can no longer be used by the Reseller or Tucows. It has been
        cancelled.
    !   Cancel Requested – The Reseller has requested that a key code be cancelled. Prior to
        cancellation it must be confirmed that the key code has not been used and that key code
        is removed from the list of valid codes. Until this is confirmed and the key code is
        cancelled, the key code will remain in the Cancel Requested state. The confirmation is
        done on a nightly basis.

The use of wildcards is supported when searching by Organization Name, Contact Name, Phone,
E-mail address, Order ID and Certificate Key.

Search results can be grouped by the status of the order. For example, to see all issued and
cancelled orders check off Issued and Cancelled. On the search results when searching by
purchase or renewal dates, the date range is selectable by using pull-down menus for beginning
and end of the day, month and year as described in the search criteria above.

A sample search results screen is shown in Figure 5, below:




Figure 5: Digital Certificates Search Results screen

On the Search Results screen, orders may be sorted chronologically or alphabetically (by
Certificate Order ID, Purchase Date, Organization name, Contact name, E-mail address and
Status.) Sorting order may be changed at any time by clicking on one the hyperlinked headers at
the top of the search results table.

At the far right of the Search Results Table action buttons appear. The list of available actions is
a function of the status of the order/key code.

When a particular order is marked Pending, the following action buttons shall appear:



              Page 133 of 174 - Release Version 2.56 - support@opensrs.org
    !   Edit - Edit the purchase information.
    !   Accept - Submit the order to the system for fulfillment resulting in your account being
        decremented.
    !   Cancel - Removes the order from the pending orders table.

When a particular order is marked Issued, the following action buttons shall appear:

    !   Edit - Edit the purchase information.
    !   Resend - Resends the confirmation e-mail to the customer using the order information
        in the database.
    !   Cancel Key - Initiates Cancel Request Procedure for all key codes contained in the
        order. Note: Pending orders can only be dealt with on an entire order basis. Key Codes
        that are in the “Issued” state can be dealt with individually.

There are no actions available for orders/key codes in the Cancel Requested, Cancelled or
Used states.

 12.4.3 View Pending Orders
This view is a shortcut to finding all the Pending Orders for certificates. To view this screen click
on the hyperlink labeled, View Pending Orders For Web Certificates, in the RWI shown in Figure
1. A sample output is shown in Figure 6, below:




Figure 6: Pending Digital Certificate Orders Screen




              Page 134 of 174 - Release Version 2.56 - support@opensrs.org
When an order is pending, The Reseller account has not been decremented and no key codes
have been issued. These orders will not be processed until the Reseller accepts the order either
here or from a search results page. An order is accepted by clicking on the Accept action button
that is displayed in the “Actions” column. If the Reseller’s account does not contain enough funds
to process the order(s), the full order will be lost upon submission, unless the order was put into
pending prior to acceptance. The order will have to be re-generated when sufficient funds are
available. There is no processing of partial orders.

Note: Orders are broken out into separate orders per cert requested. For example, Order 33 in
Figure 6 requested five Web Certificates; therefore Order 33 will appear five times. However,
since the order is Pending and Certificate Keys have not yet been assigned, any of the actions
will be applied to the entire order and not just the individual row. Once a Certificate Key has
been issued (i.e. after the Order has been Accepted) each cert ordered becomes its’ own order
each of these Orders can be edited, cancelled or re-sent.

12.4.4 Cancel Key Codes
This gives you the ability to cancel a key code individually. The customer must provide the key
code that is to be cancelled. To cancel a key code click on the hyperlink labeled, Cancel Key
Codes, in the RWI shown in Figure 1. The key code cancellation form is displayed in Figure 7.




Figure 7: Cancel a Key Code screen

Resellers can only cancel key codes that were sold through their Reseller account, and that are
valid in the database and that have Issued status. Please Note: Key codes can only be cancelled
if it is within 30 days of the issue date. Notes may be entered regarding the cancellation request.
When a cancellation is requested on a valid key code the confirmation screen shown in Figure 8,
will be displayed.




             Page 135 of 174 - Release Version 2.56 - support@opensrs.org
Figure 8: Cancel a Key Code confirmation screen

If the Reseller selects Yes, the key code will enter Cancel Requested state and the Reseller will be
directed back to the RWI screen shown in Figure 1. If No is selected, the Reseller will be returned
to the Cancel a Key Code screen shown in Figure 7. The Cancel Requested state will be verified
nightly, and converted to a cancelled state if successful. The verification includes checking with
Geotrust nightly to ensure that the certificate key has not been used on the
certificateregistration.com site.

 12.4.5 Modifying Reseller Certs Preferences


To adjust your preferences click on the hyperlink labeled, Tech Contact Information, in the RWI,
under Profile Management as shown in Figure 9. (following page)




             Page 136 of 174 - Release Version 2.56 - support@opensrs.org
                                                     Figure 9: The Reseller Web Interface (RWI)

On the Reseller Modification Form, scroll down to Digital Certificate Options, as shown in Figure
10.




                                                     Figure 10: Digital Certificate Options screen



             Page 137 of 174 - Release Version 2.56 - support@opensrs.org
The Digital Certificate Options section allows you to configure administrative functions pertaining
to certificate order processing. You will also be able to customize the end user message contains
the certificate code.

The options on this form are:

    !   Process Orders Immediately
           o Yes, will submit all orders to the system for fulfillment without saving to the
               pending orders list.
           o No, will save the orders to the pending orders and thus orders will not be
               processed until they are Accepted.

    !   Send e-mail when certificate is processed – This option (when enabled) allows the
        Reseller to receive a confirmation e-mail when an order is processed.

    !   Send E-mail to – The e-mail address to which you want the confirmation e-mails to be
        sent.

    !   E-mail message to customer – An option to configure the message that will be sent
        to the customer when a certificate key is issued. To configure the message that will be
        sent to customers when a key code is issued click on the hyperlink labeled, Configure
        Message, shown in Figure 10. The e-mail configuration screen is shown in Figure 11.
        (following page)




                                 Figure 11: Configure Digital Certificate Registration E-mail screen

The registration e-mail can be configured through the following fields shown in Figure 11:

    !   From Address – The e-mail address of the sender in the format of
        johnsmith@tucows.com. Resellers use this to brand the web certificate sale. Resellers
        should also be aware that this will be the e-mail address to which customers may reply.




             Page 138 of 174 - Release Version 2.56 - support@opensrs.org
        If no from address is specified the software will default to the administrative contact of
        record for that Reseller.
    !   Subject – Allows Reseller to brand the Subject Heading.
    !   Message Header – The header text of the registration e-mail.
    !   Message Footer – The footer text of the registration e-mail.

Please note that the message body cannot be customized as it contains the key code, which is
supplied by Tucows. Selecting Save Changes will reveal a confirmation screen which shows all
information captured in the e-mail configuration form as displayed in Figure 12. (following page)




                                             Figure 12: Confirm Configuration of the E-mail screen

Once confirmed the information the changes will be submitted to the system and take effect
immediately.

 12.5     General Notes around Certificate Processing
Bounced Messages:
Bounced messages sent to the customer are lost. The customer is notified of their Certificate
Keys at time of purchase, is given instruction as to how to use them, and is notified that they will
be receiving an e-mail as confirmation of the transaction. If the e-mail is not received, the
customer is instructed to contact their reseller. The reseller has the ability to modify the order
and re-send the confirmation e-mail.

 12.6 Changes to the Manage Domain Interface for Web
Certificates
There are no changes to the Manage Domain Interface. The only management function required
is the ability to revoke a certificate. Currently that can be done at the
www.certificateregistration.com website.

 12.7 Renewing Certificates
Renewals are facilitated on the http://www.certificateregistration.com website. The buy process
is the same, the codes used are the same, the process is the same but instead, choose the
Renewal Y/N option. Assuming no changes to the contact information all you will have to do is
enter the contact information and submit a new CSR (Certificate Signing Request). Should your
company be registered from Geotrust the year prior, the validation will be immediate.



              Page 139 of 174 - Release Version 2.56 - support@opensrs.org
13.0 .info Registrations

 13.1 .info Reseller Qualification

In order to apply for access to sell .info names from our live environment, resellers must:

        Remit a new Reseller contract to OpenSRS authorizing you to act as an OpenSRS .info
        domain reseller. The contract can be found at:
        http://resellers.tucows.com/opensrs/resources/docs/contracts/infoagreement.pdf

        and…

        Bind your customers to the .info registration terms, found at:
        http://resellers.tucows.com/opensrs/info/infoexhibita

Once you have Exhibit A on your website (or can demonstrate your alternative method for
binding your customers to this agreement) email rite-bc@opensrs.org with the following
information:

To: rite-bc@opensrs.org
Subject: {RSP Username} *.INFO agreement

Include the URL (from your website) where you have posted the agreement for Tucows review.
Once Tucows receives this email and checks your website, you will be able to offer .INFO
registrations.

 13.2 .info Overview

On October 16, 2000, .info was approved by ICANN as one of seven new gTLDs to be offered to
users. Of the seven new gTLDs, .info is the only unrestricted TLD which means that anyone can
register a .info domain.

With more than 23 million dot com names already registered, there is a growing need and
demand for quality namespace on the internet; .info clearly answers this need.
The .info domain targets individual users wishing to use the internet as a vehicle for sharing of
information such as family photos, online resumes or general information. It also targets global
corporations wishing to provide users with product and/or company information. It is the most
easily translatable domain offered as it means the same in the English, French, Spanish and
German languages to name a few –suggesting that .info truly has global appeal.

 13.3 .info Registration Considerations

Since .info is an unrestricted gTLD, there are no special requirements for registering a .info
domain. Any organization can get as many available .info names as they are willing to pay for.
Registration for .info is ‘real-time’; the OpenSRS system sends commands to the Afilias Registry,
which in turn replies immediately with either confirmation of the requested change, or the
appropriate error message. In either case, the result of the transaction is displayed for the
Reseller (or in some cases the end user) immediately.

 13.4 Registering .info names via the RWI

The Reseller Web Interface supports the registration of .info TLDs. However, as with previous
versions of OpenSRS, the “Quick Start” method will not offer the full robust range of options



             Page 140 of 174 - Release Version 2.56 - support@opensrs.org
available to resellers with the “Full Access” client implementation. For example, a Quick Start
implementation will not allow Resellers to build payment processing into their domain registration
process.

From the main menu in the RWI, resellers are now also able to register .info names via the RWI
by using the ‘Place Order Manually’ link. A .info domain can be registered by selecting .info from
the bottom of the drop down TLD menu.

Please note: For .info real-time registration, a minimum 2 year registration term is required.
Additionally, the phone number MUST be in a specific format:

+CCC.NNNNNNNNNNNNxEEEE

Where C = the country dial code, N is up to twelve digits of the phone number, and E is the
extension. The x character is ONLY required if an extension is specified. For Tucows phone
number, this would be +1.4165350123 (where 1 is the dial code for Canada)

 13.5 .info Registrar/Reseller/Registrant Transfers

The following will describe the process that is followed for .info Registrar->Registrar transfers,
and Reseller->Reseller transfers. They are functionally identical.

    1. Tucows receives transfer request order.
    2. Tucows sends authorization email to admin contact with a URL to approve the transfer,
       and a temporary password to accept/reject pages.
    3. Admin must also use the auth_code when approving a transfer. This code is obtainable
       from the current registrar of record and is domain specific.




    4. If either the admin contact or OpenSRS cancel the request (on behalf of registrant)
       transfer request is cancelled.
    5. If the admin contact approves the transfer and includes the auth code, Tucows sends the
       request to registry. (Same as existing gTLD process)
    6. Registry approves transfer.
    7. Tucows notifies reseller/registrant of successful transfer.


Transfer requests are allowable for a minimum one-year period, and a maximum of the number
of years allowable. (e.g. if registrant has 5 years remaining in registration, they may transfer and
choose a five year term instead of a one year term). This term is specified at the time the
transfer is ordered.

 13.6 Reseller Pricing

Tucows resellers will be charged $10US per domain year. As the Afilias registry has requested a
minimum two-year registration period for real-time registration, resellers will be charged


              Page 141 of 174 - Release Version 2.56 - support@opensrs.org
$10/year x 2 years = $20 for each registration. Therefore if a reseller submits 10 registrations,
they are expected to have 10 x $20 = $200 in their account to cover the cost of the transaction.

 13.7 Updates on the Client Code

The OpenSRS clients v.2.20 (and later) will be able to add .info to their existing products.
Resellers will however be required to add ‘.info’ to the drop down menu in the TLD list. To
ensure you have the required checking of special information (such as 2 year minimum and the
phone number format), the latest client code is suggested.
 13.8 .info Registration Flow

Description
   1. Registrant chooses to register the domain.
   2. Registrant completes required information (via RCL or some other method)
   3. Registrant submits information to reseller. (via RCL or some other method)
   4. Order information is submitted to OpenSRS (via RWI or RCL).
   5. OpenSRS submits registration to Afilias.
   6. OpenSRS debits reseller account upon successful registration.
   7. OpenSRS notifies reseller of successful domain registration.

 13.9 .info Deletion Requests

Registrants/resellers must cancel registrations within five days of submitting the registration. If
this timeline is met – there is no penalty for cancellation and a full refund will be provided for the
domain.

 13.10 .info Renewals

.info renewal functionality is identical to that for .com/.net/.org

 13.11 .info auth_code

Once registrants successfully register a .info domain, they are provided an “auth_code” which is
a secret pass phrase which shows verifiable proof of ownership of a domain. This is specific to
the registry technologies employed by the .info registry. This code should be kept secret, and is
separate from the management username/password required to manage your OpenSRS domains.
You may obtain this information via the Manage Domain interface, or from the current Registrar
of record.

Registrants can change their auth_code using the manage interface. Registrants will log in to the
page using their existing data and either modify or change the necessary data.




              Page 142 of 174 - Release Version 2.56 - support@opensrs.org
 13.12 .info Manage Considerations

.info names can now be managed using the manage.cgi, or https://manage.opensrs.net. Please
note the following:

    !   Current ‘manage’ integration only includes the ASCII character set for .info and .biz
        domains.
    !   Registrants will have the ability to register associated .info names with profiles created
        with a previous gTLD registration, but not with a previous ccTLD.
    !   Registrants can obtain the Auth_code for .info domains via the Manage Domain interface.

 14 .biz Registrations

 14.1 .biz Reseller qualification

In order to apply for access to sell .biz names from our live environment, resellers must:

        a) Remit a new Reseller contract to OpenSRS authorizing you to act as an OpenSRS .biz
        domain reseller. The contract can be found at:
        http://resellers.tucows.com/opensrs/resources/docs/contracts/bizagreement.pdf

        and…

        b) Bind your customers to the .biz registration terms, found at:
        http://resellers.tucows.com/opensrs/biz/bizexhibita

Once you have the above on your website (or can demonstrate your alternative method for
binding your customers to this agreement) email rite-bc@opensrs.org with the following
information:

To: rite-bc@opensrs.org
Subject: {RSP Username} *.BIZ agreement

Include the URL (from your website) where you have posted the agreement for Tucows review.
Once Tucows receives this email and has checked your website, you will be able to offer .BIZ
registrations.

 14.2 biz registration Considerations

Registrations in the .biz TLD are intended primarily for bona fide business or commercial
purposes, and registrations in the .biz TLD must comply with the Uniform Dispute Resolution
Policy (UDRP), as adopted and as may be amended by the Internet Corporation of Assigned
Names and Numbers. For proceedings initiated before the Commencement-of-Service Date, a
modified version of the UDRP, known as the Start-Up Trademark Opposition Policy (STOP), will
apply.

For purposes of the .biz registration restrictions, “bona fide business or commercial use” shall
mean the use or intent to use the domain name or any content, software, materials, graphics or
other information thereon, to permit Internet users to access one or more host computers
through the DNS for the exchange of goods, services or property of any kind; or to facilitate the
exchange of goods, services, information or property of any kind.




             Page 143 of 174 - Release Version 2.56 - support@opensrs.org
Registering a domain name solely for the purposes of selling, trading or leasing the domain name
for compensation; or the unsolicited offering to sell, trade or lease the domain name for
compensation shall not constitute a "bona fide business or commercial use" of that domain name.

For illustration purposes, the following shall not constitute a “bona fide business or commercial
use” of a domain name:

Using or intending to use the domain name exclusively for personal, noncommercial purposes; or
using or intending to use the domain name exclusively for the expression of noncommercial ideas
(i.e., registering abcsucks.biz exclusively to criticize or otherwise express an opinion on the
products or services of ABC company, with no other intended business or commercial purpose).

 14.3 Modifications to the reseller Web interface for .biz

From the main menu in the RWI, resellers are now able to register .biz names by using the Place
Order Manually link. A .biz domain can be registered by selecting .biz from the drop-down TLD
menu.

Please note: For .biz real-time registration, a minimum 2 year registration term is required.
Additionally, the phone number MUST be in a specific format:

+CCC.NNNNNNNNNNNNxEEEE

Where C = the country dial code, N is up to twelve digits of the phone number, and E is the
extension. The x character is ONLY required if an extension is specified. For Tucows phone
number, this would be +1.4165350123 (where 1 is the dial code for Canada)

 14.4 The .biz auth_code

Once registrants successfully register a .biz domain, they are provided an “auth_code” which is a
secret pass phrase which shows verifiable proof of ownership of a domain. This is specific to the
registry technologies employed by the .biz registry. This code should be kept secret, and is
separate from the management username/password required to manage your OpenSRS domains.
You may obtain this information via the Manage Domain interface, or from the current Registrar
of record.

The latest OpenSRS release provides users the ability to change their auth_code using the
manage interface. Registrants will log in to the page using their existing data and either modify
or change the necessary data.

 14.5 .biz registrant/registrar/reseller transfers

The following will describe the process that is followed for Registrar->Registrar transfers, and
Reseller->Reseller transfers. They are functionally identical.

    1. Tucows receives transfer request order.
    2. Tucows sends authorization email to admin contact with a URL to approve the transfer,
       and a temporary password to accept/reject pages.
    3. Admin must also use the auth_code when approving a transfer. This code is obtainable
       from the current registrar of record and is domain specific.




             Page 144 of 174 - Release Version 2.56 - support@opensrs.org
    4. If either the admin contact or OpenSRS cancel the request (on behalf of registrant)
       transfer request is cancelled.
    5. If the admin contact approves the transfer and includes the auth code, Tucows sends the
       request to registry. (Same as existing gTLD process)
    6. Registry approves transfer.
    7. Tucows notifies reseller/registrant of successful transfer.
    8. One domain year is charged to the Reseller, and added to the domain

 14.6 .biz registration flow

Description

    1.   Registrant completes required information (RCL or other)
    2.   Registrant submits information to reseller (RCL or other)
    3.   Reseller submits information to OpenSRS (via RWI or RCL)
    4.   OpenSRS submits registration to NeuLevel
    5.   OpenSRS debits reseller’s account
    6.   OpenSRS notifies reseller of successful domain registration

 14.7 .biz deletion requests

Registrants/resellers must cancel registrations within 48 hours of submitting the registration. If
this timeline is met, there is no penalty for cancellation. This policy is the same as the current
OpenSRS deletion policy.

 14.8 Reseller pricing for .biz

Tucows resellers are charged $10 per domain year. As the NeuLevel registry has requested a
minimum two-year registration period for real-time registration, resellers are charged $20 for
each registration. Therefore if a reseller submits 10 registrations, they are expected to have
$200 in their account to cover the cost of the transaction.

 14.9 .biz Manage considerations

.biz names can now be managed using the manage.cgi, or https://manage.opensrs.net. Please
note the following:

    !    Registrants will have the ability to register associate .biz names with profiles created with
         a previous gTLD registration, but not with a previous ccTLD.

Registrants can obtain the Auth_code for .biz domains via the Manage Domain interface.

 14.10 .biz Domain Name Application Reserved Names by NeuLevel

A. Labels Reserved at All Levels. The following names shall be reserved at the second level
and at all other levels within the TLD at which Registry Operator makes registrations:


              Page 145 of 174 - Release Version 2.56 - support@opensrs.org
ICANN:
aso
dnso
icann
internic
pso
IANA-related names:
afrinic
apnic
arin
example
gtld-servers
iab
iana
iana-servers
iesg
ietf
irtf
istf
lacnic
latnic
rfc-editor
ripe
root-servers

B. Additional Second-Level Reservations. In addition, the following names shall be reserved
at the second level:

All single-character labels.

All two-character labels shall be initially reserved.

The reservation of a two-character label string shall be released to the extent that the Registry
Operator reaches agreement with the government and country-code manager, or the ISO 3166
maintenance agency, whichever appropriate. The Registry Operator may also propose release of
these reservations based on its implementation of measures to avoid confusion with the
corresponding country codes.

aero
arpa
biz
com
coop
edu
gov
info
int
mil
museum
name
net
org



              Page 146 of 174 - Release Version 2.56 - support@opensrs.org
pro

C. Tagged Domain Names. All labels with hyphens in the third and fourth character positions
(e.g., "bq--1k2n4h4b")

D. Second-Level Reservations for Registry Operations. The following names are reserved
for use in connection with the operation of the registry for the Registry TLD. They may be used
by Registry Operator under Subsection 3.6.1, but upon conclusion of Registry Operator's
designation as operator of the registry for the Registry TLD they shall be transferred as specified
by ICANN:
nic
whois
www

Names staying with the Registry in the event of reassignment:

advisory.biz
api.biz
autorenew.biz
billing.biz
bizdomain.biz
bizinfo.biz
bizlogin.biz
bizlock.biz
bizname.biz
bizness.biz
biznotification.biz
bizregistrar.biz
bizregistrars.biz
bizwebaddress.biz
bulkrenew.biz
business.biz
callcenter.biz
cctld.biz
claims.biz
customercare.biz
customersupport.biz
digitalcertificates.biz
directory.biz
dns.biz
domain.biz
domainname.biz
domainnames.biz
domains.biz
dotbizpromotions.biz
dotbiz.biz
dotbizaccounting.biz
dotbizbilling.biz
dotbizcallcenter.biz
dotbizcards.biz
dotbizcustomercare.biz
dotbizcustomersupport.biz
dotbizhelp.biz



               Page 147 of 174 - Release Version 2.56 - support@opensrs.org
dotbizhelpdesk.biz
dotbizinfo.biz
dotbizmail.biz
dotbizorder.biz
dotbizregistrar.biz
dotbizregistrarsupport.biz
dotbizsecurity.biz
dotbizsite.biz
dotbiztechnicalsupport.biz
dotbiztroubledesk.biz
dotbizwebmaster.biz
ebiz.biz
ebizness.biz
findyour.biz
ftp.biz
getyour.biz
gopher.biz
gtld.biz
helpdesk.biz
hostmaster.biz
identify.biz
imap.biz
info.biz
ldap.biz
multilingual.biz
mybiz.biz
network.biz
nntp.biz
ntp.biz
order.biz
pop.biz
pop3.biz
questions.biz
questionsdotbiz.biz
register.biz
registry.biz
registeryour.biz
registeryourbiz.biz
registrant.biz
registrar.biz
registrarreports.biz
registrars.biz
registrarsupport.biz
registrylock.biz
renew.biz
renewnames.biz
root.biz
rootserver.biz
securedomain.biz
securename.biz
security.biz
servicemark.biz
services.biz



             Page 148 of 174 - Release Version 2.56 - support@opensrs.org
smtp.biz
snmp.biz
technicalsupport.biz
telnet.biz
thebizdomain.biz
thebizregistry.biz
theregistry.biz
troubledesk.biz
usergroup.biz
webmaster.biz
whatbiz.biz
whois.biz
whoisbiz.biz
www.biz
xrp.biz
yourbiz.biz
zone.biz
zonefile.biz
melbourneit.biz
neulevel.biz
neu-level.biz
neulevelinc.biz
neulevelbiz.biz
neulevelllc.biz
neulevelregistrar.biz
neulevelregistrars.biz
neulevelregistry.biz
neulevel-inc.biz
neulevel-llc.biz
neulevel-biz.biz
neustar.biz
newlevel.biz
new-level.biz

 15. .name Registrations

 15.1 The .name opportunity

On October 16, 2000, .name was approved by ICANN as one of seven new gTLDs to be offered
to users. Of the seven new gTLDs, .name targets individual users and is intended for personal
use.

 15.2     .name reseller qualification

In order to apply for access to sell .name domains from our live environment, resellers must:

        Remit a new Reseller contract to Tucows authorizing you to act as an OpenSRS .vc
        domain reseller. The contract can be found at:
        http://resellers.tucows.com/opensrs/resources/docs/contracts/nameagreement.pdf

        Bind your customers to the .vc registration terms, a copy of which can be found at:
        http://resellers.tucows.com/opensrs/name/nameexhibita




              Page 149 of 174 - Release Version 2.56 - support@opensrs.org
Once you have registry terms on your Web site (or can demonstrate your alternative method for
binding your customers to this agreement) e-mail rite-bc@opensrs.org with the following
information:

To: rite-bc@opensrs.org
Subject: {RSP Username} *.name agreement

Include the URL where you have posted the agreement for Tucows review. Once Tucows
receives this e-mail and checks your Web site, you will be able to offer .name pre-registrations.

 15.3 .name registration considerations


Please note: the current release of .name products allows resellers to register a .name domain
or a .name domain/SLD e-mail forward bundle only. No other products are offered in this
release. Note that upgrading to an e-mail bundle is currently not available.

Registrations in the .name TLD will be subject to the following restrictions:

Only top level registrations will be available for domain registration and e-mail forwarding:

So a .name Web address must look like this:

        Firstname.Lastname.name
        or
        Lastname.Firstname.name

And a .name e-mail address must look like this:
        Firstname@Lastname.name
        or
        Lastname@Firstname.name

Definition of a personal name:

Any person can register his or her own personal name. Further, a parent may register the
personal name of his/her child, provided that the registration is in the name of the child. The
same applies to names given as gifts. All registrations must remain in the name of the rightful
owner of the domain. Any individual or entity can register a personal name of a fictional
character if that individual or entity has trade or service mark rights to that name. Registrants
can add numeric characters to the beginning or end of a personal name to differentiate it from
other personal names. For instance, if john.smith.name is already registered, an eligible
registrant may opt to purchase john5.smith.name or john.smith5.name.

 15.4 Modifications to the reseller Web interface for .name

A new link has been placed in the Reseller’s Interface for .name (Place Order Manually for
.name). This is the same interface you’re used to seeing, with one new piece. If you wish to
order the Domain/Email bundle, you MUST fill in the following section:




              Page 150 of 174 - Release Version 2.56 - support@opensrs.org
Note that if you do not enter information here (or if you DO enter information here), once the
order is processed you cannot alter this order.

Please note: For .name real-time registrations the phone number MUST be in a specific format:

+CCC.NNNNNNNNNNNNxEEEE

Where C = the country dial code, N is up to twelve digits of the phone number, and E is the
extension. The x character is ONLY required if an extension is specified. For Tucows phone
number, this would be +1.4165350123 (where 1 is the dial code for Canada)

 15.5 Reseller pricing for .name

Domain registration

Tucows resellers are charged $10 per domain year. The GNR registry is allowing registrations for
periods of one, two or ten years. Therefore, resellers are charged $10, $20 or $100 for each
registration, based on the selected term. If a reseller submits 10 two-year registrations, they are
expected to have $200 in their account to cover the cost of the transaction.

Domain/e-mail forwarding bundle pre-registration

Tucows resellers are charged $20 per registration year. The GNR registry is allowing
registrations for periods of one, two or ten years. Therefore resellers are charged $20, $40 or
$200 for each registration. If a reseller submits 10 two-year registrations, they are expected to
have $400 in their account to cover the cost of the transaction.

 15.6 .name deletion requests

Registrants/resellers must cancel registrations within 48 hours of submitting the registration. If
this timeline is met, there is no penalty for cancellation. This policy is the same as the current
OpenSRS deletion policy.

 15.7 .name renewals and transfers

At the time of this document’s writing, .name renewals and transfers are not available. We will
make every effort to make this work identically to .info/.biz domains, including notification and
auto-renewal functionality.

 15.8 Reserved names

The following names shall be reserved at the second level and at all other levels within the TLD
at which the registry operator makes registrations.

ICANN:


             Page 151 of 174 - Release Version 2.56 - support@opensrs.org
aso
dnso
icann
internic
pso
IANA-related names:
afrinic
apnic
arin
example
gtld-servers
iab
iana
iana-servers
iesg
ietf
irtf
istf
lacnic
latnic
rfc-editor
ripe
root-servers

The following names and domains will be reserved on .name, and as a result, will be restricted
from being registered in the RWI, client code when applicable.

1. All two-letter combinations on the second level (e.g. ab.name, ie.name, li.name, xi.name)
2. All pure numbers on the second level (e.g. 101.name, 534231.name)
3. All labels with hyphens in the second and third character positions (e.g., "bq--
1k2n4h4b")

All of the following second levels:
     1. aero
     2. afrinic
     3. alerts
     4. apnic
     5. arin
     6. arpa
     7. aso
     8. biz
     9. celeb
     10. celebrity
     11. cert
     12. certificate
     13. com
     14. coop
     15. directory
     16. dns
     17. dnso
     18. dotname
     19. edu
     20. etsi



              Page 152 of 174 - Release Version 2.56 - support@opensrs.org
21.   example
22.   famous
23.   findyour
24.   findyourfamily
25.   findyourname
26.   finger
27.   ftp
28.   getyour
29.   getyourname
30.   global
31.   globalregistry
32.   gnr
33.   gopher
34.   gov
35.   gtld-servers
36.   hostmaster
37.   iab
38.   iana
39.   iana-servers
40.   icann
41.   iesg
42.   ietf
43.   imap
44.   info
45.   int
46.   internic
47.   irtf
48.   istf
49.   itu
50.   lacnic
51.   lanic
52.   ldap
53.   login
54.   mil
55.   museum
56.   myname
57.   name
58.   name
59.   namedomain
60.   nameregistry
61.   net
62.   nic
63.   nntp
64.   no1
65.   ntp
66.   org
67.   pop
68.   pop3
69.   pro
70.   pso
71.   registeryour
72.   registeryourname
73.   registry



          Page 153 of 174 - Release Version 2.56 - support@opensrs.org
     74. rfc-editor
     75. ripe
     76. root-servers
     77. scp
     78. security
     79. smtp
     80. snmp
     81. tel
     82. telnet
     83. theglobal
     84. theglobalname
     85. theglobalnameregistry
     86. theglobalregistry
     87. thenamedomain
     88. thenameregistry
     89. w3c
     90. whois
     91. www
     92. yourname
     93. zone
All of the following third levels (where ____ is any second level):
     1. www[1,100].____.name (e.g. www1.____.name, www23.____.name)
     2. mx[1,100].____.name
     3. ns[1,100].____.name
     4. mail.____.name
     5. email.____.name
     6. wap.____.name
     7. http.____.name
     8. directory.____.name
     9. dir.____.name
     10. genealogy.____.name

The following names, which the registry will delegate to an appropriate third party

    1. Jesus.Christ.name
    2. Santa.Claus.name

 16 .US Registrations

 16.1 .us Reseller qualification

In order to apply for access to sell .us names from our live environment, resellers must:

        a) Remit a new Reseller contract to OpenSRS authorizing you to act as an OpenSRS .us
        domain reseller. The contract can be found at:
        http://resellers.tucows.com/opensrs/resources/docs/contracts/usagreement.pdf

        and…

        b) Bind your customers to the .biz registration terms, found at:
        http://resellers.tucows.com/opensrs/us/us_exhibita




             Page 154 of 174 - Release Version 2.56 - support@opensrs.org
Once you have the above on your website (or can demonstrate your alternative method for
binding your customers to this agreement) email rite-bc@opensrs.org with the following
information:

To: rite-bc@opensrs.org
Subject: {RSP Username} *.US agreement

Include the URL (from your website) where you have posted the agreement for Tucows review.
Once Tucows receives this email and has checked your website, you will be able to offer .US
registrations.

 16.2 us registration Considerations

Prospective registrants in the usTLD must fall in one of three U.S. Nexus categories and must
certify that they have a "bona fide presence in the United States." Prospective registrants
must indicate their use of the domain by selecting one of the following categories: Note: By
agreeing to the policies of the registry, registrants agree to having one of the requirements
below. Nothing further is required from the reseller to prove the registrant has a legitimate
registration.

For an up to date version of the official Nexus Requirements from the Neustar registry, please
see the document located here:
http://www.neustar.us/policies/docs/ustld_nexus_requirements.pdf.

Nexus Category 1
A natural person (i) who is a United States citizen, (ii) a permanent resident of the United
States of America or any of its possessions or territories, or (iii) whose primary place of
domicile is in the United States of America or any of its possessions.

Nexus Category 2
An United States entity or organization that is (i) incorporated within one of the fifty (50) U.S.
states, the District of Columbia, or any of the United States possessions or territories or
organized, or otherwise constituted under the laws of a state of the United States of America,
the District of Columbia or any of its possessions or (including a federal, state, or local
government of the United States, or a political subdivision thereof, and unincorporated
organizations based in the United States).

Nexus Category 3
An entity or organization (including a federal, state, or local government of the United States,
or a political subdivision thereof) that has a bona fide presence in the United States of America
or any of its possessions or territories.
    •   If foreign entity, Applicant must state country of citizenship.

    •   Check from category list, basis for compliance with Nexus requirement - regularly sells
        goods in the United States; regularly provides services in the United States; regularly
        engages in business activities, trade or other business (commercial or non-commercial
        including not-for-profit) relations in the United States;

    •   Maintains an office or other property within the United States.


Nexus requirements can be entered during the registration process, and altered via the Manage
interface.




             Page 155 of 174 - Release Version 2.56 - support@opensrs.org
 16.3 Modifications to the reseller Web interface for .us

From the main menu in the RWI, resellers are now able to register .us names by using the Place
Order Manually for .us link.

Nexus Requirements MUST be filled in for .us domain names:




Please note: For .us real-time registration, a minimum 2 year registration term is required.
Additionally, the phone number MUST be in a specific format:

+CCC.NNNNNNNNNNNNxEEEE

Where C = the country dial code, N is up to twelve digits of the phone number, and E is the
extension. The x character is ONLY required if an extension is specified. For Tucows phone
number, this would be +1.4165350123 (where 1 is the dial code for Canada)

 16.4 The .us auth_code

Once registrants successfully register a .us domain, they are provided an “auth_code” which is a
secret pass phrase which shows verifiable proof of ownership of a domain. This is specific to the
registry technologies employed by the .us registry. This code should be kept secret, and is
separate from the management username/password required to manage your OpenSRS domains.
You may obtain this information via the Manage Domain interface, or from the current Registrar
of record.

The latest OpenSRS release provides users the ability to change their auth_code using the
manage interface. Registrants will log in to the page using their existing data and either modify
or change the necessary data.

 16.5 .us registrant/registrar/reseller transfers

The following will describe the process that is followed for Registrar->Registrar transfers, and
Reseller->Reseller transfers. They are functionally identical.

    1. Tucows receives transfer request order.




             Page 156 of 174 - Release Version 2.56 - support@opensrs.org
    2. Tucows sends authorization email to admin contact with a URL to approve the transfer,
       and a temporary password to accept/reject pages.
    3. Admin must also use the auth_code when approving a transfer. This code is obtainable
       from the current registrar of record and is domain specific.




    4. If either the admin contact or OpenSRS cancel the request (on behalf of registrant)
       transfer request is cancelled.
    5. If the admin contact approves the transfer and includes the auth code, Tucows sends the
       request to registry. (Same as existing gTLD process)
    6. Registry approves transfer.
    7. Tucows notifies reseller/registrant of successful transfer.
    8. One domain year is charged to the Reseller, and added to the domain

 16.6 .us registration flow

Description

    1.   Registrant completes required information (RCL or other)
    2.   Registrant submits information to reseller (RCL or other)
    3.   Reseller submits information to OpenSRS (via RWI or RCL)
    4.   OpenSRS submits registration to NeuStar
    5.   OpenSRS debits reseller’s account
    6.   OpenSRS notifies reseller of successful domain registration

 16.7 .us deletion requests

Registrants/resellers must cancel registrations within 48 hours of submitting the registration. If
this timeline is met, there is no penalty for cancellation. This policy is the same as the current
OpenSRS deletion policy.

 16.8 Reseller pricing for .us

Tucows resellers are charged $10 per domain year. As the NeuStar registry has requested a
minimum two-year registration period for real-time registration, resellers are charged $20 for
each registration. Therefore if a reseller submits 10 registrations, they are expected to have
$200 in their account to cover the cost of the transaction.

 16.9 .us Manage considerations

.us names can now be managed using the manage.cgi, or https://manage.opensrs.net. Please
note the following:

    !    Registrants will have the ability to register associate .us names with profiles created with
         a previous gTLD registration, but not with a previous ccTLD.




              Page 157 of 174 - Release Version 2.56 - support@opensrs.org
Registrants can obtain the Auth_code for .biz domains via the Manage Domain interface.

 17. Order Queuing
Note that this feature will not be available until sometime after July 15th 2002.

 17.1 Queuing setting in Reseller Web Interface

This is a new powerful feature in the OpenSRS system. This allows you the ability to have our
system automatically queue transactions if a supplier (registry) is offline or having
communications problems, and then process those transactions once the supplier (registry) is
reachable again. If enabled, this is done in real-time and requires no effort on your part.

Note that this will ONLY queue billable transactions (new domains, transfer requests, renewals).
Funds are not removed from your account until the queue (and transactions therein) is
processed. Additionally, any transactions entering the queue are NOT guaranteed, since the
transaction has not yet reached the registry. Given this, you must ensure that if you are enabling
this capability you are aware that you are potentially turning a synchronous supplier into an
asynchronous supplier. While this will allow you to take orders when a supplier is offline (either
scheduled, unscheduled, or unreachable due to internet connectivity issues) it will also mean that
you may be taking orders (paid for) that won’t process.

NOTE: .ca transfers, due to their unique processing nature, are NOT queued transactions.

First, there are new settings and interfaces in the Reseller Web Interface
(http://resellers.opensrs.net/) as seen below:




 17.2 Queuing Settings

The default for transaction Queuing is OFF for all suppliers. If you have “Enabled” selected, it will
turn on queuing for ALL the products you offer. If you select “Disabled”, you can then opt to
select whichever supplier concerns you (or you are willing to handle the potential asynchronous
billing for). Note that the wording of the interface is currently misleading – this will be corrected
in future releases (perhaps before the product is launched). Below is an example of an account
that has only com/net/org, .biz and .us enabled for queuing.

Request Queuing for ALL Registry's (this will OVERRIDE any settings in the Individual Settings,
                                             below):

                                         Enabled        Disabled

                                       Individual Settings
                                   Registry        Queuing Enabled

                             NSI: .com .org .net

                             CIRA: .ca



              Page 158 of 174 - Release Version 2.56 - support@opensrs.org
                             Afilias: .info

                             Neulevel: .biz

                             Neustar: .us

                                           e      ng   tngs
                                      U pdat Q ueui Seti


 17.3 Viewing Queued Requests

During a supplier outage (or unavailability), any transactions that are queued (if you’ve opted for
them) are viewable via this interface. This will show the Request ID, Registry, Time Queued,
Request Details, and an option to Cancel.

The Request ID is for internal purposes only and can be ignored, unless you require specific
support (i.e. why is this ID not leaving the queue). The registry shows which supplier for which
this transaction has been queued. Time Queued shows the date and timestamp for when the
transaction was placed into the queue (consequently, ordered). Request Details show details
such as order type (new domain/renew/transfer), the reg_system order #, and the domain in
question.

The queues are processed automatically by our system as it determines supplier availability. This
is done in real-time without any interaction required by you. Transactions are done first in, first
out from the queue. If, during the processing of the transaction, there are any errors (domain
not available, insufficient funds, etc) an error is generated and the order is placed into Pending
Orders.

You may opt to cancel a transaction that resides in the queue before it’s processed. Note that
this will ONLY work if a) the supplier is down or b) that particular transaction hasn’t been re-
processed from the queue.

                                     View Queued Requests
Request ID Registry          Time Queued                     Request Details                Cancel
                          14-JUN-2002            sw_register new tucowsqueuetest.com
    196       NSI
                          13:36:28               for 1
                          14-JUN-2002            process_sw_order #3489343 for
    291       Neulevel
                          14:39:00               tucowsqueue.biz
                          14-JUN-2002            process_sw_order #3490102 for
    345       Neustar
                          14:39:09               tucowsqueue.us
                                               ect         s
                                      C ancelSel ed R equest




 18. Technical Support

This section will outline the various support resources available to Resellers.




              Page 159 of 174 - Release Version 2.56 - support@opensrs.org
 18.1 Technical Support

OpenSRS support can be reached using the following methods:

    -   email; support@opensrs.org
    -   phone; 416 535 0132 or 800 798 1114 in North America, M-F 8AM to 8PM EST, S-S 9AM
        to 5PM EST
    -   fax; 416 531 2516
    -   emergency pager; http://www.opensrs.org/.emerg/ - 7x24 pager; for guidelines on
        emergency support use, please review:
        http://resellers.tucows.com/opensrs/faq/support_faq#Live_Emergency

 18.2 The OpenSRS Web Site

The OpenSRS web site (http://resellers.tucows.com/opensrs/) has been designed with three
goals in mind:

    -   to generate interest in prospective Resellers, and to sign them up
    -   to provide existing Resellers with the resources they need to run a domain registration
        business through the OpenSRS system
    -   to provide End Users with enough information about the OpenSRS system that they
        might choose to register a domain name through an OpenSRS reseller.

Please send any questions or comments regarding the OpenSRS web site to
suggest@opensrs.org

 18.3 Peer based support

OpenSRS operates and maintains several mailing lists for our Resellers. We heavily encourage
participation in these lists, as they allow Resellers to discuss issues, and solve business and
technical problems. The lists are closely monitored by Tucows staff, who contribute regularly.
For current information and subscription methods, please refer to:

http://resellers.tucows.com/lists/

 18.4 Other documentation

Other documentation is available from the OpenSRS web site or in the current code distribution.
All current documents can be found at:

http://resellers.tucows.com/opensrs/documentation/

This documentation includes:

    -   “Upgrade Overview” – for existing Quickstart and Full Access Resellers, provides an
        overview of changes in this release and their business impact
    -   “OpenSRS Protocol Spec” – for Resellers who wish to develop their own implementation
        of OpenSRS in a language of their choice
    -   “OpenSRS PERL Client Manual” – for Full Access Resellers, provides details on the PERL
        client provided

In addition to this, our web site has several FAQs which are updated an a daily basis.




              Page 160 of 174 - Release Version 2.56 - support@opensrs.org
 18.5 Communication methods

The following is a description of how Tucows communicates important information our Resellers.

Live reseller notification

We have a system that sends messages to all active resellers. Resellers are able to control where
these messages are directed, by selecting "Emergency Contact Information", then "System Status
Announcements" in the RWI (Reseller Web Interface) on our *live* (as opposed to ‘test’) system

This will get a message to all live Resellers who have configured this setting appropriately (by
default it is populated with your technical contact info). This is used for:

    a) downtime announcements (scheduled and unscheduled)
    b) new release information
    c) critical operational information

It is important to ensure that this setting is configured correctly so you will receive these
important announcements.

 19. Appendix A. Data Constraints
The following section shows the data rules that must be followed when entering data in the
various OpenSRS fields.

phone numbers
        - max 40c
        - whitespace stripped
                 - /^[\d\-\(\)\.\+\#\*]{4,}((x|ex|ext|xt)\.?\d+)?(TDD)?$/i
                 - >= 4d
                 - > 1/3 digits total
                 - matching # left/right brackets
For EPP domains (.info/.biz/.us/.name)
        - EPP Phone Format
        - +CCC.NNNNNNNNNNNNxEEEE
        - C = Country Dial Code, N = number, E = extension
        - x is ONLY required if an extension is specified
        - /^\+\d{1,3}\.\d{1,12}( *x\d{1,4})?$/

fax numbers
        - max 40c
        - whitespace stripped
                 - /^[\d\-\(\)\.\+]{4,}$/
                 - >= 4d
                 - > 1/3d total
                 - matching # left/right brackets
        - checking not currently implemented
For EPP domains (.info/.biz/.us/.name)
        - EPP Phone Format
        - +CCC.NNNNNNNNNNNNxEEEE
        - C = Country Dial Code, N = number, E = extension
        - x is ONLY required if an extension is specified
        - /^\+\d{1,3}\.\d{1,12}( *x\d{1,4})?$/



              Page 161 of 174 - Release Version 2.56 - support@opensrs.org
email addresses
       - uses RFC822 check in Email::Valid

field limits:

NOTE: .biz and .us domains follow these requirements, EXCEPT the maximum for fields is 30
characters (or less)

        *_first_name     =>   64
        *_last_name      =>   64
        *_org_name       =>   64
        *_address1       =>   64   (note, conflicts in various areas)
        *_address2       =>   64   (optional) (note, conflicts in various areas)
        *_address3       =>   64   (optional) (note, conflicts in various areas)
        *_city           =>   64
        *_state          =>   32
        *_country        =>   2
        *_postal_code    =>   32(req'd if country =~ /^(us|ca)$/
        *_phone                  => 20 (note, conflicts in various areas)
        *_fax            => 20 (note, conflicts in various areas) (optional)
        *_email          => 100
        *_url            => 255 (optional)
        reg_username     => 100
        reg_password     => 20, 1S+
        domain           => 80
        fqdn1            => 60, /^[a-z0-9][a-z0-9\.\-]*[a-z0-9]$/
        fqdn2            => 60, /^[a-z0-9][a-z0-9\.\-]*[a-z0-9]$/
        fqdn3            => 60, /^[a-z0-9][a-z0-9\.\-]*[a-z0-9]$/
        fqdn4            => 60, /^[a-z0-9][a-z0-9\.\-]*[a-z0-9]$/
        fqdn5            => 60, /^[a-z0-9][a-z0-9\.\-]*[a-z0-9]$/
        fqdn6            => 60, /^[a-z0-9][a-z0-9\.\-]*[a-z0-9]$/
        lang_pref        => (for .ca domains)
        isa_trademark    => (for .ca domains)
        legal_type       => (for .ca domains)
        period           => int 1..10 (1 if renewal)




                Page 162 of 174 - Release Version 2.56 - support@opensrs.org
 20. Appendix B. Detailed .com/net/org Transfer
Process
The following section outlines, in detail, the .com/.net/.org Transfer process.
                                                    1 .0 T u c o w s T ra n s fe r P ro c e s s -G a in in g
      S TAR T
                                                                     R e g is tra r (G R )

                                                                                                             4
         1                                  2                                                                                           5
                                                                                                     Tucows O penSRS
  Entity initiates                  Tucows system                          3                                                     Adm inistrative
                                                                                                   sends em ail to Dom ain
 Dom ain Transfer                   retrieves W hois                Is Dom ain on                                               contact of record
                                                                                                      Adm in Contact
   Request to                      output from Losing               Restricted list?                                             responds in 7
                                                                                                  requesting authorization
     Tucows                             Registrar                                                                                    days
                                                                                                        of Transfer

                                                                                       NO
                                                                                            YES                        YES



                                7                                        6
                                                                                                          8
                       Transfer request is                       Is Adm inistrative
                                                    NO                                             Adm inistrative
                          placed into a                          contact of record
                                                                                                  contact of record
                         holding queue                                valid?                YES   visits W ebsite to
                                                                                                  approve or reject
       YES                                                                                             transfer




                                                                 10
                                 9
                                                          Adm inistrative
                         Tucows Adm in
                                                         contact of record                                11
                       attem pts to correct
                                                          em ail address                             Is Transfer
                          em ail address
                                                           Corrected?                               approved by                     NO
                                                                                                     Authorized
                                                                                                        party?                                      NO


                                                               NO                                        YES



                                                                                                          13
                                                                                                                                     13
                                                                                                       Record of
                                                               12                                                             Record of Denial
                                                                                                     Authorization
                                                          Tucows Staff                                                           stored with
                                                                                                      stored with
                                                         cancels transfer                                                      transaction by
                                                                                                    transaction by
                                                             request                                                         Tucows O penSRS
                                                                                                  Tucows O penSRS




                                                                                                                                 Transfer
                                                                                                       Continu
                                                                                                                                   Fails
                                                                                                        e 1.2
                                                                                                                                   (1.1)
         14
 Transfer request
    placed into
"restricted" holding
       queue




              15                                                          16
                                                                                                                                    17
   Tucows Staff exam ines                                           Tucows Staff
                                              YES                                                                              Tucows Staff
 holding queue and contacts                                       authorizes transfer
                                                                                                                              cancels transfer
   Registrant of record to                                             request
                                                                                                                                  request
m anually re-verify intention to
           transfer




                                          18
                                       Transfer                                                     NO
                                       verified?




                       Page 163 of 174 - Release Version 2.56 - support@opensrs.org
                            1.1 Tucow s Transfer P rocess -
                                    Transfer Fails




     IN




                                            20
     19                             Tucows sends
Transfer Fails                     em ail that transfer
                                          failed




                                          END




             Page 164 of 174 - Release Version 2.56 - support@opensrs.org
                           1.2 Tucow s Transfer P rocess -
                               G aining R egistrar (G R )




      1.2




       21
Transfer request
sent to Registry




       22
                                23
 Registry sends
                         Losing Registrar
    transfer
                        m inim um attribute
announcem ent to
                               check
Losing Registrar




                                                Continu
                                                 e 1.3




              Page 165 of 174 - Release Version 2.56 - support@opensrs.org
                            1 .3 T u c o w s T ra n se r P ro ce s s - G a in in g
                                             R e g is tra r (G R )




                      1.2




                                                                      24                                 25
                                                               Attribute Check    NO              Losing Registrar
                                                                   passed?                         denies transfer




                                                                    YE S


                                        27
         26                                                          28
                                    Registry                                                          29
 G aining Registrar                                           Losing Registrar
                                  undertakes                                                  Registry cancels
notifies Registrant                                            does nothing/
                                 transfer and                                                 transfer, notifies
    of record of                                               acknowledges
                                notifies G aining                                             G aining Registrar
successful transfer                                               transfer
                                   Registrar




                                                                                                         30
                                                                       31
                                                                                                  Tucows receives
                                                               Transfer Tim es-   NO
                                                                                                   em ail within 5
       END                                                      O ut at Tucows
                                                                                                       days




                                                                                            YE S




                                                                                       Transfer
                                                                                         Fails
                                                                                         (1.1)




                                                See 2.0 for M ore Detail on
                                               the Losing Registrar process
                                                    that Tucows uses




             Page 166 of 174 - Release Version 2.56 - support@opensrs.org
                                       2.0 Tu cow s T rans fer P ro ces s - Los ing
                                                    R eg istra r (LR )




        1.2




                                                                34
          32
                                                       Tucows O penSRS                    35
Tucows O penSRS                                                                                                          36
                                    33                      retrieves              Tucows O penSRS
      receives                                                                                                    Does Registrant
                             Is it a Tucows            Registrant contact           sends em ail to
   notification of                                                                                                 of record visit
                                Dom ain?                    of record               Registrant and
 transfer request                                                                                                     website?
                                                        inform ation from           Losing Reseller
   from Registry
                                                         local database


                                                                                                                                     YES
                                                     NO (tim eout)


                                                                                                                     38
         37                       NO                                                                          Transfer approved
Em ail from registry                                                 YES                                       by Registrant of
   not relevant                                                                                                   Record?




                                                                                                     39
                                                                                                                       NO
                                                                                            Tucows O penSRS
                                                                                                sends "deny
      STOP
                                                                                            transfer" com m and
                                                                                                 to registry




                                         41                                                          43
                                                                      42
              40                     Registry                                                Registry cancels
                                                             Tucows O penSRS
      Tucows O penSRS               undertakes                                                transfer request
                                                               sends "approve
      waits for Registry           transfer and                                                  and notifies
                                                             transfer" com m and
         notification               notifies the                                             Gaining Registrar
                                                                  to registry
                                 Gaining Registrar




                                                                                                 Transfer
                                                                                                   Fails
                                                                                                   (1.1)
              END




 Transfer Process Flow Narrative


NOTE: These numbers correspond to the transfer process in the process
flow diagrams above. Numbers run from [1] to [43].


[1]           Entity initiates Domain Transfer Request to Tucows – The entity in question may
              or may not be the actual registrant or someone authorized to act on their behalf. This
              transfer request is filed with an authorized Tucows Reseller via the Tucows OpenSRS
              API. Identity of Entity is not verified. This qualifies Tucows as the Gaining Registrar.
              Tucows OpenSRS creates a domain transfer record in the OpenSRS database and stores
              the information provided by the un-verified entity. The Entity is bound, by the Reseller,
              to the Tucows OpenSRS gTLD Registration Agreement as part of this request procedure.



                       Page 167 of 174 - Release Version 2.56 - support@opensrs.org
[2]   Tucows system retrieves Whois output from Losing Registrar – Tucows
      OpenSRS performs a Whois query against whois.crsnic.net to retrieve the identity of the
      Losing Registrar and the address of the Whois server of the Losing Registrar. Tucows
      OpenSRS then performs an automated Whois query against the Whois server of the
      Losing Registrar to retrieve the complete Whois record for the domain name described in
      the original transfer request. Each Losing Registrar typically has a different display format
      for their Whois data output. This data is then stored in the OpenSRS database along with
      the original Transfer request data. Once stored, the output becomes a permanent record
      of the status of the domain name at the time the transfer request was filed. This ensures
      continuity of sponsorship, contact details, expiration and nameservice.

[3]   Is Domain on Restricted List – Tucows maintains a list of domain names that should
      not be transferred to Tucows under normal circumstances. This is an evolving list
      consisting of the domain names of high-profile web sites. Tucows OSRS checks the
      domain for which a transfer is being requested, against this list of “restricted” domains.
      Tucows Staff must manually process a transfer requests matching domains names that
      are on the restricted list.


[4]   Tucows OpenSRs sends email to Domain Admin Contact requesting
      authorization of the Transfer - Tucows OpenSRS sends an email to the Administrative
      Contact of record as specified by the Whois output of the Losing Registrar. This is a
      Reseller customizable message that is sent for every transfer request.

      Tucows OpenSRS logs that this email was sent by making an entry in the domain notes
      table, indicating the date and time the email was sent.

      If the email that is sent to the Administrative Contact or record bounces, then Tucows
      OpenSRS automatically forwards the bounced email to the Technical Contact of Record.

[5]   Administrative Contact of record responds in 5 days - The Administrative Contact
      of record is given 5 days to respond to the instructions in the email that was sent by
      Tucows OpenSRS (see [4]). The instructions include a URL that the admin contact must
      visit to either accept or reject the transfer request. If the Administrative Contact of
      record does not visit the URL to either confirm or deny the transfer within 5 days,
      Tucows OpenSRS will not undertake the transfer request as the appropriate authorization
      has not been obtained.

      If the Administrative Contact of record does not respond at the specified URL within 5
      days, then the transfer request is considered to have “timed-out”. Tucows OpenSRS
      notifies the Gaining Reseller by email, informing them that the transfer has timed-out.
      Tucows OpenSRS logs that this email was sent by making an entry in the domain notes
      table, including the date and time the email was sent. Bounces of this email are
      automatically forwarded by Tucows OpenSRS to data_admin@opensrs.org - where
      Tucows Staff manages them.

      In addition, Tucows OpenSRS notifies the Registrant by email, informing them that the
      transfer has timed-out. Tucows OpenSRS logs that this email was sent by making an
      entry in the domain notes table, indicating the date and time the email was sent.
      Bounces of this email are sent to the Tucows Reseller.




           Page 168 of 174 - Release Version 2.56 - support@opensrs.org
[6]    Is Administrative Contact of record valid – In order to contact the Administrative
       Contact of record to verify the transfer request, the email address must be acquired. If
       this is not listed in the Whois database of the Losing Registrar, then this verification
       cannot occur in an automated fashion.

       Tucows OpenSRS attempts to determine the email address for the Administrative Contact
       of record by querying the Whois output of the Losing Registrar. If Tucows OpenSRS
       cannot determine the email address of the admin contact (e.g. it is missing, does not
       contain valid characters or does not adhere to the RFC dictated format for an internet
       email address), the transfer request is placed into a holding queue for processing by
       Tucows Staff (see [7]). If the email address is available from the Whois output and is
       properly formed, the system can proceed to email the Administrative Contact of record
       with instructions for approving or denying the transfer request (see [4]).

[7]    Transfer request is placed into a holding queue – If the email address of the
       Administrative Contact of record is not valid (see [6]), then the transfer request is placed
       into a holding queue to be manually processed by Tucows Staff.

[8]    Administrative Contact of record visits Website to approve or reject transfer –
       The Administrative Contact of record has received an email instructing them to visit a
       URL where they can either approve or deny a domain transfer request (see [4]).

[9]    Tucows Admin attempts to correct email address - Tucows Staff will use the
       information captured from the Whois database of the Losing Registrar to ascertain the
       correct email address of the Administrative Contact or record.

[10]   Administrative Contact of record email address Corrected – If Tucows Staff can
       determine the correct email address of the domain admin contact, they will add it to the
       transfer request, and re-submit the transfer for automated processing. At this point, the
       procedure will continue at [4]. If Tucows Staff cannot determine the correct email
       address for the Administrative Contact of record, the transfer will be cancelled as shown
       in [12].

[11]   Is Transfer approved by Authorized party - This is a decision point during which the
       Registrant or Administrative Contact of record for the domain must determine whether or
       not they wish to undertake the transfer request. One of two results is possible, either

       Administrative Contact of record denies authorization – The Administrative
       Contact of record will visit the URL listed in the email that they were sent by Tucows
       OpenSRS. By clicking on the “I Do Not Wish To Proceed With This Transfer” button, the
       Administrative Contact of record is explicitly denying Tucows the authorization to
       continue with the transfer.

       Tucows OpenSRS notifies the Gaining Reseller by email, informing them that the transfer
       has been rejected. Tucows OpenSRS logs that this email was sent by making an entry in
       the domain notes table, indicating the date and time the email was sent. Bounces of this
       email are sent to data_admin@opensrs.org - where they are administered by Tucows
       Staff.

       In addition, Tucows OpenSRS notifies the Registrant by email, informing them that the
       transfer has been rejected. Tucows OpenSRS logs that this email was sent by making an
       entry in the domain notes table, including the date and time the email was sent.
       Bounces of this email are sent to the email address of the Technical Contact of record.



            Page 169 of 174 - Release Version 2.56 - support@opensrs.org
OR

       Administrative Contact of record verifies transfer request – If the Administrative
       Contact of record visits the URL listed in the email that they were sent by Tucows
       OpenSRS and clicks on the “I Wish To Proceed With This Transfer” Tucows can
       undertake a transfer request from the registry due to the procurement of the appropriate
       authorization from the Domain Holder, or someone with the apparent authority to
       authorize the transfer.

       Tucows’ system OpenSRS notifies the Gaining Reseller by email, informing them that the
       transfer has been approved. Tucows’ system OpenSRS logs that this email was sent by
       making an entry in the domain notes table, indicating the date and time the email was
       sent. Bounces of this email are sent to data_admin@opensrs.org - where Tucows Staff
       handles them.

       In addition, Tucows’ system OpenSRS notifies the Registrant by email, informing them
       that the transfer has been approved. Tucows’ system OpenSRS logs that this email was
       sent by making an entry in the domain notes table, indicating the date and time the
       email was sent. Bounces of this email are sent to the Gaining Reseller.


[12]   Tucows Staff cancels transfer request – Tucows could not determine the correct
       email address of the Administrative Contact of record, therefore the transfer request is
       cancelled by Tucows Administrative Staff. Tucows OpemSRS will not undertake the
       transfer request, as the appropriate authorization to transfer has not been obtained.

[13]   Record of authorization/denial stored with transaction by Tucows OpenSRS –
       Regardless of whether the Administrative Contact of record approves, denies, or does
       nothing with the transfer request, the status of the transaction is stored in the Tucows
       OpenSRS database. The elements requested from the Administrative Contact of record,
       or otherwise automatically acquired include Owner Confirm Date, Owner Confirm IP
       address, Owner Confirm Phone, Registry Request Date. These additional elements are
       stored with the original domain name transfer request record described in endnoteError!
       Bookmark not defined.



[14]   Transfer request placed into “restricted” holding queue – If the domain name is
       on the restricted list, it will be placed in a holding queue to be manually inspected by
       Tucows Staff.

[15]   Tucows Staff examines holding queue and contacts Registrant of record to
       manually re-verify intention to transfer – Tucows Staff will use the information
       captured from the Whois database of the Losing Registrar to contact the Registrant and
       manually re-confirm their intention to transfer. This is typically conducted via telephone.

[16]   Tucows Staff authorizes transfer request – If the Administrative Contact of record
       re-verifies their intention via the manual process described in [16], then Tucows staff will
       approve the transfer request for processing by the registry.

[17]   Tucows Staff cancels transfer request – If the Administrative Contact of record fails
       to re-verify their intention via the manual process described in [16], then Tucows staff
       will cancel the transfer request.




             Page 170 of 174 - Release Version 2.56 - support@opensrs.org
[18]   Transfer verified – This is a decision point representing the wishes of the
       Administrative Contact of record for the domain name subject to the transfer request.

[19]   Transfer fails – The transfer will not be forwarded to the Registry for processing as a
       legitimate transfer.

[20]   Tucows sends email that transfer failed – Tucows OpenSRS notifies the Gaining
       Reseller by email, informing them that the transfer has failed, and the reason for the
       rejection. Tucows OpenSRS logs that this email was sent by making an entry in the
       domain notes table, indicating the date and time the email was sent. Bounces of this
       email are sent to data_admin@opensrs.org - where Tucows Staff handles them.

       In addition, Tucows OpenSRS notifies the Registrant by email, informing them that the
       transfer has failed and the reason for the failure. Tucows OpenSRS logs that this email
       was sent by making an entry in the domain notes table, including the date and time the
       email was sent. Bounces of this email are sent to the email address of the Technical
       Contact of record.

[21]   Transfer request sent to registry – this is undertaking exclusively via the RRP to
       Verisign Global Registry Services.

[22]   Registry sends transfer announcement to losing registrar – This process is
       external to Tucows and cannot be sufficiently documented.

[23]   Losing registrar minimum attribute check – Upon receipt of the transfer
       announcement sent by the registry, the losing registrar must undertake to ensure that
       the domain registration possesses the following attributes:
           - it is not subject to situations described in the UDRP or other legal proceedings
              that supercede the registrants authority to transfer
           - the registrant is not pending bankruptcy
           - there is no dispute over the identity of the registrant
           - the domain name has been registered for at least 60 days

[24]   Attribute Check Passed – The losing registrar conducts the minimum attribute check
       described in [23], if the check passes, then the transfer is allowed, as described in [28].
       If the check fails, then the transfer is explicitly disallowed, as described in [29].

[25]   Losing Registrar denies transfer – If the registration pending transfer does not
       possess the aforementioned attributes, the losing registrar may deny the transfer
       request.

[26]   Gaining Registrar notifies Registrant of record of successful transfer – Tucows
       OpenSRS notifies the Registrant of record and Reseller via email that the transfer (to
       Tucows) was successful.

       Tucows OpenSRS logs that these emails were sent by making an entry in the domain
       notes table, indicating the date and time the email was sent.. Any bounces of the email
       sent to the Reseller are automatically forwarded OpenSRS to data_admin@opensrs.org -
       where Tucows Staff handles them.

       Any bounces of the email sent to the Registrant are automatically sent to the email
       address of the Technical Contact of record.




            Page 171 of 174 - Release Version 2.56 - support@opensrs.org
[27]   Registry undertakes transfer and notifies Gaining Registrar – self-explanatory.

[28]   Losing Registrar does nothing/acknowledges transfer – if the registration
       pending transfer possesses the aforementioned attributes, then the Losing Registrar
       must authorize the transfer request from the registry or do nothing.

[29]   Registry cancels transfer, notifies Gaining Registrar – self explanatory

[30]   Tucows receives email within 9 days – When the Registry cancels the transfer
       request (see [29]) it sends an email notification to the party that would have been the
       Gaining Registrar (had the transfer succeeded). Tucows OpenSRS monitors for this
       email, and when received, it records the transfer has having failed.

[31]   Transfer Times-Out at Tucows – When the Registry cancels the transfer request (see
       [29]) it sends an email notification to the party that would have been the Gaining
       Registrar (had the transfer succeeded). Tucows OpenSRS monitors for this email, if no
       email is received from the registry within 9 days of a transfer request being made, the
       system assumes that the transfer failed.

[32]   Tucows OpenSRs receives notification of transfer request from Registry – The
       registry sends email notifications to the Losing Registrar that a transfer request is in
       process. Tucows OpenSRS automatically receives this email, parses its contents and
       continues the Losing Registrar transfer procedure as described in later steps.

       Transfer emails (from Registry) are received at transfers@opensrs.org and then copied to
       transfers-copy@opensrs.org for processing. The original email sent to
       transfers@opensrs.org is kept for audit purposes.

[33]   Is it a Tucows domain – Tucows OpenSRS validates that the domain that is referred to
       in the Registry notification email (see [32]) is a domain that is sponsored by Tucows. If
       it is, processing continues (see [34]). If not, the email is ignore (see [37]).

[34]   Tucows OpenSRS retrieves Registrant Contact of record information from local
       database – Once Tucows OpenSRS has ascertained that the domain being transferred is
       a Tucows sponsored domain, it queries the Tucows OpenSRS database for the contact
       information of the registrant, including the email address of the Registrant which is used
       in [35].

[35]   Tucows OpenSRS sends email to Registrant and Losing Reseller - Tucows sends
       an email to the Registrant of record and the Losing Reseller notifying them that a request
       exists to transfer their domain to another Registrar. The email that is sent to the
       Registrant contains instructions for the Registrant of record to visit a specific URL where
       they can either confirm or deny the transfer

       Tucows OpenSRS automatically forwards bounces of this email to the tech contact email
       address of the Losing Reseller.

       Tucows OpenSRS logs that this email was sent by making a record in the domain notes
       table.

[36]   Does Registrant of record visit website – Upon receiving the instructional email (see
       [35]), the Registrant of record can choose to visit the URL provided and confirm or deny
       the transfer. In addition, the Registrant can choose to do nothing, in which case the



            Page 172 of 174 - Release Version 2.56 - support@opensrs.org
       opportunity for the Registrant to deny the transfer times-out, and the Registry
       automatically completes the transfer (see [41]).

[37]   Email from registry not relevant – Tucows OpenSRS determines that the transfer
       notification email received from the Registry does not pertain to a domain under Tucows’
       sponsorship. In this case, the email is ignored and no further processing occurs.

[38]   Transfer approved by Registrant of record - Upon receiving the instructional email
       (see [35]), the Registrant of record visits the URL provided and confirms ([42]) or denies
       the transfer ([39]) by clicking on the appropriate button on the transfer web page.

[39]   Tucows OpenSRS sends "deny transfer" command to registry - Tucows OpenSRS
       denies the transfer and sends a "deny transfer" command to registry using the Registry
       defined machine-to-machine registration protocol.

       Tucows OpenSRS makes an entry in the domain notes table that the transfer was denied.

       If this command to the registry fails, Tucows OpenSRS makes a log of the registry failure
       in the domain notes table.

       Tucows OpenSRS sends an email to the Losing Reseller that the domain will not be
       transferred. Tucows OpenSRS logs that this email was sent by making an entry in the
       domain notes table, indicating the date and time the email was sent.. Any bounces of
       this email are automatically forwarded by the system OpenSRS to
       data_admin@opensrs.org - where Tucows Staff handles them.

       Tucows OpenSRS sends an email to the Registrant of record that the transfer was denied
       (and the transfer will not occur). Tucows OpenSRS logs that this email was sent by
       making an entry in the domain notes table, indicating the date and time the email was
       sent.. Any bounces of this email are automatically forwarded by the system OpenSRS to
       the email address of the Technical Contact of record.

[40]   Tucows monitors Registry for transfer to be effected – Once a transfer away from
       Tucows is in progress, Tucows OpenSRS continually monitors the registry to determine at
       which point Tucows has lost the domain to the Gaining Registrar.

       Once the transfer has been determined, the domain is marked as “transferred” from the
       OSRS system. This is necessary because if the Registrant does not explicit approve or
       deny the transfer request, it times-out at the registry level, at which point the registry
       proceeds with the registrar transfer, but Tucows (the losing registrar) is not explicitly
       informed of this (for Verisign transfers).

       Once the transfer is determined, Tucows OpenSRS sends an email to the Registrant
       informing them that the transfer has concluded and that Tucows is no longer the
       Registrar of record for the domain. Tucows OpenSRS logs that this email was sent by
       making an entry in the domain notes table, indicating the date and time the email was
       sent.. Bounces of this email are automatically forwarded by Tucows OpenSRS to the
       email address of the Technical Contact of record.

[41]   Registry undertakes transfer and notifies the Gaining Registrar – The registry
       completes the transfer request and notifies the Gaining Registrar. This occurs, either as
       a result of the Losing Registrar’s timeout (failure to respond in the time allotted) see
       [36], or because of the Losing Registrar’s explicit approval of the transfer (see [42]).



            Page 173 of 174 - Release Version 2.56 - support@opensrs.org
[42]   Tucows OpenSRS sends "approve transfer" command to registry - Tucows
       OpenSRS acknowledges the transfer by sending an "approve transfer" command to
       registry using the Registry defined machine-to-machine registration protocol. Tucows
       OpenSRS logs that the registry command was issued by making a record in the domain
       notes table.

       If this command to the registry fails, Tucows OpenSRS makes a log of the registry failure
       in the domain notes table.

       Tucows OpenSRS notifies the Losing Reseller by email, informing them that the transfer
       was approved by the Registrant of record. Tucows OpenSRS logs that this email was sent
       by making an entry in the domain notes table, indicating the date and time the email was
       sent.. Bounces of this email are automatically forwarded (by OSRS) to
       data_admin@opensrs.org - where Tucows Staff handles them.

[43]   Registry cancels transfer request and notifies Gaining Registrar – The Registry,
       upon receiving a denial of transfer command from the Losing Registrar, cancels the
       transfer request and notifies the Gaining Registrar of this fact.




            Page 174 of 174 - Release Version 2.56 - support@opensrs.org

				
DOCUMENT INFO
Shared By:
Tags:
Stats:
views:69
posted:5/14/2011
language:English
pages:174