November 2017 - Gdd-gnso-ppsai-impl

Re: [Gdd-gnso-ppsai-impl] Materials, action items from 17 Oct Privacy/Proxy IRT call
by Sara Bockey 01 Dec '17

01 Dec '17

Caitlin, Thanks for the revised docs. A few items at first glance that need to be revised, as I believe they have been discussion/raised before. I will take a closer look and follow up with additional edits, but in the meantime… 1. Edit the definitions of Proxy Service and Privacy Service to match the definitions provided in the Final Report/2013 RAA * The definitions of Privacy Service and Proxy Service reflect those in the 2013 RAA. * In this context, the 2013 RAA also defines “Registered Name” as a domain name within the domain of a gTLD, about which a gTLD Registry Operator (or an Affiliate or subcontractor thereof engaged in providing Registry Services) maintains data in a Registry Database, arranges for such maintenance, or derives revenue from such maintenance, and “Registered Name Holder” is defined as the holder of a Registered Name. * It’s noted that ICANN staff has replace “Registered Name Holder” with “Customer” in many instances, but I question the logic in that since it is inconsistent with the RAA. 1. Edit Sections 3.5.3.3. thru 3.5.3.6 to take into consideration GDPR requirements regarding consent. * Consent must be explicitly given for each purpose and can be withdrawn at any time and not a requirement for registration or use of the service. Therefore, 3.5.3.3. – 3.5.3.6 (at a minimum) are not compatible and must be revise. 1. Edit section 3.12.2, as it still contains new language that has been added since the IRT agreement on language in August. The first sentence in its entirety should be removed. * The section should start with “Well founded…” Additionally, the following sections need revision or at a minimum further discuss by the IRT 1. Edit Section 3.14 to remove the language re no automation. This is not feasible. This language must be removed: * Provider shall not use high-volume, automated electronic processes (for example, processes that do not utilize human review) for sending Requests or responses to Requests to Requesters or Customers in performing any of the steps in the processes outlined in the Intellectual Property Disclosure Framework Specification. 1. Edit Section 3.15 – Labeling – to remove excessive language. * Provider shall ensure that each Registered Name for which Provider is providing the Services is clearly labeled as such in the Registration Data Directory Service, as specified in the Labeling Specification attached hereto, and shall otherwise comply with the requirements of the Labeling Specification attached hereto. This language is duplicative and not necessary. Let’s not add unnecessary words to this already long document. If there are doing to be extra works, perhaps mention complying with applicable local laws in light of GDPR. sara bockey sr. policy manager | GoDaddy™ sbockey(a)godaddy.com 480-366-3616 skype: sbockey This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments. 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: Wednesday, October 25, 2017 at 4:44 AM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] Materials, action items from 17 Oct Privacy/Proxy IRT call Dear Colleagues, Thanks so much for your participation on today’s Privacy/Proxy IRT call. For those who could not attend, I encourage you to review the recording and materials on the wiki, https://community.icann.org/display/IRT/24+October+2017. During the call, we discussed an overview of the changes to the draft PPAA. Please note that ICANN proposed a deadline of Tuesday, 14 November for all comments, concerns, and edits to the draft PPAA. The changes from the last iteration, provided to the IRT in July, have been highlighted in the attached issues list. Please respond to the list if you would like to request a longer review period. During ICANN60, we will be presenting an overview of the P/P program’s status to the community. Attached, please find the slide deck for the presentation. To highlight a few notes from the IRT’s discussion this morning, we received feedback to: 1. Edit the definition of Working Group in Section 1.43, to specify that the Provider Stakeholder Group, if formed, shall only appoint the provider representatives of the Working Group, and the GNSO may appoint other members of the community. 1. Add back in the previously-deleted Code of Conduct language in Section 3.5.1. 1. Add back in the previously-deleted review provision in Section 7 of the Customer Data Accuracy Program Specification. If you believe the above items do not reflect the intent of the Working Group’s recommendations, please reply to the list by 14 November 2017. Thank you, and safe travels to those of you attending ICANN 60! Kind 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

14 39

RrSG comments on the current drafts.
by Theo Geurts 01 Dec '17

01 Dec '17

Dear IRT members. Attached the comments from several RrSG members. Thank you for the comments and support and the valuable discussions: Key-Systems, Volker Greimann Netearth One, Chris Pelling Nordreg, Benny Samuelsen One.com, Rieke Poppe 1und1, Thomas Keller Astutium, Rob Golding Godaddy, Sara Bockey, thank you for assisting me with the reviews. DNS Africa, Vlad Dinculescu Best regards, Theo Geurts

2 1

Materials, action items from 14 Nov IRT Call
by Caitlin Tubergen 16 Nov '17

16 Nov '17

Dear Colleagues, Thanks so much for your participation on Tuesday’s Privacy/Proxy IRT call. For those who could not attend, I encourage you to review the recording and materials on the wiki, https://community.icann.org/display/IRT/14+November+2017. On the call, the group agreed to a deadline for Friday, 1 December for all IRT members to provide feedback on the most recent draft PPAA (from 20 October). Accordingly, please use this time to review the draft and provide feedback via the list. The next IRT meeting will be Tuesday, 5 December at 1500UTC. Please let me know if you have any questions. Thank you! Kind 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

1 0

Re: [Gdd-gnso-ppsai-impl] [Ntfy-gdd-gnso-ppsai-impl] Privacy and Proxy Services Accreditation Program IRT Meeting
by theo geurts 14 Nov '17

14 Nov '17

I won't be able to attend. Thanks, Theo Geurts On 14-11-2017 00:09, ICANN Policy Calendar wrote: > > ICANN Policy Calendar has invited you to Privacy and Proxy Services > Accreditation Program IRT Meeting > > Title: > > > > Privacy and Proxy Services Accreditation Program IRT Meeting > > Location: > > > > 15:00 UTC > > When: > > > > Tue 14 Nov 2017 16:00 – 17:30 > > > > > Organizer: > > > > ICANN Policy Calendar <PolicyCalendar(a)icann.org> > > Description: > > > > ****Due to Daylight Savings time change, we are changing the start > time to 15:00 UTC**** Dear Colleagues, Please find below the remote > participation details for the Privacy and Proxy Services Accreditation > Program IRT Meetings which will now be held WEEKLY on Tuesdays, > starting on 29 November 2016 at 15: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 > > Attachments: > > > > Comment: > > > > Attendees: > > > > > ntfy-gdd-gnso-ppsai-impl(a)icann.org <ntfy-gdd-gnso-ppsai-impl(a)icann.org> > > Amy Bivins <amy.bivins(a)icann.org> > > pp_imp_staff(a)icann.org <pp_imp_staff(a)icann.org> > > Owen Smigelski <owen.smigelski(a)icann.org> > > Graeme Bunton <graemeb(a)gmail.com> > > Russ Weinstein <russ.weinstein(a)icann.org> > > Related Link: > > > > > > _______________________________________________ > Ntfy-gdd-gnso-ppsai-impl mailing list > Ntfy-gdd-gnso-ppsai-impl(a)icann.org > https://mm.icann.org/mailman/listinfo/ntfy-gdd-gnso-ppsai-impl

2 1

Review SPECIFICATION 2: CUSTOMER DATA ACCURACY PROGRAM SPECIFICATION
by theo geurts 14 Nov '17

14 Nov '17

Hi all, A question to the IRT and staff. SPECIFICATION 2: CUSTOMER DATA ACCURACY PROGRAM SPECIFICATION I think I understand most of the requirements here. What am I not sure of, as it is fuzzy, what is a provider supposed to do when Registrant activates a privacy service for a domain name that is*already* registered, has*not *been transferred and has *not* received updates? Currently, I think the language says the provider shall do *nothing* except turning on the privacy service. Do we agree this is how it should work? Thanks, Theo Geurts Below the current language in the agreement. Except as provided for in Section 3 below, within fifteen (15) days of (i) the registration of a Registered Name for which Provider is providing the Services, (ii) the transfer of the sponsorship of a Registered Name for which Provider is providing the Services, or (iii) any change in the Customer information associated with a Registered Name for which Provider is providing the Services, Provider will, with respect to the Customer account holder contact information related to such Registered Name:

3 2

Materials, action items from 17 Oct Privacy/Proxy IRT call
by Caitlin Tubergen 06 Nov '17

06 Nov '17

Dear Colleagues, Thanks so much for your participation on today’s Privacy/Proxy IRT call. For those who could not attend, I encourage you to review the recording and materials on the wiki, https://community.icann.org/display/IRT/24+October+2017. During the call, we discussed an overview of the changes to the draft PPAA. Please note that ICANN proposed a deadline of Tuesday, 14 November for all comments, concerns, and edits to the draft PPAA. The changes from the last iteration, provided to the IRT in July, have been highlighted in the attached issues list. Please respond to the list if you would like to request a longer review period. During ICANN60, we will be presenting an overview of the P/P program’s status to the community. Attached, please find the slide deck for the presentation. To highlight a few notes from the IRT’s discussion this morning, we received feedback to: Edit the definition of Working Group in Section 1.43, to specify that the Provider Stakeholder Group, if formed, shall only appoint the provider representatives of the Working Group, and the GNSO may appoint other members of the community. Add back in the previously-deleted Code of Conduct language in Section 3.5.1. Add back in the previously-deleted review provision in Section 7 of the Customer Data Accuracy Program Specification. If you believe the above items do not reflect the intent of the Working Group’s recommendations, please reply to the list by 14 November 2017. Thank you, and safe travels to those of you attending ICANN 60! Kind 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

7 7