NetEarth Group, inc Get the latest information about NetEarth Group or any of its subsidiary companies.

November 17, 2016

Important – ICANN Policy IRTP-C and how it will affect the transferring and movement of domains.

Filed under: Changes on the LB platform,NetEarth One — chrisp @ 17:16

Following my participation in the recent ICANN meeting in India, a number of registrars had a very productive discussion with ICANN compliance, we have been trying to move the removal of PP services COA from the IRTP-C into the PPSAI IRT, which we have found a route to hopefully make this happen and the RrSG is currently working on this.  Below is the current implementation, and if we are succesful the removal or enablement of PP on a domain will not trigger the unnecessary emails to the registrant.

 
IRTP-C implementation on the LB platform.

As you know, ICANN has implemented a new Transfer Policy which affects all ICANN-accredited registrars. The Transfer Policy takes effect 1st December 2016.

LB would like to take this opportunity to give you an insight into the various processes that will be affected in the OrderBox.

Processes Affected in OrderBox :

Quite a few processes will be directly impacted by this policy change and the platform will be updated to comply.

A. Contact Details Modification

The following are applicable throughout OrderBox for all gTLDs. The Customer/Reseller will no longer be able to:

1. Modify the contact details from the Customer Control Panel, under Contacts Management (this is logged in as Customer >> Settings). However, the Customer/Reseller will continue to have rights to modify the contacts via the Domain Order Overview page.
2. Use the ‘Update all Domain Names currently using this contact (wherever applicable)’ option while updating the Contact Details of a Domain Name.
3. The API call ‘contacts/modify’ will be deprecated.

The IRTP-C process is compulsory for all Registrars and the following changes are applicable:

1. Multiple Domain Contact Modification actions will no longer be queued. Only one Domain Contact Modification will be allowed to be in progress for a Domain Name. An attempt to place another Domain Contact Modification action when one is already in progress will return an appropriate error.
2. If the registrant contact either in the whois (for .COM/.NET) or at the Registry for other gTLDs does not match with the contacts in OrderBox, then the Registrant contact at the registry will be cloned, a new contact will be created in OrderBox with these details and this new contact will be associated with the domain. The current Contact Modification action will then fail. The Customer/Reseller will then have to request a Domain Contact Modification action once again (This point will also be applicable in case of Bulk Domain Contact Modification)

B. Move Service

This change is applicable throughout OrderBox for all TLDs. Move Service with the Default Contact option will be deprecated.
The Customer/Reseller will no longer be able to:

1. Move domains by using the ‘Use new customer’s default contact’ . The old contact will continue to be used.
2. Parameter ‘default-contact’ of the API call ‘products/move’ will no longer accept the value ‘default’.

C. Domain Transfer

Transfer request initiated with no request to modify contact details (name, company and/or email) on the domain

1. When a transfer is requested on a gTLD domain, the transfer Form of Authorization (FOA) will be sent to the Admin Email on WHOIS
2. This transfer FOA will be valid for 60 days; however, it will expire earlier if one of the following occurs:
The domain name expires before the transfer is completed
A change of Registrant is completed (platform level)
3. If the transfer FOA is not approved or if it expires, the transfer will be canceled.

Transfer request initiated where there is a request to modify contact details (name, company and/or email) on the domain

1. When a transfer is requested on a gTLD domain, the transfer FOA will be sent to the Admin Email on WHOIS.
2. This transfer FOA will be valid for 60 days; however, it will expire earlier if one of the following occurs:
The domain name expires before the transfer is completed
A change of Registrant is completed (platform level)
3. If the transfer FOA is approved, then an additional change of registrant FOA will be sent across to the parties involved [To minimize delays in transfer, we recommend using the same registrant details (name, company and email) as mentioned on the WHOIS, as this will prevent the Change of Registrant process from getting triggered. The registrant can be modified after the successful transfer of a domain into OrderBox]
4. If either of the Registrants disapprove the change of registrant FOA, the domain transfer request will also fail
5. Once the change of registrant FOA approval is received from both the registrants, an additional WHOIS check will be made to validate if the Registrant of the domain has changed in the interim. If yes, then the domain transfer request (including the change of registrant action) will fail, else it will proceed.
6. Post successful transfer, both the prior and the new registrant will receive an email notifying them about the change of registrant.

D.   Privacy Protection

While enabling/disabling Privacy Protection, the Registrar on Record will act as the Designated Agent to approve a change of registrant. No explicit approval will be needed from the Registrant.

A notification email will be sent to both the Registrants (Old and New) whenever the status of Privacy Protection is changed. This email is a compulsory email.

Relevant clauses to authorize the Registrar on Record as a Designated Agent have been added to the Domain Registration Agreement.

 

PPSAI = Privacy Proxy Service Accreditation Issues Working Group

IRTP-C = Inter Registrar Transfer Policy

IRT = Inplementation Recommendation Team

RrSG = Registrar Stakeholder Group

No Comments

No comments yet.

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.

Powered by WordPress