Text

Registrar Stakeholder Group position on multistakeholder participation threatens ICANN.

More than .xxx; 

More than new gTLDS;

More even than the GAC on the issue of ‘sensitive strings’;

The Registrars’ attitude on the process of negotiating changes to the Registrar Accreditation Agreement (RAA) is, in my opinion, the greatest threat to the ICANN model.  

The Registrars have flatly refused to allow members of the ICANN community to participate in the negotiations on possible amendments to the RAA.  They have even refused access to the members of the GNSO Non Contracted Parties to these negotiations as observers.  This is a rejection, I believe, of the fundamental nature of ICANN, and is a most pernicious threat to ICANN’s ability to do its job properly.

Not only have the Contracted Parties prevented the acceptance of a Working Group Report that recommends adding observers to the group, they have stated flatly and unequivocally, that even if the GNSO were to succeed in a motion to allow Observers, they would not agree and would not participate in any discussion that included observers.

The Registrars insist on negotiating with ICANN Staff in a secret back room with no one watching.  True they plan to give periodic reports, but these are no substitute for participation.

This goes against every ICANN requirement for transparency.  This also goes against the fundamental ICANN bargain that allows the contracted parties to have a voice in their regulation in exchange for the participation of those who are affected by the contracts - the Commercial and Non Commercial Users of the DNS as well as the community at large.

In refusing so absolutely, the Registrars are challenging the fundamental agreements that give ICANN legitimacy and precipitating a real crisis in the multistakeholder fabric of ICANN.

The basis of the Registrar refusal, as I understand it, is that the contract is between the Registrars and ICANN.  As such having a bunch of interlopers observing, commenting and possibly even having a position, is something they will just not abide. No discussion or compromise on this issue will be brooked.

There have been several startling statements of this refusal that have been made verbally and that can be found in various meeting transcripts.  One clear statement was made on the GNSO list:

Begin forwarded message:

From: “Tim Ruiz” <tim@godaddy.com>

Date: 8 March 2011 22:41:09 PST

Cc: council@gnso.icann.org

Subject: RE: [council] RAA Motion

As I’ve tried to point out before, this is a waste of time. The RAA is between ICANN and Registrars and only they will decide how the process takes place. And as was made clear to the RAA WG, Registrars will not engage if observers are present. All the Council should do at this point is thank the WG and let Registrars and Staff take from it there.

Tim

So the question comes down to: Who is ICANN?

The easiest and most complete answer: ICANN is us.

ICANN is not just the CEO.

ICANN is not just the Operational Staff.  

ICANN is not just the Registrar Support Staff.

ICANN is not just the General Counsel.

ICANN is the multistakeholder organization as defined by the Articles of Incorporation, the Bylaws and even the Registrar Accreditation Agreement.

If you go to About ICANN on the web site you see:

ICANN was formed in 1998. It is a not-for-profit public-benefit corporation with participants from all over the world dedicated to keeping the Internet secure, stable and interoperable. It promotes competition and develops policy on the Internet’s unique identifiers.

You will also see an organizational chart that shows that ICANN Staff is but one part of ICANN.  

In the Bylaws one sees that:

Except as otherwise provided in the Articles of Incorporation or these Bylaws, the powers of ICANN shall be exercised by, and its property controlled and its business and affairs conducted by or under the direction of, the Board.

ICANN and its constituent bodies shall operate to the maximum extent feasible in an open and transparent manner and consistent with procedures designed to ensure fairness.

In carrying out its mission as set out in these Bylaws, ICANN should be accountable to the community for operating in a manner that is consistent with these Bylaws, and with due regard for the core values set forth in Article I of these Bylaws.

In other words, in all it does ICANN is governed by its bylaws, which includes accountability to its community as one of the constituent parts defined in the bylaws.

Also, in all it does ICANN is governed by its commitment to transparency.  Secret negotations without observers are not transparent by any definition of the word.

In the Articles of Incorporation it says:

4. The Corporation shall operate for the benefit of the Internet community as a whole, carrying out its activities in conformity with relevant principles of international law and applicable international conventions and local law and, to the extent appropriate and consistent with these Articles and its Bylaws, through open and transparent processes that enable competition and open entry in Internet-related markets. To this effect, the Corporation shall cooperate as appropriate with relevant international organizations.

Again, the primary importance of openness and transparency in it operations consistent with the Bylaws.

(Note I included the entire quote to remind people about the commitment to International Law, something that can’t be done often enough and something that is also frequently denied by US national ICANN participants - but that is another discussion)

It is also intersting to note that the current versions of the RAA says:

2.3 General Obligations of ICANN. With respect to all matters that impact the rights, obligations, or role of Registrar, ICANN shall during the Term of this Agreement:

2.3.1 exercise its responsibilities in an open and transparent manner;

2.3.2 not unreasonably restrain competition and, to the extent feasible, promote and encourage robust competition;

2.3.3 not apply standards, policies, procedures or practices arbitrarily, unjustifiably, or inequitably and not single out Registrar for disparate treatment unless justified by substantial and reasonable cause; and

2.3.4 ensure, through its reconsideration and independent review policies, adequate appeal procedures for Registrar, to the extent it is adversely affected by ICANN standards, policies, procedures or practices.

So ICANN is committed to transparent operation in all matters related to the registrars. That is, no secrets.  Not only is it illegitimate for the Registrars to demand a private negotiation with ICANN Staff, it is against the rules for ICANN Staff to agree to such a situation.

This clause also indicates, by its reference to reconsideration and independent review, that the RAA process is part of other ICANN processes and not some special exception to normal ICANN processes.

The RAA is an agreement between the Registrars and Internet Corporation for Assigned Names and Numbers, the California non-profit, public benefit corporation. The nature of that non-profit, public benefit organization is defined in the Bylaws, and neither the Registrars nor ICANN Staff can subvert that definition, and the rights of the stakeholders, without risking the destruction of one of the most fundamental basis of ICANN.

I hope that the Registrars find the wisdom to end their destructive behavior.  I also hope the ICANN Staff has the sense not to enter into secret negotiations with the Registrars that exclude the rest of ICANN - the community that makes ICANN what it is.


Text

Incumbent ICANN Registrars & Registries create roadblocks to assisting gTLD applicants from developing economies.

Despite protestations to the contrary made at the beginning of the GNSO meeting in Cartagena about how much the incumbent Registries and and Registrars of the Contracted Parties House (CPH) care about helping gTLD applicants from developing economies, it is my opinion that they are seeking to cripple the group trying to provide a framework for development aid to applicants for new gTLDs from developing economies.

Background

Early in process of creating a new gTLD program, concerns were raised that the program was not being sufficiently supportive of people from developing economies. These issues always got a polite nod of the head, and then the process moved on.  The final recommendations from the GNSO had very little to say about development support.  And as member of the group that came up with these recommendations, I am ashamed that our work product missed that critical point.  We worried about so many things, including intellectual property, morality and public order, protecting the reputation of minority communities, and protecting the interests of the incumbents. But in the end we said nothing about helping applicants from developing economies; the only possible mention of helping anyone was in the sub-text of what might happen with the windfall topics from auctions, should that be the method picked by the staff for deciding between contenting applications - as if there was any chance they would have chosen another method. Of course we did not know at that time that the expense for applications would be an order of magnitude greater than it had been in the previous round, but still we did not think of developing economy applicants.  This is something that ICANN must remedy, and some people are working hard to do so.

It became obvious that something needed to be done when the first implementation drafts, aka Draft Applicant Guidebooks or  DAG, appeared with price tags such as $185,000 USD for an application for a single name in addition to over-specified financial and technical obligations that would cost hundreds of thousands of USD. While these were seen as possibly reasonable for a technology entrepreneur with a Marina del Rey wallet, they were obviously prohibitive for anyone from a developing economy.  The Government Advisory Committee (GAC) was the first to raise the alarm at the way the program was being shaped. In May and August of 2009, the GAC raised the issue that the costs were prohibitive for the developing world.  For the most part their early warnings were ignored, after the appropriate nod of concern. It took until 13 March 2010 for there to be a Board resolution mandating that something be done to solve the problem of making the new gTLD program accessible to applicants from developing countries. That is, 5 years into the program, just before the end of the process, support for developing economies became a concern.  Late, but at least it happened.

As a result of the Board resolution the Joint AC/SO (Advisory Committee, Supporting Organization) Working Group for support of gTLD applicants (JAS WG for short) was created. Within 10 months of meeting twice weekly or more, this group created a package of recommendations for ways in which applicants from developing economies could be helped.  The types of assistance recommended for qualifying applicants include:

  • Application fee cost reduction
  • Sponsorship and other funding support
  • Modification to the continued financial support mechanism
  • Logistical support
  • Technical Support
  • Exception to rules concerning the separation of of Registries and Registrars.

It is important to note that this was a unified package that was the result of a bottom-up effort of many people, including participants from developing economies of what could be done.  These recommendations are available online in the 6 UN Langauges.

The idea was that different types of aid would be required for different applicants.  It was also the recommendation that ICANN volunteers and staff would work together to create the process for providing the aid.  Time is short, and we all need to pitch in to reach this important goal.  One of the important tasks has to do with fund raising and distribution.  One of the special concerns in fund distribution, including any auction windfall profits mentioned above, is that management of these funds not become part of ICANN’s budget management. Especially when it came to the windfall from auctions, these were not to be lost inside the ICANN budget, but rather be applied to helping new gTLD applicants with the multi-year expenses required by the new gTLD program.  Additionally, it was understood that the prospect of raising funds to help new applicants would also need to be handled separately from ICANN funds. It was, therefore, recommended that in order to both raise monies that could be given in aid and to handle any auction monies, an external fund of some sort would need to be established as soon as possible in order to be ready by the time the new gTLD process started.

The JAS WG knows what work needs to be done and is ready to do it - though they are looking for more volunteers to do the work (hint, hint). It was time for next steps.

Both the ICANN Board of Directors and the GAC encouraged the JAS WG to keep working and to take those next steps in their work, i.e actually figuring out how to do what it was recommending be done.  To this end the ALAC approved a motion to extend the charter so that it could do exactly that.  As the second of its chartering organizations, the GNSO Council, was also asked to approve a motion extending the charter of the working group.  It was at that point that the Contracted Parties House (CPH), composed of incumbent Registrars and Registries originally informed the JAS WG chairs that they would unanimously vote against the proposed charter.  After a set of conversations meant to try and find a compromise with the CPH, and with no attempt by the CPH to compromise, they eventually offered an alternate motion that, if approved, will cripple the efforts of the JAS WG.

Why is the CPH motion so crippling

(Note the text of all of the motions is included below)

In the charter extension approved by the ALAC there is a work item assigned to each of the recommendations made by the JAS WG.  In the incumbent CPH proposal they have removed half of the work items.  Instead of mandating the JAS WG to propose methods for fulfilling all of the recommendations, they only mandate the JAS WG to:

  • Propose criteria for defining need;
  • Propose methods for determining need;
  • Propose methods to determine what sort of aid applicants should get;
  • Make proposal how applicants could go about seeking aid.

These are of course important and do match some of the work items in the charter approved by the ALAC; about half of them.  They left out, however, any further work to raise funds, to find methods to deal with funds or methods to actually provide assistance.  Instead they want the JAS WG to propose a way to determine who needs aid, to determine what sort of aid they need and then to tell them how to go pull themselves up by their own boot straps.  The want to bar the group from doing any work that might actually provide any sort of aid.  That is what I mean by crippling the effort.

Without making any assumption about the intentions of the incumbents in the approach they take, the approach they are offering is the neo-colonial way of doing things. Instead of giving people the leg up they need to start a registry in a developing country, the type of aid that would be provided would restrict helping the applicants find a northern partner to help them. Instead of helping the applicant from a developing economy with lower fees, grants or loans that would help them do a local start-up registry service provider or to gain accreditation as a registrar, the proposal only provides help with pointers on where to find incumbent registry service providers, top-level domain consultants, translators, and technicians.  And while this a form of aid the JAS WG suggests, it should not be the only type of aid available.

I believe that the CPH motion go one step further.  In paragraph 4 of their proposed motion it declares that the JAS WG must not report to anyone other than the chartering organizations (the GNSO Council and the ALAC) and seeks to restrict the JAS WG from communicating directly with the ICANN Board, the GAC or the community at large.  The incumbent Registrars and Registries in the GNSO want to force all communications through a military style chain of command that goes through them.  This top-down control is wholly inappropriate in a bottom-up organization.  Yes, the chartering organizations are asked to endorse the work and are responsible for managing the process to make sure that it is inclusive, fair and transparent; but they are not empowered to restrict the ability of a WG to communicate as it sees fit with other parts of the organization.

A final thing I need to explain is why I believe that this crippling motion is the responsibility of the entire Contracted Parties House of incumbent Registries and Registrars instead of just the responsibility of the council members who made the motion and seconded it. These stakeholder groups engage in the practice of voting in blocks where their council representatives are not permitted an individual vote, but must vote as the leadership in the stakeholder groups have decided.  I was informed by both incumbent groups, the Registries Stakeholder Group and the Registrars Stakeholder Group, that they would vote against the charter approved by the ALAC and can only assume that the new motion made and seconded by CPH council members is one that both incumbent stakeholder groups in the CPH will support.

Having been the co-chair of the JAS WG during the first half of its work, though I have since been replaced by a new co-chair from a developing economy, I am very sad to see the work we did possibly rendered useless by these actions on the part of the Registries and Registrars.  I am concerned that the conflict over the motion has more to do with the CPH not understanding the priorities of a development agenda and the responsibilities of Northern wealth, than any sort of mean spirit. During the recent meeting in Cartagena, while I was explaining the work of the JAS WG, many good and sincere GNSO members from registries and registrars came up to me and explained that they had worked hard, started from nothing and had pulled themselves up by their own bootstraps.  They saw no reason why those from developing countries should not do the same.  They did not see that the needs of those in developing economies are special.  They did not understand that it was incumbent on the rest of us to actually help them join our club.  They did not understand that it is easier to pull yourself up by your bootstraps when you have boots.

Getting the work of the JAS WG to support applicants from developing countries done correctly is an imperative for ICANN.  It is an imperative that I hope is not crippled by a bad charter.  I think the alternate motion offered by the CPH is a bad charter that should be rejected.

——————————————————————————————————

Charter proposals for reference

——————————————————————————————————

Charter extension as approved by ALAC meeting on 11 Nov 2010

Whereas:

The GNSO Council and ALAC established the Joint SO/AC Working group on support for new gTLD applicants in April of 2010; and

The Working Group has completed the work as defined in its initial charter and published a Milestone report  on 10 November 2010 covering those chartered items 

and including a list of further work items that it recommended further work on; and

In recognition of the ICANN Board’s resolution 2010.10.28.21 in response to an Interim report from the JAS WG, which states: 

the  Board encourages the JAS WG and other stakeholders to continue their work on the matter, and in particular, provide specific guidelines on the implementation of their recommendations such as determining the criteria for eligibility for support.

Resolved:

1. The charter of the Joint SO/AC New gTLD Applicant Support Working Group is extended to include the following objectives:

a) Establish the criteria for financial need and a method of demonstrating that need. Financial need has been established as the primary criterion for support. The group should be augmented to have the necessary expertise to make a specific recommendation in this area, especially given the comparative economic conditions and the cross-cultural aspects of this requirement.

b) Definition of mechanisms, e.g. a review committee that would need to be established operating under the set of guidelines established in the Milestone Report and those defined in objective (a) above, for determining whether an application for special consideration is to be granted and what sort of help should be offered; 

c) Establishing a framework, including a possible recommendation for a separate ICANN originated foundation, for managing any auction income, beyond costs. for future rounds and ongoing assistance; 

d) Establish methods for coordinating the assistance, and discussions on the extent of such coordination, to be given by Backend Registry Service Providers; e.g. brokering the relationships, reviewing the operational quality of the relationship. 

e) Discuss and establish methods for coordinating any assistance volunteered by providers (consultants, translators, technicians, etc.); match services to qualified applicants; broker these relationships and review the operational quality of the relationship.

f) Establish methods for coordinating cooperation among qualified applicants, and assistance volunteered by third parties. g) In cooperation with ICANN Staff and donor experts establish policies and practices for fundraising and for establishing links to possible donor agencies. This activity may include assisting in the establishment of initial relationships with any donor(s) who may be able to help in first round with funding

h) Review the basis of the US$100,000 application base fee to determine its full origin and to determine what percentage of that fee could be waived for applicants meeting the requirements for assistance. 

2. The Working group is asked to present a schedule for the work that allows for completion in time for the opening of the application round, currently scheduled for Q2 2011.

——————————————————————————————————-

Charter extension as offered by the Contracted Parties House of the GNSO:

Whereas:

The GNSO Council and ALAC established the Joint SO/AC Working group on support for new gTLD applicants in April of 2010; and

The Working Group has completed the work as defined in its initial charter and published a Milestone report on 10 November 2010 covering those chartered items and including a list of further work items that it recommended further work on; and

In recognition of the ICANN Board’s resolution 2010.12.10 which reiterated its 2010.10.28.21 in response to an Interim report from the JAS WG, which states:

the Board encourages the JAS WG and other stakeholders to continue their work on the matter, and in particular, provide specific guidelines on the implementation of their recommendations such as determining the criteria for eligibility for support.

Resolved:

1. The charter of the Joint SO/AC New gTLD Applicant Support Working Group is extended to include the following limited objectives:

a) Propose criteria for financial need and a method of demonstrating that need. Financial need has been established as the primary criterion for support. The group should seek out expert advice in this area, especially given the comparative economic conditions and the cross-cultural aspects of this requirement.

b) Propose mechanisms for determining whether an application for special consideration should be granted and what sort of help should be offered;

d) Propose methods for applicants to seek out assistance from registry service providers. 

e) Propose methods for applicants to seek out assistance  from other top-level domain consultants, translators, and technicians,  in the application for, and administration of, a new top-level domain)

2. The Working group is asked to present a schedule for the work that allows for completion in time for the opening of the application round, currently scheduled for Q2 2011, in any event no delays for the new gTLD program should result from the working group’s work.

3.  The Working group shall report its results and present a final report directly to the GNSO Council and the ALAC for discussion and adoption, as appropriate, according to their own rules and procedures.

4.  All communication to the ICANN Board regarding the work of this Working Group shall be through the respective SO/AC unless expressly approved by the respective SO/AC.

——————————————————————————————————

Compromise solution offered by NCSG council member and pending a vote.

Whereas:

The GNSO Council and ALAC established the Joint SO/AC Working group on support for new gTLD applicants in April of 2010; and

The Working Group has completed the work as defined in its initial charter and published a Milestone report on 10 November 2010 covering those chartered items and including a list of further work items that it recommended further work on; and

In recognition of the ICANN Board’s resolution 2010.10.28.21 in response to an Interim report from the JAS WG, which states:

the Board encourages the JAS WG and other stakeholders to continue their work on the matter, and in particular, provide specific guidelines on the implementation of their recommendations such as determining the criteria for eligibility for support.

Resolved:

1. The charter of the Joint SO/AC New gTLD Applicant Support Working Group is extended to include the following objectives:

a) Propose the criteria for financial need and a method of demonstrating that need. Financial need has been established as the primary criterion for support. The group should be augmented to have the necessary expertise to make a specific recommendation in this area, especially given the comparative economic conditions and the cross-cultural aspects of this requirement.

b) Propose mechanisms, e.g. a review committee that would need to be established operating under the set of guidelines established in the Milestone Report and those defined in objective (a) above, for determining whether an application for special consideration is to be granted and what sort of help should be offered;

c) Propose mechanism(s) for revenue income and other asset management to support new gTLD applicants who meet the criteria as established in objective (a) of this charter amendment.

d) Discuss with Backend Registry Service Providers the extent of coordination, to be given by Backend Registry Service Providers (e.g. brokering the relationships, reviewing the operational quality of the relationship) and propose methods for coordinating that assistance. 

e) Discuss and propose methods for coordinating any assistance volunteered by providers (consultants, translators, technicians, etc.); match services to qualified applicants; broker these relationships and review the operational quality of the relationship.

f) Propose methods for coordinating cooperation among qualified applicants, and assistance volunteered by third parties.

g) In cooperation with ICANN Staff and donor experts propose policies and practices for fundraising and for establishing links to possible donor agencies. This activity may include assisting in the establishment of initial relationships with any donor(s) who may be able to help in first round with funding

h) Review the basis of the US$100,000 application base fee to determine its full origin and to propose a percentage of that fee that could be waived for applicants meeting the requirements for assistance. Work with the ICANN new gTLD implementation staff to determine how the fee waivers would be accommodated.

i) Design mechanisms to encourage the build out of Internationalized Domain Names (IDNs) in small or underserved languages.

2. The Working group is asked to present a schedule for the work that allows for completion in time for the opening of the application round, currently scheduled for Q2 2011, in any event no delays for the new gTLD program should result from the working group’s work.