COMPANY
CONFIDENTIAL

 
New TLD Application

Presented to THE
Internet Corporation for Assigned Names and Numbers
New tld applications
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90202

 

presented by

 

Registerypro
Due October 2, 2000, 5:00 P.M. PT

 

 

 

 

Description of TLD Policies

 

 

 

 

Specific portions of this document are confidential and are governed by the confidentiality restrictions identified in
Section F: Statement of Requested Confidential Treatment of Materials Submitted.


TABLE OF CONTENTS

TABLE OF CONTENTS.. ii

GRAPHICS TABLE OF CONTENTS.. iv

Description of TLD Policies. 5

Description of TLD Policies. 5

I. GENERAL TLD POLICIES.. 5

E1. Full and detailed description of all policies to be followed in the TLD.. 5

E2. Proposed TLD Subdomains. 6

E3. Describe the naming conventions and structure within the TLD. 8

E4. Describe in detail the policies for selection of, and competition among, registrars. 9

E5. Describe the policies for protection of intellectual property. 13

E5.1. What measures will be taken to discourage registration of domain names that infringe intellectual property rights?. 14

E5.2. If you are proposing pre‑screening for potentially infringing registrations, how will the pre‑screening be performed?. 15

E5.3. What registration practices will be employed to minimize abusive registrations?  16

E5.4. What measures do you propose to comply with applicable trademark and anti‑cybersquatting legislation?. 18

E5.5. Are you proposing any special protections (other than during the start‑up period) for famous trademarks?. 18

E5.6. How will complete, up‑to‑date, reliable, and conveniently provided Whois data be maintained, updated, and accessed concerning registrations in the TLD?. 18

E6. Describe the policies for domain name and other dispute resolution. 19

E6.1. To what extent are you proposing to implement the UDRP?. 19

E6.2. Please describe any additional, alternative, or supplemental dispute resolution procedures you are proposing. 20

E7. Describe the proposed policies on data privacy, escrow and Whois service. 20

E8. Describe variations in or additions to the policies for billing and collection. 21

E9. What registration services do you propose to establish charges for and, for each such service, how much do you propose to charge?. 23

E10. Other. Please describe any policies concerning topics not covered by the above questions. 24

II. REGISTRATION POLICIES DURING THE START‑UP PERIOD (Required for all TLDs) 27

E11. Describe all policies (including implementation details) that you propose to follow during the start‑up phase of registrations in the TLD. 27

E12. 27

E13. Do you propose to place limits on the number of registrations per registrant? Per registrar? If so, how will these limits be implemented?. 28


E14. Will pricing mechanisms be used to dampen a rush for registration at the initial opening of the TLD? If so, please describe these mechanisms in detail. 29

E15.  Will you offer any "sunrise period" in which certain potential registrants are offered the opportunity to register before registration is open to the general public? If so, to whom will this opportunity be offered (those with famous marks, registered trademarks, second‑level domains in other TLDs, pre‑registrations of some sort, etc.)? How will you implement this?  29

III. REGISTRATION RESTRICTIONS.. 30

E16. As noted in the New TLD Application Process Overview, a restricted TLD is one with enforced restrictions on (1) who may apply for a registration within the domain, (2) what uses may be made of those registrations, or (3) both. In this section, please describe in detail the restrictions you propose to apply to the TLD. Your description should define the criteria to be employed, the manner in which you propose they be enforced, and the consequences of violation of the restrictions. Examples of matters that should be addressed are: 30

E17. Describe in detail the criteria for registration in the TLD. Provide a full explanation of the reasoning behind the specific policies chosen. 30

E18. Describe the application process for potential registrants in the TLD. 33

E19. Describe the enforcement procedures and mechanisms for ensuring registrants meet the registration requirements. 34

E20. Describe any appeal process from denial of registration. 35

E21. Describe any procedure that permits third parties to seek cancellation of a TLD registration for failure to comply with restrictions. 35

IV. CONTEXT OF THE TLD WITHIN THE DNS.. 36

E22. This section is intended to allow you to describe the benefits of the TLD and the reasons why it would benefit the global Internet community or some segment of that community. Issues you might consider addressing include: 36

E23. What will distinguish the TLD from existing or other proposed TLDs? How will this distinction be beneficial?. 36

E24. What community and/or market will be served or targeted by this TLD? To what extent is that community or market already served by the DNS?. 36

E25. Please describe in detail how your proposal would enable the DNS to meet presently unmet needs. 36

E26. How would the introduction of the TLD enhance the utility of the DNS for Internet users? For the community served by the TLD?. 37

E27. How would the proposed TLD enhance competition in domain‑name registration services, including competition with existing TLD registries?. 37

V. VALUE OF PROPOSAL AS A PROOF OF CONCEPT.. 38

E28. Recent experience in the introduction of new TLDs is limited in some respects. The current program of establishing new TLDs is intended to allow evaluation of possible additions and enhancements to the DNS and possible methods of implementing them. Stated differently, the current program is intended to serve as a "proof of concept" for ways in which the DNS might evolve in the longer term. This section of the application is designed to gather information regarding what specific concept(s) could be evaluated if the proposed TLD is introduced, how you propose the evaluation should be done, and what information would be learned that might be instructive in the long‑term management of the DNS. Well‑considered and articulated responses to this section will be positively viewed in the selection process. Matters you should discuss in this section include: 38

E29. What concepts are likely to be proved/disproved by evaluation of the introduction of this TLD in the manner you propose?. 38

E30. How do you propose that the results of the introduction should be evaluated? By what criteria should the success or lack of success of the TLD be evaluated?. 38

E31. In what way would the results of the evaluation assist in the long‑range management of the DNS?  40

E32. Are there any reasons other than evaluation of the introduction process that this particular TLD should be included in the initial introduction?. 40

Registry Operator's Signature Page. 41

 

GRAPHICS TABLE OF CONTENTS


Figure 1: The .pro roles: Consumers, Registrars, Registry. 10

Figure 2: WHOIS Results. 15

Figure 3: Registrar Billing Cycle Flowchart 22

Figure 4: Bid to Full Registration Flowchart 27

Figure 5: Part of the Registration Form Showing Qualifications. 33


Description of TLD Policies

 

[For sponsored TLDs, this part of the application is to be completed by the sponsoring organization. For unsponsored TLDs, the registry operator should complete this part of the application. Please refer to the Detailed Application Instructions for more information on the requirements for new TLD applications.

The operation of a TLD involves the implementation of policies on a very large number of topics. Applicants are urged to use their response to this part of the application to demonstrate their detailed knowledge of what topics are involved and their careful analysis and clear articulation of the policies they propose on these topics.

Please place the legend "CONFIDENTIAL" on any part of your description that you have listed in item F3.1 of your Statement of Requested Confidential Treatment of Materials Submitted.

Section III of this application applies only to applicants for restricted TLDs. Ordinarily, restricted TLDs should be sponsored.]

 

I. GENERAL TLD POLICIES

(Required for all TLDs. Note that two special policy areas‑‑policies during the start‑up period and restrictions on who may register within the TLD and for what purpose‑‑are covered in sections II and III below.)

 

 

E1. Full and detailed description of all policies to be followed in the TLD

(other than those covered in response to items E11‑E21). If the TLDs policy on a particular topic is proposed to be identical to that reflected by a particular version of any of the following documents, it is sufficient for your response to identify the topic, to give a brief summary of the policy, and for the details to reference the document and section:

 

1.      ICANN Registrar Accreditation Agreement

 

2.      NSI Registrar License and Agreement

 

3.      ICANN‑NSI Registry Agreement

 

4.      Uniform Domain-Name Dispute-Resolution Policy (UDRP)

 

Your response should comprehensively describe policies on all topics to be followed in connection with the proposed TLD. The following items (E2‑E10) are examples only and should not limit your description.

 

RegistryPro intends to comply with and help support ICANN policies, including those in the above agreements and others produced by consensus.  Additionally, RegistryPro proposes a range of policies to guide the creation, implementation and maintenance of a trusted new TLD and create best practices for all registries.  This proposal for a restricted TLD offers a number of unique features that will enhance the domain name system (DNS) and Internet usage for consumers.

RegistryPro proposes technical systems that will improve trademark protection beyond the capacity of current systems.  We will develop an enhanced database system with expanded search functions (Whois plus, an enhanced Whois as described in our responses to questions E5.6 and E7) ruled by specific policies geared toward greater protection of intellectual property.

RegistryPro proposes a community refund that contributes a portion of Register.com's and Virtual Internet's registry profits to promote stability within the DNS and encourage competition among registrars.

From the outset RegistryPro will look to an Advisory Board to assist with the development and implementation of these plans. RegistryPro will form the Board from among ICANN constituencies, professional organizations, as well as respected experts in the domain name space.  Where references to an Advisory Board appear below, please see our response to question E10 for a description of its proposed role and composition.

 

E2. Proposed TLD Subdomains.

For format requirements for TLD strings, see the answer to FAQ #5.

 

The Usefulness of .pro to the DNS.

 

Although the proliferation of the Internet as a means of communication and commerce has vastly expanded the ways in which  business and personal matters are conducted, it has not been without certain perils and pitfalls.  Credit card fraud on the Internet has reached heretofore unknown levels.  Cybersquatting has cost well-known brands and trademarks hundreds of thousands of dollars.  Even legitimate duplication of names has bred confusion within the DNS.  Consumers are finding it more and more difficult to find what they are looking for on the web. In over 1000 people surveyed by RegistryPro to test the viability of .pro, 51% indicated a level of frustration in attempting to locate information online, indicating that they were either overwhelmed with pages and pages of search results or needed to redo/refine their searches.

The addition of .pro as a new, restricted TLD will simplify and segment the use of domain names in a logical and ordered fashion.  For the first time, professionals will have the opportunity to register within the DNS in a meaningful fashion.  The initial rollout of doctors, lawyers and accountants will have a first and unfettered opportunity to register within the .pro domain.  That opportunity will not be extended to the public at large, but will be limited to professionals who have been qualified to practice within their respective professions.

 

 

More than 94% of over 1000 consumers surveyed thought that these designations would help them find what they were looking for on the Internet, or at least narrow the search.  Those consumers overwhelmingly selected doctors, lawyers and accountants as the professionals they expected to find registered at .pro.  Consumers also included architects, engineers and financial planners as professionals they would like to look for on .pro.

We propose the .pro TLD with the following initial subdomains:

§         .med.pro

§         .law.pro

§         .cpa.pro

 

It is our belief that the .pro TLD will become extremely popular.  Where the .com TLD now restricts professionals from distinguishing themselves, .pro with our initial TLD subdomains will help professionals in the medical, legal and accounting services.  As these initial subdomains prove successful, and with ICANN approval, additional .pro subdomains would be developed to foster further segmentation within the professional community.  For example, new .pro subdomains could be established for professional areas such as engineering, architecture, and psychology.

We perceive a number of advantages to starting with traditional and established lines of business as the testbeds for new TLDs:

§         Inspiring trust. The .pro TLD with its very name and the power of the experienced and professional companies backing its introduction will inspire trust within the professional sector using it and the consumers searching through it. Further, companies and individuals registering with a .pro TLD will be required to produce evidence of professional qualification and/or membership of a professional association. Consumers will know that someone registered in .law.pro has, for example, received a license to practice law or is a member of a bar association.  As registrations will take place every two years at a maximum, the consumer will know that the qualification is current.  In this way the .pro TLD will inspire greater consumer confidence in finding and using services on the Internet.

§         Acceptance in multiple languages. The .pro TLD has a recognition value in Spanish, French, English, Italian and Portuguese.

§         Established business areas. These first three .pro subdomains have been chosen deliberately with a view to stability.  Each of these professional sectors, medicine, law and financial services, are traditional business areas with internationally accepted accreditation requirements and associations.  Most countries have domestic governing bodies in each area.

§         Familiarity with self-regulation. Professionals in these industry areas have a tradition of developing rules of self-governance and both working within those guidelines and policing their industry area for unscrupulous activity.


§         Need for Internet-based activity. Professionals in these industry areas have a great need for Internet-based business activity, including communication, product development and sales, and overall marketing. Where there are greater opportunities for professionals to distinguish themselves on the Internet, we believe the professional community will come flocking.

§         Improved access.  The consumers searching the .pro TLD for professional services will find their targets more easily and with greater accuracy.

§         Solid marketing opportunities.  Each of these professional areas have established associations and other networking groups that offer the opportunity for joint marketing initiatives, current and accurate mailing lists and other relatively clear communication lines with which to promote the new TLD to professionals and consumers.

§         Intellectual property protection.  An additional benefit of the .pro TLD is that it will protect intellectual property.  A restricted TLD inherently narrows the category of potential registrants.  The target business sector is a class of trusted professionals, who are far less likely to engage in cybersquatting, particularly as they would not want to compromise their professional relationships and reputations.  Finally, we expect fewer trademark interests in the .pro TLD than in many other TLDs since most individual and firm names are not registered trademarks.  We believe fewer registration challenges will arise due to .pro registrants minimizing the burden on the UDRP system.  But even given these benefits, we have provided for enhanced IP protection as described in detail in our responses to questions E5-E7.

 

E3. Describe the naming conventions and structure within the TLD.

E.g., will registrants have names registered at the second level (directly under the TLD, as in registered‑name.com), or will the TLD be organized with sub‑domains so that registered domain names are created at a lower level (as in registered‑name.travel. com)?

The .pro TLD and associated subdomains will allow different professionals with similar or same names to use that name without conflicting with others.  The sub-domains will help categorize different professions helping the professionals distinguish themselves to consumers. 

 

And as these new TLDs prove successful, geographic or professional delineations can be added to our TLD subdomains to further differentiate professions in the same or different professions.


For example, using the new .pro TLD:

§         TomSmith.ny.law.pro

§         TomSmith.ip.law.pro

§         TomSmith.fr.med.pro

 

The cpa.pro TLD subdomain would apply to those markets internationally where a chartered public accounting certification is recognized for accountants;  Other subdomains will be established to accommodate accounting professionals accredited by other certifications.

E4. Describe in detail the policies for selection of, and competition among, registrars.

 

1.                  Will domain‑name holders deal through registrars, directly with the registry operator, or some combination of the two?

 

Registrars will continue to be the interface with domain name holders.  The registry will offer a global service to ICANN-accredited registrars.


Figure 1: The .pro roles: Consumers, Registrars, Registry

 

 


2.                  What are the respective roles, functions, and responsibilities for the registry operator and registrars?

The registry will provide the services described in the ICANN-NSI Registry Agreement and based the NSI Registrar License and Agreement, plus added functionality.  The registry’s roles, functions and responsibilities include:

§         Operate the centralized, authoritative and shared database of .pro domain names, in compliance a new service level agreement

§         Update the database, per commands received through registrars

§         Provide a domain name lookup capability

§         Establish a set of .pro restrictions (in coordination with professional associations, ICANN, and the Advisory Board (For a description of the Advisory Board, please see E10 below)), including an easy to use menu of qualifications, which will be part of the registrant record.

§         Comply with the UDRP or other applicable dispute policies, including providing for registry hold or take down of domain name registrations as appropriate.

§         Provide an interactive web page and centralized Whois plus service, with public query-based access and Boolean searches to a real time updated database

§         In addition to a query-based access that would provide more information than currently available in the gTLDs, RegistryPro intends to build improved searchability tools for use by intellectual property and law enforcement interests, and such others as may be determined with ICANN and the Advisory Board.

§         Ensure stability of the database by building redundant systems and escrowing data as often as is currently done in the gTLDs

§         Provide equivalent access to all accredited registrars

§         Enter into agreements with registrars that identify the registry’s and registrars' responsibilities and compliance with ICANN and .pro policies

§         Provide reasonable notice to registrars of upcoming expirations of registrations

§         Provide registrars with technical, billing, and other customer support

§         Provide documentation and tool kits to facilitate communication with the registry using RRP.

 

The registrars will provide the service described in the ICANN Registrar Accreditation Agreement and the NSI Registrar License and Agreement, plus those corresponding to the added functionality of .pro.  The registrars’ roles, functions and responsibilities include:

§         Interface with the registrants

§         Collect and send to the registry accurate and reliable registrant information, as required by ICANN and the registry, including information outlined in NSI-Registrar License and Agreement, Section 2.5, and the ICANN Registrar Accreditation Agreement, Section II.F, as well as

§         Identify a registrant’s qualification for .pro based on the menu provided by RegistryPro, and

§         During the sunrise period, information regarding the registrant’s trademark or service mark.

§         Collect  evidence of registrant’s professional qualification.

§         Update the database per changes in registrant’s information, transfers, deletions, renewals, or other commands.

§         Provide an interactive web page and centralized Whois service, with public query-based access to a real time updated database.

§         Provide a domain name lookup capability.

§         Require registrants to comply with ICANN and RegistryPro policies.


§         Provide a dispute resolution policy and require registrants to comply with it. In case of challenges of a registrant’s qualification as .pro registrant, require such registrant to produce evidence, take down such registration if such evidence is not produced, and place registration on hold in cases of dispute.

§         Comply with the UDRP or other applicable dispute policies, including placing domain name registrations on hold or taking them down as appropriate.

§         Provide registrants with technical, billing, and other customer support.

§         Pay registry fees in a timely manner.

§         Provide registrants with reasonable notice of upcoming expirations of registrations.

§         Comply with the laws and regulations of their jurisdictions.

§         Provide query-based searches and bulk data access as required in the ICANN Registrar Accreditation Agreement and other ICANN consensus policies, and modeled on the NSI-Registrar License and Agreement.

§         With a centralized Whois database adding security to .pro registrants, data storage at the registrar level will be less important.

§         Release domain name registrations in case of non-payment by registrant or expiration of registration term to prevent hoarding.

 

3.                  If registrars are to be employed, how and by whom will they be selected or accredited?

 

All registrars will be eligible to register professionals in the .pro TLD as long as they are ICANN accredited and agree to the policy and business requirements in the .pro TLD agreement, which would be crafted to reflect this application and ensure the stability trustworthiness and superior standards of the .pro registry.  Equivalent access for, and fees to, all registrars will be guaranteed in order to create a level playing field.

 

4.                  If the number of registrars will be restricted, what number of registrars will be selected?

The number will not be restricted.

 

5.                  Have the qualifying registrars already been selected?

All ICANN accredited registrars will qualify to apply to become a .pro registrar.  As long as a registrar agrees to the .pro TLD policies, as agreed with ICANN, a registrar will qualify to register professionals in the .pro TLD.

 


6.                  On what basis will selections among those seeking to be registrars be made, and who will make them?

All ICANN accredited registrars will qualify to apply to become a .pro registrar.  As long as a registrar agrees to the .pro TLD policies, as agreed with ICANN, a registrar will qualify to register professionals in the .pro TLD.

 

7.                  If registrars are to be used, what mechanisms will be used to ensure that TLD policies are implemented?

 

RegistryPro will help ensure protection of registrants by including in its agreements with registrars policies regarding the restricted nature of the .pro TLD and other policies designed to set best practices.  These will be based on the experience of Register.com and Virtual Internet, guidance from the Advisory Board (See E10 below), and in coordination with ICANN.  The registry agreement will be enforced by an independent dispute resolution provider, modeled on the UDRP and on the precedent in the ICANN Registrar Accreditation Agreement, Section II.P.  Such arbitration could also be used to enforce the ICANN Registrar Accreditation Agreement and other consensus policies.

 

E5. Describe the policies for protection of intellectual property.

By its restricted nature, this TLD will be less vulnerable to cybersquatting. 

§         First, a restricted TLD inherently creates an additional bar to an inappropriate registrant and as an additional screen against cybersquatting. 

§         Second, .pro is aimed at professionals, most of whom are individuals and will register their names.  There are fewer .pro domain names that will be subject to a registered trademark or service mark, minimizing the burden on the UDRP.

§         Third, the target business sectors are classes of trusted professionals, who are used to dealing with registrations far less likely to engage in cybersquatting, particularly as they would not want to compromise their professional relationships and reputations. 

§         Finally, the market for .pro domain names is focused and segregated, so that there is a reduced market for resale of such names.

RegistryPro will be governed by the UDRP and require .pro accredited registrars to comply with the UDRP.  For further details, please refer to our response to question E6.1.

RegistryPro also proposes a pre-registration phase (sunrise period) to provide adequate intellectual property protection for registered trademark and service mark holders. For further details, please refer to our response to question E5.2.

RegistryPro also proposes providing a Whois Plus database and accessibility. For further details, please refer to our responses to questions E5.6 and E7.


E5.1. What measures will be taken to discourage registration of domain names that infringe intellectual property rights?

The registrars to this registry will be required to comply with the established policies of the UDRP.  Further, the sunrise pre-registration period will limit infringement on intellectual property rights.  For further details, please refer to our response to question E5.2.

RegistryPro will operate a centralized shared Whois system that incorporates the information found in the gTLD Whois and additional information to identify a registrant (see Whois results in Figure 2 below).  RegistryPro will also offer query-based and Boolean-based access and searchability that is at least as complete and robust as that of the current gTLDs, with plans to build enhanced search capability.  The enhanced capability is being built to address the specific interests of the intellectual property community.  All in all, RegistryPro is proposing to immediately offer Whois Plus, with extra capability in the future. For further details, please refer to our responses to questions E5.6 and E7.

Figure 2: Sample WHOIS Results

 

E5.2. If you are proposing pre‑screening for potentially infringing registrations, how will the pre‑screening be performed?

RegistryPro will open a pre-registration period to protect owners of trademarks and service marks.  RegistryPro proposes following the policy published by the IP Constituency: 

§         Owners of trademarks and service marks having been registered in a national trademark office for at least one year prior to the creation of the new TLD will be able to pre-register on a first-come, first-served basis. 

§         The material textual element(s) (i.e., the word portion of their marks) as a domain name in the TLD.

§         These domain name pre-registrations would be confined to a single registration corresponding to a trademark.

§         This pre-registration also would be subject to compliance with the registration requirements of the .pro TLD. 

In order to ensure that the pre-registration period is used as it is intended only for trademark protection, registrants will be required to provide the registration number, date, and jurisdiction for their trade or service mark, and such information will be published as part of a registrant’s Whois record.

In order to enforce this policy and protect against cybersquatting and abuse of this pre-registration period, there will be an opportunity to challenge the registrations through the UDRP:

§         If a sunrise registration is challenged on the basis of not owning a registered mark, the purported owner must produce a valid trademark registration document.  Challenges will be governed by the UDRP.

§         If a sunrise registration is challenged on the basis of being unqualified for the .pro restrictions, such challenge will follow the procedures outlined in our responses to questions E17-E21 below.

§         During the challenge, the registrar must place the registration on hold.

§         Standing to challenge a registration during sunrise period will be open to help ensure policy compliance.

§         If a successful challenge is made by a superior registered trademark owner, the challenger will have the right to register that name. 

§         If the challenge is successful but the challenger does not hold a superior registered trademark, the domain name will be released into the open database.

§         If the challenge is not successful the original registrant retains the name.

 

E5.3. What registration practices will be employed to minimize abusive registrations?

RegistryPro contemplates a balance to protect both consumers and registrars.

1.      The sunrise pre-registration period provides significant protection against abusive registrations.  For further details, please refer to our responses to questions E5.2 and E5.6.

2.      The complete domain name records will be housed at the registry level, making it easier for intellectual property interests to review records. Please see our response to question E5.6

3.      The registrar will be required to obtain specific evidence of professional qualification from all registrants.  Please see our response to question E17-21

4.      At a minimum, registrars will be required to collect and post such information as required by the NSI-Registrar License and Agreement, Section 2.5, and the ICANN Registrar Accreditation Agreement, Section II.F This includes:

§         second-level domain name and the TLD in which the second-level domain name is registered;

§         registrant’s name and postal address;

§         administrative and technical contacts’ names, postal addresses, e-mail addresses, telephone numbers and (if any) facsimile number;

§         original registration date and expiration date;

§         Internet Protocol addresses and corresponding names of primary and secondary nameservers for the second level domain; and

§         registrar’s identity.

See Figure 2 in our response to question E5.1.

The following information will also be required and displayed by the registry:

§         a registrant’s qualification for .pro based on the menu provided by RegistryPro,

§         during the sunrise period, information regarding the registrant’s trademark or                              service mark.

5.  RegistryPro will provide enhanced Whois access and searchability. Please refer to our responses to questions E5.6 and E7. 

6.  The .pro restrictions are governed by internal and external mechanisms to minimize registrations by unqualified registrants. Please refer to our responses to questions E17-E21.

7.  Hoarding, frontrunning and enforcement policies have been developed:

§         No hoarding:. In general, registrations may only be held by registrants who are independent of registrars.  Domain name registrations that are expired must be released. Registrars may not register domain names on their own behalf, or on behalf of any director, officer, employee or agent of a registrar. There would be an exception for  registration on behalf of a registrar’s legitimate interest.  For example, if a professional association becomes an accredited registrar, it may register its own name in .pro .


§         No frontrunning: Registrars shall not engage in anticipating a consumer’s preference for a domain name (via sniffing of Whois data or other processes) and subsequently registering such domain names on behalf of the registrar, or any director, officer, employee or agent of a registrar.

§         Enforcement: RegistryPro will require all registrars to agree to the registry policies and to comply with ICANN policies in order to participate in the .pro TLD.  Compliance with the terms and conditions of the registry-registrar agreement will be enforced via a trusted independent arbitration mechanism, including the providers approved to provide UDRP services.  For a model, please see the ICANN Registrar Accreditation Agreement, Section II.P and the UDRP.

 

E5.4. What measures do you propose to comply with applicable trademark and anti‑cybersquatting legislation?

The new registry will comply with all applicable trademark and anti-cybersquatting legislation and arbitration mechanisms, including the UDRP, and will require compliance by registrars.  Upon notice of a complaint filed under applicable intellectual property laws or the UDRP, the registrar will send  a hold command to the registry, which will place such domain name registration on registry hold until resolution of the complaint. A registrar and the registry will comply with the UDRP or court decision.

 

E5.5. Are you proposing any special protections (other than during the start‑up period) for famous trademarks?

RegistryPro will provide enhanced protection for all registered trademarks during the sunrise period.  RegistryPro will also comply with applicable laws and the UDRP. As a restricted registry, RegistryPro will require each registrant to qualify as a member of the profession corresponding to the .pro extension.  This will further help to screen out potential cybersquatters.  RegistryPro believes further restrictions would only hinder the ability of solo practitioners and smaller professional firms from registering in the .pro TLD. 

RegistryPro intends to be mindful of public concerns regarding the openness and availability of the domain name system.  The policies described in E5 appropriately balance those concerns with protection of intellectual property interests.

E5.6. How will complete, up‑to‑date, reliable, and conveniently provided Whois data be maintained, updated, and accessed concerning registrations in the TLD?

From the start, RegistryPro will more than match the current gTLDs’ Whois accessibility.  For  a technical description of the Whois system, please refer to our response to question D15.2.8.

RegistryPro will operate a shared registry system with a centralized Whois Plus database.


§         RegistryPro will incorporate on a real time basis new and updated information provided by registrars. RegistryPro will publish the data currently found in the gTLD Whois records, plus additional information, as identified in E5.3. Hence, RegistryPro will offer a comprehensive, up-to-date and reliable source of .pro data.

§         RegistryPro will also offer improved query-based and Boolean-based access and searchability. From the start, the completeness and robustness of the searches will match that of the current gTLDs.  Moreover from the beginning, the additional information required by RegistryPro will be visible in the searches.  This policy will help enforce the .pro restrictions as well as enforce trademark protection.

§         RegistryPro also plans to build the capability to provide the next level of enhanced searchability.  This search capability will further protect intellectual property by:

§         Increasing the number of query results to any one query, 

§         Allowing searches using more fields; and

§         Allowing searches for text strings

As this enhanced capability requires additional investment of time and resources, it will be built after first dedicating all resources to establishing the core registry. 

§         Query-based access to the Whois will be provided both via the registrars and the registry.  Updates to the Whois will be made through the registrars in order to retain registrars’ central role as the interface with their customers, but the registry will be a complete and authoritative database. 

§         Bulk access requirements will be modeled on those in the ICANN Registrar Accreditation Agreement and the ICANN-NSI Registry Agreement.  Registrars will have the capability to comply with the privacy laws and regulations of their jurisdictions, if so required, by sending a request to the registry to mask certain private information.  The registry will work with ICANN and its Advisory Board (See E10 below) to ensure a proper balance between such legal requirements and the goals of providing appropriate access to information.

 

E6. Describe the policies for domain name and other dispute resolution.

If you are proposing variations to the policies followed in .com, .net, and .org, consider the following questions:

 

E6.1. To what extent are you proposing to implement the UDRP?

RegistryPro proposes full compliance with the established policies of the UDRP, including during the sunrise period.  Please refer to our response to question E5.2.

 

E6.2. Please describe any additional, alternative, or supplemental dispute resolution procedures you are proposing.

With the goal of enforcing the .pro charter and ensuring that it is a mark of the professional sector that it serves, RegistryPro proposes leveraging the experience provided by the UDRP and the model in the ICANN Accreditation Registrar Agreement, Section P.II.  The idea is for an independent, trusted dispute resolution mechanism to help enforce .pro registrant restrictions and other registry policies as are specified in the registry-registrar agreement and as may be added from time to time per guidance from ICANN or the Advisory Board (See E10 below).  The arbitration mechanism would provide a strong, independent enforcement mechanism.  For further detail, please refer to our responses to questions E17-E21.

 

E7. Describe the proposed policies on data privacy, escrow and Whois service.

Escrow

RegistryPro shall deposit into escrow all registry data on a schedule to be agreed with ICANN (suggested weekly for a complete set of registry data and daily for incremental updates) and in an electronic format mutually approved by RegistryPro and ICANN. The escrow shall be maintained, at RegistryPro’s expense, by a reputable independent escrow agent.  In preparation for the possibility of being awarded the bid, RegistryPro has initiated a process of  seeking bids from escrow agents. Attached are examples of incoming bids, redacted to protect confidential and commercially sensitive information.

The use of the escrow data will be limited to verification that the deposited data is complete and in proper format to protect the privacy of the data.  The data would be released to ICANN or the United States Department of Commerce upon termination of the registry agreement or in the event of an applicable court order or subpoena.

The registry will also encourage registrars to deposit into escrow all registrar data on a similar schedule.  But as the registry will have a centralized shared database, including all Whois records listed herein, the registry’s escrow commitment will ensure the availability of accurate records in case of possible registrar failure.

Data Privacy and Whois

The registry will operate a centralized shared Whois Plus database. The database will be accessible to query-based and Boolean-based searching. Its Boolean-based search capability will be significantly enhanced in the future.  For further details, please refer to our responses to questions E5.6 and D15.2.8.

RegistryPro’s goal is to help protect intellectual property interests against cybersquatting and allow queries that further the goal of public openness, while protecting registrants’ private information as contemplated in and protecting registrants from spamming or other unethical and inappropriate commercial practices.  There appears to be a growing movement, that began in Europe, to protect personal data provided on the Internet.  At the same time, there are legitimate reasons to release data, such as to protect intellectual property rights or enforce a court order or subpoena.  RegistryPro’s goal is to balance these competing concerns.

RegistryPro proposes to provide for query-based access and Boolean-based searches for violations of trademarks as described in our response to question E5.3.  Clearly, RegistryPro would accommodate court orders and subpoenas and similar law enforcement-related orders.

For bulk access, RegistryPro and the registrars registering on .pro TLD will comply with the requirements of the ICANN Registrar Accreditation Agreement and the ICANN-NSI Registry Agreement and other ICANN consensus policies.

 

E8. Describe variations in or additions to the policies for billing and collection.

RegistryPro is going to establish practical billing policies, which are easy for registrars to use, ensure stability of registration services, protect registrants, and encourage competition.  There will not be a fee to join the .pro TLDs.

Billing Process

The core billing processes are ones with which the RegistryPro partners and other registrars are familiar, and are therefore simple to use.  For the current model, please refer to the NSI-Registrar License and Agreement Sections 5.2-5.4.

§         The registry will collect a letter of credit from each registrar, from which the registry can withdraw funds in the event of non-payment by that registrar for domain registrations.

§         The registry monitors the volume of registrations daily. If the monetary value of registered names exceeds 80% of the letter of credit, the registrar is provided appropriate notice. The registrar can increase the letter of credit or make a pre-payment to maintain an acceptable credit balance. Once the credit limit has been reached and unpaid past due balances remain, the registry shuts off the registrars ability to register more names.

§         At the end of each monthly billing period, the registry compiles registration data for each registrar. An invoice is created and the data is made available either by sending paper or electronic documents, or by posting the data on a secure FTP site.

§         The registrar normally pays the invoice in full upon receipt. The registry updates the registrar’s account and sends a confirmation of the registrar's credit balance.

§         In some cases, registrars may make partial payments pending minor disputed amounts relating to a small number of names. In these situations, the registry works with the registrar to answer questions and have outstanding invoice amounts paid.

§         If a registrar does not pay, the letter of credit can be drawn upon to pay outstanding amounts.  If the letter of credit limit has been reached, the registry shuts off a registrar’s ability to register names.


§         The precautions (described above) taken to prevent a registrar from registering new domain names if the registrar is delinquent serves several goals.  A registrar’s non-payment of registrations may indicate their impending bankruptcy.  Hence cutting off a registrar will limit the number of registrants affected by a registrar’s failure. Strict billing policies establish disincentives to a registrar’s speculative and other irresponsible business practices.

Figure 3: Registry Billing Cycle Flowchart

 

Indemnification Bond

The registry will also require registrars to post a surety bond to indemnify the registry and its employees from all costs and damages which it may suffer by reason of a registrar’s failure to otherwise indemnify the registry.  Please refer to the NSI-Registrar License and Agreement Section 2.14.

E9. What registration services do you propose to establish charges for and, for each such service, how much do you propose to charge?

For background, please refer to the NSI-Registrar License and Agreement Sections 5.2-5.4.  For the most part, RegistryPro proposes to continue the current system, except for improvements, as indicated below.  Moreover, RegistryPro proposes charging a competitive registration fee -- no higher than the current .com registry fee.

 

 

Billable Events

§         Registration -  $6.00 (plus VAT where applicable), per one year, per domain name.  RegistryPro’s business plan has established this rate for the company to maintain itself as a competitive, stable and sustainable operation.

§         The term of registration will be a minimum of one year and maximum of two years.

§         There will be a 5-day grace period to delete a registration.  If a domain name registration is deleted during the grace period, the registry will credit the registrar’s account in the full amount of such deletions.

§         Renewal - $6.00 (plus VAT where applicable), per name, per year, provided that the total registration term does not exceed two years.

§         There will be a 5-day grace period to delete a renewal term. The registry will credit a registrar’s account if a registration or renewal is deleted within the 5-day grace period. 

§         No automatic renewals – this is an innovation on the current system designed to avoid potential, or the appearance of, hoarding of unwanted or expired domain names. 

§         The registry will, however, send reasonable notice to registrars in order to ensure that the domain name is not allowed to inadvertently expire and be registered by someone else.  The registry will also provide a 5-day grace period after expiration of a domain name registration in order to provide an opportunity to a registrant to reinstate the expired name.

§         If a registration is deleted or not renewed, there will be a 5-day grace period to allow reinstatement by the registrant.  During this grace period, the domain name registration will be on hold.  At the end of the 5-day grace period, if not reinstated, the domain name will be immediately released back to the open market and the registrar will be reimbursed the registration fee.

§         Transfer a registrant from one registrar to another - $6.00 (plus VAT where applicable). In this case, the registry will extend the registration by one year, provided that the total registration term does not exceed two years. 


§         By placing the maximum registration term at two years, the registry will maintain its restricted and consumer-trusted qualities.  At renewal, all .pro TLD registrants will resubmit their qualifications to the registrar, showing evidence of their continued good standing within their professions.

The registry will not charge for:

§         Transfers of a domain name registration between registrants and,

§         Searches or look ups on the Whois database equivalent to the current searching capacity on the .com registry.

§         The .pro TLD registry fees will support:

§         Consumer education (brand positioning) around the .pro TLD.

§         The restricted registration process, supporting professional standards for the .pro TLD.

§         The staff  to liaison with ICANN and the RegistryPro Advisory Board and coordinate policies and activities with professional associations.

§         The development of products (proprietary software and other services) to help registrars communicate with the registry and market the .pro TLD.

§         The centralized database, 24/7 technical support and backup systems that will ensure no downtime for the .pro TLD.  This system will respond in real time to registrants’ electronic input and will reduce the burden on the registrars.

§         The discrete roll out of this product to a limited target market, resulting in a smaller market share potential than an unrestricted TLD.

 

Additional Services

In addition to providing a premier service at the base fee, RegistryPro intends to develop future value added services and products, which it may offer to registrars for an additional fee.  Providing these additional services will require additional staff and technical resources and therefore will require additional fees.  RegistryPro seeks to maintain an affordable base registry fee where the fundamental services of the .pro TLD are easily available to all.

E10. Other. Please describe any policies concerning topics not covered by the above questions.

RegistryPro seeks to comply with the relevant policies described in the ICANN Registrar Accreditation Agreement, the NSI Registrar License and Agreement, the ICANN-NSI Registry Agreement, and the UDRP, and other ICANN consensus policies as may be promulgated in the future.  In particular, the RegistryPro partners are committed to operating a transparent and fair registry, providing equivalent access to all ICANN accredited registrars. 

RegistryPro proposes two innovative policies to ensure that there is transparency and equal treatment, in fact and appearance:

Advisory Board

RegistryPro is creating an Advisory Board to contribute to the development and implementation of the new .pro TLD.  This new board will assist in identifying relevant professional associations, help identify new subdomains, and help determine and approve each sub domain's criteria and rules.  The board will advise the registry in general on general business practices, policies, and technological issues, with the goals of improving the registry’s services, ensuring its stability, ensuring its compliance with ICANN policies and helping to set best practices for the registry sector.

This Advisory Board will be composed of individuals who will uniquely contribute to this project.  Board members will be:

§          recognized experts on the domain name system, and

§         representatives from a cross section of professional sectors, and

§         representatives from ICANN constituencies.

Identification of members of this board has begun. As of October 2, 2000, the individuals identified in Appendix D__ have expressed their interest in joining the Advisory Board.

Community Refund

RegistryPro is considering a mechanism which by design dispels the concerns raised by the precedent of Verisign/Network Solutions (NSI) operating as both a registrar and a registry in the same TLD.  There have been a number of concerns that NSI has used its position as a registry to gain an unfair competitive advantage over competitor registrars.  This appears to be due to several reasons.  First, it holds a bank of domain names as residue of its registar-monopoly status.  Further, NSI does not incur registry fees, like other registrars, as its corporate parent recoups both registry and registrar fees.  There have also been criticisms that NSI has hoarded expired and unpaid domain names, which it can do because it does not actually incur a registry fee. 

The RegistryPro partners have been concerned with these practices and intend to avoid these situations with the .pro TLD. Fundamentally, RegistryPro is different because it will operate as a wholly separate entity, with a separate Board of Directors, Advisory Board (see E10 above), and Management Team; not a subdivision of a registrar. 

As added insurance against even the appearance of impropriety, RegistryPro proposes to establish a program that (a) automatically removes the partners’ ability to abuse the registry and (b) institutes a financial disincentive to hoarding.  In fact, this program creates incentives for RegistryPro to promote registrations by competitor registrars. 

§         Once RegistryPro has recouped investment costs, the registry profit associated with the .pro registrations registered by its parent companies (Register.com and Virtual Internet) will be used to support competition and the stability of the domain name system. 

Since the more competitor registrars there are, the less profit RegistryPro must distribute, there is a natural incentive to attract competition.  Since the parent companies are giving away a portion of their registry profit, they are, in effect, paying registry fees, like all .pro competitor registrars.  Since, the parent companies thus incur a registry fee, there is a disincentive to hoarding.

The use of these funds will be determined with the assistance of the Advisory Board and could include:

§         Support of the DNSO

§         Support for additional arbitration mechanisms

§         Consumer focused domain name education programs and

§         Support for ICANN policies.

 


II. REGISTRATION POLICIES DURING THE START‑UP PERIOD (Required for all TLDs)

 

Figure 4: Bid to Full Registration Flowchart

 

RegisteryPro will roll out the .pro TLD following approval of this application by ICANN.  Upon approval, RegistryPro’s management and operations team will commence negotiations with ICANN to determine best practices and systems to make the .pro TLD part of the existing DNS. This team will be composed of experienced staff from the parent companies as described in Section D (see our response to question D9).

We will hire staff, rent or purchase facilities and equipment and establish the systems necessary to build and maintain RegistryPro.  We will develop proprietary software, roll out our business and marketing plan and begin the registration process with the initial sunrise period building toward full registration.

E11. Describe all policies (including implementation details) that you propose to follow during the start‑up phase of registrations in the TLD.

To the extent they differ from the General TLD Policies covered in items E1‑E9. The following questions highlight some of the areas that should be considered for start‑up policies:

 

 

E12.

1.                  How do you propose to address the potential rush for registration at the initial opening of the TLD?

 

RegistryPro will establish an initial period for registering domain names in a manner, that does not unfairly benefit any registrar or registrant.

§         During this initial period, each registrar will be allowed to periodically submit lists of registration applications, on a rolling basis.

§         The registry will set up an application to pick randomly among registrars, and randomly from within each registrar’s list. 

§         During each cycle, the application will provide for each registrar to be picked at least once, but no more than once, before the registry begins the next cycle.

§         Each cycle will proceed according to a new random order picked by the application.

§         If a domain name is already taken, the application will continue to randomly pick from that registrar’s list until there is a successful registration by that registrar, before proceeding to another registrar.

Preregistration will not be honored and in fact, would be impossible to satisfy.

In order to ensure stability to the registration process, the five-day grace period described in our responses to questions E8 and E9 will not apply during this landrush period.  No changes or updates to the registration information will be permitted during this land rush period, including transfers between registrars or registrants.

 

2.                  How many requested registrations do you project will be received by the registry operator within the first day, week, month, and quarter?

 

 

RegistryPro is rolling out a new product with the .pro TLD.  Not only is it a new product, but the restricted domain name area is untested and country code or non-commercial (e.g., .edu) TLDs provide little relevant historical data upon which to draw comparisons and make projections.  The system we will build will have an initial capacity to handle 100,000 registrations per day.  RegistryPro believes this capacity will more than meet the initial potential demand for the .pro TLD.

What period do you believe should be considered the TLDs "start‑up period," during which special procedures should apply?

 

The appropriate length of this period will be determined in combination with ICANN and the Advisory Board (see E10 above) and upon evaluation of the more extensive consumer research we plan to conduct to determine the volume of the landrush.

 

E13. Do you propose to place limits on the number of registrations per registrant? Per registrar? If so, how will these limits be implemented?

Artificial limits would stymie the growth of the registry and frustrate consumer demand, and may unfairly and unreasonably harm some classes of registrants.  Instead, the system described in our response to question E12 will regulate initial demand.

 


E14. Will pricing mechanisms be used to dampen a rush for registration at the initial opening of the TLD? If so, please describe these mechanisms in detail.

RegistryPro is concerned that raising prices would unfairly penalize smaller or non-profit registrars and registrants.  We have substantially addressed this concern through the use of a sunrise period, a landrush period, and the professional qualifications requirement of all registrants.  We believe these measures leave in place a level playing field for all registrants and registrars.  See our responses to questions E12 and E17-E21 for more details on our plans to control the initial registration process.

E15.  Will you offer any "sunrise period" in which certain potential registrants are offered the opportunity to register before registration is open to the general public? If so, to whom will this opportunity be offered (those with famous marks, registered trademarks, second‑level domains in other TLDs, pre‑registrations of some sort, etc.)? How will you implement this?

RegistryPro will offer a sunrise period to holders of registered trademarks.  Please refer to our response to question E5.2.

 


III. REGISTRATION RESTRICTIONS

(Required for restricted TLDs only)

 

E16. As noted in the New TLD Application Process Overview, a restricted TLD is one with enforced restrictions on (1) who may apply for a registration within the domain, (2) what uses may be made of those registrations, or (3) both. In this section, please describe in detail the restrictions you propose to apply to the TLD. Your description should define the criteria to be employed, the manner in which you propose they be enforced, and the consequences of violation of the restrictions. Examples of matters that should be addressed are:

 

 

E17. Describe in detail the criteria for registration in the TLD. Provide a full explanation of the reasoning behind the specific policies chosen.

The .pro TLD will be divided into specific subdomains that correspond to professional sectors.  In line with ICANN’s wish to have a controlled roll out the new TLDs, we propose that a limited number of subdomains are issued initially, so that the  process can be fully analyzed and understood.

We recommend beginning with .law, .med, and .cpa.  Further roll out will be based on market research, the guidance of the Advisory Board (see E10 above), and coordination with the corresponding professional associations and ICANN.  The .pro TLD itself may be made available as an umbrella TLD corresponding to the introduced sublevel domains.

Working with its Advisory Board and professional associations around the world, RegistryPro will develop appropriate guidelines for the registration process to the .pro TLD.  Specific evidence of professional credentials will be required of all registrants showing their qualification for the professional area in which they wish to register.

Any individual, entity, or association that complies with one or more of the qualifications of the subdomain would be eligible.  RegistryPro will provide a menu of qualifications, based on advice of the Advisory Board (see E10 above) and the professional association corresponding to that subdomain. The reasons for establishing a menu are to help ensure that:

(a)    .pro is international - RegistryPro will accommodate the variety of professional accreditation methods found in different jurisdictions; and

(b)   the qualifications are serious and consistent and support the trusted nature of the professional class – the menu will specify the qualification choices.

The intention is to craft criteria which will emphasize the “trust” concept of the brand (.pro) and provide comfort to the users of the brand.

Registrars would be responsible for receiving a registrant’s evidence of qualification.  If an exceptional case arises,  it will be reviewed by registrars pursuant to policy developed by RegistryPro with guidance from the Advisory Body, the appropriate professional associations, and ICANN.

RegistryPro proposes the following criteria as a starting point for discussion with ICANN and the relevant professional associations:

·        .law.pro:

                                                               i.      passage of a certification exam, such as the U.S. state bar exam,

                                                             ii.      accreditation to a judicial system, which allows such party to represent clients before such judiciary, 

                                                            iii.      membership in professional association, such as the American Bar Association, or

                                                           iv.      An entity or association that provides legal services and whose employees or members satisfy one of the above criteria.

·        .med.pro:

                                                               i.      passage of a certification exam, such as U.S. board exams,

                                                             ii.      holding of a medical license from the appropriate government authority to practice medicine and/or prescribe medicine,

                                                            iii.      admitting privileges to a hospital,

                                                           iv.      membership in professional association, such as the American Medical Association, or

                                                             v.      An entity or association that provides medical services and whose employees or members satisfy one of the above criteria.

·        .cpa.pro

                                                               i.      passage of a certification exam, such as the U.S. certified public accountant exam,

                                                             ii.      holding license to prepare and sign clients’ tax returns, 

                                                            iii.      membership in professional association, such as the Association of Certified Public Accountants, or

                                                           iv.      an entity or association that provides certified accounting services and whose employees or members satisfy one of the above criteria.

For all of these, continued good standing as a member of the profession will be required.   This will be ensured by limiting the registration term to 2 years and requiring requalification each time.

Applications can be from individuals, entities, or associations that are members. As a result of these plans, the potential market for applications, the usefulness of .pro, and the overall commercial viability of the registry will be maximized.

 

Eventually if RegistryPro introduces narrower subdomains, such as fr.med.pro, the qualification process would likewise become more specific.

Figure 5 below shows a portion of what the RegistryPro registration sign up page might look like.

E18. Describe the application process for potential registrants in the TLD.

Figure 5: Part of the Registration Form Showing Qualifications

 

Registrations will be made on a first come, first served basis. A registrant would be allowed to register for multiple domain names.  For example, a lawyer named John Smith may register both JohnSmith.law.pro and his law firm, SmithandDoe.law.pro.  Likewise a registrant may register on all of the subdomains that he is qualified to join. A professional who is both a C.P.A. and a practicing attorney may register both as JohnSmith.law.pro and JohnSmith.cpa.pro.

The registration process:

(a)    The qualifications described in E17 would appear in a drop down menu of a registrar’s domain name registration system. 

(b)   A registrant would have to check off one of the qualifications and provide supporting evidence to the registrar in order to register. 

(c)    The registrar will confirm to the registry receipt of the evidence and the qualifications would appear in the Whois record of the registrant.

 

E19. Describe the enforcement procedures and mechanisms for ensuring registrants meet the registration requirements.

The initial and fundamental enforcement mechanism is the registration process (please refer to our responses to questions E17 and E18).  Beyond that, RegistryPro believes that the most fair, effective, and efficient way to enforce the .pro restrictions is to allow challenges of a registrant’s qualifications, as follows:

(a)    A challenge may be brought by any interested party. 

(b)   RegistryPro proposes looking to independent arbitration providers, such as those involved in the UDRP, for adjudication.  Professional associations may have an interest in being one of the alternative venues for such challenges, and would be well-suited to doing so.

(c)    Upon notice of such challenge, the registrar must place the registration on hold (prevent its transfer) and request the registrant to respond to the challenge.

(d)   If after 10 business days the registrant has not responded, the registrar will take down the registration.

(e)    If the registrant responds as contemplated in (c), the registrar will comply with the arbitration decision, or remove the hold status if notified that the complaint is dropped.

(f)     The registry will reflect changes in the registration’s status in the centralized database.

RegistryPro’s Advisory Body (please refer to E10  for further details) will provide guidance for developing and continually refining both the .pro restriction criteria and the enforcement mechanism.  The Advisory Board will assist in identifying and coordinating with the relevant professional associations to help determine and approve each subdomain's criteria and rules.

 

 

Additionally, RegistryPro would allow professional associations or other verification agencies to offer a verification service.  For example, not only would a registrant have to provide evidence of, for example, passing a medical board, but the association would also certify that fact.  This enhanced verification could be posted by the registrant.  But as it would significantly slow down and complicate an already multi-step registration process, it is not contemplated as a registration requirement.

E20. Describe any appeal process from denial of registration.

Denial of registration may be appealed through the arbitration mechanism established to review challenges to registrations. Please see our response to question E19 for further details.

 

E21. Describe any procedure that permits third parties to seek cancellation of a TLD registration for failure to comply with restrictions.

Please refer to our response to question E19.

 


IV. CONTEXT OF THE TLD WITHIN THE DNS

(Required for all TLDs)

 

E22. This section is intended to allow you to describe the benefits of the TLD and the reasons why it would benefit the global Internet community or some segment of that community. Issues you might consider addressing include:

 

E23. What will distinguish the TLD from existing or other proposed TLDs? How will this distinction be beneficial?

 

The .pro TLD will be aimed at the professional sectors.  These are easily identifiable, specialized markets, making it easy to screen appropriate registrants.  The .pro TLD is quite specific and will not be confused with other restricted or general TLDs.  This set of subdomains is an ideal testbed because it is aimed at business sectors that are, by their very nature, used to dealing with rules and policies. 

Please see our responses to questions D13.1.5 and  D13.2.4 regarding our mission and marketing plan, respectively, for further details and explanations as to the benefits of this distinction.

 

E24. What community and/or market will be served or targeted by this TLD? To what extent is that community or market already served by the DNS?

The .pro TLD will serve professional sectors around the world.  The .pro TLD will be segregated into specific TLDs such as .cpa, .law, .med, etc.  The idea is to begin with a testbed of the more traditional, global professions, and branch out in a measured manner to other professions.  The DNS is not serving this sector at present, see below.

Also, please see our response to questions D13.1.5 and  D13.2.4 regarding our mission and marketing plan, respectively, for further details and explanations.

 

E25. Please describe in detail how your proposal would enable the DNS to meet presently unmet needs.

Today, professionals have no way of distinguishing themselves on the web.  This makes for potential confusion among consumers seeking to find professionals on the web.  It undermines the professionals’ use of the DNS – the Internet lags behind basic published directories in this sense. 

The .pro TLD will establish TLDs tailored to specific professions.  This will become a directory to professionals around the world.  It will help consumers locate professionals around the globe.

The Internet has given the world the technology for better communication around the world.  The .pro TLD will provide the unique service for a consumer in Japan to find a doctor in New York, or a businessman in London to find a lawyer in Beijing.  No other tool is presently available that is comprehensive, robust, nor current enough to be truly useful.

 

E26. How would the introduction of the TLD enhance the utility of the DNS for Internet users? For the community served by the TLD?

In addition to our response to question E25, RegistryPro is committed to an ambitious marketing and advertising campaign (See our response to D13.2.4), which will benefit the entire DNS by educating the general public about the value and role of domain names.  Furthermore, RegistryPro will establish best practices from the technology, business and policy standpoints which will in turn raise the standard for other registries.

 

E27. How would the proposed TLD enhance competition in domain‑name registration services, including competition with existing TLD registries?

The .pro TLD will enhance competition by offering a popular service to broad sectors.  Professionals are already some of the most active Internet users.  We believe this group will quickly recognize the value of the .pro TLD to their business activities.  We believe these professionals will be extremely attracted to the capacity for our system and the .pro TLD to engender trust among consumers looking for professional services within the .pro TLD.

 

 

In market research conducted by RegistryPro in the United Kingdom and the United States, over 94% of consumers polled expressed interest in seeing a TDL at some level.  70% of that majority were very or extremely interested. Ten in-depth interviews revealed that key decision makers felt on balance that .pro would serve as a beneficial and reliable way to find professionals on the Web and will promote search engine efficiency.

This popular TLD will bring competition to the registry sector and enhance consumer choice.

RegistryPro’s JV partners have created a financial structure that promotes competition (see our response to question E10 regarding the community refund) and ensures that assets of the registry would not be utilized to unfairly advantage them to the detriment of other registrars in the .pro TLD.


V. VALUE OF PROPOSAL AS A PROOF OF CONCEPT

 (Required for all TLDs)

 

E28. Recent experience in the introduction of new TLDs is limited in some respects. The current program of establishing new TLDs is intended to allow evaluation of possible additions and enhancements to the DNS and possible methods of implementing them. Stated differently, the current program is intended to serve as a "proof of concept" for ways in which the DNS might evolve in the longer term. This section of the application is designed to gather information regarding what specific concept(s) could be evaluated if the proposed TLD is introduced, how you propose the evaluation should be done, and what information would be learned that might be instructive in the long‑term management of the DNS. Well‑considered and articulated responses to this section will be positively viewed in the selection process. Matters you should discuss in this section include:

 

 

E29. What concepts are likely to be proved/disproved by evaluation of the introduction of this TLD in the manner you propose?

By introducing the .pro TLD with a limited number of sub-domains a number of key concepts related to the DNS can be evaluated. These concepts include:

(a)    whether restricted TLDs will be robust and popular and increase the use of the web,

(b)   whether they will retain or support the stability of the DNS,

(c)    whether they will minimize confusion,

(d)   whether the web is a useful alternative to traditional directories,

(e)    whether new DNS extensions security measures and other security features will become widely accepted by consumers, registrars and registries,

(f)     whether the centralized Whois Plus database will improve the DNS and address intellectual property and consumer concerns.

 

E30. How do you propose that the results of the introduction should be evaluated? By what criteria should the success or lack of success of the TLD be evaluated?

We believe the .pro TLD is an ideal testbed for ICANN to evaluate some significant aspects of consumer use of the Internet and the naming structures that will best serve the Internet community at-large.  The results of the new .pro TLD should be evaluated based on a number of basic business indicators including:

Growth —

§         Evaluate RegistryPro as a commercially viable and sustainable stand alone business;

§         Evaluate the .pro TLDs capacity to increase competition among registrars and registries;

§         Evaluate registry services throughout the Internet. With RegistryPro’s improved services and greater level of consumer options presented to consumers and registrars, we anticipate providing a better value to registrars and consumers.  RegistryPro suggests that its combination of services and specialized features will set a new standard by which other registries will measure themselves, resulting in better services throughout the DNS system;

§         Evaluate consumer confidence in the .pro TLD vs. other TLDs;

§         Working with professional associations, evaluate the number of professionals on-line before and after the introduction of the .pro TLD;

§         Working with professional associations, evaluate the level of confidence of professionals in the Internet before and after the introduction of the .pro TLD;

§         Evaluate the level of consumer confidence in the Internet before and after the introduction of the .pro TLD;

§         Compare the use of and registration volume in the .pro TLD to .com; and

§         Compare current monthly registrations throughout the DNS before and after the introduction of the .pro TLD to determine its ability to attract new registrants.

Stability —

§         Review the financial, managerial and database stability of the .pro TLD in six months following introduction;

§         Review compliance with the Service Level Agreement; and

§         Survey registrars to evaluate their experience registering names within the new TLD.

Confusion —

§         Survey registrants and consumer users to evaluate the value-added or increased difficulty to Internet navigation after the .pro TLD has been introduced.

Innovative use of Technology

§         Assess the use of DNS security extensions to evaluate their adoption within the Internet community.

 

E31. In what way would the results of the evaluation assist in the long‑range management of the DNS?

Our plans for the .pro TLD will offer a testbed for a more organized system for segmenting the DNS in ways that make it more useful to both registrants and consumers.  Our results will offer guidance on long-range planning for the management of the DNS. 

Results will indicate the successes or failures of all aspects of the new naming conventions including:

§         the operations of the registry and registrar;

§         the desire for new structured naming systems by registrants; and

§         the ability of consumers to navigate new naming structures with sub-domains, and in the future, geographic and other sub-domain designations.

Results will also indicate the success or failure of a centralized shared database with enhanced search capability, including:

§         whether this alleviates registrars' burden,

§         whether it ensures against data loss associated with registrar failure, and

§         whether it better meets intellectual property and consumer needs.

 

E32. Are there any reasons other than evaluation of the introduction process that this particular TLD should be included in the initial introduction?

 

As described above in the Policy section of the application and in more detail in the marketing plans of the Registry Operator's Proposal, we have identified a need within the professional services industry that the current DNS does not meet.

Professionals in many industries are underserved by the current system making it difficult for them to distinguish themselves on the Internet.  Further, consumers are less likely to find and use services that are not clearly differentiated and trustworthy.

A .pro TLD will uniquely demonstrate that competition can be enhanced without losing stability within the DNS.

Furthermore, stability will be guaranteed by the tech expertise and resources that the three entities bring to bear.   For further detail, see Section D, III, Technical Plan.


Registry Operator's Signature Page.

By signing this application through its representative, the Applicant attests that the information contained in this Description of TLD Policies, and all referenced supporting documents, are true and accurate to the best of Applicant's knowledge.

 

Please see the hardcopy submission of this application for a complete and original signature page.

 

 

 

 

_______________________________

Signature

 

_______________________________

Name (please print)

 

_______________________________

Title

 

_______________________________

Name of Applicant Entity

 

_______________________________

Date

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

(c) 2000 The Internet Corporation for Assigned Names and Numbers

All rights reserved.

 

Updated August 15, 2000