The ICA participated in responding to the United Nations, who had written a letter to the ICANN Board complaining about the IGO Working Group Final Report. The ICA was extensively involved in this Working Group and took issue with the UN’s complaints about the outcome. This Working Group spent four years examining the UDRP and how IGO’s and INGO’s could fairly access it. The response to the UN letter, submitted on August 16th, illustrates that the Final Report received support from a variety of stakeholders and that no new special dispute resolution system was required for IGOs and INGOs. For more information and to read full versions of the documents mentioned here, use the following links: Final Report, UN Letter and the Response: Group Letter to ICANN August 16 2018
Once again, as it was with .Travel, the vast majority of comments on the proposed renewal Registry Agreements (RAs) for the legacy .Cat and .Pro gTLDs are united in their opposition to imposition of Uniform Rapid Suspension (URS) and other new gTLD rights protection mechanisms (RPMs) by contract, arguing that this is a consensus policy decision that can only be fairly made through the policy development process (PDP).
Comments following this general line of reasoning were filed on .Cat by, among others, the Electronic Frontier Foundation, IP Justice, ICANN’s Business Constituency (BC) and Non-Commercial Stakeholders Group (NCSG) — and of course the ICA along with individual comments filed by ICA Board member Nat Cohen and ICA members Jay Chapman and Greg McNair.
As we saw with the comments on .Travel, the only commenters supporting URS by contract at legacy gTLDs were ICANN’s Intellectual Property Constituency (IPC) and new gTLD portfolio registry operator Donuts.
An identical list of commenters and positions appears at the comment forum for .Pro.
A Staff Report on the .Cat and .Pro comments is scheduled to be filed on July 21st. But odds are that these will be late, given that the due date for the staff report on .Travel comments was July 5th but all that appears at its website is this – “Report Overdue”. It’s difficult to understand why it is taking staff so long to complete and post that document, because that Staff Report is supposed to be an objective compilation and summary of the comments received – and not a defense brief to justify the staff action of proposing the inclusion of URS in these renewal RAs that has drawn such broad criticism and opposition.
We will continue to monitor the .Travel website, along with those for .Cat and .Pro, to see when those Staff Reports are filed and what they say.
Meantime, here is what ICA said in the additional comments we filed on both .Cat and .Pro:
This comment by the Internet Commerce Association incorporates by reference and supplements the comment letter we filed in regard to the proposed renewal registry agreement (RA) for .Travel on June 21st.
The issues are essentially identical, in that:
This issue of staff creation of de facto Consensus Policy arose several times at the just concluded ICANN 53 meeting held in Buenos Aires. At its opening session on Sunday morning, June 21st ICANN’s GNSO Council met with senior staff of ICANN’s Global Domains Division (GDD). Many Council members raised their own strong concerns about the staff action and its destructive impact on the GNSO’s role in making gTLD policy. GDD staff provided the weak response that “we did not push anyone to accept” the URS, maintaining that .Travel, .Pro, and .Cat registry operators had all “volunteered” to include it in their proposed renewal agreements. That justification strains credulity given that GDD staff proposed its inclusion as the starting point for registry agreement renewal.
As we stated in our comment letter regarding .Travel–
There can be no doubt that this is a staff attempt to create de facto Consensus Policy, as is clearly documented by the fact that the same objectionable provision appears in the proposed renewal RAs for .Cat and .Pro, both released for comment on May 28th. This evidences a deliberate and illegitimate attempt by contracting staff to create a series of precedents that would lead inevitably to the imposition of the URS on major legacy gTLDs such as .Org, .Net and .Com when they come up for renewal, despite the fact that the URS is not an ICANN Consensus Policy.
GDD staff also said they would change their position if the GNSO told them not to seek to impose new gTLD RPMs on legacy gTLDs – which is not only an impossibility for this proposed renewal RA, given the time required for the GNSO to establish policy via the standard PDP, but completely misunderstands and reverses the proper relationship between the stakeholders and staff. It is stakeholders who create ICANN policies through a bottom up process, which are subsequently administered by staff – not staff given free rein to initiate policy in a top down and unaccountable manner via contract negotiations until the stakeholders stop them.
The same concerns were raised when the Council met with the ICANN Board on the afternoon of June 21st, where they received a far more sympathetic reception. Several Board members agreed that staff should not initiate policy changes.
In addition to the concerns raised by Council members, and at community members at the Public Forum in Buenos Aires, the comments filed on .Travel ran overwhelmingly against incorporation of the URS in the renewal RA.
Only two comments supported the action by GDD staff to propose it as a starting point:
In closing, we repeat the conclusion of our comment letter regarding .Travel —
Consensus Policy regarding RPMs must be vetted within the community to assure a proper balancing of the interests and rights of both trademark owners and domain registrants.
In order to assure that balance two indispensable steps are necessary:
In addition, we repeat the request that ICA made directly to ICANN’s Board at the Buenos Aires Public Forum –
First, we need a commitment that any further alterations of the new gTLD RPMs will be made through a standard PDP. We are far past the implementation details stage and it is now crystal clear that these decisions will implicate legacy gTLDs as well.
Second, if GDD staff ignores the overwhelming weight of comments and retains the URS in the final RAs for legacy gTLDs, you need to vote up and down on those RAs. You need to “own” that decision and in that way indicate whether you believe this GDD staff action is or is not acceptable.
We hope that GDD staff will recognize that they have overreached on these legacy gTLD contracts and that the proper action is to strike the RPMs adopted from the new gTLD program from them and leave that decision to the multistakeholder community.
If staff does not do the right thing then we will press for an up and down Board vote on this and the other affected contracts before they take effect.
Philip S. Corwin
Counsel, Internet Commerce Association
The comment period on the proposed renewal registry agreement for the .Travel legacy gTLD closed on Sunday, June 21st and the comments submitted are overwhelmingly opposed to ICANN staff’s attempt to impose any of the new gTLD rights protection mechanisms, including Uniform Rapid Suspension (URS), on legacy gTLDs through contracting rather than a formal Policy Development Process (PDP).
In addition to ICA’s own comment (reproduced below) opposition to the contracting route were submitted by ICANN’s Business Constituency and Non-Commercial Stakeholders Group as well as the Electronic Frontier Foundation and IP Justice, plus numerous participants in the domain industry. The only outliers supporting this brazen attempt to detour around ICANN’s Bylaws were ICANN’s Intellectual Property Constituency and the Donuts new gTLD portfolio registry operator.
At its opening session on Sunday morning in Buenos Aires, ICANN’s GNSO Council met with senior staff of ICANN’s Global Domains Division (GDD). Many Council members raised their own strong concerns about the staff action and its destructive impact on the GNSO’s role in making gTLD policy. GDD staff provided the weak response that “we did not push anyone to accept” the URS, maintaining that .Travel, .Pro, and .Cat registry operators had all “volunteered” to include it in their proposed renewal agreements. That justification strains credulity given that GDD staff proposed its inclusion as the starting point for registry agreement renewal – and our friends in the registry and registrar community inform us that ICANN staff play serious hardball in closed door contracting negotiations. GDD staff also said they would change their position if the GNSO told them not to seek to impose new gTLD RPMs on legacy gTLDs – which of course will never happen for both procedural and internal political reasons.
The same concerns were raised when the Council met with the ICANN Board on Sunday afternoon, where they received a more sympathetic reception. Several Board members agreed that staff should not initiate policy changes – but there was no firm Board commitment to intervene against the staff action.
So while the battle has been joined its outcome is far from settled. ICA intends to raise this matter again at the Public Forum on Thursday afternoon. As stated in our comment letter, “if the decision is made by staff to retain these RPMs in the .Travel renewal RA following the close of the public comment period, we believe that the proposed final contract must be forwarded to, reviewed by, and voted upon by the ICANN Board”. In other words, the Board needs to “own” the final decision, and in that action demonstrate whether it is truly committed to the bottom-up consensus policy process.
Here’s ICA’s comment letter:
Philip S. Corwin, Founding Principal
1155 F Street, NW Suite 1050 Washington, DC 20004
202-559-8597/Direct 202-559-8750/Fax 202-255-6172/Cell
June 21, 2015
By E-Mail to firstname.lastname@example.org
Internet Corporation for Assigned Names and Numbers
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
Re: Proposed Renewal of .TRAVEL Sponsored TLD Registry Agreement
I am writing on behalf of the members of the Internet Commerce Association (ICA). ICA is a not-for-profit trade association representing the domain name industry, including domain registrants, domain marketplaces, and direct search providers. Its membership is composed of domain name registrants who invest in domain names (DNs) and develop the associated websites, as well as the companies that serve them. Professional domain name registrants are a major source of the fees that support registrars, registries, and ICANN itself. ICA members own and operate approximately ten percent of all existing Internet domains on behalf of their own domain portfolios as well as those of thousands of customers.
This letter addresses the Proposed Renewal of .TRAVEL Sponsored TLD Registry Agreement that was published for public comment on February 2, 2015.
Summary of Position
The ICA is strongly opposed to the inclusion of new gTLD rights protection mechanisms (RPMs), particularly Uniform Rapid Suspension (URS), in this renewal agreement (RA) for a legacy gTLD. We believe that this attempt by ICANN contracting staff to create de facto Consensus Policy via individual registry contract, absent a relevant Policy Development Process (PDP), is a glaring example of the type of top down, unaccountable action that should be targeted by enhanced accountability measures accompanying the IANA transition proposal. Contracts with legacy gTLDs can contain and enforce Consensus Policy, but it is an impermissible violation of ICANN’s Bylaws for contracts to attempt to create Consensus Policy.
We strongly urge that Section 2 of Specification 7 of the Renewal Agreement (RA) for .Travel, which contains the URS as well as the Trademark Post‐Delegation Dispute Resolution Procedure (PDDRP) be deleted in its entirety. Failure to take that action, and the resulting approval of a .Travel RA that contains these RPMs, will constitute a gross and unacceptable violation of ICANN Bylaws. We hope that contracting staff will promptly take the corrective action required on this matter.
However, if the decision is made by staff to retain these RPMs in the .Travel renewal RA following the close of the public comment period, we believe that the proposed final contract must be forwarded to, reviewed by, and voted upon by the ICANN Board. The potential addition of these RPMs to legacy gTLDs through this inappropriate avenue will have a substantial and deleterious effect on ICANN’s policymaking process going forward, will create a new and dangerous precedent whereby de facto Consensus Policy can be created by contractual fiat in violation of ICANN Bylaws, and will substantially and adversely affect third parties around the world consisting of the existing registrants of more than one hundred million legacy gTLD domains.
Unaccountable and Uninformed Top Down Policymaking is Unacceptable
On May 13, 2015 I had the honor and privilege of addressing the Subcommittee on Courts, Intellectual Property, and the Internet of the Judiciary Committee of the U.S. House of Representatives. I spoke on ICA’s behalf at the Subcommittee’s hearing on “Stakeholder Perspectives on ICANN: The .Sucks Domain and Essential Steps to Guarantee Trust and Accountability in the Internet’s Operation”.
In my oral statement before the Subcommittee I said the following:
While enhanced ICANN accountability measures are overdue they will operate best only if ICANN’s Board and senior staff embrace a culture of accountability that assumes responsibility for the fallout of ICANN decisions and encompasses early consultation with the multistakeholder community that provides organizational legitimacy.
The current situation regarding the proposed renewal RA for the .Travel gTLD is a perfect illustration that a ‘culture of accountability’ that includes proper deference to the multistakeholder community and to the letter and spirit of ICANN’s Bylaws is presently lacking at ICANN. That is extremely dismaying and disheartening, especially for those who believe in the multistakeholder model (MSM) of governance for the unique experiment in technical DNS management known as ICANN.
When the Applicant Guidebook for the new gTLD program was being drafted I was extensively engaged on ICA’s behalf in the vigorous community debate over its RPMs. Throughout their development by the IRT, STI-RT, and then the full community I repeatedly inquired of other stakeholders as well as ICANN senior staff whether adopting these RPMs as new gTLD program “implementation details” would in any way result in their automatic application to legacy gTLDs like .Com. I received repeated assurances that this would not occur – that the RPMs could be imposed on legacy gTLDs only after their impact and efficacy was fully assessed, and then only via a standard PDP to create new Consensus Policy in conformity with ICANN Bylaws.
The present proposal to impose the URS on .Travel is a betrayal of those assurances and a clear violation of ICANN’s Bylaws. The rationale for this decision – “With a view to increase the consistency of registry agreements across all gTLDs, ICANN has proposed that the renewal agreement be based on the approved new gTLD Registry Agreement as updated on 9 January 2014.” – is flimsy and unconvincing. ICANN staff possesses no legitimate authority to create and impose what amounts to Consensus Policy. Proposing that the RA take the new gTLD RA as its starting point is tantamount to creating Consensus Party given the overwhelming negotiating advantage that ICANN has in such a context.
There can be no doubt that this is a staff attempt to create de facto Consensus Policy, as is clearly documented by the fact that the same objectionable provision appears in the proposed renewal RAs for .Cat and .Pro, both released for comment on May 28th. This evidences a deliberate and illegitimate attempt by contracting staff to create a series of precedents that would lead inevitably to the imposition of the URS on major legacy gTLDs such as .Org, .Net and .Com when they come up for renewal, despite the fact that the URS is not an ICANN Consensus Policy. Acting in a manner that is consistent with ICANN’s Bylaws is far more important than consistency of RAs – if that latter principle had been paramount then there would be no RPMs at new gTLDs to begin with because they are inconsistent with the Consensus Policy in effect at legacy gTLDs.
This staff decision is all the more troubling because it was made in an irresponsibly uninformed manner without waiting for a full evaluation and identification of issues concerning the new gTLD RPMs. On May 1st the public comment period on “Draft Report: Rights Protection Mechanisms Review” (https://www.icann.org/public-comments/rpm-review-2015-02-02-en) closed, and on May 29th ICANN staff issued a “Report of Public Comments” (https://www.icann.org/en/system/files/files/report-comments-rpm-review-29may15-en.pdf) based upon community input. The Background on that Draft Report states that it “is intended to be available to inform the Issue Report requested by the GNSO as well as the independent review of Trademark Clearinghouse recommended by the GAC. In addition, this paper will serve as input to the Review Team on Competition, Consumer Trust, and Consumer Choice to be convened under Section 9.3 of the Affirmation of Commitments, charged with assessing the effectiveness of the safeguards developed for the New gTLD Program.”
None of these additional reviews have been completed. Further, one of the major reasons that the GNSO requested the referenced Issue Report was so that GNSO’s stakeholders could decide whether those RPMs should become Consensus Policy for all gTLDs. And that Issue Report will not even be delivered until late September because policy staff requested a six-month extension of the delivery date so that additional studies and analysis could be conducted – and the GNSO Council granted that request on January 29th of this year. Yet this near-total lack of evaluated data regarding the performance of the RPMs seems not to have mattered to contracting staff.
Policy and Implementation Considerations
The recently published Final Report on Policy and Implementation (P&I) (https://community.icann.org/display/PIWG/Final+Report+Redline+Version) is also germane to this discussion. That Report, issued with the full consensus support of its working group, defines a “GNSO Consensus Policy” (p.9) as “A Policy established (1) pursuant to the procedure and required minimum elements set forth in ICANN’s Bylaws, and (2) covering those topics listed in Section 1.2 of the consensus policies and temporary policies specification of the 2013 RAA (see Annex I) or the relevant sections in the gTLD registry agreements (see Annex II). GNSO Consensus Policies, adopted following the outlined procedures, are applicable and enforceable on contracted parties as of the implementation effective date.” (Emphasis added)
The PDDRP and URS both fit within the cited topics but have not been adopted pursuant to the outlined procedures for stablishing Consensus Policies. Therefore, their imposition by contractual fiat on legacy gTLDs is clearly in violation of the procedural path and required minimum elements set forth in the Bylaws.
In addition, the P&I Report adopts as its first principle that “Policy development processes must function in a bottom-up manner. The process must not be conducted in a top-down manner and then imposed on stakeholders”. Yet in this instance we have ICANN staff engaged in imposing policy from the top down, first on registries and through them onto registrars and registrants. This is absolutely unacceptable. The one exception to that first principle, “emergency cases such as where there are risks to security and stability”, bears no relationship to the RPMs at issue.
Finally, the P&I Report states a first standard, which is “As outlined in the ICANN Bylaws, the GNSO is responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains. As such, gTLD policy development should not take place outside of the GNSO.” (Emphasis added) That standard has been grossly violated by the proposed RA as it imposes staff-dictated policy decisions on legacy gTLDs absent any GNSO involvement.
Unfair Impact on Registrants
Registrants at new gTLDs had clear notice that they would be subject to the new RPMs. Registrants at legacy gTLDs expect that they shall only be subject to Consensus Policy adopted in accordance with ICANN’s Bylaws. The proposed RA is a complete betrayal of that legitimate expectation and is totally at odds with ICANN rhetoric in support of registrant rights. It is also likely to raise legality of enforceability issues if there is any attempt to enforce new gTLD RPMs against registrants at legacy gTLDs absent their adoption via Consensus Policy.
The danger for legacy gTLD registrants is compounded by the fact that the URS that staff is trying to impose today may differ materially from what the URS becomes in the next few years. In this regard, the Report of Public Comments on the “Draft Report: Rights Protection Mechanisms Review” was released on May 29th.
The Report’s URS section makes clear that some parties would like Uniform Rapid Suspension converted into Uniform Rapid Transfer, with additional tweaks that would put domain registrants at a substantial disadvantage in URS proceedings.
Among the ideas suggested for the URS by various commenters were:
Taken collectively, these suggestions would undo whatever rough balance between rights holders and registrants was achieved in the creation of the URS. They make clear that the URS could be changed in the future to become an accelerated, lower-cost version of the UDRP, with the same burden of proof plus a domain transfer option. Those two changes alone would probably cause a mass shift from UDRP filings to URS by trademark owners – thereby converting the URS from its intended use as a narrow supplement to the UDRP to a complete substitute for it. Registrants would have less time to respond, shorter word limits in which to state their replies, and be denied the option of requesting a three member expert panel. Other potential changes could be adoption of a loser pays requirement, requiring registrants to pay a response fee in all cases, and changing what must be proved by complainant to bad faith registration or use.
ICA is sensitive to some legitimate concerns of trademark owners regarding the effectiveness of the URS and we have suggested means to address those concerns without undermining registrant rights. But proposals such as those listed above illustrate that the staff attempt to put the URS in place at legacy gTLDs via contractual fiat puts the cart far before the horse. We must know what the URS is going to be before we can consider its impact on legacy gTLD registrants and debate whether it should be adopted as Consensus Policy.
It is also a dangerous and destructive approach. If staff can succeed in this effort, and if the URS is then modified for new gTLDs though a non-PDP “implementation” route, that modified URS would automatically take effect at legacy gTLDs with contract provisions such as the one that staff is attempting to impose on .Travel . The result would be a radically different URS effectively put in place at legacy gTLDs absent any compliance with ICANN Bylaws pertaining to Consensus Policy.
Consensus Policy regarding RPMs must be vetted within the community to assure a proper balancing of the interests and rights of both trademark owners and domain registrants.
In order to assure that balance two indispensable steps are necessary:
In addition, any suggestion that legacy gTLDs can “voluntarily” adopt new gTLD RPMs that have been proposed by ICANN staff in the course of renewal RA negotiations should be rejected as specious, given the differential in bargaining leverage between a registry operator in need of a RA and ICANN staff with the power to approve or deny it.
We appreciate the opportunity to provide these comments on the proposed renewal RA for .Travel.
For all the reasons outlined above, the attempted imposition of new gTLD RPMs on this legacy gTLD are absolutely unacceptable and in gross violation of ICANN Bylaws. They must be stripped out of the RA and reserved for consideration in a future PDP by the full ICANN multistakeholder community.
While much is at stake for legacy gTLD registrants, ICANN’s own credibility is also on the line in this instance. At a time when enhanced accountability measures are being designed, a successful end run around the PDP requirements for establishing Consensus Policy would suggest the need for even stronger accountability measures than those presently under consideration. Fortunately, the accountability process will still be ongoing when ICANN decides whether to withdraw this illicit action or double down in its pursuit.
Philip S. Corwin
Counsel, Internet Commerce Association
The Electronic Frontier Foundation (EFF) has just told ICANN to drop the notion of applying the Uniform Rapid Suspension (URS) dispute resolution system to .Travel and other legacy gTLDs without undertaking a full Policy Development Process (PDP).
In a June 12 letter, EFF stated:
ICANN should not apply URS to the .travel domain, or to any additional domains, by the unaccountable means of staff inserting new conditions into the renewal of the registry operator’s contract. Rather, the public policy implications of such a move demand that a full PDP be undertaken first.
EFF’s letter also states:
The introduction of the URS, in response to a 2009 recommendation from the new gTLD program’s Implementation Recommendation Team (IRT), was characterized (however dubiously) as an implementation detail of the new gTLD program…The URS never became a consensus policy that would be applicable across all gTLDs…If the URS is to be extended to legacy domains such as .travel, this would place many further domains at risk of rapid suspension, which raises significant free speech concerns. It would also set a bad precedent for the extension of the URS to other legacy domains such as .com, .net and .org as their registries’ contracts come up for renewal.
ICANN contracting staff decided to impose the URS on .Travel based upon the misguided notion that it was more important “to increase the consistency of registry agreements across all gTLDs” than to act consistently with ICANN’s Bylaws. They didn’t even wait for their colleagues in the policy department to deliver the ‘Issues Report on new gTLD RPMs’ to the GNSO Council this coming September. One of the reasons the GNSO Council requested that report was so the GNSO could decide if those RPMs should become Consensus Policy for all gTLDs.
And it’s not just .Travel targeted by this staff power grab. Two weeks after publishing that proposed Registry Agreement (RA) ICANN published the proposed RAs for .Cat and .Pro, which also contain the URS. You can draw a dot-ted line through those registries that brings the URS to .org, .net and .com when they come up for renewal as de facto, staff-determined policy absent any demonstrated community consensus.
And when the URS reaches those big legacy domains, what will it look like? A review of the Report of Public Comments on the “Draft Report: Rights Protection Mechanisms Review” makes clear that if certain interests have their way the URS could be changed in the future to become an accelerated, lower-cost version of the UDRP, with the same burden of proof plus a domain transfer option. The result of transforming URS into URT (Uniform Rapid Transfer) would be more opportunities for domain hijackers and far less due process for domain registrants.
Whether the URS should change, much less if it should become a consensus policy for legacy gTLDs, are important policy decisions that should be decided by ICANN’s multistakeholder community through the standard PDP – not imposed in an unaccountable top down manner by ICANN staff.
EFF has made a valuable contribution to ICANN accountability by expressing its strong opposition to this high-handed attempt to short-circuit proper decision-making procedures. Let’s hope that more organizations and individuals speak out while the public comment period on these RAs remain open — and at the upcoming ICANN meeting in Buenos Aires.
In another unpredicted development the entire community of ICANN stakeholders has sent a joint letter to CEO Fadi Chehade and the ICANN Board that strongly questions the “Enhancing ICANN Accountability and Governance – Process and Next Steps” document published by ICANN staff on August 14th over widespread community objections. Signatories to the August 26th letter (text below) include the GNSO Council and all of the GNSO’s stakeholder groups and constituencies, the Country Code Name Supporting Organization, the At-Large Advisory Committee, the Security and Stability Advisory Committee – and, most surprisingly, the Governmental Advisory Committee.
The letter states that “substantial questions and concerns remain unanswered, including around the process to date and the plan as constructed” and promises to deliver a “list of clarifying questions and comments within seven days” so that the signatories “not only understand the proposed approach, but are able to endorse it”. In other words, the current Accountability Process lacks the endorsement of any stakeholder group within ICANN.
In addition to this letter and the detailed questions to be delivered to ICANN next week, a number of ICANN stakeholder groups are preparing to file a formal Reconsideration Request to ICANN’s Board by the required 14-day (August 28) deadline in which the Board will be asked to review and reverse or modify the staff plan on the grounds that both its substance and the process by which it was created have materially harmed their interests. In an ironic twist those stakeholders are requesting that the Board hold the staff accountable for the alleged violations arising from publication and adoption of this non-endorsed Accountability Process.
Comments filed with ICANN as well as other community input indicated a strong preference for the establishment of a standard Cross-Community Working Group (CCWG) to develop the vital enhanced accountability measures that are supposed to accompany any proposal for facilitating the IANA functions transition away from US control, with experts available to facilitate the work of that CCWG at its request. Instead, ICANN’s staff are trying to unilaterally impose an overly complicated tripartite construct that resembles a Rube Goldberg machine.
The staff proposal would segregate community discussion into an Accountability & Governance Cross Community Group that would have a restricted ability to appoint participants to the Accountability & Governance Coordination Group in which the real decisions would be made, and which would issue a final report and recommendations. Meanwhile, a separate Accountability & Governance Public Experts Group (PEG) would appoint up to seven “experts” to the decision-making group. Many within the ICANN community view the proposed structure as designed to dilute the strength of any final recommendations for new enhanced accountability measures; especially the establishment of an independent appeals mechanism with the power to reverse decisions that violate ICANN Bylaws, and to discipline Board members and staff. It is highly doubtful that anything as robust as the “KEY PRINCIPLES FOR COORDINATION OF INTERNET UNIQUE IDENTIFIERS” that are attracting increasing support among Internet companies, trade associations, and civil society could ever emerge from such a process.
In addition, the staff-imposed Process contains this key language:
Following public comment, the Coordination Group will submit its final report to the ICANN Board. The ICANN Board will immediately and publicly post the final report, consider whether to adopt all or parts of it, and direct the CEO to implement those parts it has accepted once that decision is made. ICANN staff should be involved in assessing feasibility and flagging implementation concerns as early as possible in the recommendation development process to allow for alternatives to be identified. To be clear, ICANN’s goal is to have this work develop recommendations that are capable of implementation, and not solely to go through the exercise of a review. Any decision by the Board to not implement a recommendation (or a portion of a recommendation) will be accompanied by a detailed rationale.
As described, ICANN staff will have free rein to assess “feasibility” and to flag “implementation concerns” throughout the process, and the Board will be able to cherry-pick the final recommendations and reject anything it cares to, with no standard for rejection and subject only to the requirement that it provide some rationale for its decision. It is almost impossible to envision anything that imposes enhanced accountability and binding disciple on the Board and staff resulting from such a Process.
On August 19th, five days after imposing this Process as a fait accompli without any opportunity for public comment, ICANN announced the members of the PEG. They are:
It is particularly disquieting to see Secretary Strickling on this list as it may be viewed by some parties as implying US government endorsement and support for an ICANN staff-originated Process that was imposed over the objections and concerns of ICANN community leaders and that has subsequently elicited widespread pushback from the entire community. This is not how the much vaunted multistakeholder model is supposed to operate.
Just two months ago all of the GNSO constituencies issued a joint statement at ICANN’s London meeting in which they called for “the Board to support community creation of an independent accountability mechanism that provides meaningful review and adequate redress for those harmed by ICANN action or inaction in contravention of an agreed upon compact with the community” and asked “the ICANN Board and Staff to fulfill their obligations and support this community driven, multi-stakeholder initiative”.
Instead of supporting the community’s desire for an Accountability CCWG, the staff has indicated its apparent mistrust of the community through this attempt to impose its own Accountability Process that many believe will dilute any final recommendations — and even then allow the Board to reject any of them for any reason whatsoever. That staff attempt has resulted in this new and broader message to ICANN that extends well beyond the boundaries of the GNSO, including the GAC. It appears that ICANN’s staff is driving unprecedented unity within the ICANN community – unfortunately, that unity is based on unanimous and extremely serious concerns about staff actions on a matter of overarching importance.
The road ahead on Accountability will either follow the flawed path developed by staff – with active community participation in substantial doubt – or, even if significant modifications are achieved through united community resistance, the forthcoming Process may well be marred by lingering mistrust as a result of this high-handed staff action. All of this is very unfortunate and was totally avoidable if ICANN had simply allowed for bottom-up development and made adequate solicitation of public comment before adopting a final Accountability Process.
The text of the letter follows:
August 26, 2014
Fadi Chehadé, CEO, ICANN
Dr. Stephen Crocker, Chair, ICANN Board of Directors
Dear Fadi, Steve and ICANN Directors,
Regarding ICANN’s announcement on August 14, 2014, Enhancing Accountability: Process and Next Steps, the Supporting Organisation, Advisory Committee, Stakeholder Group and Constituency chairs formally request additional time and opportunity to review and discuss the proposal contained in the announcement and in the subsequent FAQ’s published on August 22, so that next steps can be confirmed with increased support from the ICANN community.
Recognizing that the ICANN plan is a brand new construct that was announced without a corresponding public comment period, substantial questions and concerns remain unanswered, including around the process to date and the plan as constructed.
The undersigned Supporting Organisation, Advisory Committee, Stakeholder Group and Constituency leaders are currently engaging our respective groups’ bottom-up, consensus processes at this time to develop and finalize a list of questions that will require clarification or correction. As a result, additional opportunity is needed to ensure understanding of the proposal and the ways in which it is responsive to the interests and working methods of the ICANN stakeholder groups. We commit to submitting to ICANN staff our list of clarifying questions and comments within seven days of this letter.
Since the Enhancing Accountability process will affect ICANN’s future, as well as the range of stakeholders impacted by its decisions, we trust that this request will be received positively and lead to further engagement on this important matter to ensure that the SOs, ACs and SGs and Cs not only understand the proposed approach, but are able to endorse it.
Elisa Cooper, Commercial Business Users, Commercial Stakeholder Group
Olivier Crépin-LeBlond, At-Large Advisory Committee
Rafik Dammak, Non-Commercial Stakeholder Group
William Drake, Non-Commercial Users
Keith Drazek, Registry Stakeholder Group
Heather Dryden, Governmental Advisory Committee
Patrik Fältström, Security and Stability Advisory Committee
Byron Holland, Country Code Names Supporting Organization
Tony Holmes, Internet Service Providers, Commercial Stakeholder Group
Michele Neylon, Registrar Stakeholder Group
Jonathan Robinson, Generic Names Supporting Organization Council
Kristina Rosette, Intellectual Property, Commercial Stakeholder Group
In an unprecedented development, all stakeholder groups and constituencies comprising ICANN”s Generic Names Supporting Organization (GNSO) unanimously endorsed a joint statement in support of the creation of an independent accountability mechanism “that provides meaningful review and adequate redress for those harmed by ICANN action or inaction in contravention of an agreed upon compact with the community”. The statement was read aloud during a June 26th session on the IANA transition process held on the last day of the ICANN 50 public meeting in London.
The creation of this new accountability structure is meant to accompany the transition of the IANA functions away from US control and is intended to encompass accountability issues beyond those that are IANA-specific. Business, intellectual property, and civil society members of the GNSO will likely be delivering the message to Congress and the NTIA that creation of this new accountability mechanism must be assured before any final action is taken on an IANA transition plan developed within ICANN’s multistakeholder community.
During an earlier session on ICANN accountability, ICA Counsel Philip Corwin delivered remarks emphasizing that there was a preexisting need for improved ICANN accountability and transparency independent of the IANA transition, but that the contemplated termination of US counterparty status in regard to the IANA contract presented the opportunity and increased the need for establishment of an independent review and redress mechanism to address ICANN actions. He noted that ICANN’s fairly unique combination of public policy functions and substantial self-funding capabilities created an enhanced need for measures that could address the substantial potential for self-dealing behavior by the organization.
Here is the full text of the unanimous GNSO statement:
The entire GNSO join together today calling for the Board to support community creation of an independent accountability mechanism that provides meaningful review and adequate redress for those harmed by ICANN action or inaction in contravention of an agreed upon compact with the community. This deserves the Board’s serious consideration – not only does it reflect an unprecedented level of consensus across the entire ICANN community, it is a necessary and integral element of the IANA transition.
True accountability does not mean ICANN is only accountable to itself, or to some vague definition of “the world,” nor does it mean that governments should have the ultimate say over community policy subject to the rule of law. Rather, the Board’s decisions must be open to challenge and the Board cannot be in a position of reviewing and certifying its own decisions. We need an independent accountability structure that holds the ICANN Board, Staff, and various stakeholder groups accountable under ICANN’s governing documents, serves as an ultimate review of Board/Staff decisions, and through the creation of precedent, creates prospective guidance for the board, the staff, and the entire community.
As part of the IANA transition, the multi-stakeholder community has the opportunity and responsibility to propose meaningful accountability structures that go beyond just the IANA-specific accountability issues. We are committed to coming together and developing recommendations for creation of these mechanisms. We ask the ICANN Board and Staff to fulfill their obligations and support this community driven, multi-stakeholder initiative.