<<<
Chronological Index
>>> <<<
Thread Index
>>>
[council] Registrars: Inter- Registrar Transfers Policy Information
- To: "council" <council@xxxxxxxxxxxxxx>
- Subject: [council] Registrars: Inter- Registrar Transfers Policy Information
- From: "GNSO SECRETARIAT" <gnso.secretariat@xxxxxxxxxxxxxx>
- Date: Thu, 6 Nov 2003 20:09:05 +0100
- Importance: Normal
- Reply-to: <gnso.secretariat@xxxxxxxxxxxxxx>
- Sender: owner-council@xxxxxxxxxxxxxx
[To: council@xxxxxxxxxxxxxx]
For your information:
http://www.icann.org/transfers/
GNSO Secretariat <BASE HREF="http://www.icann.org/transfers/";>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<TITLE>ICANN | Transfers (Inter-Registrar Transfers Policy Information)</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<style type="text/css">
<!--
p, li, td, ul { font-family: Arial, Helvetica, sans-serif}
-->
</style>
</HEAD>
<BODY bgColor=#ffffff>
<TABLE align="center" cellSpacing=2 cellPadding=0 width="95%" border=0>
<TR>
<TD width=40 height=127> </TD>
<TD width=158 height=127>
<a href="/index.html"><IMG height=145 alt="ICANN Logo"
src="/logos/icann-logo.gif" width=188 align=bottom border="0"></a></TD>
<TD width=781 height=127 align="center">
<p><font size="+2">Transfers</font><br>
<font size="+1">Inter-Registrar Transfers Policy
Information</font><br>
Last Updated 5 November 2003</TD>
</TR>
<tr>
<td colspan="3"> <hr noshade>
<p>The new transfer policy is intended to provide a procedure for the smooth
transition of a domain name from one registrar to another when such a change is
requested by the domain name holder. The Transfer Task Force Group has
developed 29 policy recommendations for guiding such transfers. The Transfer
Assistance Group (TAG) along with ICANN Staff, is currently in the process of
implementing the new transfer procedures, based on the 29 policy
recommendations, approved by the ICANN Board.</p>
<p><b>Background</b></p>
<p>The shared registry system implemented for the .com, .net, and .org
top-level domains (TLDs) in 1999 (and extended to the other new TLDs as they
were introduced in 2001) creates a competitive environment among accredited
registrars. To permit effective competition, registrants not only may choose
among registrars at the time of their initial registration, but also may choose
to transfer their registrations between registrars during the term of their
registration.</p>
<p>For the unsponsored gTLDs (.biz, .com, .info, .name, .net, .org, and .pro),
the procedure for transfers of registrations between registrars is described in
each registrar's agreement with each registry operator. The procedure is
essentially the same in all unsponsored TLDs. For sponsored TLDs (.aero, .coop,
and .museum), the procedure for transfers between registrars are set by the
top-level domain's sponsor.</p>
<p>When several members of the community expressed concerns regarding the
current procedure for transfer of domain names between registrars, the GNSO
Transfer Task Force Group was formed.</p>
<p>At its meeting on 20 February 2003, the GNSO Council voted unanimously to
accept the Final Report of the GNSO Transfers Task Force and to forward it to
the ICANN Board as a consensus-policy recommendation. That report included 29
specific policy recommendations with direction that the new transfer procedure
must comply with those recommendations. The final report can be found <a
href="http://www.icann.org/gnso/transfers-tf/report-12feb03.htm";>here</a>.</p>
<p>It was resolved at the ICANN Board meeting 25 April 2003 that the Board
adopts the recommendations from the GNSO Transfer Task Force Group, and further
that the President and General Counsel are authorized to ensure implementation
of the new procedures contained in the 29 policy recommendations. The
implementation was requested to be performed with guidance from relevant
knowledgeable parties and to be pursuant to ICANN's agreements with registries
and registrars.</p>
<p><b>Formation of Transfers Assistance Group</b></p>
<p>In order to adopt the findings of the GNSO report, ICANN Staff formed the
Transfer Assistance Group (TAG) in July 2003 in consultation with the Registry
and Registrars Constituencies, the GNSO Transfers Task Force Group, and the
ALAC. Each of these groups returned nominees and the group first met in August
2003.</p>
<p>The members of the TAG are charged with the implementation of the new
transfer policy. The TAG's scope is limited to the findings of the GNSO report
of the 29 policy recommendations therein.</p>
<p>Hence, this group is not charged with undertaking any outreach or consensus
development itself; its only charge is to provide, from its members as a group,
input and assistance in implementing these policy recommendations.</p>
<p><b>Members of the Transfers Assistance Group</b></p>
<p>The Transfer Assistance group members are:</b>
<ul>
<li>Bruce Tonkin - Melbourne IT
<li>Chuck Gomes - Verisign Registry
<li>Elana Broitman - register.com
<li>Grant Forsyth - TelstraClear
<li>Jeff Neuman - NeuLevel
<li>Paul Westley - Internetters
<li>Ross Rader - Tucows
<li>Sebastian Riccardi - ALAC member
<li>Thomas Roessler - ALAC member
</ul>
<p>For comment to the TAG group please email ICANN's Chief Registry Liaison,
Tina Dam at <<a
href="mailto:dam@icann.org";>dam@icann.org</a>>.</p>
<p><b>Status of the New Transfer Procedures</b></p>
<p>12 February 2003: The GNSO Transfer Task Force Group finalized their
recommendation in a <a href="/gnso/transfers-tf/report-12feb03.htm">Final
Report on Gaining and Losing Registrars</a> to the GNSO Council. (The 29 policy
recommendations).</p>
<p>20 February 2003: the GNSO Council voted unanimously to accept the GNSO
Transfer Task Force Report. The report was then forwarded to ICANN's Board for
further action and approval.</p>
<p>25 April 2003: the ICANN Board adopted the 29 policy recommendations, and
further the President and General Counsel of ICANN were authorized to implement
the policy recommendations, by consulting with knowledgeable parties.</p>
<p>July 2003: In consulting with such parties ICANN staff formed the TAG
group.</p>
<p>To date the TAG has met four times, most recently at the ICANN conference in
Carthage. During these meetings the 29 policy recommendations have been divided
into subgroups according to the categories listed below.</p>
<ol>
<li>Registrar Accreditation Agreement
<li>Standardized Form of Authorization
<li>Dispute Resolution Policy
<li>Registry-Registrar Agreement
<li>Timeline for completing transfers
<li>Advisories to registries and registrars regarding new policies
</ol>
<p>To date categories 1, 2 and 5 have been finalized on a preliminary basis.
The categories are not viewed as finalized until all 29 policy recommendations
have been included in one of these, or in a new established category.</p>
<p>All categories are being discussed by ALAC, and on Registry and Registrar
Constituency mailing lists, and the new policy procedures will be released
simultaneously to provide a complete overview of the requirements to Registries
and Registrars. Once the new procedures are released Registrars and Registries
will be presented with a timeline for the implementation of the new transfer
procedure.</p>
<p>Further, once the new transfer procedures are in place, the implementation
and execution of the procedures will be monitored by the GNSO. More
specifically, the policy recommendations require the ICANN Staff to analyze and
report to the GNSO at three, six and twelve month intervals after
implementation of the procedure with the goal of determining various effects of
the new procedures.</p>
<CENTER>
<HR noshade>
<font face="Arial, Helvetica, sans-serif" size="-1">Comments concerning
the layout, construction and functionality of this site <BR>
should be sent to <A
href="mailto:webmaster@icann.org";>webmaster@icann.org</A>.</font>
</CENTER>
<P align="center"> <font face="Arial, Helvetica, sans-serif"
size="-1">Page
Updated
<!-- #BeginDate format:En2 -->05-Nov-2003<!-- #EndDate -->
<BR>
</font><font face="Arial, Helvetica, sans-serif"
size="-2">©2003
The Internet Corporation for Assigned Names and Numbers. All rights
reserved.</font>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|