4. Object transfer

Object transfer is a mechanism that allows to change the designated registrar of an object.

Each object has authorization information (AuthInfo for short) that in this case represents a transfer password. The AuthInfo must be provided with the transfer request to authorize the transfer. More information about AuthInfo TTL can be found at AuthInfo TTL.

The transfer process in the FRED is different from the standard one (see RFC 5730#section- and it works as follows:

  1. A contact linked to an object intended for transfer requests AuthInfo of the object. He can do so via the current registrar, via the new registrar or by submitting a public request to the Registry directly.

  2. The AuthInfo is provided to the contact either through one of the involved registrars, or sent from the Registry.

  3. The contact requests the transfer from the new registrar and provides the AuthInfo.

  4. The new registrar requests the transfer from the Registry (via EPP) and provides the AuthInfo.

  5. The Registry transfers the object immediately and generates new AuthInfo for the transferred object.

  6. The Registry notifies the old registrar and the linked contacts about the transfer.

This model favours the holder because it does not allow the current designated registrar to reject nor inhibit the transfer.

Object transfer process sequence diagram

Sequence diagram – Object transfer process

4.1. Further authorization options

A transfer of a domain may also be authorized using AuthInfo of the domain holder or any of its administrative contacts.

A transfer of an nsset or keyset may also be authorized using AuthInfo of any of its technical contacts.