Showing posts with label Governmental Advisory Committee. Show all posts
Showing posts with label Governmental Advisory Committee. Show all posts

2018-03-16

ICANN61 San Juan, Puerto Rico: GAC Communique & ICANN61 Tweets

Editor's note: ICANN61 ended in San Juan, Puerto Rico, on Thursday, March 15. Below is the GAC Communique issued March 15 by the Governmental Advisory Committee (GAC), as well as a selection of tweets courtesy of @sgdickinson.

1) ICANN 61 GAC Communique:


2) ICANN61 Report via Tweets
GDPR / WHOIS:
FY19 ICANN Budget:
CCWG-Accountability WS2 jurisdiction report:
New gTLD .AMAZON:
GAC vs ICANN Board re 2-letter country codes at second level:
See also on Domain Mondo: News Review: ICANN61 March 10-15, San Juan, Puerto Rico (video of Public Forums, Board Meeting, ICANN Org Executive Team, and session on GDPR)

feedback & comments via twitter @DomainMondo


DISCLAIMER

2016-03-10

ICANN55, Marrakech, GAC Communique

The ICANN Governmental Advisory Committee (GAC) has issued its ICANN55 Communique, embedded below. The GAC also welcomed Burundi, Cambodia, Haiti, Republic of Palau and Chad as new Members, and the West African Telecommunications Regulators Assembly (WATRA) as a new Observer. This brings the number of GAC Members to 162, and the number of observers to 35.

The GAC will next meet during the 56th ICANN meeting, scheduled for the 27th to 30th of June 2016.



See also on Domain MondoICANN55: GAC Letter on ICANN Accountability Final Proposal







DISCLAIMER

2016-03-09

ICANN55: GAC Letter on ICANN Accountability Final Proposal

The ICANN Governmental Advisory Committee (GAC) has responded to the CCWG's Supplemental Final Proposal (part of the IANA stewardship transition plan) which is scheduled to be approved and transmitted by the ICANN Board of Directors on Thursday, March 10, 2016, to NTIA

"... The GAC has considered the CCWG's proposal and supports Recommendations 1 to 10 and 12. However, there is no consensus on Recommendation 11 and the “carve-out” provision contained in Recommendations 1 and 2. As regards Recommendations 1 and 2, the GAC expresses its willingness to take part in the envisioned empowered community mechanism as a decisional participant, under conditions to be determined internally ... the GAC has no objection to the transmission of the proposal to the ICANN Board."  

Complete GAC letter embedded below:

See also on Domain Mondo:




DISCLAIMER

2015-10-24

GAC Communique, ICANN 54, Future gTLD Rounds, CCWG Stress Test 18

The Governmental Advisory Committee (GAC) meeting at ICANN54 in Dublin, issued its GAC Dublin 54 Communiqué [PDF, 169 KB].on October 21, 2015. Two of the many issues covered by the communique were future gTLD rounds (new generic top-level domains) and Stress Test 18 (relating to CCWG-Accountability's work)(emphasis added):

Future gTLD Rounds
"The GAC advises the Board that: i. before defining the modalities for future rounds, a rigorous assessment of all public policy related aspects of the current round should be undertaken, taking into account the advice given by the GAC on this subject since the beginning of the New gTLD process, including advice relating to community-wide engagement on the issues of communication to and access by developing countries and regions; and advice regarding past policy decisions taken by the Board to reserve the Red Cross and Red Crescent designations and names. In this regard, the GAC expects that those elements of the current framework for new gTLDs that are considered appropriate by the GAC will remain and that the elements that are not considered satisfactory will be improved for subsequent rounds."

Stress Test 18
"Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability): The GAC recognizes that much progress has been made by the CCWG-Accountability in its ongoing work, and welcomes the CCWG’s achievements to date and supports the efforts to finalise its proposal for enhancing ICANN accountability as required for the IANA stewardship transition. In assessing the specific accountability recommendations put forth so far by the CCWG-Accountability, the GAC considers that whatever the final outcome of this process may be, the new accountability framework to be agreed upon must preserve the current role of governments in ICANN. The discussions on Stress Test 18 have helped the GAC to have a better understanding of the different views on the issue. In assessing the different rationales presented so far related to Stress Test 18, the GAC considered:
• The need that each and every Advisory Committee ensures that the advice provided is clear and reflects the consensus view of the Committee; 
• The need that each and every Advisory Committee should preserve its own autonomy in its definition of consensus; 
• The value the Board attributes to receiving consensus advice; 
• The recommendation of the BGRI WG, as reiterated by the ATRT2, to set the threshold for the ICANN Board to reject GAC advice to a 2/3 majority voting, consistent with the threshold established for rejection of ccNSO and GNSO PDP recommendations." 

"In view of the above, having considered concerns expressed by various parties, the GAC agreed to further work on the issue of Stress Test 18, and to submit any further input to the CCWG taking into account the timelines of the CCWG. GAC Members will continue to work within the CCWG to finalise the proposal for enhancing ICANN accountability." (emphasis added)

Editor's Note: CCWG-Accountability has proposed changes to ICANN bylaws related to CCWG's Stress Test 18: "Governments in ICANN’s Government Advisory Committee (GAC) amend their operating procedures to change from consensus decisions to majority voting for advice to ICANN’s board. Consequence: Under current bylaws, ICANN must consider and respond to GAC advice, even if that advice were not supported by consensus. A majority of governments could thereby approve GAC advice that restricted free online expression, for example." Bylaw changes have been proposed by CCWG-Accountability to prevent such an outcome.




DISCLAIMER

2015-10-17

ICANN 54, GAC Saturday Sessions Online, ICANN Accountability

ICANN's Governmental Advisory Committee (GAC) Saturday Sessions, October 17, 2015, ICANN 54, Dublin, Ireland: 14:00 to 18:00 IST time converter - 9am-1pm ET (US)

Agenda Details: (times are local Dublin, IST - Irish Standard Time)
14:00 - 14:30 - Opening Plenary
14:30 - 16:00 - ICANN Accountability
16:00 - 16:30 - Break
16:30 - 17:00 - ICANN Accountability
17:00 - 17:30 - Current gTLD Round: Safeguards

Online: Virtual Meeting Room Stream Live  English

Scribe Stream Live  English

Other Remote Participation:
Low Bandwidth
Service Type  Language
Audio Stream Live العربية
Audio Stream Live English
Audio Stream Live Español
Audio Stream Live Français
Audio Stream Live Português
Audio Stream Live Русский
Audio Stream Live 简体中文

High Bandwidth
Audio Stream Live العربية
Audio Stream Live English
Audio Stream Live Español
Audio Stream Live Français
Audio Stream Live Português
Audio Stream Live Русский
Audio Stream Live 简体中文

About The GAC - ICANN’s Governmental Advisory Committee (GAC):

What is the GAC? The GAC is an advisory committee to ICANN, created under the ICANN ByLaws. It provides advice to ICANN on public policy aspects of ICANN’s responsibilities with regard to the Internet Domain Name System (DNS). The GAC is not a decision-making body. It advises ICANN on issues that are within ICANN’s scope. GAC advice has a particular status under the ICANN ByLaws. Its advice must be duly taken into account by the ICANN Board, and where the Board proposes actions inconsistent with GAC advice it must give reasons for doing so and attempt to reach a mutually acceptable solution. The GAC appoints a non-voting liaison to the ICANN Board. This is normally the GAC Chair.

Who are the GAC’s Members? The GAC elects a Chair and Vice Chairs from its membership. The new (elected at ICANN 51) GAC Chair is Mr Thomas Schneider from Switzerland, and the Vice Chairs are from Argentina, Spain, Namibia, Thailand, Turkey.  GAC membership consists of national governments and distinct economies recognized in international fora; and, usually in an observer capacity, multinational governmental and treaty organisations and public authorities (including all the UN agencies with a direct interest in global Internet governance such as the ITU, UNESCO and WIPO). There are currently 150 GAC Members and 32 Observers.

Why does ICANN have a Governmental Advisory Committee? ICANN is a multi-stakeholder entity in which governments need to participate alongside the domain names industry, the technical community, business and non-commercial users, and civil society. The GAC was established in 1999, in parallel with ICANN’s first public meetings, and has operated continuously since then. ICANN looks to the GAC for advice on public policy aspects of specific issues for which ICANN has responsibility. This is an important dimension of ICANN’s work. (source: About The GAC - GAC Website)

ICANN54 | Dublin: Oct 16-23 Schedule



DISCLAIMER

2015-07-13

DCA Trust IRP Decision: ICANN Failed the Global Internet Community

UPDATE June 16, 2016: New gTLD AFRICA Litigation: Defendant ZACR Dismissed as a Party.

UPDATE (July 17, 2015): See Domain Mondo: ICANN dot AFRICA IRP: WHO Redacted WHAT In the Final Declaration?

UPDATE (July 16, 2015) Approved Board Resolutions | Special Meeting of the ICANN Board re: DotConnectAfrica Trust (DCA) v. ICANN IRP Final Declaration --

Resolved (2015.07.15.01) [note this appears to be an error on the ICANN website as the Resolution is actually 2015.07.16.01], the Board has considered the entire Declaration, and has determined to take the following actions based on that consideration:
  1. ICANN shall continue to refrain from delegating the .AFRICA gTLD;
  2. ICANN shall permit DCA's application to proceed through the remainder of the new gTLD application process as set out below; and
  3. ICANN shall reimburse DCA for the costs of the IRP as set forth in paragraph 150 of the Declaration.
Resolved (2015.07.16.02), since the Board is not making a final determination at this time as to whether DCA's application for .AFRICA should proceed to contracting or delegation, the Board does not consider that resuming evaluation of DCA's application is action that is inconsistent with GAC advice.

Resolved (2015.07.16.03), the Board directs the President and CEO, or his designee(s), to take all steps necessary to resume the evaluation of DCA's application for .AFRICA and to ensure that such evaluation proceeds in accordance with the established process(es) as quickly as possible (see Applicant Guidebook at http://newgtlds.icann.org/en/applicants/agb for established processes).

Resolved (2015.07.16.04), with respect to the GAC's consensus advice in the Beijing Communiqué that DCA's application for .AFRICA should not proceed, which was confirmed in the London Communiqué, the Board will ask the GAC if it wishes to refine that advice and/or provide the Board with further information regarding that advice and/or otherwise address the concerns raised in the Declaration.

Resolved (2015.07.16.05), in the event that DCA's application for .AFRICA successfully passes the remainder of the evaluation process, at that time or before, the Board will consider any further advice or information received from the GAC, and proceed as necessary, balancing all of the relevant material information and circumstances. Should the Board undertake any action that may be inconsistent with the GAC's advice, the Board will follow the established process set out in the Bylaws (see ICANN Bylaws, Article XI, Section 2.1).

See also: ICANN announcement re above Board action.

UPDATE (July 16, 2015): This morning at the IGFUSA meeting in Washington, DC, ICANN Board Chairman Steve Crocker reported: "... among many many contentious issues that we deal with has been what happens when you are competing parties that want the same domain name and dot Africa has been the subject of a particular contention. Last Friday an independent review panel that is fairly high up in the escalation process for adjudicating disputes, issued a report and took issue with the direction that we had been taking in our evaluation process. The Board of ICANN met this very morning which is what we were doing at 8 o'clock this morning. And we passed a Resolution acknowledging the panel's report decision accepting it and taking action, primary action is to put the -- what the losing, the dot connect Africa trust application back in to the evaluation process. And there are other aspects of the panel's decision that we will have to deal with later. It does not represent a final decision about anything. It just moves that process forward. There will be posting of the Resolution and press release probably as we are sitting here. And I thought that, you know, your comment about the issues about domain names led perfectly in to this." (emphasis added, quote verbatim from session transcript)

UPDATE (July 15, 2015): ICANN has called a Special Meeting of its Board of Directors for July 16th, with the Agenda indicating only "DotConnectAfrica Trust (DCA) v. ICANN IRP Final Declaration" and AOB (all other business). Did ICANN Staff help a favored new gTLD applicant? See: Unredacted: ICANN's hidden role in fierce battle over .Africa rights • The Register by Kieren McCarthy.

Question: Does ICANN have an organizational culture of impunity, making it unfit for global internet governance? One answer here.
* * * * * 
ICANN, DCA Trust, .AFRICA, IRP Decision, Fallout and Ramifications: All of ICANN, however broadly defined, failed the global Internet community--

Page 18 of IRP decision between DotConnectAfrica Trust (DCA Trust) and ICANN
From decision, page 18, of IRP between DotConnectAfrica Trust (DCA Trust) and ICANN 
"[T]he Panel declares that both the actions and inactions of the [ICANN] Board with respect to the application of DCA Trust relating to the .AFRICA gTLD were inconsistent with the Articles of Incorporation and Bylaws of ICANN." --DCA Trust IRP ¶148
"16. Accountability requires an organization to explain or give reasons for its activities, accept responsibility for them and to disclose the results in a transparent manner."--DCA Trust IRP ¶38
ICANN was the losing party, in more ways than one, in the Independent Review Panel's (IRP) declaration deciding DotConnectAfrica Trust (DCA Trust) claims involving new gTLD .AFRICA. The entire 63 page IRP declaration was published on the ICANN website (pdf) Friday, July 10, 2015. The entire record (October 24, 2013 - July 9, 2015) of the IRP is also on the ICANN website. The three member IRP panel's declaration will likely be studied, commented on, and cited as legal precedent for years to come. *Excerpts from the IRP declaration are cited herein by IRP paragraph (¶) number (emphasis added). Q&A:
ICANN has already entered into an agreement with ZA Central Registry for the .AFRICA string but it has not yet been delegated. What happens to new gTLD .AFRICA?
IRP ¶133. "Pursuant to Article IV, Section 3, paragraph 11 (d) of ICANN’s Bylaws, therefore, the Panel recommends that ICANN continue to refrain from delegating the .AFRICA gTLD and permit DCA Trust’s application to proceed through the remainder of the new gTLD application process."

"Where feasible, the Board shall consider the IRP Panel declaration at the Board's next meeting. The declarations of the IRP Paneland the Board's subsequent action on those declarations, are final and have precedential value."--ICANN Bylaws Article IV §3 (emphasis added)

"Consistent with ICANN's Bylaws, ICANN will carefully review the [IRP] panels [sic] declaration and the ICANN Board will be asked to consider the matter at its next meeting on 28 July 2015."
--John Jeffrey, ICANN's General Counsel and Secretary [see July 15 UPDATE above]

What will happen on and after July 28th is unknown. Quoting from IRP ¶143: "... this case was extraordinary and ... 'was in many senses a first of its kind.' According to ICANN, among other things: This IRP was the first associated with the Board’s acceptance of GAC advice that resulted in the blocking of an application for a new gTLD under the new gTLD Program; this was the first IRP associated with a claim that one or more ICANN Board members had a conflict of interest with a Board vote; and this was the first (and still only) IRP related to the New gTLD Program that involved a live hearing, with a considerable amount of debate associated with whether to have a hearing."
ICANN set aside funds for new gTLD legal costs--How much has this IRP cost ICANN so far?
IRP ¶144." ... the Panel is unanimous in deciding that DCA Trust is the prevailing party in this IRP and ICANN shall bear, pursuant to Article IV, Section 3, paragraph 18 of the Bylaws, Article 11 of Supplementary Procedures and Article 31 of the ICDR Rules, the totality of the costs of this IRP and the totality of the costs of the IRP Provider."

It is likely ICANN's total costs and expenses, including its own legal fees, of this IRP will be in the millions ($US)--just the IRP panelists’ compensation and expenses total $403,467.08 ($US) and "shall be born entirely by ICANN" (IRP ¶150), but ICANN does not have to pay DCA Trust's attorney fees (IRP ¶151).
Who are the "other" losing parties as a result of the IRP Declaration?
Although sections of the IRP Declaration are heavily redacted, it is clear from reading the Declaration and its recitation of DCA Trust's averments that there are others, besides the ICANN Board of Directors, who share, directly, the "blame" here--ICANN staff, Governmental Advisory Committee (GAC), and perhaps others purportedly acting in support of the other applicant for .AFRICA, ZA Central Registry, which will now likely face a further delay in delegation of the .AFRICA string, if not outright rescission of its Registry agreement. From the IRP Declaration (reciting DCA Trust averments, p.24): "Finally, the Board’s failure to inquire into the actions of its staff, even when on notice of the myriad of discriminatory actions, violates its obligation to comply with its Bylaws with appropriate care and diligence."
"The ICANN Board and staff members had actual knowledge of information calling into question the notion that there was a consensus among the GAC members to issue the advice against DCA’s application, prohibiting the application of the rule in the AGB concerning consensus advice (which creates a “strong presumption” for the Board that a particular application “should not proceed” in the gTLD evaluation process). The irregularities leading to the advice against DCA’s application included proposals offered by Alice Munyua, who no longer represented Kenya as a GAC advisor at the time, and the fact that the genuine Kenya GAC advisor expressly refused to endorse the advice." (DCA Trust IRP, page 25)
The ramifications of the DCA Trust IRP decision even extend to the IANA Stewardship Transition and Enhancing ICANN Accountability processes, particularly since the CWG-Stewardship (Names) proposal has dependencies upon the outcome of the CCWG-Accountability WS-1 work, including, possibly now re-writing all bylaws, including provisions dealing with IRPs and GAC "advice." The ICANN Board of Directors is going to have to become "proactive"--questioning (and holding accountable) all ICANN officers and staff, as well as all SO/ACs and their so-called "consensus" advice or recommendations, bearing in mind that the Board's duty is to act in the public interest at all times, the  "public interest" defined as what is in the best interests of the global internet community NOT just special interest groups or "stakeholders" within ICANN. This Public Interest Standard should be the standard by which the Board makes all its decisions.

From decision, page 39, of IRP between DotConnectAfrica Trust (DCA Trust) and ICANN
The "buck stops with the Board"--everyone should hold the ICANN Board accountable (if you can't stand the heat, get out of the kitchen)--and the Board should hold itself, ICANN officers and staff, and ICANN's own constituencies accountable. In the final analysis, the loser in the DCA Trust case was the entire governing and operating structure of ICANN--from the GNSO which propagated an ill-conceived, misbegotten new gTLDs policy, to ICANN officers and staff who "horribly implemented" the new gTLDs program, to the GAC and other constituencies who failed to stop, object, or otherwise contributed to the dysfunction which resulted in this IRP declaration--including the US government, NTIA, which failed in its oversight role. All of ICANN, however broadly defined, failed the global Internet community.

Where from here, particularly in light of the IANA transition? CCWG-Accountability is struggling with that now, and will meet face-to-face in Paris, July 17-18. Stay tuned.

See also on Domain Mondo: IRP Panel in DCA Trust Case Overrules ICANN Bylaws Provision


2015-07-11

ICANN 53 Buenos Aires Recap, MarkMonitor video



ICANN 53 Buenos Aires Recap - Featuring MarkMonitor domain management and gTLD experts, Elisa Cooper and Matt Serlin. Published on Jul 9, 2015

Key Takeaways:
• New gTLD Program Status, Review and Next Round; Suspect Registry Pricing Practices
• Status of the IANA Transition and ICANN Accountability Working Group
• Governmental Advisory Committee (GAC) Communique

source: MarkMonitor | Brand Protection, Domain Management, Anti Piracy, Anti Fraud

Domain name: markmonitor.com


2015-06-08

Internet DNS Root Stability, New gTLD Domains, ICANN Study RFP

UPDATE: The fragilista. Frequently found spending a lot of time in ICANN meetings, they prefer to tinker with things they do not understand rather than doing nothing. They tend to mistake the unknown for the nonexistent. They lack humility and respect for the first law of ecology: we can never do merely one thing. Any action we take results in some unwanted consequences. We should avoid small, immediate, and visible benefits that introduce the possibility for large (and possibly invisible) side effects. Less is more. When we mess with an existing (complex) system we’re intervening; we can never do merely one thing. According to Nassim Taleb, the problem with the fragilista is that they “make you engage in policies and actions, all artificial, in which the benefits are small and visible, and the side effects (are) potentially severe and invisible.” An example is ICANN's new gTLDs policy and program--
"... [that] does not mean that 'adding hundreds of new entries per year to the root is safe.' Our ability to survey the regions in which discontinuities may lie for one or more of the root zone management functions is limited to assessment of risk, not absolute conclusions about 'safety'... 'Any increase in the size or volatility of the root zone involves risk' ... --Root Scaling Study Report (pdf) on the Impact on the DNS Root System of Increasing the Size and Volatility of the Root Zone (7 September 2009) (emphasis added) 
ICANN foolishly decided to expand the generic top-level domains (gTLDs) from just 22 gTLDs to more than 1300 new gTLDs (new generic top-level domains), without taking necessary prudent precautions, and yet knowing that new gTLD domain names would "break stuff" and "fail to work as expected on the internet" and could negatively impact the stability or security of the entire Internet DNS. So now ICANN has decided to issue a RFP (request for proposal) to determine "the impact of the New gTLD Program on the DNS root system." Here's the ICANN announcement:

ICANN Root Stability Study RFP: "The Internet Corporation for Assigned Names and Numbers (“ICANN”) is seeking one or more providers to conduct a technical study examining the impact of the New gTLD Program (the Program) on the DNS root system. Consistent with its mission supporting the security and stability of the Internet’s system of unique identifiers, ICANN will undertake an examination of the Program’s impact on the DNS root system. The selected provider(s) will design and execute one or more studies incorporating the collection and analysis of data from root server operators, historical performance data, data gathered from previous studies, and other tools and measures. ICANN is seeking one or more qualified providers to manage this complex exercise in a timely and efficient manner. A review of the [New gTLDs] Program for security and stability impact is a previous commitment based on advice from ICANN’s Governmental Advisory Committee [GAC] and other discussions. Specifically, ICANN committed to review the effects of the New gTLD Program on the operations of the DNS root system, and to postpone delegations in a future round until it is determined that the delegations in the 2012 round have not jeopardized the root system's security or stability.

"The goals of this study include, at a minimum:
  • Executing a thorough review of the impact of the Program on the security and stability of the DNS.
  • Identifying what steps, if any, should be undertaken as a prerequisite to adding more TLDs to the root zone.
  • Identifying what steps, if any, should be undertaken by the community going forward to assess the state of the root zone on an ongoing basis.
"For additional information, complete timeline, and instructions for submitting responses please click. [ZIP, 983 KB] Proposals should be submitted to RootStabilityStudy-RFP@icann.org by 23:59 UTC on 2 July 2015." (emphasis added)

The real question is whether ICANN will hire a professional and competent firm and allow it to assess and make determinations without undue influence or interventions from self-interested, self-serving "stakeholders" of the new gTLD domain names industry or its ICANN sycophants?

See also on Domain Mondo:


Domain Mondo archive