March 2017 - Bc-gnso - lists.icann.org

FILED: BC comment on Independent Review of the ICANN At-Large Community (ALAC)
by Steve DelBianco March 24, 2017

March 24, 2017

Today the BC filed the attached comment on the Independent Review of the ICANN At-Large Community (ALAC). (comment page at https://www.icann.org/public-comments/atlarge-review-draft-report-2017-02-0… ) Thanks to drafters Ari Giovenco, Gail Slater, Tim Smith, Lawrence OlaWale Roberts, Hibah Kamal-Grayson, and Steve DelBianco. It was approved in accord with the BC Charter. — Steve DelBianco Vice chair for policy coordination ICANN Business Constituency

1 0

GAC Copenhagen Communique
by Steve DelBianco March 19, 2017

March 19, 2017

Is here<https://gacweb.icann.org/display/gacweb/Governmental+Advisory+Committee?pre…> and attached. Note that they qualified all their advice at this meeting as “Consensus Advice” per the new bylaws. GAC Advice is excerpted below (highlights are mine) 1. Protection of the Red Cross and Red Crescent designations and identifiers Re-affirming previous GAC Advice for a permanent reservation of the Red Cross and Red Crescent designations and identifiers, the GAC acknowledges the conclusions of the facilitated dialogue held during ICANN 58 on resolving outstanding differences between the GAC’s previous advice and the GNSO's past recommendations to the Board on the protections of the names and identifiers of the respective Red Cross and Red Crescent organizations. Consistent with the conclusions of the abovementioned dialogue, a. The GAC advises the ICANN Board to: I. request the GNSO without delay to re-examine its 2013 recommendations pertaining to the protections of Red Cross and Red Crescent names and identifiers (defined as “Scope 2” names in the GNSO process) which were inconsistent with GAC Advice. 2. IGO Protections The GAC notes that a dialogue facilitated by the Board on this topic has begun between the GAC and the GNSO (including its relevant Working Groups). The GAC expects that these discussions would resolve the long-outstanding issue of IGO acronym protections and understands that temporary protections will continue to remain in place until such time as a permanent agreed solution is found. Based upon the facilitated discussions up to this stage, a. The GAC advises the ICANN Board to: I. pursue implementation of (i) a permanent system of notification to IGOs regarding second-level registration of strings that match their acronyms in up to two languages and (ii) a parallel system of notification to registrants for a more limited time period, in line with both previous GAC advice and GNSO recommendations; 1. facilitate continued discussions in order to develop a resolution that will reflect (i) the fact that IGOs are in an objectively unique category of rights holders and (ii) a better understanding of relevant GAC Advice, particularly as it relates to IGO immunities recognized under international law as noted by IGO Legal Counsels; and 2. urge the Working Group for the ongoing PDP on IGO-INGO Access to Curative Rights Protection Mechanisms to take into account the GAC’s comments on the Initial Report. 3. Mitigation of Domain Name Abuse a. The GAC advises the ICANN Board to: I. provide written responses to the questions listed in the Follow-up Scorecard attached to this Communique, no later than 5 May 2017 for appropriate consideration by the GAC before the ICANN 59 meeting in Johannesburg, taking into account that the ICANN President and CEO will act as contact point for the GAC in this matter. RATIONALE The GAC is seeking to assess the effectiveness of its Advice to the ICANN Board. Annex 1 of the GAC Hyderabad Communiqué listed a number of questions to conduct such assessment in relation to Advice implemented as part of the 2013 Registrar Accreditation Agreement and the New gTLD Registry Agreement. The GAC is also interested in assessing the contribution of the SSR and Contractual Compliance departments of ICANN to the prevention and mitigation of domain name abuse. While ICANN responded to Annex 1 of the GAC Hyderabad Communiqué, the information provided was not sufficient to conduct the necessary assessments. 4. 2-Character Country/Territory Codes at the Second Level In light of the discussions with the ICANN Board in Copenhagen on the Board Resolution of 8 November 2016 and its implementation of 13 December 2016 regarding two-letter country codes as second level domains, a. The GAC advises the ICANN Board to: 1. Take into account the serious concerns expressed by some GAC Members as contained in previous GAC Advice 2. Engage with concerned governments by the next ICANN meeting to resolve those concerns. 3. Immediately explore measures to find a satisfactory solution of the matter to meet the concerns of these countries before being further aggravated. 4. Provide clarification of the decision-making process and of the rationale for the November 2016 resolution, particularly in regard to consideration of the GAC advice, timing and level of support for this resolution. RATIONALE The GAC noted serious concerns expressed by some governments about the consequences introduced by the changes created by the 8 November 2016 Resolution. In particular, according to the new procedure it is no longer mandatory for the registries to notify governments of the plans for their use of 2-letter codes, nor are registries required to seek agreement of governments when releasing two-letter country codes at the second level, which, for example, allows registries to charge governments substantial fees.

3 2

ICANN58 BC Newsletter Now Online!
by Chantelle Doerksen March 15, 2017

March 15, 2017

Dear BC Members, Attached is the digital copy of the ICANN58 Newsletter. You can also find this in our Newsletter section of the website, http://www.bizconst.org/newsletter. Thanks and kind regards, Chantelle

1 0

Ethos Award 2017 Nominations - Reminder | Close 20 March 2017
by Chantelle Doerksen March 12, 2017

March 12, 2017

https://www.icann.org/news/announcement-2017-02-07-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Reminder: Nomination Period For ICANN Multistakeholder Ethos Award | Award Targeted for ICANN59 | Nominations Close 20 March 2017 Submit Nominations Via the Ethos Award Nomination Form[goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_forms_sKJcUjdA5…> ICANN is pleased to remind community members that the nomination period for ICANN's Multistakeholder Ethos Award will be open until 20 March 2017. Launched in 2014 at ICANN50 in London, the Multistakeholder Ethos Award recognizes ICANN participants who have deeply invested in consensus-based solutions, acknowledging 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 its community. The ideal recipient(s) will have served in roles in multiple ICANN working groups or committees and collaborated with more than one Supporting Organization and/or Advisory Committee in a significant capacity. Candidates for the award will demonstrate at least five years of participation in the ICANN Community. Candidates will be evaluated by a panel of community members appointed by the Chairs of each Supporting Organizations and Advisory Committees using a merit-based point system evaluated against three criteria: 1. Demonstrated ability to work across community lines with both familiar and unfamiliar ICANNStakeholders with the aim of consensus building and collaboration that substantiate ICANN's multistakeholder model; 2. Facilitator of dialogue and open discussion in a fair and collegial manner, through the spirit of collaboration as shown through empathy and demonstrating a sincere desire to engage with people from other backgrounds, cultures, and interests; and 3. Demonstrated additional devotional factors exhibited by time spent supporting ICANN's multistakeholder model and its overall effectiveness through volunteer service via working groups or committees. Please submit your nominations via this Nomination Form[goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_forms_sKJcUjdA5…> including detailed information outlining why the nominee meets the award criteria. Any additional information in support of nominations and/or questions about the award process may be submitted via email at ethosaward2017(a)icann.org<mailto:ethosaward2017@icann.org>. Award recipient(s) will be announced in June 2017 at ICANN59 Johannesburg. For more insights on the award program, please consult the ICANN Community Wiki[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>. Submit Nominations Via the Ethos Award Nomination Form[goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_forms_sKJcUjdA5…>

1 0

ICANN58 - GNSO Working Session: Briefing Materials | Sunday, 12 March 2017
by Chantelle Doerksen March 12, 2017

March 12, 2017

Dear BC, IPC, and ISPCP Members: For those seeking materials from the GNSO Working Group Session held on Sunday, 12 March 2017, they will be made available here: https://community.icann.org/x/cZ3Raw. Recordings and transcripts will be available following the meeting. Kind regards, Chantelle

1 0

Letter from Göran Marby to CSG in response to 5 January 2017 letter
by Jared Erwin March 11, 2017

March 11, 2017

Dear Commercial Stakeholder Group, Please find attached a letter from Mr. Göran Marby, ICANNs President and CEO, in response to the Commercial Stakeholder Group letter of 5 January 2017. This response will be posted alongside the initial letter on the ICANN Correspondence page shortly (https://www.icann.org/resources/pages/correspondence; https://www.icann.org/en/system/files/correspondence/csg-to-marby-et-al-05ja n17-en.pdf). If you have any questions about this message, you may direct your question to correspondence(a)icann.org <mailto:correspondence@icann.org> . Thank you, The ICANN Correspondence Team correspondence(a)icann.org <mailto:correspondence@icann.org>

1 0

Krista Papac Named as ICANN Complaints Officer
by Steve DelBianco March 10, 2017

March 10, 2017

This just in… Krista Papac Named as ICANN Complaints Officer https://www.icann.org/news/announcement-2017-03-10-en 10 March 2017 – The Internet Corporation for Assigned Names and Numbers (ICANN) today announced that Krista Papac, Director of Registry Services and Engagement for ICANN's Global Domains Division, has been named as ICANN's Complaints Officer. "The Complaints Officer is an important new function within ICANN to help improve the ICANNorganization," said CEO Göran Marby. "Krista is a long-time contributor to the ICANN organization and multistakeholder community. She is widely respected by her colleagues across the organization and has built extensive relationships with members of the community. I could not be happier with a candidate to fill this important role." The Complaints Office will provide a centralized mechanism to track complaints received about the ICANN organization and is an additional way for the ICANN organization to be accountable for and transparent about its performance. The Complaints Officer will work with ICANN's various internal complaints processes to assist improvements and collect data about complaints received across the organization. The Complaints Officer will help ensure that any complaints about systemic issues or concerns about the organization are heard, reviewed, analyzed and resolved as openly as appropriate. ICANN receives complaints through the Ombudsman, Reconsideration Requests and Independent Review Process filings and through various ICANN functions such as Contractual Compliance. All of these mechanisms and functions will remain the same and are not affected by this additional accountability process. "I am honored to take on this new role for ICANN," said Krista. "My goal is to help build this new avenue for the community to have their voices heard. As the Complaints Officer, I can help give the organization better visibility into any possible systemic issues that may exist now or in the future, so we can proactively consider improvements." The Complaints Officer will report directly to John Jeffrey, ICANN's General Counsel and Secretary. Krista will be transitioning away from her Global Domains Division role in the coming weeks, and will begin to build out the Complaints office. Krista Papac is a seasoned executive with over 15 years of experience in the domain name industry holding a variety of roles including executive leadership and management, strategic planning, business process development, and business development. Krista joined ICANN in May 2013 as the Director of Registry Services & Engagement. During this time, she built a global team of relationship and service development experts by putting people, process and infrastructure in place to support the growth of the gTLD marketplace.

1 0

FILED: BC comment on GNSO Report on IGO-INGO Access to Curative Protection Mechanisms
by Steve DelBianco March 7, 2017

March 7, 2017

Today we filed the attached comment on the GNSO Initial Report on the IGO-INGO Access to Curative Rights Protection Mechanisms PDP. (comment page at https://www.icann.org/public-comments/igo-ingo-crp-access-initial-2017-01-2… ) Thanks to drafters Jay Sudowski and Andy Abrams.

1 0

UPDATED: BC response to public comments on our proposed Charter
by Steve DelBianco March 4, 2017

March 4, 2017

(Updated 3-Mar-2017 by Jimson Olufuye, to correct the description of Africa outreach events and General Counsel duties) Rob, The public comment period on the proposed BC charter recently concluded (link<https://www.icann.org/public-comments/bc-charter-amend-2017-01-06-en>). There were 4 comments posted, plus our reply to Afnic’s comment. As we discussed at the Iceland meeting, the BC has prepared a point-by-point response to the public comments. We provide these responses in order to help facilitate Staff’s report to the ICANN Board. If Staff has further questions regarding the Charter or these responses, please do not hesitate to contact us. Regards, Steve DelBianco Vice chair for policy coordination ICANN Business Constituency

1 0

Corrections to BC Response on Charter comments General Counsel duties
by Steve DelBianco March 4, 2017

March 4, 2017

BC members — Jimson, our vice chair for finance and administration, made 2 corrections yesterday to the BC response to charter comments. I will re-send the attached docs to ICANN staff. Below is the explanation of the corrections: First, Jimson edited the sentence on page 3 regarding BC outreach events: Original: • BC Outreach support for and speaking at the AfiCTA Summit and the Asia - Oceania Computing Industry Organisation (ASOCIO) events in Asia To be revised to: • BC Outreach support for and speaking at the AfiCTA Summits in Africa and the Asia - Oceania Computing Industry Organisation (ASOCIO) events in Asia. Second, Jimson added this section on the Charter, regarding duties of our General Counsel: 2.5.5 The General Counsel is empowered to: a. Incorporate the BC as a non-profit entity in the District of Columbia; b. Process and forward the BC’s postal mail; c. Register and secure an Employer Identification Number (EIN) for the BC; d. File and sign the BC’s applicable tax returns; e. Utilize his/her registered address to facilitate his/her duties herein. Since a number of these functions have already been implemented and are not recurring, can we reframe as follows: a. Maintain a continuous incorporation of the "The ICANN GNSO 'Business Constituency' LLC" in the District of Columbia b. Maintain the BC's postal mail c. Maintain an Employer Identification Number (EIN) for the BC d. ok e. ok

1 0