February 2018 - Bc-gnso - lists.icann.org

Joint IPC/BC response to ICANN on a convergence model for GDPR and Whois
by Steve DelBianco Feb. 27, 2018

Feb. 27, 2018

Last Friday I circulated a proposed BC & IPC joint letter to ICANN regarding its anticipated draft interim model to achieve GDPR compliance for Whois. No BC members registered any objections or edits as of 17UTC Monday, so we agreed to the joint letter. Then late on Monday, IPC members added a section regarding self-certification/accreditation. The IPC wanted to submit the letter at 17 UTC today, and I felt there was not sufficient time to allow BC members to review that specific section. Therefore, that section is attributed only to the IPC, as noted below. Otherwise, the attached document is joint input of both the IPC and BC. That said, the section on self-certification (plus) has much merit and should be reviewed by BC members this week. See pages 5-6 in the attached letter --Steve From: Brian Winterfeldt Sent: Tuesday, February 27, 2018 12:01 PM To: 'goran.marby(a)icann.org' <goran.marby(a)icann.org<mailto:goran.marby@icann.org>>; 'akram.atallah(a)icann.org' <akram.atallah(a)icann.org<mailto:akram.atallah@icann.org>>; 'john.jeffrey(a)icann.org' <john.jeffrey(a)icann.org<mailto:john.jeffrey@icann.org>> Subject: RE: [Ext] Update re IPC/BC Representative Discussions with Contracted Party Representatives and Forthcoming Input to ICANN Dear Göran, Akram, and John, Attached please find a joint IPC/BC document that provides input on key issues and concerns with the proposed ICANN interim compliance model based on our prior discussions of this model. To briefly summarize, this document highlights the following model elements / issues where we believe the IPC and BC views diverge from what is currently presented (or omitted) in the ICANN model: 1. Territorial scope 2. Scope of application to natural vs. legal persons 3. Non-publication of Registrant email address 4. Self-certification/accreditation issues 5. Data accuracy 6. Bulk / aggregated data access Each section provides our specific comments as well as citations and links to prior input which we believe ICANN should note in connection with our stated views. As you will recall, we had offered to provide this kind of input when we spoke on Friday February 16, 2018. We note that the IPC and BC membership raised no objections to the content of the document. However, we note that the section on self-certification/accreditation was added pursuant to IPC members’ suggestions, and there was not sufficient time to obtain formal BC endorsement of that specific section after re-circulating the updated draft last night. Therefore, that section specifically should be attributed only to the IPC. Otherwise, the document should be considered joint input of both the IPC and BC. As previously mentioned, we understand that ICANN anticipates formally publishing its draft interim compliance model shortly. We hope ICANN will review and consider the attached input prior to publication. Of course, this document should serve as input in further refining the model in any case, and we will anticipate providing any further input once the draft model is formally published. Best regards, Brian ________________________________ <https://www.winterfeldt.law/>[https://daks2k3a4ib2z.cloudfront.net/59358b8cf7332631232417e8/595fb59d73c5b…]<https://www.winterfeldt.law/><https://www.winterfeldt.law/> Brian J. Winterfeldt Principal Winterfeldt IP Group 1200 17<x-apple-data-detectors://12/1>th<x-apple-data-detectors://12/1> St NW<x-apple-data-detectors://12/1>, Ste 501<x-apple-data-detectors://12/1> Washington, DC 20036<x-apple-data-detectors://12/1> brian(a)winterfeldt.law<mailto:brian@winterfeldt.law> +1 202 903 4422 On Feb 23, 2018, at 14:15, Brian Winterfeldt <Brian(a)Winterfeldt.law<mailto:Brian@Winterfeldt.law>> wrote: Dear Göran, Akram, and John: As you all know, certain members of the IPC and the BC met with certain members of the Contracted Parties House on Wednesday, February 21, 2018, to discuss the ongoing development of an interim GDPR compliance model. I wanted to let you know that the participants in that meeting are working together to prepare a written “communiqué” that summarizes some of the key takeaways from that discussion, which we hope to share with ICANN by close of business on Monday February 26, 2018. Separately, the IPC and BC are preparing a joint letter to ICANN, which will include some initial input regarding the ICANN proposed interim model, which we have been discussing in our constituencies since our call with you last Friday February 16, and of course was a key focus of our IPC/BC webinar on Thursday February 22 (thanks again to Akram and John for participating in that discussion). We also hope to share this document with ICANN by close of business on Monday. Our hope is that these documents will be received and considered prior to publication of the ICANN proposed interim compliance model, which we understand is expected sometime early next week. Of course, we expect to provide additional input following publication of the proposed model, but wanted you to consider the specific materials mentioned above before ICANN publishes the model, if at all possible. We understand that the timeline for input is short, and we appreciate your efforts to allow us this brief window to provide some important pre-publication feedback based on what we know so far about the proposed model and the community discussions we have held in response, at your request. Best regards, Brian ________________________________ <image003.png>[winterfeldt.law]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.winterfeldt.law_&d…> Brian J. Winterfeldt Principal Winterfeldt IP Group 1200 17<x-apple-data-detectors://12/1>th<x-apple-data-detectors://12/1> St NW<x-apple-data-detectors://12/1>, Ste 501<x-apple-data-detectors://12/1> Washington, DC 20036<x-apple-data-detectors://12/1> brian(a)winterfeldt.law<mailto:brian@winterfeldt.law> +1 202 903 4422

1 0

Pre-ICANN61 Policy Report and GNSO Policy Briefing
by Chantelle Doerksen Feb. 26, 2018

Feb. 26, 2018

[cid:image001.png@01D3AF26.9C48C870] --Pre-ICANN61 Policy report: http://go.icann.org/pre61 --GNSO Policy Briefing for ICANN61 is now available: http://go.icann.org/gnsobriefing

1 0

Register Now: Pre-ICANN61 Policy Open House – 1 March 2018 - ICANN
by Chantelle Doerksen Feb. 8, 2018

Feb. 8, 2018

https://www.icann.org/news/announcement-2-2018-02-08-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Register Now: Pre-ICANN61 Policy Open House – 1 March 2018 The Policy Development Support Team is pleased to announce two sessions for an upcoming webinar: Pre-ICANN61 Policy Open House Thursday, 1 March 2018 10:00 and 19:00 Coordinated Universal Time (UTC) The webinar will run in English and will be conducted in Adobe Connect along with a dial-in conference bridge for audio. Recordings of the sessions will be made available here[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. Please register via this form[goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_vZw8kM&d=DwMGaQ…> by 26 February 2018! In this interactive 60-minute open house, the focus will be an active question and answer session with the Policy Development Support Team. To ensure that your questions about policy activities are addressed during the session, the Policy Team invites you to submit your questions through the registration form[goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_forms_dVbmhQOT8…> or email them to policyinfo(a)icann.org<mailto:policyinfo@icann.org>. To assist with your preparation for this webinar and for ICANN61, the "Pre-ICANN61 Policy Report" and "Generic Names Supporting Organization Policy Briefing: ICANN61 Edition" will be published by Monday, 26 February 2018. Please be sure to download and review these materials beforehand for helpful background on policy activities and topics that the Policy Development Support Team will discuss during the open house, such as: * An overview of the cross-community discussions that will take place at ICANN61: * General Data Protection Regulation (GDPR): WHOIS Compliance Models * A Walk in the Shoes of a New Generic Top-Level Domain (gTLD) Registry Operator * Name Collisions * Open Data at ICANN * Policy development processes underway in the Country Code Names Supporting Organization (ccNSO), the Generic Names Supporting Organization (GNSO) and the Address Supporting Organization (ASO): * Retirement of Country Code Top-Level Domains (ccTLDs) * Review of All Rights Protection Mechanisms in All gTLDs * Next-Generation Registration Directory Service to Replace WHOIS * International Governmental Organizations and International Non-Governmental Organizations Access to Curative Rights Dispute Resolution Mechanisms * Protections for Red Cross National Society Names in the Domain Name System * New gTLD Subsequent Procedures * Regional Internet Registry policy development activities * Advisory Committee activities within the At Large Advisory Committee (ALAC), Governmental Advisory Committee (GAC), Root Server System Advisory Committee (RSSAC) and Security & Stability Advisory Committee (SSAC): * Organizational Review of the At-Large community * At-Large Summit (ATLAS) III * GAC discussion on the .amazon Independent Review Process * GAC discussion on evolving relationships with ICANN Board and ICANN Org * RSSAC statement on entries in DNS Root Sources * RSSAC & SSAC Response to the GNSO's New gTLD Subsequent Procedures Working Group on Root Scaling * SSAC Response to the ICANN Internationalized Domain Name Guidelines Working Group * SSAC work concerning the use of emoji in domain names * Other topics of note: * Organizational Review of the ASO * ccNSO Rejection Action Procedure as a Decisional Participant in the ICANN Empowered Community * Impact of ICANN's Implementation of the General Data Protection Regulation (GDPR) on ccTLDs The Policy Development Support Team looks forward to helping the ICANN community prepare for ICANN61! Please register via this form[goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_vZw8kM&d=DwMGaQ…> by 26 February 2018! 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

Business Constituency (BC) comment on ICANN proposed Operating Standards for Specific Reviews
by Steve DelBianco Feb. 2, 2018

Feb. 2, 2018

The ICANN Business Constituency (BC) submits the attached comment on ICANN’s proposed Operating Standards for Specific Reviews ( ICANN comment page at https://www.icann.org/public-comments/reviews-standards-2017-10-17-en ) This comment was drafted by Faisal Shah, Steve DelBianco, Susan Kawaguchi, Marilyn Cade, and Lawrence OlaWale-Roberts. It was approved in accord with the BC Charter. — Steve DelBianco Vice chair for policy coordination ICANN Business Constituency

1 0

Business Constituency (BC) comment on Proposed Changes to the ICANN Meetings Strategy
by Steve DelBianco Feb. 2, 2018

Feb. 2, 2018

The ICANN Business Constituency (BC) submits the attached comment on Proposed Changes to the ICANN Meetings Strategy. ( ICANN comment page at https://www.icann.org/public-comments/proposed-changes-meetings-strategy-20… ) This comment was drafted by Marilyn Cade, Arinola Akinyemi, Michelle Chaplow, Christian Bope, and Tola Sogbesan, and edited by Steve DelBianco. It was approved in accord with the BC Charter. — Steve DelBianco Vice chair for policy coordination ICANN Business Constituency

2 1