The ice has broken: KC has published a draft document on the paperless transfer of .RU domains between registrars

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


Important points:

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

9.4. The donor registrar has the right to refuse to transfer domain support in the event of:
- signs of fraud;
- the occurrence of a reasonable dispute related to the identification / authorization of the administrator;
- non-payment for past (completed) registration periods if the domain name registration has expired, or for past and current registration periods if the domain registration has not expired (...)

9.1. By the time specified in clause 9 of the Rules [5 earth days; approx. la0], the donor registrar has the right to additionally identify the administrator and / or ask the administrator for confirmation of the application for transferring domain support to the recipient registrar.
Additional verification of the donor registrar is optional. As part of such a check, the administrator is not required to confirm to the donor registrar an application for the transfer of domain support to the recipient registrar. Therefore, in the absence of a direct administrator’s refusal to transfer domain support to the recipient registrar (if the administrator is inactive), the donor registrar may not prevent the transfer of domain support.

4. The recipient registrar is obliged to verify:
- if the AuthInfo code stored in the Registry for the given domain name matches the one specified in the application for transferring domain support;
- the validity of the AuthInfo code;
- coincidence of the data of the person who filed the application for the transfer of domain support with the data of the administrator of this domain name stored in the Registry

The bottom line (I do not consider cases of expiration of registration, blocking, etc.):

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 via sms or email, asks for confirmation from the administrator and, if received, initiates a transfer, incl. using auth code.
4. When the transfer is initiated, the donor registrar has five days to receive an administrator protest, and if the registrar and administrator do not protest in any way, the registrar is changed.

In general, everything is the same as EPP in gTLD, with the same pros and cons:
Pros: fast (up to 12 days), fashionable, youth paperless
Cons: stupid email access, re-issuance of a sim card ... well, you get the idea.
Important: So you can change only the registrar. Administrator can be changed only a month after the transfer.
With security it is always like this: either convenient or safe.

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

PPS, I understand perfectly that paperless transfer is possible now. One way or another, for most registrars this is now implemented by issuing a power of attorney to the registrar to carry out the corresponding operation.