[190520] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: New ICANN registrant change process

daemon@ATHENA.MIT.EDU (Blake Hudson)
Wed Jul 6 15:47:11 2016

X-Original-To: nanog@nanog.org
To: nanog@nanog.org
From: Blake Hudson <blake@ispn.net>
Date: Wed, 6 Jul 2016 14:47:02 -0500
In-Reply-To: <800550479.18808.1467654861589.JavaMail.zimbra@baylink.com>
Errors-To: nanog-bounces@nanog.org

As a customer of OpenSRS they sent us a notice about the change. The 
notice, and this page you linked, speak to their customer communication 
about policy changes.

To be honest, I just breezed the email message and noted that it seemed 
like a positive change (without knowing the reasons that prompted the 
change). We rarely update registrant information and rarely transfer 
domains. We also know our customers. I expect this will have zero impact 
on our day to day operations other than potentially preventing some 
hijackings (we have had some customers experience hijackings in the days 
when all it took was a fax on letterhead to NetSol to get your domain 
info changed).



Jay R. Ashworth wrote on 7/4/2016 12:54 PM:
> I'll go ahead and assume I wasn't the last person to get this memo (courtesy
> Lauren Weinstein's PRIVACY Digest):
>
> https://opensrs.com/blog/2016/06/icanns-new-transfer-policy-will-impact-business-customers/
>
> It does seem that this is going to make life difficult for a bunch of pretty
> normal business processes.
>
> If you didn't know about it either... ask yourself why not.
>
> Cheers,
> -- jra
>


home help back first fref pref prev next nref lref last post