| A | B | C | D | E | |
|---|---|---|---|---|---|
1 | Step in transfer process | Action | Who does it & where? | Messaging | Notes |
2 | Request to prepare domain for transfer | - unlock domain - request TAC | Domain owner or account holder, in Control Panel (or other method?) provided by losing Registrar | Optional Notification of TAC Request | This could mean the TAC doesn't already exist, or, requesting it could be looking at it in CP where it already is. Clarification: It is not required to unlock the domain before requesting the TAC. WG discussed that this notification would be sent to the "domain owner." Additional work needed around definitions of the individuals involved in the process? |
3 | Prepare domain for transfer | - verify validity of request - remove any other locks as appropriate - create TAC in Ry system - set TTL on TAC | Losing Registrar, in Registry system (via EPP?) | "Verify validity" could include confirming request is from the right person (this might be automated based on password login to CP), confirming the domain is not locked due to Change of Registrant (if that still exists), domain does not have Registry Lock to deal with, domain is more than 60 days old. - 5 day window might be at this step | |
4 | Fulfill request to prepare domain for transfer | - provide TAC | Losing Registrar | "Here is your TAC" Policy does not need to define this template | The few steps here could all happen basically at the same time, via the automated control panel (as it does today). - Do we still want the 5 day window for Losing Rr to provide the TAC? - Do we need to dictate who the TAC is provided to? - How exactly is the TAC provided? What is "a secure manner"? Could be sent by email, SMS, could be displayed on screen. Do we need to define? |
5 | - send separate notification saying the TAC has been provided | Losing Registrar | Required Notification of TAC Provision | Sent in case the TAC was requested by someone who should not have had access to do so, in order to ensure that the domain owner is aware Sept 14 - could be required to send this to RNH if the TAC was sent to a different email address -- but under what circumstances would TAC be emailed somewhere else? - if TAC is sent by email to RNH, then this separate notification is not required - Are there circumstances where it might be appropriate to send this notice to multiple email addresses? | |
6 | Notify domain owner (pre-transfer) | - notify domain owner that transfer is being requested | Losing Registrar | Notification of Pending Transfer | We have two possible templates to be sent in this step, should choose one (they seem to be very close to the same already). Both are sent at the same time as the TAC is provided to the domain owner. If we're sending the Notification of TAC Provision (row 5) we likely do not also need this notice. Sarah thinks only one pre-transfer notice to the domain owner should suffice. |
7 | Initiate transfer | - submit domain and TAC to gaining Registrar | Domain owner or account holder, in Control Panel/website of gaining Registrar | Gaining FOA Working Doc | Gaining Rr is not required to send any confirmation request (no gaining FOA) but is likely to send a welcome message, payment receipt, etc. |
8 | Request transfer at Registry | - submit domain and TAC to registry operator - request domain to be moved to new Rr cred | Gaining Registrar, via EPP | ||
9 | Move domain to new Registrar | - confirm domain OK to transfer & TAC is valid - move domain to new Rr cred - Send poll messages to Losing/Gaining of transfer completion - add 1 year to registration term (or does Rr do this?) | Registry | Gaining FOA Working Doc | - Is adding a year to the registration term up for modification in this PDP? Do we want to consider that? - On 7 Sep call, some support expressed for one-year add-on period. |
10 | Post-transfer updates | - update domain to show contact data provided in transfer request (could include updating contact data in Ry system) - reset TAC or invalidate TTL or whatever this process is | Gaining Registrar (in both internal system and maybe Ry) | See comment in cell -- do we need structure around the contact updates which may also be ownership changes? Working assumption: Registry to be responsible for TAC reset/TTL invalidation. | |
11 | Notify domain owner (post-transfer) | - send notification of complete transfer | Losing Registrar | Required Notification of Transfer Completion | Does (should) the gaining Registrar also have a policy obligation to send a notice at this stage? They will likely want to send one for business/marketing purposes, but are they required to do so? Should the Losing Registrar be required to provide links/info about procedures to follow if Registrant feels the transfer was done in error? Some support expressed for requiring this notification. |
12 | Fast-Undo Transfer | - identify that a transfer was fraudulent/problematic - notify gaining and losing Rrs - put that thing back where it came from or so help me - remove renewal that came with transfer, reverse payment made by gaining Rr? | Gaining and Losing Registrars? | This has also been called "reverse transfer" but I am concerned that won't clearly indicate that this is a specific UNDO moment? Lots of TBD here |