ICANN ICANN Email List Archives

[transfers-wg]


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

[transfers-wg] Regarding confirmations from the registrant

  • To: <transfers-wg@xxxxxxxxxxxxxx>
  • Subject: [transfers-wg] Regarding confirmations from the registrant
  • From: "Bruce Tonkin" <Bruce.Tonkin@xxxxxxxxxxxxxxxxxx>
  • Date: Tue, 23 Aug 2005 14:24:04 +1000

Hello Jon,


        1. I'll take the likely unpopular view that a positive response
to a    confirmation e-mail should be required.

I don't support adding to the complexity for a registrant of a "double"
confirmation.

However a compromise could be to have a mechanism where the confirmation
information is copied to the gaining registrar at the same time as the
losing registrar.  Often when we have a transfer dispute, we waste a lot
of time asking the gaining registrar for a copy of the
communications/correspondence etc that was received from the registrant.
Once we have evidence of the transfer confirmation, and supply this to
the customer, the customer realizes that they have in fact approved the
transfer.

I would rather put the effort into improving the implementation of the
approval process to the satisfaction of both gaining and losing
registrar.   Auth-Info codes are one step in the right direction.
Perhaps a standard format (or formats) for collecting proof of approval,
and a mechanism for automatically sending this to the losing registrar
as well would be a big improvement.
 

        2.  We should consider limiting how long a registrar may hold an
FOA before      submitting a transfer request.  We've run into problems
when a registrar        requests a transfer a month or two after they
have received the FOA.  By that         time, the registration
information may have changed, and the new registrant    doesn't respond
to a confirmation request (see 1 above).  Perhaps FOAs should   be
effective only 5 or 10 days to avoid fraudulent transfers out.

Good idea.

Regards,
Bruce Tonkin




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

Privacy Policy | Terms of Service | Cookies Policy