ICANN has received a proposal from Registry Services Corporation, operator for the .PRO top-level domain, requesting a set of changes to the .PRO registry agreement. These changes are being posted for public comment prior to consideration by the ICANN Board of Directors. .PRO is a restricted TLD, currently available for registration by credentialed professionals and related entities.
Current Requirements for Registering .PRO Names
In accordance with the current .PRO Registry Agreement between ICANN and RegistryPro, eligible registrants may register .PRO domain names consistent with the following parameters:
- Third-level registrations are currently available under profession-specific second-level domains (e.g., med.pro). Currently available profession-specific second-level domains (PS-SLDs) are med.pro, law.pro, cpa.pro, eng.pro, and ing.pro. An authentication and verification process confirms that the registrant meets the eligibility requirements for the specific PS-SLD (for example, verifying that a registrant under med.pro is a licensed medical professional). An example of this type of registration would be <smith.med.pro>.
- Second-level registrations with a redirect to a third-level registration are currently available to registrants who meet the eligibility requirements for one of the PS-SLDs above. For example, a registrant might register a the name <smith.pro>, which would redirect to <smith.med.pro>.
- Second-level registrations are currently available under .PRO in the case where a registrant provides multiple professional services and meets eligibility requirements for two or more PD-SLDs. An example of this type of registration would be <smithconsulting.pro>, if Smith Consulting employs both lawyers and accountants.
Proposed Requirements for Registering .PRO Names
The contract amendments proposed by RegistryPro would enable the registry to allow registrations in .PRO according to the following parameters:
- Third-level registrations under PS-SLDs (e.g., med.pro) would continue to be available. However, the list of PS-SLDs offered would be expanded to include additional professions.
- Second-level registrations would be available to professionals who either: a) meet the eligibility requirements for any of the PS-SLDs, or b) are licensed by, and in good standing with, a jurisdictional licensing entity recognized by a governmental body and requiring its members to be continuously licensed or admitted to such body or entity as a prerequisite to providing the relevant professional service. A redirect to a corresponding third-level name would not be required.
- Second-level registrations would continue to be available under .PRO in the case where a registrant provides multiple professional services and meets eligibility requirements for two or more profession-specific second-level domains.
Side-by-Side Comparison of Registration Requirements
|2nd Level (e.g., smith.pro)||3rd Level (e.g., smith.med.pro)|
|Entities meeting the eligibility requirements for two or more PS-SLDs||Credentialed professionals in the medical, law, accounting, and engineering professions|
|Credentialed professionals in the medical, law, accounting, and engineering fields (names must redirect to a third-level name)|
|2nd Level (e.g., smith.pro)||3rd Level (e.g., smith.pro)|
|Entities meeting the eligibility requirements for two or more professions|
Additional Background on RegistryPro Request
After some preliminary discussions with ICANN staff, RegistryPro submitted to ICANN on 12 March 2008 a formal request to amend its Registry Agreement to allow it to offer expanded types of domain registrations.
The request included:
- Outreach letter describing the purpose of and proposed changes to registry agreement.
- A redlined Appendix L incorporating changes to the naming conventions and registration requirements as summarized above.
Public Comment Requested
Public comment is being solicited on the proposed changes. Comments may be submitted to email@example.com by 10 April 2008. Comments may be viewed at http://forum.icann.org/lists/rproproposal.
This announcement was sourced from ICANN at icann.org/announcements/announcement-14mar08.htm.