Marilyn - I, for one, really welcome this great offer. Scheduling is always tough but I’d love to participate. Thanks again Steven Koltai Managing Director, Koltai & Company, LLC & Visiting Scholar, Brookings Institution steven@koltai.co http://koltai.co @koltaico LinkedIn Profile <https://www.linkedin.com/in/steven-koltai-09a78a1> Peace through Entrepreneurship: Investing in a Startup Culture for Security and Development, Brookings Institution Press, 2016, INFO & ORDERING AT: Peace through Entrepreneurship <https://peace-through-entrepreneurship.squarespace.com/> <https://www.brookings.edu/book/peace-through-entrepreneurship/> <https://www.brookings.edu/book/peace-through-entrepreneurship/>
On Mar 19, 2017, at 4:25 PM, Marilyn Cade <marilynscade@hotmail.com> wrote:
Dear BC colleagues
I am wondering if perhaps some of the BC members might welcome a short briefing on a few of the challenges to ICANN from external activities, regarding implications for ICANN, at some point. The external activities I note from my view are as follows: United Nations Commission on Science and Technology for Development Working Group on Enhanced Cooperation ITU Council's Internet Public Policy ITU WTDC ITU Expert Group on the ITRs G-7 and G-20 WSIS Forum and its relevance to ICANN
There are also some other broader activities, such as some of the multi stakeholder proposals to establish principles and norms on cyber security for the Internet.
While this may seem out of scope for the BC, I wonder if we might consider an informational briefing for those interested, and volunteer to help to coordinate such a session -- a briefing, really, not a debate or rebuttal. The CCWG-IG public session highlighted some of these challenges, but I know that with all the competing events during ICANN meeting, many would have been unable to attend that session.
As an FYI, during WSIS Forum, ICANN staff has organized a workshop, and CCWG-IG has also proposed a workshop on capacity building activities of ICANN, that has been accepted.
I mention all of this only as it relates to where and how governments may be addressing challenges, if they cannot achieve satisfactory and moderated solutions at ICANN. It just helps to know what is going on elsewhere.
Marilyn Cade
From: bc-gnso-bounces@icann.org <mailto:bc-gnso-bounces@icann.org> <bc-gnso-bounces@icann.org <mailto:bc-gnso-bounces@icann.org>> on behalf of Steve DelBianco <sdelbianco@netchoice.org <mailto:sdelbianco@netchoice.org>> Sent: Thursday, March 16, 2017 7:24 AM To: BC List Subject: [bc-gnso] GAC Copenhagen Communique
Is here <https://gacweb.icann.org/display/gacweb/Governmental+Advisory+Committee?prev...> 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; 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 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 Communiqué 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 Communiqué, 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: Take into account the serious concerns expressed by some GAC Members as contained in previous GAC Advice Engage with concerned governments by the next ICANN meeting to resolve those concerns. Immediately explore measures to find a satisfactory solution of the matter to meet the concerns of these countries before being further aggravated. 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.
_______________________________________________ Bc-gnso mailing list Bc-gnso@icann.org <mailto:Bc-gnso@icann.org> https://mm.icann.org/mailman/listinfo/bc-gnso <https://mm.icann.org/mailman/listinfo/bc-gnso>
