- RDS-WHOIS2-RT - lists.icann.org

Materials - Your Brussels Meeting
by Alice Jansen July 24, 2018

July 24, 2018

Dear Review Team Members, In preparation for your meeting this week, we invite you to review: * The updated subgroup report gap assessment * The updated recommendation assessment These two tables will provide you with an overview of gaps that still need to be addressed in Brussels. In addition, please make sure to scan through the draft report circulated by Lisa yesterday – see https://mm.icann.org/pipermail/rds-whois2-rt/2018-July/000777.html (also attached for your convenience) that includes all subgroup reports. Please note: per the agenda, the review team will be asked to approve the draft report’s background section on day1 (pages 9-11). As a result, please make sure to read the text prior to the session. The full reading list for the meeting can be found on the wiki at https://community.icann.org/display/WHO/Face+to+Face+Meeting+%233+-+26-27+J… We look forward to seeing you soon. The meeting agenda is attached to this email. Please let us know if you have any questions. Safe travels! Kind regards Alice

1 0

Consolidated Draft RT report - July 23
by Lisa Phifer July 24, 2018

July 24, 2018

Dear all, Attached please find a draft of the consolidated RT report, as of 23 July. Please review this in preparation for this week's F2F meeting. The latest subgroup drafts submitted as of this writing are included in the consolidated report. Comments note where rapporteurs still have open action items to provide updated subgroup drafts. However, due to travel, it will not be possible to merge any further updates into this consolidated report between now and the F2F meeting. In this draft, you will also note some redlined text. These redlines indicate text that was inserted during consolidation, either for consistency or to pull in conclusions from ICANN62 slides as the basis for F2F discussion. Minor copy edits for formatting or spelling are not redlined. Finally, most remaining gaps are indicated by yellow highlighted text. Both PDF and Word files are attached for your convenience. Best regards Lisa

1 0

Compliance subgroup draft report
by Susan Kawaguchi July 23, 2018

July 23, 2018

Hello All, After a meeting by the subgroup on Friday I have made revisions to the subgroup report for discussion during our call on Monday. - Rec#1 - revise to read "enforced as required" to address Stephanie's comment on F2F#2 - Rec#4 - incorporate into Outreach report existing recommendation 3.2 as a specific example of desired outreach, and refer to the Outreach recommendation from Section 3.2.1.2 in Compliance report - Rec #5 - expand recommendation text to focus on compliance processes to encourage use of Bulk tool, - Rec #8 - refer to Bulk WHOIS tool when discussing possible sources of input to identify systemic abuse - Rec#7 - discuss clarified text for this Recommendation in plenary - To address Accuracy issue where accuracy of P/P registration data is not monitored and cannot be enforced, draft a new recommendation that P/P registration data providers must adhere to the current RAA requirements for verification and validation. - Raise as comments on Rec #11 subgroup report (Common Interface) for discussion in plenary call: (1) As a result of GDPR implementation, RR and Ry interpretations may result in different registration data returned by WHOIS for the same domain name (e.g., the Ry may redact data that the RR displays) (2) Bulk data access has become less reliable (e.g., timeouts more frequent) I also started a draft recommendation on accuracy in PP registrations *Privacy and Proxy registration data providers must adhere to the current RAA requirements for verification and validation of the underlying registrant data. * The following is from the PPSAI final report, I thought it may help in the discussion. P/P service providers should be required to inform the P/P service customer annually of his/her requirement to provide accurate and up to date contact information to the P/P service provider. If the P/P service provider has any information suggesting that the P/P service customer information is incorrect (such as the provider receiving a bounced email notification or non-delivery notification message in connection with compliance with data reminder notices or otherwise) for any P/P service customer, the provider must verify or re-verify, as applicable, the email address(es). If, within fifteen (15) calendar days after receiving any such information, the P/P service provider does not receive an affirmative response from the P/P service customer providing the required verification, the P/P service provider shall verify the applicable contact information manually. Susan

2 1

Plenary call #35 | Monday 23 July 2018 | 15:00 – 16:30 UTC
by Jean-Baptiste Deroulez July 23, 2018

July 23, 2018

Dear review team members, In preparation for your plenary call #35<https://community.icann.org/x/jYRHBQ> scheduled for Monday 23 July 2018 | 15:00 – 16:30 UTC, please find below the approved meeting agenda: * Welcome, roll-call, SoI * Subgroups Status Update * Rec. #2: Single WHOIS Policy * Rec. #15-16: Plan & Annual Reports * Subgroup 5: Safeguarding registrant data. * Plenary Call Schedule * A.O.B. * Confirm Decisions Reached and Action Items You should all have received dial-in details to join this call. If not, please contact us (off list) at rds-whois2-staff(a)icann.org<mailto:rds-whois2-staff@icann.org>. We would also like to kindly remind you that Sunday 22 July 23:59 UTC is the deadline to submit your updates to subgroup reports. As always, let us know if you have any questions or concerns. Kind regards, Jean-Baptiste

6 5

SLIDES - Plenary call #35 | Monday 23 July 2018 | 15:00 – 16:30 UTC
by Alice Jansen July 23, 2018

July 23, 2018

Dear review team members, Please find attached meeting slides in preparation for your call #35. The agenda is available below. Thanks, Kind regards Alice From: RDS-WHOIS2-RT <rds-whois2-rt-bounces(a)icann.org> on behalf of Jean-Baptiste Deroulez <jean-baptiste.deroulez(a)icann.org> Date: Friday 20 July 2018 at 14:56 To: Cathrin Bauer via RDS-WHOIS2-RT <rds-whois2-rt(a)icann.org> Subject: [RDS-WHOIS2-RT] Plenary call #35 | Monday 23 July 2018 | 15:00 – 16:30 UTC Dear review team members, In preparation for your plenary call #35 [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> scheduled for Monday 23 July 2018 | 15:00 – 16:30 UTC, please find below the approved meeting agenda: * Welcome, roll-call, SoI * Subgroups Status Update * Rec. #2: Single WHOIS Policy * Rec. #15-16: Plan & Annual Reports * Subgroup 5: Safeguarding registrant data. * Plenary Call Schedule * A.O.B. * Confirm Decisions Reached and Action Items You should all have received dial-in details to join this call. If not, please contact us (off list) at rds-whois2-staff(a)icann.org<mailto:rds-whois2-staff@icann.org>. We would also like to kindly remind you that Sunday 22 July 23:59 UTC is the deadline to submit your updates to subgroup reports. As always, let us know if you have any questions or concerns. Kind regards, Jean-Baptiste

1 0

DAAR Methodology
by Alan Greenberg July 23, 2018

July 23, 2018

Please note https://www.icann.org/news/announcement-2018-07-20-en. There was a comment during the ICANN62 engagement session on this. Alan

1 0

Fwd: [Accred-Model] Accreditation and Access Model for Non-Public WHOIS Data
by PolicyCalendar＠icann.org July 20, 2018

July 20, 2018

Dear all, FYI, perhaps interested members of the RDS RT could join together from the ICANN office? Best regards Cathrin Begin forwarded message: From: "ICANN Policy Calendar" <PolicyCalendar(a)icann.org<mailto:PolicyCalendar@icann.org>> To: "accred-model(a)icann.org<mailto:accred-model@icann.org>" <accred-model(a)icann.org<mailto:accred-model@icann.org>>, "Ozan Sahin" <ozan.sahin(a)icann.org<mailto:ozan.sahin@icann.org>> Subject: [Accred-Model] Accreditation and Access Model for Non-Public WHOIS Data Meeting: Accreditation and Access Model for Non-Public WHOIS Data Call Date/time: Thursday, 26 July 2018 at 16:00 UTC for 90 minutes 09:00 PDT, 12:00 EDT, 18:00 Paris CEST, 21:00 Karachi PKT, (Friday) 01:00 Tokyo JST, (Friday) 02:00 Melbourne AEST For other times: https://tinyurl.com/ybrtnvo2 Link to join Adobe Connect Room: https://participate.icann.org/gnso-welcome Please allow yourself additional time before start of the meeting to log into Adobe Connect. If you’re having trouble joining, please check your plug ins: http://tinyurl.com/icannactest For the best audio quality, we recommend you join the audio bridge as well. Please see Dial in Numbers and Participant Passcode below. If you require a dial-out (do not send to full email group) please send an email request with your preferred contact number to ozan.sahin(a)icann.org<mailto:ozan.sahin@icann.org><mailto:ozan.sahin@icann.org> Please let me know if you have any questions. Thank you. Kind regards, Ozan Sahin ______________________________________________________________________ Participant passcode: ACCREDITATION Dial in numbers: Country Toll Numbers Freephone/ Toll Free Number ARGENTINA 0800-777-0519 AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 AUSTRIA 43-1-92-81-113 0800-005-259 BELGIUM 32-2-400-9861 0800-3-8795 BRAZIL SAO PAULO: 55-11-3958-0779 0800-7610651 CHILE 1230-020-2863 CHINA CHINA A: 86-400-810-4789 10800-712-1670 CHINA CHINA B: 86-400-810-4789 10800-120-1670 COLOMBIA 01800-9-156474 CROATIA 080-08-06-309 CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 DENMARK 45-7014-0284 8088-8324 EGYPT 0800000-9029 ESTONIA 800-011-1093 FINLAND 358-9-5424-7162 0-800-9-14610 FRANCE LYON: 33-4-26-69-12-85 080-511-1496 FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 GERMANY 49-69-2222-20362 0800-664-4247 GREECE 30-80-1-100-0687 00800-12-7312 HONG KONG 852-3001-3863 800-962-856 HUNGARY 36-1-700-8856 06-800-12755 INDIA INDIA A: 000-800-852-1268 INDIA INDIA B: 000-800-001-6305 INDIA INDIA C: 1800-300-00491 INDONESIA 001-803-011-3982 IRELAND 353-1-246-7646 1800-992-368 ISRAEL 1-80-9216162 ITALY MILAN: 39-02-3600-6007 800-986-383 ITALY ROME: 39-06-8751-6018 800-986-383 ITALY TORINO: 39-011-510-0118 800-986-383 JAPAN OSAKA: 81-6-7878-2631 0066-33-132439 JAPAN TOKYO: 81-3-6868-2631 0066-33-132439 LATVIA 8000-3185 LUXEMBOURG 352-27-000-1364 8002-9246 MALAYSIA 1-800-81-3065 MEXICO GUADALAJARA (JAL): 52-33-3208-7310 001-866-376-9696 MEXICO MEXICO CITY: 52-55-5062-9110 001-866-376-9696 MEXICO MONTERREY: 52-81-2482-0610 001-866-376-9696 NETHERLANDS 31-20-718-8588 0800-023-4378 NEW ZEALAND 64-9-970-4771 0800-447-722 NORWAY 47-21-590-062 800-15157 PANAMA 011-001-800-5072065 PERU 0800-53713 PHILIPPINES 63-2-858-3716 1800-111-42453 POLAND 00-800-1212572 PORTUGAL 351-2-10054705 8008-14052 ROMANIA 40-31-630-01-79 RUSSIA 8-10-8002-0144011 SAUDI ARABIA 800-8-110087 SINGAPORE 65-6883-9230 800-120-4663 SLOVAK REPUBLIC 421-2-322-422-25 0800-002066 SOUTH AFRICA 080-09-80414 SOUTH KOREA 82-2-6744-1083 00798-14800-7352 SPAIN 34-91-414-25-33 800-300-053 SWEDEN 46-8-566-19-348 0200-884-622 SWITZERLAND 41-44-580-6398 0800-120-032 TAIWAN 886-2-2795-7379 00801-137-797 THAILAND 001-800-1206-66056 TURKEY 00-800-151-0516 UNITED ARAB EMIRATES 8000-35702370 UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 URUGUAY 000-413-598-3421 USA 1-517-345-9004 866-692-5726 VENEZUELA 0800-1-00-3702 VIETNAM 120-11751

1 0

Fwd: ICANN Request to Preserve WHOIS Data Referred to German Appeal Court
by Carlton Samuels July 20, 2018

July 20, 2018

The beat goes on..... -Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* ============================= [image: ICANN] <http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2-2018-07-19-en ------------------------------ ICANN Request to Preserve WHOIS Data Referred to German Appeal Court 19 July 2019 LOS ANGELES – 19 July 2018 – The Internet Corporation for Assigned Names and Numbers (ICANN) was informed yesterday that the Regional Court in Bonn, Germany, has decided to refer to the Higher Regional Court in Cologne, Germany, the injunction proceedings ICANN initiated against EPAG, a Germany-based, ICANN-accredited registrar that is part of the Tucows Group. ICANN filed the injunction proceedings seeking assistance in interpreting the European Union's General Data Protection Regulation (GDPR) in order to protect the data collected in WHOIS. In its initial ruling, the Regional Court determined that it would not issue an injunction against EPAG. ICANN appealed this decision. Upon receipt of the appeal, the Regional Court exercised its option to re-evaluate its decision instead of immediately forwarding the matter to the Higher Regional Court to address the appeal. In referring the matter to the Higher Regional Court in Cologne, the Regional Court did not change its original determination not to issue an injunction against EPAG. The Regional Court also rejected the alternative claims submitted by EPAG in recent court filings. Notably, the Regional Court issued this second ruling without consideration of the additional court filings submitted earlier this week by ICANN and ICANN's Intellectual Property Constituency. Those filings will be part of the record to be transferred to the Higher Regional Court for the appeal. ICANN will continue to pursue this matter as part of its public interest role in coordinating a decentralized global WHOIS for the generic top-level domain system. ICANN awaits further direction from the Higher Regional Court on next steps, which could include referring the matter to the European Court of Justice, issuing a decision based upon the papers already submitted, requesting additional briefings or scheduling a hearing with the parties. Background: On 25 May 2018, ICANN filed the injunction proceedings against EPAG. ICANN asked the Court for assistance in interpreting the GDPR in an effort to protect the data collected in WHOIS. ICANN sought a court ruling to ensure the continued collection of all WHOIS data. The intent was to assure that all such data remains available to parties that demonstrate a legitimate purpose to access it, and to seek clarification that under the GDPR, ICANN may continue to require such collection. ICANN filed the proceedings because EPAG had informed ICANN that as of 25 May 2018, it would no longer collect administrative and technical contact information when it sells new domain name registrations. EPAG believes collection of that particular data would violate the GDPR. ICANN's contract with EPAG requires that information to be collected. EPAG is one of over 2,500 registrars and registries that help ICANN maintain the global information resource of the WHOIS system. ICANN is not seeking to have its contracted parties violate the law. Put simply, EPAG's position spotlights a disagreement with ICANN and others as to how the GDPR should be interpreted. On 30 May 2018, the Regional Court determined that it would not issue an injunction against EPAG. In rejecting the injunctive relief, the Court ruled that it would not require EPAG to collect the administrative and technical data for new registrations. However, the Court did not indicate in its ruling that collecting such data would be a violation of the GDPR. Rather, the Court said that the collection of the domain name registrant data should suffice in order to safeguard against misuse in connection with the domain name (such as criminal activity, infringement, or security problems). The Court reasoned that because it is possible for a registrant to provide the same data elements for the registrant as for the administrative and technical contacts, ICANN did not demonstrate that it is necessary to collect additional data elements for those contacts. The Court also noted that a registrant could consent and provide administrative and technical contact data at its discretion. On 13 June 2018, ICANN appealed the Regional Court's ruling to the Higher Regional Court of Cologne, Germany, and again asked for an injunction that would require EPAG to reinstate the collection of all WHOIS data required under EPAG's Registrar Accreditation Agreement with ICANN. In addition to the court proceedings, ICANN is continuing to pursue ongoing discussions with the European Commission and the European Data Protection Board to gain further clarification of the GDPR as it relates to the integrity of WHOIS services. About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. - - - - - - - - - - - - - - - -

1 0

Face-to-Face Meeting #3 Agenda | 26-27 July 2018
by Jean-Baptiste Deroulez July 20, 2018

July 20, 2018

Dear review team members, Please find attached the approved agenda for the upcoming face-to-face meeting on 26-27 July in Brussels. We would like to remind you that Sunday 22 July 23:59 UTC is the deadline to submit your updates to subgroup reports. Kind regards, Jean-Baptiste

1 0

Additional questions
by Susan Kawaguchi July 20, 2018

July 20, 2018

Hello Jean-Baptiste and Alice, I have several additional questions. Is it possible to send the following questions to the appropriate parties? For GDD If we assume the sample of ARS domain names of 40% grandfathered domain names then we can extrapolate this to 40% of all domain names registered before 2013 MAY not have this registrant data collected, displayed, verified or validated. Can GDD tell us how many domain names total fall into the Grandfathered category? For ICAAN compliance How many reports they have received concerning timeouts on the WHOIS lookup tool on ICANN.org? How many WHOIS inaccuracy reports relate to proxy privacy registrations? Thanks, Susan

2 1