Anuncios de la ICANN

Los anuncios de la ICANN brindan información actualizada sobre actividades de desarrollo de políticas, eventos regionales y demás novedades.

Inter-Registrar Transfer Policy (IRTP) Part B Policy Development Process (PDP) Recommendations for Board Consideration

8 de julio de 2011

Contenido disponible solo en los siguientes idiomas

  • English
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:

  • Requiring Registrars to provide a Transfer Emergency Action Contact (TEAC). To this end proposed language to modify section 4 (Registrar Coordination) and Section 6 (Registry Requirements) of the Inter-Registrar Transfer Policy has been provided (see GNSO resolution for further details).
  • Modifying section 3 of the IRTP to require that the Registrar of Record/Losing Registrar be required to notify the Registered Name Holder/Registrant of the transfer out. The Registrar of Record has access to the contact information for the Registrant and could modify their systems to automatically send out the Standardized Form for Losing Registrars ("Confirmation FOA") to the Registrant.
  • Modifying Reason for Denial #6 as follows: Express objection to the transfer by the authorized Transfer Contact. Objection could take the form of specific request (either by paper or electronic means) by the authorized Transfer Contact to deny a particular transfer request, or a general objection to all transfer requests received by the Registrar, either temporarily or indefinitely. In all cases, the objection must be provided with the express and informed consent of the authorized Transfer Contact on an opt-in basis and upon request by the authorized Transfer Contact, the Registrar must remove the lock or provide a reasonably accessible method for the authorized Transfer Contact to remove the lock within five (5) calendar days.
  • Deleting denial reason #7 as a valid reason for denial under section 3 of the IRTP as it is technically not possible to initiate a transfer for a domain name that is locked, and hence cannot be denied, making this denial reason obsolete.

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
None
Staff Contact: Marika Konings Email: policy-staff@icann.org

(*) 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.