ICANN ICANN Email List Archives

[gnso-irtpd]


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

Re: [gnso-irtpd] Happy new year and Š Monday's agenda

  • To: "rob.golding@xxxxxxxxxxxx" <rob.golding@xxxxxxxxxxxx>, "gnso-irtpd@xxxxxxxxx" <gnso-irtpd@xxxxxxxxx>
  • Subject: Re: [gnso-irtpd] Happy new year and Š Monday's agenda
  • From: "James M. Bladel" <jbladel@xxxxxxxxxxx>
  • Date: Fri, 3 Jan 2014 14:17:37 +0000

Responses in-lineŠ

J.


On 1/2/14, 7:52 , "rob.golding@xxxxxxxxxxxx" <rob.golding@xxxxxxxxxxxx>
wrote:

>
>> FROM AN ICANN COMPLIANCE POINT OF VIEW
>> REGARDING THE LOOSING REGISTRAR:
>> - the registrar sends the Auth Code to someone who is not the
>> registered name holder
>
>IME the majority of registrars send the EPP codes to the *admin* contact


*****JMB -  Yes, this is what we do as well.

>
>> - the registrar does not even send it at all
>
>Are ICANN siggesting they'll start doing something about the repeat
>offenders of that little 'trick' ?


*****JMB - Registrars are required to send it within 5 days of request,
but I agree that enforcement is problematic and inconsistent.



>
>> FOA related:
>> - the registrar does not send the FOA
>> - sends it to someone who is not a Transfer Contact
>
>A Transfer Contact - what's that ? I've only ever heard of Regsitrant,
>Admin, Tech and Billing contacts


*****JMB - IRTP defines the Transfer Contact as either the Registrant OR
the Admin Contact.  But as you¹ve pointed out, in practical terms & thin
registries, the Admin Contact = Transfer Contact.



>
>
>> REGARDING THE GAINING REGISTRAR:
>> - the registrar sends the FOA to someone who is not a Transfer Contact
>
>See above
>
>> - the registrar allows the transfer without receiving confirmation
>> after sending the FOA
>
>How does that compare to the 'it happens anyway after 5 days if no-one
>said no' policy ?
>
>Rob





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

Privacy Policy | Terms of Service | Cookies Policy