Ice started off: KC published a draft document on paperless transfer of .RU domains between registrars

Good day everyone.
Some time ago, a draft document “On the procedure to be applied when transferring support for domain name information between registrars” appeared on the CC website.
Read about key features under the cat.


Important points:

3. The issuance of the AuthInfo code to the administrator is performed by the donor registrar in one of the ways chosen by the administrator, including:
- submission in writing;
- using sms-authorization on the administrator's phone number stored in the Registry (with the function of receiving short text messages (sms)), intended for carrying out the procedure for transferring domain support between registrars;
- using e-mail authorization at the administrator's e-mail address stored in the Registry, intended for carrying out the procedure for transferring domain support between registrars.

9.4. The donor registrar may refuse to transfer domain support in the event of:
- the presence of signs of fraud;
- the occurrence of a valid dispute related to the identification / authorization of the administrator;
- non-payment for the past (completed) registration periods, if the domain name registration has expired, or for the past and current registration periods, if the domain registration period has not expired (...)
')
9.1. In the period specified in paragraph 9 of the Regulations [5 earth days; approx. la0], the donor registrar has the right to conduct additional identification of the administrator and / or request from the administrator confirmation of the application for the transfer of domain support to the recipient registrar.
Additional verification of the donor registrar is not mandatory. As part of this check, the administrator is not obliged to confirm to the donor registrar an application for the transfer of domain support to the recipient registrar. Therefore, in the absence of the administrator’s direct refusal to transfer domain support to the registrar-recipient (if the administrator does not act), the donor registrar has no right to prevent the transfer of domain support.

4. Recipient registrar shall verify:
- the coincidence of the AuthInfo-code stored in the Registry for the given domain name with that specified in the application for the transfer of domain support;
- validity of the AuthInfo code;
- the coincidence of the data of the person who applied for the transfer of domain support with the data of the administrator of this domain name stored in the Registry

Essence (cases of expiration of registration, blocking, etc., I do not consider):

1. The donor registrar must issue an Auth code within 3 days.
2. The administrator carries this code to the new registrar.
3. The new registrar in writing or by sms or email asks for confirmation from the administrator and, if he receives it, initiates a transfer including using auth code.
4. When the transfer is initiated, the donor registrar has five days to receive the administrator’s protest and, if the registrar and the administrator do not protest in any way, the registrar is changed.

In general, everything is the same as EPP in gTLDs, with the same advantages and disadvantages:
Pros: fast (up to 12 days), fashionable, youthlessly
Cons: stale access to email, re-issue of the sim card ... well, you understand.
Important: So you can change only the registrar. The administrator can be changed only a month after the transfer.
With security is always like this: either convenient or safe.

Thus: I believe that this is important and necessary, since it will enable the end user to change the registrar " in case of what" [1] and [2] and "vote with their feet."
Will it be accepted and in what form - time will tell.

PPS, I understand that paperless transmission is possible now. Anyway, most registrars now implement this by issuing a power of attorney to the registrar to carry out the relevant operation.