Hi all, I think the approach can be simplified. * We have a bunch of current requirements. * New requirements. Fast track the current privacy providers (this can be done in advance). If correct, compliance should know which Registrars are in good standing and have data of the current requirements in combination with Registrars due to the previous audits. No need to to pre-screen this all. New requirements, this can be dealt with the future compliance audits. This will save everyone heaps of time and thus money, plus the bulk has now been dealt with in a short time frame. I expect that non-affiliated privacy providers can be on-boarded in a similar fashion. The WG did not make recommendations on fees and lengthy application processes. The current proposal will most likely not survive the comment period; this is something, we as an IRT, have to keep in mind. Thanks, Theo Geurts On 11-9-2017 13:29, Michele Neylon - Blacknight wrote:
Amy
Thanks for sharing this.
I have several concerns.
Firstly the fees that are being proposed.
I cannot understand why or how ICANN can justify charging $4k / year for this to a provider.
From our perspective this makes zero sense, as there is no value being provided by ICANN and the cost is very high – you’re essentially doubling how much I pay ICANN per year.
Background screening – this seems to be complete overkill for an “affiliated” provider.
In our case for example ICANN is going to be dealing with the same person you’ve always dealt with.
If you insist on subjecting us to this kind of scrutiny I don’t mind, but I just see it as being a waste of resources.
6.5 – I thought there was no clear agreement on different labelling of whois privacy in whois?
8.3 – where on earth did that come from?
Regards
Michele
--
Mr Michele Neylon
Blacknight Solutions
Hosting, Colocation & Domains
Intl. +353 (0) 59 9183072
Direct Dial: +353 (0)59 9183090
Personal blog: https://michele.blog/
Some thoughts: https://ceo.hosting/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845
*From: *<gdd-gnso-ppsai-impl-bounces@icann.org> on behalf of Amy Bivins <amy.bivins@icann.org> *Reply-To: *"gdd-gnso-ppsai-impl@icann.org" <gdd-gnso-ppsai-impl@icann.org> *Date: *Friday 8 September 2017 at 14:55 *To: *"gdd-gnso-ppsai-impl@icann.org" <gdd-gnso-ppsai-impl@icann.org> *Subject: *[Gdd-gnso-ppsai-impl] Materials for 12 Sept PP IRT Meeting
Dear Colleagues,
Our next Privacy/Proxy IRT meeting is scheduled for this upcoming Tuesday, 12 September at 1400 UTC. I hope you all can make it.
On this call, I will walk you through the updated Applicant Guide, and then there will be time for Q&A and your feedback on the document. The most significant changes you’ll note in this discussion draft v2 is a proposed streamlining of the application for providers that are affiliated with an ICANN-accredited registrar, privacy/proxy provider (not applicable in the initial application window), or a gTLD registry operator. We’ve also added a fees proposal.
Please review prior to our meeting, and we look forward to discussing on Tuesday. Please share any feedback you have prior to our call on-list.
Have a great weekend!
Amy
*Amy E. Bivins*
Registrar Services and Engagement Senior Manager
Registrar Services and Industry Relations
Internet Corporation for Assigned Names and Numbers (ICANN)
Direct: +1 (202) 249-7551
Fax: +1 (202) 789-0104
Email: amy.bivins@icann.org <mailto:amy.bivins@icann.org>
www.icann.org <http://www.icann.org>
_______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl@icann.org https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl