- Bc-gnso - lists.icann.org

BC comment on Proposed Renewal of .COOP Sponsored Registry Agreement
by Steve DelBianco July 28, 2018

July 28, 2018

Attached is the comment of the ICANN Business Constituency (BC) regarding the Proposed Renewal of .COOP Sponsored Registry Agreement. This comment was drafted by Zak Muscovitch. It was approved in accord with the BC Charter. Steve DelBianco Vice Chair for Policy Coordination ICANN Business Constituency

1 0

BC comment on Open Data Initiative Datasets and Metadata
by Steve DelBianco July 28, 2018

July 28, 2018

Attached is the comment of the ICANN Business Constituency (BC) regarding Open Data Initiative Datasets and Metadata. This comment was drafted by Denise Michel, Faisal Shah, Mark Datysgeld, and Mark Svancarek, with edits by Claudia Selli and Tim Chen. It was approved in accord with the BC Charter. Steve DelBianco Vice Chair for Policy Coordination ICANN Business Constituency

1 0

New ICANN blog post on enforcing the Temp Spec
by Steve DelBianco July 16, 2018

July 16, 2018

Please see the 16-Jul blog post from ICANN’s Jamie Hedlund, Sr. VP for Contractual Compliance & Consumer Safeguards (here<https://www.icann.org/news/blog/enforcing-the-temporary-specification> and below) In May, the ICANN Board adopted the Temporary Specification for gTLD Registration Data<https://www.icann.org/resources/pages/gtld-registration-data-specs-en>, modifying our agreements with registries and registrars to comply with the European Union's General Data Protection Regulation (GDPR). Since then, ICANN Contractual Compliance has received a number of questions regarding how we would enforce these new provisions. The purpose of this blog is to describe our approach to enforcing the Temporary Specification, explain how to file complaints about potential violations of the new provisions, and share information on some of the issues we have seen so far. As noted at the Global Domains Division (GDD) Industry Summit in May and at the ICANN62 Policy Forum in June, ICANN Contractual Compliance is enforcing the requirements of the Temporary Specification as of 25 May 2018, as it does any other ICANN agreement or policy requirement. This is done through the Contractual Compliance function, which employs the same approach and process for all enforcement areas. Details regarding this approach and process can be found here<https://www.icann.org/resources/pages/approach-processes-2012-02-25-en>. All contracted parties are advised to review the Temporary Specification carefully. Many of the requirements apply even if the registry or registrar is not in the European Union and has no registrations from the European Economic Area. Enforcement of the Temporary Specification applies to all ICANNcontracted parties. For a high level review of the Temporary Specification, ICANN also published and regularly updates a Frequently Asked Questions document<https://www.icann.org/resources/pages/gtld-registration-data-specs-faqs-201…>. One recurring concern we have received is how ICANN Contractual Compliance will obtain non-public registration data that is required to process a complaint. Among the complaints received to date, ICANNContractual Compliance has received two alleging denial of access to non-public registration data for legitimate purposes. Most of the other complaints received concern the availability of data published in WHOIS. For registrars, some of the registration data issues include: · Over-redacting public registration data, e.g.: · All contact fields are redacted when only some should be; · Missing Administrative/Technical email field and/or value; · Missing Registrant Organization/State/Province/Country field and/or value; and · Redacting privacy/proxy information · Non-compliant redacted fields e.g., missing anonymized email and/or webform to contact Registrant/Admin/Tech contact or using non-compliant values in the field for ex. "00000" · Registrar appears to be using registry WHOIS data causing endless loop of referral from registry to registrar data · Transfer requests being denied due to non-functional anonymized email address for registrant Some of the registry issues include: · Missing required Registrant/Admin/Tech Email (requirement for registries) · Required Registrant/Admin/Tech Email message in legal disclaimer only · Not providing full registration data to the Uniform Rapid Suspension System (URS) provider · Registry providing thick Bulk Registration Data Access (BRDA) files to ICANN instead of thin data We have also received a number of questions regarding the process for filing complaints alleging noncompliance with the Temporary Specification. As many have observed, there is not a "Temporary Specification" complaint form. To file a complaint about potential violations of the Temporary Specification or any other part of the agreements, please use the most relevant form published on the ICANN.org compliance page<https://www.icann.org/compliance/complaint>. ICANN Contractual Compliance will process complaints regardless of the form used. I hope this information is helpful. If you have any other questions or concerns regarding enforcement of the Temporary Specification, please let us know by emailing either the Contractual Compliance department at compliance(a)icann.org<mailto:compliance@icann.org> or me at Jamie.hedlund(a)icann.org<mailto:Jamie.hedlund@icann.org>.

1 0

BC comment on Draft Community Travel Support Guidelines
by Steve DelBianco July 16, 2018

July 16, 2018

Attached is the comment of the ICANN Business Constituency (BC) regarding Draft Community Travel Support Guidelines. This comment was drafted by Jimson Olufuye, with edits by Marilyn Cade and Mark Datysgeld. It was approved in accord with the BC Charter. Steve DelBianco Vice Chair for Policy Coordination ICANN Business Constituency

1 0

Audio link for EPDP Charter Drafting Team / Wednesday, 11 July 2018 at 12:00 UTC
by Steve DelBianco July 10, 2018

July 10, 2018

BC members can listen to the GNSO Council Drafting Team discuss the charter for an expedited PDP (EPDP). Next call is Wednesday, 11 July 2018 at 12:00 UTC for 2 hours. Agenda wiki page: https://community.icann.org/x/GohHBQ [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> An audio cast will be provided for this meeting, allowing non-councilors to listen in, please circulate the Audio Cast information below only, and not the access information to the AC room and audio bridge. ePDP DT Audio Cast To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream01 [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…>

1 0

Slides I used for Tuesday's Cross Community/High Interest Topic session on Accredited Access to Whois
by Steve DelBianco June 28, 2018

June 28, 2018

Some members asked for a copy of the slides I did for Tuesday’s session on Accredited Access to non-public Whois. --Steve

3 2

Official Announcement - 2018 Multistakeholder Ethos Award Honors Stéphane Van Gelder
by Chantelle Doerksen June 25, 2018

June 25, 2018

https://www.icann.org/news/announcement-2018-06-25-en 2018 Multistakeholder Ethos Award Honors Stéphane Van Gelder [ICANN announces Stéphane Van Gelder as 2018 Multistakeholder Ethos Award recipient] PANAMA CITY – 25 June 2018 – The Internet Corporation for Assigned Names and Numbers (ICANN) is honored to announce the recipient of the 2018 Multistakeholder Ethos Award. This year, the community selection panel posthumously recognized a long-time member of the ICANN community: Stéphane Van Gelder. The award was presented today at ICANN62 in Panama City to Stéphane Van Gelder’s wife Julie Talfournier Van Gelder. Community member Keith Drazek presented the award on behalf of the community selection panel. He enumerated Stéphane Van Gelder’s many contributions and attested to how he was admired for “his passion, his fairness, his ability to find the best in people, and his true gift for uniting people.” Cherine Chalaby, Chair, ICANN Board, and Göran Marby, President and CEO, ICANN, also remembered Stéphane Van Gelder. Chalaby stated that Van Gelder’s “impact on the ICANN community, and many of us individually, cannot be overstated.” Marby urged community members present to continue in Stéphane Van Gelder’s spirit and “see the people behind the discussions.” Marby turned the podium over to Julie Talfournier Van Gelder, who spoke movingly about her husband, a man who she said “helped reveal the strength and skills in so many people.” The Multistakeholder Ethos Award honors members of the ICANN community who have made outstanding contributions to ICANN’s multistakeholder model of Internet governance. Stéphane Van Gelder was selected from a list of 16 nominees as the person who best demonstrated the spirit of collaboration, strongly promoting consensus. The community selection panel composed of nine members from different Supporting Organizations and Advisory Committees recognized Van Gelder for his immense dedication and commitment to ICANN’s multistakeholder model, which served as an example to others in the community. The multistakeholder model is built on achieving consensus, and Van Gelder’s contributions epitomize this ideal, making him the perfect recipient for the 2018 Multistakeholder Ethos Award. A unique point that stood out from the beginning of the community selection panel’s process was that Stéphane Van Gelder received nominations or endorsements from at least 10 different community groups, and also from several individuals and community leaders. It was an unprecedented level of support and something that the selection committee immediately recognized as important. The breadth and depth of cross-community support spoke directly to his impact representing each of the award’s criteria – breaking down silos, working across multiple groups, engaging in a collegial manner, and a record of substantive and meaningful contribution over many years. Stéphane Van Gelder’s contributions were distinct, and the level of support from the ICANN community was undeniable. From 2008 to 2012, he served on the Generic Names Supporting Organization (GNSO) Council as an elected representative of what was then called the Registrars Constituency (now the Registrar Stakeholder Group). On the GNSO Council, he served as vice chair in 2010 and was elected and served two consecutive terms as chair in 2011 and 2012. During his tenure as GNSO chair, Van Gelder oversaw and shepherded multiple key projects, including: · Completion of an extensive update of the GNSO's operating procedures. · Establishment of the Domain Name System Security (DNS) Security and Stability Analysis Working Group, working jointly with the At-Large Advisory Committee (ALAC), Country Code Names Supporting Organization (ccNSO), and Number Resource Organization (NRO). · Completion of the Fast Flux, Post-Expiration Domain Name Recovery and Inter-Registrar Transfer Policy (IRTP) Part B Policy Development Processes (PDPs), and the joint ccNSO-GNSOInternationalized Domain Name Working Group. · Launch of the IRTP Part C, Thick WHOIS, and Locking of Domain Names subject to Uniform Dispute Resolution Policy Proceedings PDPs. · Completion of the Applicant Guidebook for the 2012 New Generic Top-Level Domain (gTLD) Program and the launch of the program. Van Gelder was also a long-time contributor to the ICANN Nominating Committee, beginning in 2013, serving as its chair in 2015 and associate chair in 2017. He was a well-respected and much appreciated member of not only the GNSO, but of the broader ICANN community. His genuine passion, energy, and commitment to ICANN’s mission and his achievements in various roles across the community were second to none. All of these qualities and accomplishments strongly support the selection of Stéphane Van Gelder as the recipient of ICANN’s 2018 Multistakeholder Ethos Award. At this time when we celebrate his contributions, ICANN also extends our deepest condolences to his family, friends, and colleagues. Launched in 2014 at ICANN50, the Multistakeholder Ethos Award<https://community.icann.org/x/YyOAAw> recognizes ICANN participants who have invested in consensus-based solutions, acknowledged the importance of ICANN’s multistakeholder model of Internet governance, and contributed in a substantive way to the higher interests of ICANN’s organization and community.

1 0

BC questions to ICANN board, regarding the Whois Temporary Specification
by Steve DelBianco June 22, 2018

June 22, 2018

As we discussed on the BC Member call Thursday, last night we sent the ICANN board a list of questions regarding the Whois Temporary Specification for GDPR compliance. Thanks to Margie Milam for drafting the questions, and to Tim Chen and Alex Deacon for edits. Our questions are here<https://www.bizconst.org/assets/docs/positions-statements/2018/2018_06June_…> and attached. Claudia’s letter is below: Dear Goran, Cherine and John, Please find attached a letter highlighting BC questions related to Temporary Specification (Temp. Spec) to the Registrar Accreditation Agreement (RAA) and Registry Agreement (RA) to clarify some uncertainties created by the Temp. Spec. Kind Regards, Claudia Selli

1 0

BC comment on Release for Registration of the Single-Character Label O.COM
by Steve DelBianco June 20, 2018

June 20, 2018

Attached is the comment of the ICANN Business Constituency (BC) regarding the proposed Release for Registration of the Single-Character Label O.COM This comment was drafted by Zak Muscovitch, with edits by Andrew Mack, Claudia Selli, Marilyn Cade, and Steve DelBianco. It was approved in accord with the BC Charter. Steve DelBianco Vice Chair for Policy Coordination ICANN Business Constituency

1 0

GNSO Council call: EPDP Charter Drafting Team, Tuesday 19 June 2018 at 13:00 UTC.
by Steve DelBianco June 15, 2018

June 15, 2018

On Tuesday 19-Jun at 13 UTC the GNSO Council will discuss charter drafting for an Expedited Policy Development Process (EPDP) on GDPR compliance for Whois. Our Councilors Susan and Marie will participate, and the rest of us can listen via these coordinates: Listen in browser: http://stream.icann.org:8000/stream01 <https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u <https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…>

1 0