Text

Community in the ICANN sense.

What does ICANN mean by Community?

With the start of the new gTLD application behind us and a new Application guidebook in front of us, all hope that the harsh Community Priority Evaluation Regime defined in the Application Guide Book(AGB) would be adjusted, is abandoned. So the question becomes: is the guidance that the evaluation panel will get adequate to allow all deserving communities to be considered as ICANN validated Communities. Many, have argued eloquently that it is impossible to be survive Community Evaluation in the ICANN New gTLD sweepstakes.  I have never thought this was true, despite my concerns about the crude evaluation metrics.

In a press conference given in the hours leading up to the start of this the third gTLD round,  Rod Beckstrom, CEO and President of ICANN, spoke about how a community has priority over a trademark under defined conditions. For a second I felt waves of great joy.  But then I realized he mean ICANN validated Communities, and not communities in the normal sense.

So what does ICANN mean by a Community and how close is that definition to what would be considered a community in other circumstances?  How will ICANN judge that something is a Community?  The New gTLD application claims objectivity for a definition based on a 16 point scale.  Applicants for new gTLDs who can achieve 14 points out of 16 on a series of questions on the application will be defined as worthy of the Community designation. Of those 16 possible points, only 4 of them pertain to the definition and description of the Community itself, with the other 12 points relating to conditions such as the what, the who and the how of the applicant and the string applied for.

In this note I want to explore the notion of the Community contained in those critical 4 points and look at its relevance to the reality of being an actual community in the world. Reminder: as mentioned above, many claim that it is impossible for any real community to pass the the ICANN Community Priority evaluation. I have argued that it must be possible, but for one reason only: I cannot beleive that ICANN would intentionally define a scale no one could pass. So in the definition as provided, there must be a path that can be discovered to reach the vaunted Community designation. Yes, I still have hope.

The text of the application question for those 4 points reads:

(a) Provide the name and full description of the community that the applicant is committing to serve. In the event that this application is included in a community priority evaluation, it will be scored based on the community identified in response to this question. The name of the community does not have to be formally adopted for the application to be designated as community-based 

Descriptions should include:

• How the community is delineated from Internet users generally. Such descriptions may include, but are not limited to, the following: membership, registration, or licensing processes, operation in a particular industry, use of a language.

• How the community is structured and organized. For a community consisting of an alliance of groups, details about the constituent parts are required.

• When the community was established, including the date(s) of formal organization, if any, as well as a description of community activities to date.

• The current estimated size of the community, both as to membership and geographic extent.

(from the ICANN Application Guide Book, version 2011-09-19, Page A-13,14)

In many respects they do seem to be asking the right questions, and do seem to offer a wide scope for response. The definition recognizes that there are:

  • Communities based on delineations from the norm;
  • Communities of individual or of organizations;
  • Communities that have members and those which don’t
  • Communities where participants are certified as belonging 
  • Communities where participation are self-selected in a bottom-up manner
  • Communities of different sizes
  • Communities for whom geography is an identifier and those for whom it isn’t
  • Communities defined in ways the question lists and in way it does not list  

One component of this question that troubles some is the bullet that focuses on organization and structure.  I admit that this is tricky, but when one thinks about the many forms of organization and social structure it is clear that there are many ways in which the organization and structure of a community can be defined. The trick will be defining it clearly. Some fear that the only type of structure that will be accepted is a simple hierarchical structure. I believe that this is a very corporatist way of looking at the idea of structure and that it does not even begin to scratch the scope of possible organizational structures. More about the social sciences of community theory later in this and later notes.

What else does ICANN mean by Community

ICANN has another use for the word Community. That usage comes in the context of the Objection process:

Community Objection – There is substantial opposition to the gTLD application from a significant portion of the community to which the gTLD string may be explicitly or implicitly targeted.

(from the ICANN Applicant Guidebook, version 2011-09-19 3-4,5)

3.2.2.4 Community Objection

Established institutions associated with clearly delineated communities are eligible to file a community objection. The community named by the objector must be a community strongly associated with the applied-for gTLD string in the application that is the subject of the objection. To qualify for standing for a community objection, the objector must prove both of the following:

It is an established institution – Factors that may be considered in making this determination include, but are not limited to:

• Level of global recognition of the institution;

• Length of time the institution has been in existence; and

• Public historical evidence of its existence, such as the presence of a formal charter or national or international registration, or validation by a government, inter-governmental organization, or treaty. The institution must not have been established solely in conjunction with the gTLD application process.

It has an ongoing relationship with a clearly delineated community – Factors that may be considered in making this determination include, but are not limited to:

• The presence of mechanisms for participation in activities, membership, and leadership;

• Institutional purpose related to the benefit of the associated community;

• Performance of regular activities that benefit the associated community; and

• The level of formal boundaries around the community.

The panel will perform a balancing of the factors listed above, as well as other relevant information, in making its determination. It is not expected that an objector must demonstrate satisfaction of each and every factor considered in order to satisfy the standing requirements.

(from the ICANN Applicant Guidebook, version 2011-09-19 3-7,8)

To what extent are the criteria for Community in the Objection Process, related to those defined for an Applicant?  Is the same definiton of the word ‘community’ being used?  

My assumed answer is that, of course, the usage of Community for objections must be an extension of the use of Community for applicants and thus the criteria defined for the Community based Objection will act guidance for those measuring the degree to which an applicant referenced community is a Community in the ICANN sense, and vice versa.

In judging ICANN performance in terms of Community, the relationship between the usage in these two areas of application processing will be an important indicator. And to be sure, ICANN will be judged in terms of its processing of Community applications and objections. Failure in this respect will be seen, and more importantly felt by the communities that are parties to ICANN processes. That damage that ICANN can do by denying communities their proper status in applications and objections will be one important criteria of the program’s success and of ICANN ability to manage such a complex and delicate process.

What do others mean by community?

There is a rich social science of community. As with most questions in the social sciences, there isn’t one answer to the question of “what is community?”. There are many answers and they mostly invovle considerations of behavior of several types discussed briefly below.

A community is defined in three dimensions

  • a bottom-up process of self realization - “we are a community”
  • a top down recognition - “yes, you are a community”
  • a third party recognition - “they are a community”

In the ICANN Community Priority Evaluations and Objections processes, the applicants and objectors will make their claims from the first of these perspectives. Those making the evaluations on behalf of ICANN, and the Board that is responsible for the oversight, will be looking at it from the second point of view. The global Internet that will judge ICANN’s performance will be looking from the third perspective.

A community is often defined along several axes

  • Place or territory where the thing people have in common is location
  • Common notions of selfhood: these relate to ethnicity, identity, occupation, sexual orientation and/or religious belief.
  • Common attachment to an activity or idea

All of these dimensions are included in the ICANN Application guide description of Community.

A community is defined being bordered

In most communities, there is a border between what is in-community and what is out-of-community. While this border may, in some cases be fuzzy when looked at closely, it does represent a clear boundary for most communities. In general, once a community is defined, people can tell whether some entity is a member of the community or not.

A community is often defined as network or social systems

Very few communities can be defined as single entity with a strict hierarchical structure and one apex, the so called apex communities. Most communities, including those like the multistakeholder holder community that is ICANN, are defined by a distributed patchwork of sub-groups organized along lines of subsidiarity. So one will find an organizations ranging from those where a clear hierarchical structure can be found, for example the American Association of Retired Persons (AARP) which has become for ICANN one of the commonly cited examples of a community that is easy to define, to communities like Occupy Wall Street, that exists as a loose network of individuals who have accepted a common cause and common method of communications (though of course they probably would not meet ICANN requirements for time in existence and longevity).

A community is often defined in terms of qualities

  • A tolerance for other members of the community
  • A reciprocity among members of the community
  • A sense of trust based on expectations of the behavior of other members of the community.

Of course, similar to the dynamic in families, the relationships in a community can be defined in terms of intolerance and distrust.  But what will still remain the case is that there is an expectation within a community that these qualities are important among the members.

Community organization is about democracy

There are many models of community organization from ancient tribal organization, to the local community theatre group. When looked at in terms of social dynamics, many of the processes within a community are related to finding way to increase the social well being of the participants and of society at large.

A Community is hard to define

A federal judge at a FCC workshop said “Community is like pornography, I don’t know how to define it, but I sure know it when I see it.” (Quotes from Community Building, Renewing Spirit and Learning in Business as reference by Nancy White)

Conclusion, for now

From the begining of the GNSO effort to define the conditions for this gTLD round, the notion of community was special, it came up in almost every discussion about how to choose between competing applications for the same string. The experience of the Sponsored TLD (sTLD) round taught about the importance of community and about the difficulty of providing a one size fits all definition. That round had taught that a competitive evaluation that required the Board to choose the best applicant of a worthy TLD string was fraught with all the dynamics and pitfalls of a beauty contest. So the GNSO mandated that community applicants would have preference for a string of significance to their community and would be able to stop an applicant that applied for a string that caused harm to their community. The GNSO was quite specific in its Implementation guideline for this round:

If there is contention for strings, applicants may:

i) resolve contention between them within a pre-established timeframe

ii) if there is no mutual agreement, a claim to support a community by one party will be a reason to award priority to that application.

iii) …

For the most part, the Board and the Staff have argued that they tried to remain true to the words and intentions of the GNSO and its policy process in the implementation of this round. For now I chose to accept this claim and to predict that communities will be able to find the priority that is their place in this recently initiated round.

As with any prediction or act of faith, time will tell. It is possible that those responsible for grading the Community Priority challenge will take a wide approach. It is also possible that they will be instructed to take a narrow approach. The grading system does not leave much room for variability - it is as in a black and white picture of a very colorful scene, a lot of the complexity and information is lost. One can easily argue that the current process has set an incredibly high bar for the claim based priority that the GNSO mandated. But while the work to define a community in the application may require a certain amount of rigor, I return to my belief that it can be done successfully. The guidance by which the adjudication will be done, however, still remains opaque.

This is the first in a series of blog entries on the unfolding of the ICANN New gTLD program initiated on 12 Jan 12 ay 0000 UTC. Other blog entries will explore other facets of the requirements for Community Priority status.

Text

Let a thousand flowers bloom

(This is an email I sent to the the NARALO list.  I liked it and it seems a few other people did too.  But it had some typos, that bothered me all the way from EWR to MEX  - which considering the number I make is really quite funny. So I reproduce it here with a few edits.)

Hi,

as a very active and vocal proponent of “let a thousand flowers bloom”  I feel i should offer a few words in support of this notion.

in fact the reason i am involved with ICANN is the blooming of a 1000 blooms

  • in WGIG I said ICANN should quit dithering about and new gTLD should happen now, like they long promised.
  • and people in ICANN said come put your time where your mouth is -
    (Note: I said time and not money because i didn’t and still don’t have any money)

i do this with the full awareness that I may get slammed, if ever so politely, for such heresy on the NARALO list.

personally, i always find the polite and civil slams cut the deepest.


i always liked the image of flowers blooming.  

not only are flowers very pretty, each appealing to a different personality type.

many of them are valuable, though sometimes we don’t see the value.

i live in a neighborhood where most everyone has the same kind of grass.

and for most people in the neighborhood one type of grass is enough.

and they work really hard, 

with their poisons and their weed wackers to kill all the nasty weeds.

i tend to cultivate the weeds.

scything around the pretty blooms

to get rid of the common grass.

i like the diversity that the blooms others call weeds,

brings to my world.

so too with new gTLDs.  

to be honest, I don’t really  see 

- why NYC needs a gTLD.

- why anyone would want a .sport

- or who should care about a .mine

  for some value of ‘mine’

but so what?

they think they need one.

or they think someone else needs one.

and that is good enough for me.

in a diverse world, why do i need to understand?

i just need to accept that they see a reason.

and the bees and the birds and the other critters,

like my yard better than they like the neighbor’s.

lots of places to make a habitat in the city.

and every once in a while something dangerous may happen by, but a dog, a cat and a flashlight to shine on them is usually enough to deal with it.  and sure sometimes we want to call the professional to help with the skunks.  but the skunks would be around anyway.

at least in my yard, we know where they live.

and some people think they can produce wealth 

from new gTLDs;

and good for them.

if someone had  not realized the value of the weed called tomato,

think of how boring Italian food might be.

so i say,

let a thousand flowers bloom.

some will thrive,

some will die to maybe come back again another year.

as for users and what they need.  

sure,

beyond basic food and clean water and rudimentary shelter and health care and gray sack cloth

we don’t need anything else.

or do we?

i need pretty flowers.

perhaps it is just that they suit my vanity

but so what?

a.

———

NA-Discuss mailing list

NA-Discuss@atlarge-lists.icann.org

https://atlarge-lists.icann.org/mailman/listinfo/na-discuss

Visit the NARALO online at http://www.naralo.org

———

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

Surprise and shock at yet another delay (YAD) in the start of new gTLD program.

There have been two articles that quote the Board Chair of ICANN, Peter Dengate Thrush, as saying that the decisions on the new program will be delayed until the end of the ICANN meeting in June.  Of course I can’t confirm that the facts in the articles in CircleId and Domainicite.com are indeed the case, but it sort of stands to reason, so it could be true.  

If there is going to be a prior notion of the possibility of coming to an agreement with the GAC on the Thursday before the San Francisco meeting ends, the Board can’t very well make a decision in one night to change the program.  And, given the possibility that they actually make some substantive concessions (which I hope they don’t), how can the Board initiate the program without giving us, those who created the program in ICANN’s vaunted bottom-up process, a chance for appropriate wailing and gnashing of teeth over our bitter disappointment and great chagrin.

Some would ask, but why wait for Jordan meeting to make the decision.  Well, first, who really believes we are still going to Jordan in this political climate?  But more relevantly, what’s 3 months in the geological time periods that ICANN works in?  How long have we been waiting on this program? 5 years? 10 years? More years?  What’s another few months?

One thing we can be grateful for.  We used to delay 9-12 months at a time several times a year, now the delays are only 3 months long.  ”It’s getting better all the time.”

———

Why Yet Another Delay (YAD)?  Because this is ICANN we are talking about and what good is a blog on ICANN without introducing Yet Another Acronym (YAA) or two.

Text

Is ICANN’s new gTLD program ready to roll? Is it ready for everyone?

As the San Francisco meeting comes into sight, the anticipation of those waiting for new gTLDs is becoming palpable.  Maybe this time, the Board will actually give the program the go ahead.

Much has been said and done.  For the most part the overarching issues have been handled and for those that have not yet been handled, there are expected negotiations between the Board and the GAC, which in the best of all worlds would enable the program to start in Q3 2011.  And I still believe in the best of possible worlds.

As one of those who has argued for the ‘let a thousand flowers bloom’ strategy for new gTLDs, this should excite me.  And it would, if I believed that there would be a diversity of blooms in this first round.  Unfortunately, I do not believe that there will be a global diversity of new  gTLDs as the program currently stands.

Despite the GAC’s early and continued advice on the prohibitive nature of the cost model for applicants and despite the recommendations of the JAS WG for way in which to provide help to applicants from developing areas, the likelihood that a diversity of gTLD applicants will be able to apply seems very unlikely at this point. 

There were recommendations for price reductions for applicants from developing economies, but these have been rejected.  There were proposals for starting a program to raise funds that would allow for loans and grants to help applicants from the developing economies, but the work needed to do this in the JAS WG has been banned by a decision of the GNSO Council.

It appears very unlikely that ICANN, in the normal course of its activities, will solve the problem of how applicants from developing economies can be enabled to apply in this first round.

But if we, the ICANN community, do not provide realistic material support to new applicants from the developing economies, this new start will not be in keeping with ICANN’s principles and its mandate as a corporation in the public good - not just the public good of California, the US and the rest of the developed world, but the public good of the entire world including those on the other side of the digital divide.  It is up to the ICANN community to make this a fair round of gTLD application.

A campaign of fund raising must be started.  I call on ICANN to lead the the way by making a pledging to contribute to the start of a fund for applicants from developing economies. I don’t know if ICANN is paying a fee to President Clinton to speak to the ICANN meeting in San Francisco, but if so, I would like to see a pledge of at least that amount from ICANN to such a fund - there must be a line item for this in the budget.  

I also call on the registries, registrars, domainers and others whose businesses who have made fortunes from a myriad of TLD related activities to pledge significant sums to such a fund.  I call on all who can afford to do so to pledge to contribute to a properly established and well regulated fund to assist applicants form developing economies.

It is all well and good to support the work of the JAS WG which is developing the mechanisms for administering aid to applicants from developing countries.  But the common wisdom in that group and in the GNSO related to funding is that there isn’t any money.  I do not believe that.  I have seen the profit that many companies make. I have the salaries that people working in this industry make.  And I have seen, and enjoyed, many of the parties we hold at ICANN meetings.

We all know that there is lots of money circulating in the ICANN community.  If enough of this is pledged to a campaign to help applicants from developing economies, then perhaps the common wisdom will step aside and allow for solutions to bring forth a globally diverse set of blooms.

Please think about it.  And please pledge to this yet to be created fund. Be the first!

Text

ICANN’s GNSO approves neocolonial restrictions on support for gTLD applicants from developing economies!

Today, the GNSO rejected a motion on a charter extension to the Joint AC/SO Working Group for gTLD Applicants from Developing Economies (JAS WG) that might have actually provided assistance for new applicants from developing economies.  Instead they approved a charter extension that only provides a single kind of aid.  The only type of help they approved was aid that would be provided by or through an incumbent partner or an established consultant.

Many of the types of aid approved in the ALAC charter extensions were excluded!

No application fee reductions;

No fund raising in order to give material assistance;

No use of windfall profits from auctions to help applicants from developing economies; 

No help in establishing coordinated efforts by applicants from developing economies.

The only kind of aid the JAS WG is allowed to work on is aid that makes a applicant from a developing economy beholden and subject to the control of an incumbent or an expert.

In other words, the only type of aid the GNSO approved is neocolonial aid.

Neocolonialism is a method by which corporations and multinational corporations from developed nations find ways, such as partnerships and advisor-ships, to exploit the resources of post-colonial developing economies.  The new gTLDs, especially those IDN gTLDs using local scripts and languages, are a rich resource open to exploitation.  By making partnering the only way to get assistance, the incumbent will gain some share of every new gTLD that requires aid. Further, by not providing material aid, local populations will be at a disadvantage in developing their own linguistic and cultural resources, leaving those resources as low hanging fruit available for incumbents.

Restricting the type of assistance to partnerships and advisors, though these can be an ingredient of a full program that includes material assistance, is a form of neocolonialism.  This is the case even if those in the Contracted Parties House (CPH) who tabled this motion and those in Non Contracted Parties House (NCPH) who went along with the motion and voted for it, do not know it is neocolonialism.  Even if exploitation was the furthest thing from anyone’s mind and they were only thinking of what was good for the incumbents and for their stakeholders, it is neocolonialism and it ignores the needs of developing economies.

And it is wrong.

What it is not, is a development conscious action! 

What it is not, is a response to the GAC’s advice that the new gTLD program be made accessible to developing economies!

The GNSO council went even further in that the motion that they approved gags the JAS WG by barring it from conveying its recommendations to the ICANN Board, the GAC or the community at large without first getting the approval of the GNSO.  It might even gag the WG from being able to put out a statement regarding the utter inadequacy of the motion approved by the GNSO.  The GNSO, in the process of protecting its gTLD sovereignty and its access to developing economy resources, is instituting military style top down chains of command in the ICANN bottom up organization.

These were the first major decision of the new 2011 GNSO council.  

This does not bode well.

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.

Text

ICANN’s GNSO Council is omnipotent!

Sometimes I am slow, but I never realized this before because I always looked at the GNSO council from the perspective of its need to be bottom-up and the notion that all of its policy decisions need to be endorsed by the Board.

But when it comes to its own proceses, as the manager of the processes, there is no way to appeal its decisions.  And even though I was its chair for over 2 years, I only realize this now.  As I said, I can be slow.

The GNSO Council is about to do something I find unthinkable. It is a small thing, but it is the sort of small thing that decreases the credibilty of a body.

So, what is this small thing?  The current council, which ends on 10 December 2010, has decided to elect a chair for the next council. As I said, it is a small thing,  but it is something that the GNSO has never done before, and it is the sort of thing that will make me doubt the legitimacy of the election.  I know, I am being somewhat of a stickler for sticking to the rules and for accepted process, and that can be obnoxious. But I see not reason for the rush of this council to elect the next council’s chair.

In another sense it is a big thing, because it made me realize that when the GNSO council decides to do something like this, there is no way to appeal it and no way to ask for a reconsideration. There is nothing anyone in the GNSO can do, nothing any of the constituencies can do, and nothing the Stakeholder Groups can do.  There isn’t even a method to ask for a reconsideration.

And that is something that needs to be fixed.

Text

Incomplete quote on the future of IDN TLDS

When asked by an Internet-friend whether there will be single-character TLDs in IDN and non-IDN, I responded.  My response was quoted incompletely In the Warrens’ Washington Internet Daily as:

“I think you will definitely get [China/Japan/Korea] single-character IDN TLDs, both country-code and generic,” said Avri Doria, an ICANN participant and adjunct professor at Lulea University of Technology in Sweden. Some think this is enough — except for .A., .E and .I — since these languages are the only ones with single character words, she said. Latin and ASCII IDNs will “keep dangling for a long while, except for the few that aregrand-fathered in and which serve as proof of there being no technical problems,” she said.

In additon to having done me the favor of cleaning up my language, a middle sentence was dropped which I beleive makes the quote incomplete.  This is of course a subjective opinion and I did give the author the right to quote me without any request of how.  But I figured I would put the whole quote in a blog, just so it was out there.

i think you will definitely get  CJK single character IDN TLDs, both cc and G (some in JIG argue for this since it is obvious, and some of those think this is just enough since they are the only one who have single character words.  well except for A, E and I.)

you may get single character non Latin IDN (some in JIG argue for this since they are not from CJK but still don’t use Latin letters)

and Latin IDN and ASCII Letter will keep dangling for a long while, except for the few that are grandfathered in and which serve as proof of there being no technical problem.


Another issue came up in regard to another ICANN Board decision reportedly made last night:

d. Approval of RSEP Request for Allocation of 1 and 2-Character Domains in .TRAVEL
Whereas, Tralliance submitted a request pursuant to ICANN’s Registry Services Evaluation Policy to amend the .TRAVEL Registry Agreements to allocate one and two-character domain names via a phased allocation process.
Whereas, the proposed release of single and two-character domain names in .TRAVEL would be consistent with the recommendations of the GNSO Reserved Names Working Group and other approvals to permit the release of one and two-character domain names.
Whereas, ICANN has evaluated the proposed amendment to the .TRAVEL Registry Agreement as new registry services pursuant to the Registry Services Evaluation Policy and has posted amendments for public comment and Board approval (http://www.icann.org/registries/rsep/).
RESOLVED (2010.08.05.06), the .TRAVEL amendment is approved, and the President and General Counsel are authorized to take such actions as appropriate to implement the amendments.


In my informal comments, I went on to mention:

On single letter, there is an interesting question as to whether they might be representational of sovereign states since many are used to represent countries in auto license plates (The coding system for car license plates under the 1949 and 1968 United Nations Road Traffic Conventions ).  and since ICANN is bending over backwards to every whim and desire of the sovereigns among us, they probably should be reserved and in fact may already be reserved by the language in DAGv4.  But then, one might ask what about the second level - should they be also be protected under the current new gTLD regime?  are they already? oh isn’t there is a RSTEP on this?
O, U, W, X weren’t assigned as far as I can tell and R and Y  are not  used.  i don’t think any diacriticals were assigned.


The reference to DAGv4 is a reference to the Full Draft Applicant Guidebook, version 4 (we are no longer supposed to call it DAG because DAG is a scatological word in Australian - part of the ICANN Purify the Language Program).  In section (2.2.1.4.1 Treatment of Country or Territory Names)  the following note is included: 


Country and territory names are excluded from the process based on advice from the Governmental Advisory Committee in recent communiqués providing interpretation of Principle 2.2 of the GAC Principles regarding New gTLDs to indicate that strings which are a meaningful representation or abbreviation of a country or territory name should be handled through the forthcoming ccPDP, and other geographical strings could be allowed in the gTLD space if in agreement with the relevant government or public authority.

I can only assume that the 1949 and 1968 United Nations Road Traffic Conventions are “meaningful representations” and that the ICANN implementation team has just not been made aware of them yet. I look forward to future conversations on this detail.