ICANN's new CoR Process Will Impact Every gTLD Domain Reseller

[xeqution]

Hi,

 

I apologise if this has been posted elsewhere, I've tried searching for a recent discussion regarding the new policies ICANN are implementing that will affect every gTLD distributed by ICANN. I'll use OpenSRS (Tucows) as an example here - see: https://opensrs.com/new-transfer-policy-qa/

 

With every modification to the registrant first name, last name, contact email or organization name a change of registrant is performed which means that both the old registrant and the new registrant need to approve the change in order for the details to successfully be updated.

 

An automatic lock of 60 days will be applied to the domain name once the change of registrant is completed unless opted-out.

 

I can't seem to find any discussion or release logs relative to WHMCS updating their domains WHMCS modules to reflect the above changes. From my understanding this is going to break the way WHMCS updates the contact information on a domain name (they simply wont update correctly until both the new and old registrant approve the changes to the registrant information). WHMCS will also not display the status of a 'Change of Registrant' - eg. whether it's in process etc.

 

Luckily we've custom coded our own module so we'll simply make the modifications required, however the default modules supplied by WHMCS are yet to be changed.

[brian!]

I apologise if this has been posted elsewhere, I've tried searching for a recent discussion regarding the new policies ICANN are implementing that will affect every gTLD distributed by ICANN. I'll use OpenSRS (Tucows) as an example here - see: https://opensrs.com/new-transfer-policy-qa/

there hasn't been any discussion about this in the forums, and i've no idea if WHMCS are even aware of this forthcoming change... you would think that logically they should be, but past experience has often shown otherwise.

 

I know eNom are changing their API to accommodate this policy change, and we've been getting emails from OpenSRS about this since June 2016 - so you would hope one way or another, some development and testing is currently taking place @ WHMCS in preparation for a v7.0.2 (and possibly v6 patch) release before the end of the month.

 

though they've missed similar deadlines in the past...

[WHMCS ChrisD]

Hello xeqution,

 

Looking at the OpenSRS documentation they seem to indicate that changes are not needed to be made to your system as OpenSRS will handle the basic requirements themselves:

 

"Our approach is to ensure resellers do not necessarily need to make adjustments to their systems to support the new policy. OpenSRS will be able to handle all necessary basic requirements, and provide some optional tools and features that allow resellers to optimize handling of this policy."

 

The same appears true of Enom:

 

What action will I need to take as an Enom reseller?

We have updated our Registration Agreement for Enom to be permitted to serve as the designated agent on the registrant’s behalf. Enom resellers will be required to obtain the agreement of their customers to the updated Enom Registration Agreement on or before December 1, 2016. In addition, we have made similar updates to our ID Protect Agreement, and any resellers offering the ID Protect service will be required to obtain their customers’ agreement to the updated ID Protect Agreement on or before December 1, 2016.

 

Based on this it seems no changes are required from our side as the registrars will be picking this up but I am clarifying this internally as well.

[WHMCS ChrisD]

Hi Everyone,

 

I have confirmed with our team internally that this is a registrar level change. We'll be posting a blog over at http://blog.whmcs.com/ in the next couple of days with everything you need to know.

 

In essence however you simply need to check with your registrar how they are handling it.

[WHMCS ChrisD]

Hey All,

 

Just an update here, Matt has posted a blog this morning on ICANN's New Transfer Policy: What you need to know its a great sum up of everything

[JLHC]

Chris,

 

As LogicBoxes made some backwards breaking compatibility changes to their API that will require an update to the module:-

 

1. When can we expect the update for the module to be available?

 

2. Will it be released for v6.x as well or only for v7.x only?

[WHMCS ChrisD]

1. When can we expect the update for the module to be available?

 

Should be in the next week or two, I'm waiting for an exact date.

 

2. Will it be released for v6.x as well or only for v7.x only?

 

I don't have the details here but am trying to find out I suspect it will support 6.3.x as well as 7

[WHMCS ChrisD]

Hi Everyone,

 

This morning we've published WHMCS v7.0.2 for users of WHMCS V7.0 or v7.0.1 which includes the ResellerClub & LogicBoxes API Compatibility Update you can learn more at http://blog.whmcs.com/?t=121646 or download using the Automatic Updater.

 

For version 6 you can get the patch for ResellerClub & LogicBoxes at http://www.whmcs.com/download/918/LogicBoxesIRTPUpdateForV6x.zip

 

Please do reach out if you have any questions