Re: New ICANN registrant change process

2016-07-07 Thread Rubens Kuhl
On Wed, Jul 6, 2016 at 11:13 PM, David Conrad wrote: > Rubens, > > On Jul 6, 2016, at 2:20 PM, Rubens Kuhl wrote: > >> Not sure the RPZ hammer has been brought out in force yet. I've seen a > few recommendations on various mailing lists, but no concerted effort. > Unfortunately, there is no easy

Re: New ICANN registrant change process

2016-07-06 Thread Jaap Akkerhuis
David Conrad writes: > > > But I would agree it is much easier to simply blame ICANN. > Yeah, I always blame ICANN for the bad weather :-). jaap

Re: New ICANN registrant change process

2016-07-06 Thread Christopher Morrow
On Wed, Jul 6, 2016 at 10:17 PM, David Conrad wrote: > On Jul 6, 2016, at 10:41 AM, Christopher Morrow > wrote: > > Perhaps this all self-polices? > > I figure either it does or governments get involved and that most likely > ends in tears. > > I can't wait for our gov't overloads to discover th

Re: New ICANN registrant change process

2016-07-06 Thread David Conrad
On Jul 6, 2016, at 10:41 AM, Christopher Morrow wrote: > Perhaps this all self-polices? I figure either it does or governments get involved and that most likely ends in tears. > I hate it when you are right :) Don't worry: very rarely happens. Regards, -drc (speaking only for myself) si

Re: New ICANN registrant change process

2016-07-06 Thread David Conrad
Rubens, On Jul 6, 2016, at 2:20 PM, Rubens Kuhl wrote: >> Not sure the RPZ hammer has been brought out in force yet. I've seen a few >> recommendations on various mailing lists, but no concerted effort. >> Unfortunately, there is no easy/scalable way to determine who a registrar >> for a given

Re: New ICANN registrant change process

2016-07-06 Thread Rubens Kuhl
> > Not sure the RPZ hammer has been brought out in force yet. I've seen a few > recommendations on various mailing lists, but no concerted effort. > Unfortunately, there is no easy/scalable way to determine who a registrar > for a given name is, That is called RDAP, but ICANN currently blocks g

Re: New ICANN registrant change process

2016-07-06 Thread Christopher Morrow
On Wed, Jul 6, 2016 at 4:04 PM, David Conrad wrote: > Depends on whether or not the Registry wants their TLD to be associated >> with spam/malware distribution/botnet C&C/phishing/pharming and be removed >> at resolvers via RPZ or similar. Ultimately, the Registries are responsible >> for the poo

Re: New ICANN registrant change process

2016-07-06 Thread David Conrad
> Depends on whether or not the Registry wants their TLD to be associated with > spam/malware distribution/botnet C&C/phishing/pharming and be removed at > resolvers via RPZ or similar. Ultimately, the Registries are responsible for > the pool the Registrars are peeing in -- it's the Registry's

Re: New ICANN registrant change process

2016-07-06 Thread Valdis . Kletnieks
On Wed, 06 Jul 2016 13:23:04 -0400, Christopher Morrow said: > On Mon, Jul 4, 2016 at 3:03 PM, Jay Ashworth wrote: > > > Seems to me that the proper thing to be done would have been for > > Registries to deauthorize registrars on the grounds of continuous streams > > of complaints. > > > > > > On

Re: New ICANN registrant change process

2016-07-06 Thread Christopher Morrow
On Wed, Jul 6, 2016 at 2:53 PM, David Conrad wrote: > On Jul 6, 2016, at 7:23 AM, Christopher Morrow > wrote: > > On Mon, Jul 4, 2016 at 3:03 PM, Jay Ashworth wrote: > >> Seems to me that the proper thing to be done would have been for > >> Registries to deauthorize registrars on the grounds of

Re: New ICANN registrant change process

2016-07-06 Thread Blake Hudson
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 pr

Re: New ICANN registrant change process

2016-07-06 Thread David Conrad
On Jul 6, 2016, at 7:23 AM, Christopher Morrow wrote: > On Mon, Jul 4, 2016 at 3:03 PM, Jay Ashworth wrote: >> Seems to me that the proper thing to be done would have been for >> Registries to deauthorize registrars on the grounds of continuous streams >> of complaints. >> >> > > On what metri

Re: New ICANN registrant change process

2016-07-06 Thread Christopher Morrow
On Mon, Jul 4, 2016 at 3:03 PM, Jay Ashworth wrote: > Seems to me that the proper thing to be done would have been for > Registries to deauthorize registrars on the grounds of continuous streams > of complaints. > > On what metric? Pure volume? Percent of registrations? type of complaint by simi

Re: New ICANN registrant change process

2016-07-04 Thread Jay Ashworth
Seems to me that the proper thing to be done would have been for Registries to deauthorize registrars on the grounds of continuous streams of complaints. On July 4, 2016 2:35:37 PM EDT, Mel Beckman wrote: >I've worked behind the scenes for more than one of these outfits. I can >tell you that dom

Re: New ICANN registrant change process

2016-07-04 Thread Rubens Kuhl
On Mon, Jul 4, 2016 at 2:54 PM, Jay R. Ashworth wrote: > 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 thi

Re: New ICANN registrant change process

2016-07-04 Thread Mel Beckman
I've worked behind the scenes for more than one of these outfits. I can tell you that domain registrars are basically printing money. On the other hand, I've also been the victim of domain hijacking. I can tell you that the domain registrars involved were less than useless in reversing the obvio