- Gdd-gnso-ppsai-impl - lists.icann.org

updated PPAA + documents for today's IRT call
by Caitlin Tubergen Oct. 10, 2017

Oct. 10, 2017

Dear Colleagues, Attached, please find the most recent redline version of the Privacy and Proxy Provider Accreditation Agreement. During today’s IRT call, I will provide an outline of the changes to guide your review and feedback in the upcoming weeks. We do not expect you to review and provide comments prior to today’s call, as you are just now receiving the document. I look forward to speaking to you in about an hour. In addition to the updated PPAA, we will continue discussing the De-Accredited Provider Transition Procedure (attached) and the provider application (attached). Thank you to Greg and Theo for your comments and questions on the draft application; we will discuss them during today’s call. Thank you! Best regards, Caitlin

3 2

Re: [Gdd-gnso-ppsai-impl] updated PPAA + documents for today's IRT call
by Michele Neylon - Blacknight Oct. 10, 2017

Oct. 10, 2017

Caitlin et al A few comments I still maintain that the $4k / year fee for registrars that are already accredited with ICANN and paying fees is too high. In the PPA_redline document: 3.8.3 “all services” is way too broad and is unreasonable. This should be narrowed to specify that it refers solely to proxy / privacy 3.9 for “affiliated” entities can this be simplified and combined? We already have to do this for our registrar accreditation having to do it twice is likely to cause confusion and create unnecessary duplication 3.12.3 – while the language here might be sufficient I suspect it’ll cause headaches for those of us who are trying to comply with GDPR etc., and are removing PII records as quickly as we can. My main concern is that ICANN Compliance (and others) might come looking for data we no longer hold. I also don’t really understand why the data needs to be held for this long. There is a reference in Spec 7 to a waiver, but I can’t see it here. Specification 7 section 2 has a very complicated waiver process which seems to be conflating data retention with whois policy. Unless I’m missing something this could be simplified quite a bit. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ http://blacknight.blog/ 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(a)icann.org> on behalf of Caitlin Tubergen <caitlin.tubergen(a)icann.org> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Date: Tuesday 10 October 2017 at 13:39 To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] updated PPAA + documents for today's IRT call Dear Colleagues, Attached, please find the most recent redline version of the Privacy and Proxy Provider Accreditation Agreement. During today’s IRT call, I will provide an outline of the changes to guide your review and feedback in the upcoming weeks. We do not expect you to review and provide comments prior to today’s call, as you are just now receiving the document. I look forward to speaking to you in about an hour. In addition to the updated PPAA, we will continue discussing the De-Accredited Provider Transition Procedure (attached) and the provider application (attached). Thank you to Greg and Theo for your comments and questions on the draft application; we will discuss them during today’s call. Thank you! Best regards, Caitlin

2 1

Materials, action items from 3 October Privacy/Proxy IRT call
by Caitlin Tubergen Oct. 10, 2017

Oct. 10, 2017

Dear Colleagues, Thank you for your participation on the last Privacy/Proxy IRT call on Tuesday, 3 October. For those who could not attend, I encourage you to review the recording (https://participate.icann.org/p8dnkiub56v/) and materials on the wiki, https://community.icann.org/display/IRT/03+October+2017. I attached two documents for your review: The updated Applicant Guidebook/Application (v3) The updated De-Accreditation Procedure (v2) Notes on Updated Applicant Guide We received feedback from the IRT that the application process should be simplified, which included (1) consolidation of “tracks”, i.e., rather than four tracks, there should be two tracks: unaffiliated entities and affiliated entities; (2) a streamlined application, which includes only necessary long-form/essay questions and a “check box”, short form for the majority of questions. Further to that feedback, please review the next iteration (v3) of the Applicant Guidebook, with particular attention to Sections 5-6 (p. 10-11). Please provide any additional feedback to the list by Tuesday, 10 October. We will discuss any updates on our call next Tuesday. Notes on De-Accreditation Procedure Further to your feedback on the last call about de-accreditation, we removed the text in section 2.4.6 about a customer’s personal information being revealed in WHOIS following a termination of a P/P Provider to reflect the reality of a termination, which would involve a potential suspension (per the Whois Accuracy Program Specification (WAPS) as opposed to publication of underlying customer information in RDDS. A few members of the IRT expressed concern with treating the information as inaccurate and suspending names after 15 days, per the WAPS. We proposed to change that period to 30 days, i.e., following a termination of a P/P provider, the gaining provider/registrar would have 30 days to contact the customers to correct the inaccurate WHOIS information before potential suspension. Additionally, a member of the IRT expressed a concern as to which entity (the terminated or gaining provider) would be in charge of processing abuse complaints during terminations. Until the date of P/P provider is terminated, the terminating provider would be responsible for handling abuse tickets, as that entity would still be under contract. Following the termination date, the new provider would be responsible for processing abuse complaints. A member of the IRT noted a potential gap, where an individual/entity may file a complaint with the terminating entity, but if it is not responded to, it would need to file a new version of the same complaint with the gaining entity. If you have any suggestions about how this should be handled, please feel free to make suggestions to the list by Tuesday, 10 October. On our next call on Tuesday, 10 October, we will be discussing the proposed updates to the attached documents. I am also hoping to have the next iteration of the Accreditaiton Agreement to share with you early next week. Thank you again for all of your work on this! Best regards, Caitlin

4 3

Materials, action items from last Privacy/Proxy IRT call
by Caitlin Tubergen Oct. 4, 2017

Oct. 4, 2017

Dear Colleagues, Thanks so much for your participation on the last Privacy/Proxy IRT call on Tuesday, 19 September. For those who could not attend, I encourage you to review the recording and materials on the wiki, https://community.icann.org/display/IRT/19+September+2017. A detailed account of the feedback received during the call is attached. In summary, the consensus of the group appeared to be that: ICANN org should provide the IRT with supporting cost data to facilitate the discussion surrounding proposed program fees; ICANN org should create a new draft of the accreditation application, transforming most if not all of the “essay”-type questions in sections 5 and 6 to “confirm the applicant will comply”-type questions; ICANN org should revisit the list of questions to consider which ones should, and should not, be required for registrar-affiliated applicants. The shift to confirmation-type questions may reduce the burden of these questions for affiliates. ICANN is working on these deliverables, and they should be ready to share with the IRT in a couple of weeks. In addition, I want to flag that one IRT member has recommended that we revisit the current definitions of “privacy service” and “proxy service” in the current guidebook and PPAA drafts. Non-substantive changes to these definitions from the Final Report, to conform to other defined terms in the agreement, were not opposed by any IRT member when this topic was previously discussed. However, if multiple IRT members would like to revisit this discussion, this will be added to the agenda for a future meeting. For our call next Tuesday, 3 October, we will be discussing the second draft de-accreditation process (attached). Please review prior to the call so that we can discuss the proposed changes in detail. If you are unable to attend the call, as some of you have noted, please feel free to provide feedback via the list prior to or following the call. Additionally, prior to the call, I will be providing an updated Privacy/Proxy Accreditation Agreement. While we will be not discussing the updates in detail on next week’s call, I will be providing a high-level overview of the changes to guide your review/discussion on future calls. Please let me know if you have any questions in the meantime. Best regards, Caitlin Tubergen Registrar Services and Engagement Senior Manager ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 Office: +1 310 578 8666 Mobile: +1 310 699 5326 Email: caitlin.tubergen(a)icann.org

3 2

REMINDER: CALL in 10 MIN: Meeting Info for Privacy and Proxy Services Implementation Review Team
by Caitlin Tubergen Oct. 3, 2017

Oct. 3, 2017

Dear Colleagues, Please find below the remote participation details for the Privacy and Proxy Services Accreditation Program IRT Meetings will be held on Tuesday, 3 October 2017 at 14:00 UTC for 1 hour 30 minutes. Adobe Connect link: https://participate.icann.org/ppirt Participant code: 4824695647 Dial-In Phone Numbers: US: +1-719-457-6209 Canada, Calgary: +1 403 407 5793 Canada, Montreal: +1 514 669 5928 Canada, Toronto: +1 647 426 9172 Canada, Vancouver: +1 604 222 7836 Argentina (toll free): 0800 800 1223 Argentina, Buenos Aires: +54 (0) 11 5172 6003 Australia (toll free): 1 800 804 786 Australia, Brisbane: +61 (0) 7 3015 0535 Australia, Melbourne: +61 (0) 3 8687 0553 Australia, Sydney: +61 (0) 2 8017 6064 Austria (toll free): 0800 8866 3413 Austria, Vienna: +43 (0) 1 25302 1785 Bahrain (toll free): 800 04212 Bahrain, Manama: +973 1619 8739 Belarus (toll free): 8 820 0011 0341 Belgium (toll free): 0800 39279 Belgium, Brussels: +32 (0) 2 400 6928 Brazil (toll free): 0800 887 0233 Brazil, Rio de Janeiro: +55 21 4560 0072 Brazil, Sao Paulo: +55 11 4935 7169 Bulgaria (toll free): 00800 111 4950 Bulgaria, Sofia: +359 (0) 2 491 6045 Canada (toll free): 1 855 950 3717 Chile (toll free): 171 800 835 783 Chile, Santiago: +56 (0) 2 2666 0696 China (national): +400 613 8103 China, Beijing: +86 10 5667 0003 China, Shanghai: +86 21 2039 7081 Colombia (toll free): 01 800 755 0102 Colombia, Bogota: +57 1 508 8137 Croatia (toll free): 0800 805 940 Cyprus (toll free): 800 97424 Czech Republic (toll free): 800 701 532 Czech Republic, Prague: +420 225 986 554 Denmark (toll free): 80 70 35 86 Denmark, Copenhagen: +45 32 72 78 10 Egypt (toll free): 0800 000 0593 Estonia (toll free): 800 011 1589 Estonia, Tallinn: +372 622 6551 Fiji (toll free): 00800 3322 Finland (toll free): 0800 772 236 Finland, Helsinki: +358 (0) 9 2310 1677 France (national): 0811 655 100 France (toll free): 0800 946 531 France, Paris: +33 (0) 1 70 37 16 56 Germany (national): 01801 003 899 Germany (toll free): 0800 588 9170 Germany, Frankfurt: +49 (0) 69 2222 10612 Germany, Munich: +49 (0) 89 2030 31207 Greece (toll free): 00800 128 913 Greece, Athens: +30 211 181 3824 Hong Kong: +852 3018 9111 Hong Kong (toll free): 800 901 787 Hungary (toll free): 068 001 9673 Hungary, Budapest: +36 1408 8953 Iceland (toll free): 800 9847 India, Bangalore: +91 (0) 80 6127 6710 India, Chennai: +91 (0)44 6688 6061 India, Delhi: +91 (0) 11 6641 1394 India, Mumbai: +91 (0)22 6187 5028 Indonesia (toll free): 007 803 321 8927 Ireland (national): 1890 907 630 Ireland (toll free): 1800 937 649 Ireland, Dublin: +353 (0) 1 526 9421 Israel (toll free): 1809 213 168 Israel, Tel Aviv: +972 (0)3 721 7943 Italy (toll free): 800 146 094 Italy, Milan: +39 02 3600 8006 Italy, Rome: +39 06 8750 0676 Japan (mobile): 0120 632 611 Japan (toll free): 0120 305 211 Japan, Osaka: +81 (0) 6 4560 2410 Japan, Tokyo: +81 (0) 3 4560 1270 Kazakhstan (toll free): 8800 333 7554 Latvia (toll free): 8000 4418 Latvia, Riga: +371 6601 3627 Lithuania (toll free): 8800 31449 Lithuania, Vilnius: +370 5205 5468 Luxembourg: +352 2088 1749 Luxembourg (toll free): 800 28433 Malaysia (toll free): 1 800 816 152 Malaysia,Kuala Lumpur: +60 (0) 3 7724 8010 Mexico (toll free): 01 800 733 4102 Mexico, Guadalajara: +52 33 4162 4504 Mexico, Mexico City: +52 55 8421 0326 Mexico, Monterrey: +52 81 4162 5648 Morocco (toll free): 0800 091 296 Morocco, Casablanca: +212 (0) 520 48 0022 Netherlands (toll free): 0800 020 2597 Netherlands, Amsterdam: +31 (0) 20 716 8345 New Zealand (toll free): 0800 452 947 New Zealand, Auckland: +64 (0) 9 929 1825 New Zealand, Christchurch: +64 (0) 3 974 2596 New Zealand, Wellington: +64 (0) 4 909 4674 Nigeria, Lagos: +234 1 277 3944 Norway (toll free): 800 56081 Norway, Oslo: +47 21 00 48 15 Panama (toll free): 00800 223 1390 Panama, Panama City: +507 8 335 913 Peru, Lima: +51 (0) 1 700 9571 Philippines (toll free): 1 800 111 013 99 Philippines, Manila: +63 (0)2 395 3426 Poland (toll free): 00 800 121 4356 Poland, Warsaw: +48 22 295 3570 Portugal (toll free): 800 784 442 Portugal, Lisbon: +351 21 316 4093 Qatar (toll free): 00 800 100 491 Romania (toll free): 0800 801 035 Romania, Bucharest: +40 (0) 21 529 3992 Russia (toll free): 8 800 500 9241 Russia, Moscow: +7 495 646 9181 Saudi Arabia (toll free): 800 844 6641 Saudi Arabia (toll free): 800 850 0219 Singapore: +65 6622 1957 Singapore (toll free): 800 616 3192 Slovakia (toll free): 0800 002 002 Slovakia, Bratislava: +421 (0)2 3321 5498 Slovenia (toll free): 0800 81193 Slovenia, Ljubljana: +386 1600 8695 South Africa (toll free): 0800 999 434 South Africa, Johannesburg: +27 (0)11 589 8321 South Korea (toll free): 00798 6136 1454 South Korea, Seoul: +82 (0) 2 6007 0079 Spain (toll free): 900 828 035 Spain, Barcelona: +34 93 800 1946 Spain, Madrid: +34 91 114 6653 Sweden (toll free): 0200 125 588 Sweden, Stockholm: +46 (0) 8 5065 3956 Switzerland (toll free): 0800 740 360 Switzerland, Geneva: +41 (0) 22 595 4795 Switzerland, Zurich: +41 (0) 44 580 7207 Taiwan (toll free): 0800 666 596 Taiwan, Taipei: +886 (0) 2 2650 7329 Thailand (toll free): 001 800 6136 1473 Turkey (toll free): 00800 4488 26642 Turkey, Istanbul: +90 212 375 50 49 UAE (toll free): 8000 3570 2662 UK (03): +44 (0)330 336 6002 UK (toll free): 0800 358 6385 Ukraine (toll free): 0800 500 896 Uruguay (toll free): 0004 019 0152 USA /Canada (toll free): 1-866-398-2885 Venezuela (toll free): 0 800 162 7451 Vietnam (toll free): 1800 9226 Costa Rica (toll free): 800 542 5328 France (national): 0821 231 671 India (toll free): 1800 200 9415 Indonesia, Jakarta: +62 21 2188 9084 Ireland (national): 0818 270 271 Japan (national): 0570 085 744 Serbia (toll free): 0800 190 712 UK (national): 0844 473 5010 UK (national): 0845 545 0015 Venezuela, Caracas: +58 212 720 2164 Thank you, Caitlin Tubergen Registrar Services and Engagement Senior Manager ICANN

1 0

Using PPSAI to solve remaining IRTP-C issues
by Volker Greimann Sept. 27, 2017

Sept. 27, 2017

Completely off-topic, but I believe we should take a look at clarifying a few minor points still unresolved in IRTP-C where they directly relate to the provision of PP services. On the top of the list is obviously the question whether the activation or de-activation of the service should trigger the owner change process, as this also may influence or affect the ability of a provider to cut off the service when a registrant violates their terms, or in case of a UDRP where there is under current policy an option at the beginning of the UDRP to disable the service and disclose the registrant. This would probably be solved by including a single line of text in our resulting policy: "The act of activating or de-activating proxy or privacy services shall not be considered to constitute a change of registrant in the context of the ICANN transfer policy." -- Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung. Mit freundlichen Grüßen, Volker A. Greimann - Rechtsabteilung - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann(a)key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen. -------------------------------------------- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann(a)key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.

3 2

CANCELLED: PPSAI IRT meeting - Tuesday, September 26
by Caitlin Tubergen Sept. 26, 2017

Sept. 26, 2017

Hello, All, This is a quick note to let you know that due to ICANN Staff offsite departmental meetings next week, our next scheduled IRT meeting on Tuesday, September 26 will be cancelled. Please save the date for our next meeting, which will be Tuesday, October 3 at 14:00 UTC. I will be sending out further materials for your review early next week. I hope everyone has a nice weekend, and I believe I echo everyone’s sentiments in sending best wishes to Amy and her family while she is out on maternity leave – you will be missed, Amy! Best regards, Caitlin -- Caitlin Tubergen Registrar Services and Engagement Senior Manager ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 Office: +1 310 578 8666 Mobile: +1 310 699 5326 Email: caitlin.tubergen(a)icann.org

5 4

Re: [Gdd-gnso-ppsai-impl] Agenda for tomorrow's privacy/proxy IRT call
by Margie Milam Sept. 19, 2017

Sept. 19, 2017

Hi- I am sorry, I won’t be able to attend today’s call. Margie From: <gdd-gnso-ppsai-impl-bounces(a)icann.org> on behalf of Amy Bivins <amy.bivins(a)icann.org> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Date: Monday, September 18, 2017 at 1:26 PM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] Agenda for tomorrow's privacy/proxy IRT call Hi, All, This is a reminder that we will continue to discuss draft v2 of the PP Applicant Guide on tomorrow’s IRT call. I’ll do a quick recap of the input we’ve received so far (including from this past week on the list) and then we will continue discussing the draft accreditation application and the fees proposal. Please come prepared with your comments and feedback—as this is our only topic we will have plenty of time to discuss. We should also have a more detailed list of the proposed evaluation criteria for the accreditation process ready to send to you soon—hopefully by the end of this week. 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(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DwMFAg&…>

3 2

Materials, action items from today's PP IRT meeting
by Amy Bivins Sept. 19, 2017

Sept. 19, 2017

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(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

7 20

Agenda for tomorrow's privacy/proxy IRT call
by Amy Bivins Sept. 18, 2017

Sept. 18, 2017

Hi, All, This is a reminder that we will continue to discuss draft v2 of the PP Applicant Guide on tomorrow's IRT call. I'll do a quick recap of the input we've received so far (including from this past week on the list) and then we will continue discussing the draft accreditation application and the fees proposal. Please come prepared with your comments and feedback-as this is our only topic we will have plenty of time to discuss. We should also have a more detailed list of the proposed evaluation criteria for the accreditation process ready to send to you soon-hopefully by the end of this week. 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(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0