Hello all, Escrow. Privacy providers must escrow data, we all agreed this should be the case. The scenarios demonstrated by Francisco yesterday was helpful, and I hope that the IRT members understand that these scenarios are just a few scenarios, we can identify much more that are already out there. In my opinion, it will be counter productive to try to flesh out all these scenarios. It is a lot of work, and most likely we will not be able to capture all scenarios. But if every privacy provider has to escrow we do not have to include all those scenarios. The only issue is here is the non-affiliated provider. We do not have their data, and we cannot escrow their data as a Registrar or platform provider. If the non-affiliated provider would move to our platform, no problem, but this is more of a definitional issue of what a non-affiliated privacy provider is. Everything else be it affiliated, a reseller, whatever, IF it is on our platform, we can escrow the data. Be it in one big deposit, a separate deposit, deposits with different escrow agents, technically all possible and happening. A non-affiliated privacy provider has no affiliation with a Registrar or platform provider, not technical nor contractual. They should take care of their deposits, and there are plenty of options on how to do this. They should mention in their deposits at which Registrar the domain names are located. I assume everyone in the IRT agrees we do not want to end up with a deposit that is not usable. As soon a non-affiliated privacy provider would use the service of a Registrar or platform provider there is a contractual relation, and the privacy provider is no longer not affiliated. Does this make sense? Let me know if there are any questions on this subject. Best, Theo Geurts Amy Bivins schreef op 2017-09-12 06:26 PM:
Hello, All,
Thanks so much for your active participation on today's Privacy/Proxy IRT call.
The call recording, slides and chat transcript are available on the wiki, https://community.icann.org/display/IRT/12+September+2017. If you couldn't attend, I encourage you to review these, as we covered a lot of ground this week.
In summary, with respect to data escrow, IRT members on the call said that in drafting the specification, we should keep the proposed requirements as open as possible and not attempt to create restrictions with respect to various types of provider/registrar/affiliate relationships. With respect to the accreditation application process, initial input from many IRT members was that the process may need to be simplified. With respect to accreditation criteria, some IRT members said that we are still requiring too much for affiliated providers; other IRT members said we may have cut too much for affiliated providers. WE NEED AS MUCH FEEDBACK ON THIS TOPIC AS POSSIBLE, GIVEN THAT THE VIEWS AMONG IRT MEMBERS APPEAR TO BE QUITE MIXED. WE WILL CONTINUE DISCUSSING THIS TOPIC NEXT WEEK.
IRT ACTION ITEMS
Please provide any further input you have on the topics discussed on today's call, including (a) the data escrow questions presented by Francisco Arias, (b) the "initial application window" process and (c) the proposed affiliate categories for accreditation processing purposes, NO LATER THAN NEXT MONDAY, 18 SEPTEMBER. Also, please continue reviewing the PPAA draft v1 and send any additional topics that you would like to discuss to the list (we have several topics to revisit, but once we reach the end of the list, we will move on if no other topics are raised).
Next week, we will continue discussing the second draft of the applicant guide, including any feedback you have on the topics discussed this week, plus the application questions and fees proposal. To aid this discussion, I am attaching an editable word version of the document, which Volker requested, so that proposed edits can be marked on the document. Please mark any proposed edits in track changes mode--this is how we will identify proposed changes to discuss with the group.
If you have questions or comments, please don't hesitate to reply to the list.
Best,
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
www.icann.org [1]
Links: ------ [1] 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