2005-01-24 - RegistryPro Request to Launch ENG.PRO
Category: gTLDs
Topic: Request to launch ENG.PRO
Board meeting date: 24 January 2005
Resolution number: 05.01
URL for Board minutes/resolution: http://www.icann.org/en/minutes/minutes-24jan05.htm
Status: Completed
Summary
Board approves implementation of ENG as new profession-specific second-level domain in .PRO.
Text
Tina Dam introduced the topic for discussion for requests from RegistryPro for ENG.PRO and ING.PRO. John Klensin provided additional comments. Following additional discussion, Michael D. Palage moved for a vote on a resolution approving RegistryPro's request, which was seconded by Hagen Hultzsch. During the discussion of the motion, it was determined that RegistryPro should provide additional information regarding how they intend to implement ING.PRO and instructed staff to ask RegistryPro to resubmit their request with additional information about their intended technical implementation. The following resolution was voted on by the Board:
Whereas the .PRO Registry Agreement, Appendix L, Section 4, contains a procedure by which the registry operator may propose to ICANN the implementation of additional profession specific second level domains.
Whereas, the registry operator on 20 December 2004 followed this procedure and proposed to ICANN the introduction of a new profession-specific second level domain (ENG.PRO).
Resolved (05.01), the President and the General Counsel are authorized to approve the proposal made by the registry operator and hence allow for implementation of ENG.PRO.
This resolution was unanimously approved by the Board, 12-0. Njeri Rionge and Hualin Qian were not present for the vote.
Implementation Actions
Approval of proposed implementation of ENG.PRO.
Responsible entity: Board
Due date: None provided
Completion date: 24 January 2005
Other Related Resolutions
Resolution 01.74 - Board directs President to form and chair New TLD Evaluation Process Planning Task Force (NTEPPTF): http://www.icann.org/en/minutes/prelim-report-04jun01.htm
Resolution 02.97, 02.97A - Board accepts NTEPPTF report and directs President to produce plan for action for approval by Board at October 2002 meeting in Shanghai, China: http://www.icann.org/en/minutes/prelim-report-23aug02.htm
Resolution 02.143 - Authorizing amendment to the .PRO registry agreement to implement defensive registration product offerings: http://www.icann.org/en/minutes/prelim-report-02dec02.htm
Resolutions 02.150, 02.151, and 02.152: Board authorizes President to implement NTEPPTF recommendations in Action Plan, requests GNSO to provide recommendation on structure of generic tol level namespace, and directs President to develop draft Request for Proposals: http://www.icann.org/en/minutes/prelim-report-15dec02.htm#AnnualMeetingoftheTransitionBoard
Resolution 02.40 and 02.41 - Authorizing President to enter .pro registry agreement and implement agreement once signed: http://www.icann.org/en/minutes/prelim-report-14mar02.htm
Resolution 03.112 and 03.113 - Board invites public comment on draft request for proposals for sTLDs; requests President to provide to Board detailed plan and schedule for development of appropriate long-term policy for introduction of new gTLDs: http://www.icann.org/en/minutes/prelim-report-26jun03.htm
Resolution 03.161 - Authorizing amendments to .PRO registry agreement to implement second-level registration product offering: http://www.icann.org/en/announcements/advisory-31oct03.htm
Resolutions 03.166, 03.167, and 03.168 - Board calls for the development of process and policy for streamlining introduction of new gTLDs as specified in ICANNs MoU with the U.S. Department of Commerce: http://www.icann.org/en/announcements/advisory-31oct03.htm
Resolutions 03.169, 03.170, and 03.171 - Board resolves to negotiate agreement reflecting commercial and technical terms upon completion of sTLD selection, resolves that selection process and implementation for sTLDs will be evaluated, and directs President to finalize and post open Request for Proposals for limited number of new sTLDs: http://www.icann.org/en/announcements/advisory-31oct03.htm
Resolution 04.85 - Authorizing amendment of .PRO registry agreement to implement additional mechanisms for personal data verification: http://www.icann.org/en/minutes/resolutions-30sep04.htm
Resolution 05.06 - Approving introduction of ING as new profession-specific second-level domain in .PRO: http://www.icann.org/en/minutes/minutes-18feb05.htm
Resolution __.2008 - Approving proposed changes to .PRO Registry Agreement; authorizing President and General Counsel to take appropriate actions to implement amendments: http://www.icann.org/en/minutes/minutes-30apr08.htm
Other resolutions TBD
Additional Information
.PRO registry agreement: http://www.icann.org/en/tlds/agreements/pro/
.PRO registry agreement was assigned from RegistryPro, Inc. to Registry Services Corporation on 18 February 2004: http://www.icann.org/en/minutes/prelim-report-18feb04.htm
For information on the introduction of sTLDs in 2003 - 2004, please refer to:http://www.icann.org/en/tlds/stld-apps-19mar04/
To review public comments submitted on the 2003 round, refer to: http://forum.icann.org/mtg-cmts/stld-rfp-comments/general/index.html
To review the Status Reports on the 2003 round, refer to: http://www.icann.org/en/tlds/stld-apps-19mar04/PostsTLDStatusRpt.pdf
15 December 2003 - New sTLD Application: http://www.icann.org/en/tlds/new-stld-rfp/new-stld-application-parta-15dec03.htm
24 June 2003 - Request for Proposals, Establishment of new sTLDs (Draft for Public Comment): http://www.icann.org/en/tlds/new-stld-rfp/new-stld-rfp-24jun03.htm
19 March 2004 - Status Report on sTLD Evaluation Process: http://www.icann.org/en/tlds/stld-apps-19mar04/stld-status-report.pdf
Some analysis of the sTLD program is available in Staff's 24 September 2004 report on a strategy for introducing New gTLDs, at http://www.icann.org/en/tlds/new-gtld-strategy.pdf, and additional information can be found in the documentation of the New gTLD program, at http://www.icann.org/en/topics/new-gtlds/related-en.htm.
The resolution does not address funding for the items identified therein.
Explanatory text does not modify or override Resolutions. See Board Resolutions Page for more information.