November 2018 - RDS-WHOIS2-RT

Fwd: edpb_guidelines_3_2018_territorial_scope_en.pdf
by Carlton Samuels Nov. 27, 2018

Nov. 27, 2018

Attached, the European Data Protection Board (formerly Article 29 Working Party) has issued guidelines addressing extraterritoriality of the GDPR. Grist for the mill .....and very useful as we ponder the responsibilities of the data controller in the ICANN context. The language is accessible and does'nt require rocket science knowledge or a law firm to tell us what makes sense! -Carlton

2 2

Plenary Call #42 | 26 November 2018 | 15:00 - 16:30 UTC
by Jean-Baptiste Deroulez Nov. 26, 2018

Nov. 26, 2018

Dear review team members, In preparation for your plenary call, scheduled for Monday, 26 November at 15:00-16:30 UTC, please find below the proposed meeting agenda: 1. Welcome, roll-call, SoI 2. Face-to-Face Meeting #4 3. Draft Report: Review of Public Comments Received * Domain Name Rights Coalition * Registrar Stakeholder Group (RrSG) * Non-Commercial Stakeholders Group (NCSG) 1. A.O.B. Please find the draft face-to-face meeting #4 agenda, the three public comments and the plenary call slides. As always, let us know if you have any questions or concerns. Kind regards, Jean-Baptiste

2 2

Call still on?
by Carlton Samuels Nov. 19, 2018

Nov. 19, 2018

Hi Jean -Baptiste: Is the call still on? CAS ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* =============================

4 4

Plenary Call #41 | 15:00 UTC | November 2018
by Jean-Baptiste Deroulez Nov. 19, 2018

Nov. 19, 2018

Dear review team members, In preparation for your plenary call, scheduled for Monday, 19 November at 15:00-16:30 UTC, please find below the proposed meeting agenda: 1. Welcome, roll-call, SoI 2. ICANN63 3. Draft Report * Status of public comments received * Public Comment Summary 1. Open discussion on any new issues that need to be considered in the final report 2. Potential need for a call with Contractual Compliance 3. A.O.B. As always, let us know if you have any questions or concerns. Kind regards, Jean-Baptiste

2 2

Technical Writer
by Jean-Baptiste Deroulez Nov. 14, 2018

Nov. 14, 2018

Dear review team members, We would like to confirm the appointment of Jackie Treiber as technical writer to help support the work of the review team in finalizing its report before it is submitted to the ICANN Board. Jackie Treiber is a writer, editor and artist with three years of experience in Internet Governance. In her role as the co-executive director of ICANNWiki, she focused on building grassroots translations of Internet Governance content in Swahili, Spanish, Chinese and Portuguese. She is based in Spokane, Washington. You will have an opportunity to meet Jackie in person at the face-to-face meeting #4 in Brussels on 10-12 December 2018. She will also be attending upcoming plenary and leadership calls. We look forward to our collaboration and are happy to welcome her aboard. Kind regards, Jean-Baptiste

4 3

Comments Returned from the EC on the NTIA's RFC on their approach to consumer privacy
by Carlton Samuels Nov. 14, 2018

Nov. 14, 2018

...they feel the key aspects of a modern privacy regime and the concepts are all there but offered some ideas on, among other things, data protection principles, individual rights, breach notification, enforcement and other issues. https://politi.co/2qINOaJ -Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* =============================

1 0

Re: [RDS-WHOIS2-RT] Meeting time
by Jean-Baptiste Deroulez Nov. 11, 2018

Nov. 11, 2018

Dear Lili, There is no plenary call scheduled for today, next one is scheduled for Monday 12 November 2018. Kind regards, Jean-Baptiste On 11/5/18, 7:34 AM, "RDS-WHOIS2-RT on behalf of SUN Lili" <rds-whois2-rt-bounces(a)icann.org on behalf of L.SUN(a)interpol.int> wrote: Hello all, I'll be struggling to attend the plenary calls at 12am, but I'm in Lyon France this week, so I can make it for today's plenary call. Thanks, Lili -----Original Message----- From: RDS-WHOIS2-RT [mailto:rds-whois2-rt-bounces@icann.org] On Behalf Of Alan Greenberg Sent: Friday, 2 November, 2018 5:16 AM To: RDS-WHOIS2-RT <rds-whois2-rt(a)icann.org> Subject: [RDS-WHOIS2-RT] Meeting time We have been holding our plenary calls at 15:00 UTC. For many of us that is (or very soon will be) one hour earlier in local time. Does this time still work for us, or does it need to be adjusted. I think that Volker in particular might be affected, but Lili might be adversely affected by making it an hour later. Alan _______________________________________________ RDS-WHOIS2-RT mailing list RDS-WHOIS2-RT(a)icann.org https://mm.icann.org/mailman/listinfo/rds-whois2-rt _______________________________________________ RDS-WHOIS2-RT mailing list RDS-WHOIS2-RT(a)icann.org https://mm.icann.org/mailman/listinfo/rds-whois2-rt

4 4

Perhaps of interest: Blog on DNS infrastructure abuse published
by Alan Greenberg Nov. 8, 2018

Nov. 8, 2018

https://www.icann.org/news/blog/contractual-compliance-addressing-domain-na… Contractual Compliance: Addressing Domain Name System (DNS) Infrastructure Abuse A previous blog, Six weeks in Contractual Compliance and Consumer Safeguards<https://www.icann.org/news/blog/six-weeks-in-contractual-compliance-and-con…>, briefed the ICANN community on three Contractual Compliance department initiatives. Todayâ€™s blog is an update on two of those initiatives: increasing transparency around compliance activities and Domain Name System (DNS) infrastructure abuse. Many of you may have seen some of the recent improvements in transparency. The Contractual Compliance Monthly Dashboard<https://features.icann.org/compliance/dashboard/report-list> now includes more information regarding registrar-related DNS abuse report handling complaints, including reports regarding spam, pharming, phishing, malware, and botnets. It also includes information on counterfeiting, online pharmaceutical concerns, fraudulent and deceptive practices, trademark or copyright infringement, and complaints regarding registrar abuse contacts. The second initiative, addressing DNS infrastructure abuse, takes place at a time when large sections of the community have raised concerns about the prevalence of this abuse, and questioned the willingness and ability of the ICANN organization and contracted parties to address it. For example, the Competition, Consumer Choice and Consumer Trust Review Teamâ€™s final report<https://www.icann.org/public-comments/cct-final-recs-2018-10-08-en> includes a lengthy chapter on DNSi nfrastructure abuse and includes several related recommendations. The Governmental Advisory Committee (GAC) has also raised concerns about DNS infrastructure abuse in the Copenhagen CommuniquÃ©<https://www.icann.org/en/system/files/correspondence/gac-to-icann-15mar17-e…>, and elsewhere. In Contractual Compliance, we are conducting audits that are specifically focused on the topic of DNS infrastructure abuse. We have broadened the scope of questions and testing in our registrar and registry audits, focusing on process, procedures, and handling of DNS infrastructure abuse. The revised audit testing focuses on reviewing security threat reports for completeness and comparing them against publicly available reports. ICANN previously included the expanded audit questions in the March 2018 Registry Audit<https://www.icann.org/en/system/files/files/contractual-compliance-ra-audit…> conducted on 20 generic top-level domains (gTLDs). Through this audit, we identified actions that registries and registrars are taking to address DNS infrastructure abuse. They include conducting security threat analyses frequently and retaining reports for future reference. These reports identified abusive domains that were also identified in publicly available abuse reports (e.g., MalwarePatrol, PhishTank, Spamhaus and SURBL), and included evidence of actions taken against abusive domains. The audit also showed that there were incomplete analyses and security reports for 13 top-level domains (TLDs), as well as a lack of standardized or documented abuse handling procedures and no action being taken on identified threats. These 13 new gTLDs will be retested in the next round. This week, ICANN launched an audit focused on DNS infrastructure abuse for nearly 1200 gTLDs<https://www.icann.org/en/system/files/files/compliance-registry-audit-01nov…>, and held two audit webinars<https://www.icann.org/en/system/files/files/contractual-compliance-audit-we…> with the registries to address questions and concerns. Some of these concerns were also raised in a recent email<https://www.icann.org/en/system/files/correspondence/austin-to-serad-hedlun…> from the Registries Stakeholder Group (RySG) and addressed<https://www.icann.org/en/system/files/correspondence/hedlund-to-austin-08no…> by Contractual Compliance. For the first time, and to help prepare for the upcoming audit, we sent the auditees the complete list of gTLDs that are included in the audit, and a pro-forma list of questions and data requests<https://www.icann.org/en/system/files/files/contractual-compliance-proforma…> that will be included in the November 2018 Registry Audit round. In another first, ICANN is making this information publicly available on ICANN.org<https://www.icann.org/resources/pages/audits-2012-02-25-en> in an effort to increase transparency. ICANNâ€™s mission is to maintain the security and stability of the DNS. Consistent with our mission, ICANN Contractual Compliance is now addressing DNS infrastructure abuse by conducting registry and registrar audits. The purpose of these audits is to ensure that the contracted parties uphold their contractual obligations with respect to DNS infrastructure abuse and security threats. Upon completion of the audits, ICANN Contractual Compliance will publish our findings and observations, including examples of strategies and processes to mitigate DNS infrastructure abuse. If you have any audit-related questions, please contact ICANN Contractual Compliance at complianceaudit(a)icann.org<mailto:complianceaudit@icann.org> . Jamie Hedlund Senior Vice President, Contractual Compliance and Consumer Safeguards Managing Director, Washington, DC Office Internet Corporation for Assigned Names and Numbers (ICANN) Telephone: +1 202 570 7125 Mobile: +1 202 374 3969 Skype: jamiehedlund www.icann.org<http://www.icann.org>

2 1

Update on timing and final report
by Alan Greenberg Nov. 5, 2018

Nov. 5, 2018

As you may know, Lisa Phifer will not be able to work with us to complete the report, and MSSI is looking at options for an editor. It will not be anyone with knowledge of the subject. The draft report was too long and not cohesive, so I think it needs a careful overall review and revision. Since the editor will not have a feel for the intent of the analysis and recommendations, it will fall on us to do a fair amount of the work. Given my lessened responsibilities with regard to At-Large, I am willing to do at least part of this. We will need to adjust the timeline, both for the rework and to have team members sign off. We meet 10-12 December which leaves just one week before the holiday season. That will not be enough time to complete the substantive edits and to clean up the overall report. So we will definitely go into January. My target is to issue the report no later than the end of the month. If there is a 50 day public comment once submitted to the Board (which is what was done for the CCT Review), that puts the comment ending about a week after the end of the Kobe meeting. With the support of Cathrin and Susan, I have suggested that we plan for: - An engagement session with the community; and - An opportunity for the RT leadership (and other team members if appropriate) to meeting with Board and/or ICANN Org to clarify or elaborate on any aspect of the report. Although it is not yet certain, we may have limited funding to support a small number of people travelling to Kobe. If you can attend the meeting and have no other source of funding, please let me know ASAP. Anyone funded should be able to speak on a significant number of the areas we are addressing in the report and making it clear that in the absence of our funding you are unlikely to attend. Please reply no later that Sunday, 4th November as travel lists need to be submitted two days later. Presuming more interest than we have funding, the selection will be done by the RT leadership. Alan

2 2

Meeting time
by Alan Greenberg Nov. 5, 2018

Nov. 5, 2018

We have been holding our plenary calls at 15:00 UTC. For many of us that is (or very soon will be) one hour earlier in local time. Does this time still work for us, or does it need to be adjusted. I think that Volker in particular might be affected, but Lili might be adversely affected by making it an hour later. Alan

5 4