|Comment Period Deadlines (*)||Important Information Links|
|Public Comment Box|
|Open Date:||8 July 2011||To Submit Your Comments (Forum Closed)|
|Close Date:||8 August 2011||Time (UTC):||11:00||View Comments Submitted|
|Section I: Description, Explanation, and Purpose|
The Generic Names Supporting Organization (GNSO) approved at its meeting on 22 June 2011 a number of recommendations on the Inter-Registrar Transfer Policy (IRTP) Part B Policy Development Process (PDP). The resolution, which is pending for Board action, proposes:
You are invited to submit comments until 8 August (11.00 UTC) before final consideration by the ICANN Board.
|Section II: Background|
The Inter-Registrar Transfer Policy (IRTP) aims to provide a straightforward procedure for domain name holders to transfer their names from one ICANN-accredited registrar to another should they wish to do so. The policy also provides standardized requirements for registrar handling of such transfer requests from domain name holders. The policy is an existing community consensus policy that was implemented in late 2004 and is now being reviewed by the GNSO.
The IRTP Part B Policy Development Process (PDP) is the second in a series of five PDPs that address areas for improvements in the existing Inter-Registrar Transfer Policy. The GNSO IRTP Part B Policy Development Process Working Group was tasked to address five issues focusing on issues related to domain hijacking, the urgent return of an inappropriately transferred name and "lock status". The WG delivered its Final Report to the GNSO Council on 31 May 2011. The GNSO Council acted on a number of the recommendations at its meeting on 22 June 2011. As required by the ICANN Bylaws, public notice is hereby provided of the policies that are considered for adoption as well as an opportunity to comment on the adoption of the proposed policies, prior to consideration by the ICANN Board of these recommendations.
|Section III: Document and Resource Links|
|Section IV: Additional Information|
|Staff Contact:||Marika Konings||Email:||email@example.com|
(*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses.