ICANN ICANN Email List Archives

[gnso-irtp-pdp-jun08]


<<< Chronological Index >>>    <<< Thread Index >>>

[gnso-irtp-pdp-jun08] Transfer Process: Internal Feedback on Issue I.

  • To: "IRTP-A " <Gnso-irtp-pdp-jun08@xxxxxxxxx>
  • Subject: [gnso-irtp-pdp-jun08] Transfer Process: Internal Feedback on Issue I.
  • From: "James M. Bladel" <jbladel@xxxxxxxxxxx>
  • Date: Wed, 10 Sep 2008 16:39:24 -0700

<html><body><span style="font-family:Arial; color:#000000; 
font-size:10pt;">Paul and Group:<br><br>Following our call yesterday, I had a 
chance to confer internally with some our folks who handle transfers, and 
wanted to share my findings with the group.&nbsp; <br><br>*&nbsp; To put some 
boundaries on the question of registrant email
availability:&nbsp; We established during yesterday's call that Registrant
Email is collected and maintained by all registrars, and submitted to
all "Thick" Registries.&nbsp; A quick check of gTLD WHOIS data shows that
Registrant Email is also displayed for all Thick Registries.&nbsp; So Mike
O.'s point about the elephant in the room is accurate, as this problem
is most frequently associated with the Thin registries, esp. COM / 
NET.<br><br>*&nbsp; As we have discussed earlier, problems involving WHOIS 
accuracy should be omitted from our consideration, first because it is an 
ongoing issue in other areas of ICANN.&nbsp; But mostly because the problem 
raised in Issue I is one of data access, not data accuracy.&nbsp; Even if the 
Registrant Email address is incorrect or fraudulent, it is not visible to the 
gaining registrar.&nbsp; Similarly, we should consider discussions involving 
reasons for denial out of bounds, as this occurs only after the transfer is 
initiated.<br><br>*&nbsp; GoDaddy sends all transfer communication to the Admin 
contact.&nbsp; If the transfer is NACK'ed by the Registrant, we do not pursue 
the transfer. The exception to this would be if the individual attempting the 
transfer asks us to get engaged, in which as we would attempt to facilitate 
communication between the requester and the Losing Registrar.&nbsp; 
<br><br>*&nbsp; I was incorrect in my statement that we "never send the 
AuthInfo code via email."&nbsp; In fact, a registrant can access via their 
account control panel, and request an email containing the AuthInfo 
code.<br><br>*&nbsp; The Domain Services team was able to provide me with a 
transfer flowchart (attached).&nbsp; It seems very similar to the diagram 
provided by Network Solutions.<br><br><br>Thanks--<br><br>J.<br><br><meta 
http-equiv="Content-Type" content="text/html; charset=utf-8"><img 
src="cid:48c85a5575219" height="931" width="883">
<br> </span></body></html>

JPEG image



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy