5.8.2. Transfer contact¶

A contact transfer command is used to take over sponsorship of a contact.

An AuthInfo of the contact (in role of transfer password) must be provided for authorization.

A new AuthInfo is generated for the contact by the server after a successful transfer.

The contact transfer command is a transfer element in the contact namespace (http://www.nic.cz/xml/epp/contact-1.6).

The command must be contained in the <transfer> command type. The command type must specify the request operation (@op = 'request').

5.8.2.1. Command element structure¶

The <contact:transfer> element must declare the contact namespace and schema and it must contain the following child elements:

<contact:id> (1) – the contact handle as fredcom:objIDType,
<contact:authInfo> (1) – the authorization information (AuthInfo for short, in role of transfer password) as fredcom:authInfoType.

Example¶

<?xml version="1.0" encoding="utf-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
   <command>
      <transfer op="request">
         <contact:transfer xmlns:contact="http://www.nic.cz/xml/epp/contact-1.6"
          xsi:schemaLocation="http://www.nic.cz/xml/epp/contact-1.6 contact-1.6.6.xsd">
            <contact:id>CID-TRCONT</contact:id>
            <contact:authInfo>trpwd</contact:authInfo>
         </contact:transfer>
      </transfer>
      <clTRID>gcnd002#17-08-01at13:00:14</clTRID>
   </command>
</epp>

FRED-client equivalent¶

> transfer_contact CID-TRCONT trpwd

5.8.2.2. Response element structure¶

The FRED EPP server responds with a plain result message which does not contain any response data (no <resData>).