Changes

Jump to navigation Jump to search
m
Dustin Phillips moved page IRTP to Inter-Registrar Transfer Policy over redirect
Line 1: Line 1: −
'''IRTP''' is the '''Inter-Registrar Transfer Policy''' developed by [[ICANN]] for the safe, straight-forward transfer of domain names from one [[registrar]] to another.<ref>[http://www.icann.org/en/transfers/ ICANN Transfers]</ref> The policy contains information about the method of transferring a domain name, dispute resolution mechanism and the method of undoing the transfer if it was done as a result of an error.<ref>[http://www.fateback.com/news/domain_names/data/ICANN_to_launch_new_InterRegistrar_Transfer_Policy_in_November.html FateBack]</ref>
+
The '''Inter-Registrar Transfer Policy''' (IRTP) was developed by [[ICANN]] for the safe, straight-forward transfer of domain names from one [[registrar]] to another.<ref>[http://www.icann.org/en/transfers/ ICANN Transfers]</ref> The policy contains information about the method of transferring a domain name, dispute resolution mechanism and the method of undoing the transfer if it was done as a result of an error.<ref>[http://www.fateback.com/news/domain_names/data/ICANN_to_launch_new_InterRegistrar_Transfer_Policy_in_November.html FateBack]</ref>
    
==Development==
 
==Development==
Line 15: Line 15:     
===2012 Changes===
 
===2012 Changes===
In January, 2012, ahead of its February [[ICANN 43]] meeting, the organization announced that it was considering changes to its IRTP. The GNSO council approved those changes, which entails defining a universal 5 day maximum allowable lock period for domains that have had changes made to the registrant's name in the [[Whois]] record. Domains with changes made the name of the registrant in the Whois record is locked to prevent transfer, the policy is seen as helping prevent [[Domain Hacking|domain hacking]]. The new rule is seen as largely a response to [[GoDaddy]]'s current 60 day lock policy, which has been a continued target for criticism. GoDaddy, through its representative [[James Bladel]], was involved in creating the proposed changes.<ref>[http://domainincite.com/end-in-sight-for-go-daddys-60-day-transfer-lock/ End in Sight for Go Daddys 60 Day Transfer
+
In January, 2012, ahead of its February [[ICANN 43]] meeting, the organization announced that it was considering changes to its IRTP. The GNSO council approved those changes, which entail defining a universal 5 day maximum allowable lock period for domains that have had changes made to the registrant's name in the [[Whois]] record. Domains with changes made to the name of the registrant in the Whois record are locked to prevent transfer, the policy is seen as helping prevent [[Domain Hacking|domain hacking]]. The new rule is seen as largely a response to [[GoDaddy]]'s current 60 day lock policy, which has been a continued target for criticism. GoDaddy, through its representative [[James Bladel]], was involved in creating the proposed changes.<ref>[http://domainincite.com/end-in-sight-for-go-daddys-60-day-transfer-lock/ End in Sight for Go Daddys 60 Day Transfer, DomainIncite.com]</ref>
    
==Additional Links==
 
==Additional Links==
Bureaucrats, Interface administrators, lookupuser, staff, Administrators, translator
11,770

edits

Navigation menu