ICANN says sorry for crappy hotel complaint

ICANN has apologized to the government of Senegal for its uppity letter of complaint about a hotel used for its recent Dakar meeting.
As I blogged (with sarcasm) earlier this week, ICANN marketing chief Barbara Clay had written to Senegal’s telecommunications minister Moustapha Guirassy to complain that the Hotel des Almadies was not up to the expected standards.
The poor service “damaged ICANN’s reputation as well as the reputation of the Hotel and Senegal”, the letter, which has since been removed from ICANN’s web site (read it here), stated.
Clay has now written to Guirassy to apologize. The letter (pdf) reads:

The letter was sent without appropriate clearance by ICANN’s leadership and so it was not an official statement of ICANN’s position.
ICANN’s leadership, and indeed the entire ICANN community, deeply appreciate the generosity shown by Senegal in hosting our 42nd public meeting. ICANN’s leadership – and I personally – truly regret any embarrassment or distress my letter may have caused you or the Government of Senegal.
I hope you will accept this sincere expression of regret.

The $124-a-night Almadies came in for a torrent of complaints from ICANN’s At Large Advisory Committee and others due to the substandard rooms, poor wifi, rats, smells and lack of security.

Outrage! ICANN complains about crappy hotel

Sometimes ICANN’s love of procedure defies parody.
It’s no secret that the $124-a-night Hotel des Almadies used at its recent meeting in Dakar, Senegal, was not really up to the Club Med* standards that ICANN wonks are accustomed to.
The At-Large Advisory Committee even conducted a survey of its members after the meeting and found that a whopping 68% of them had complained to hotel management for one reason or another.
ICANN’s response?
It’s sent a letter to Senegal’s telecommunications minister, complete with a 20-page illustrated ALAC report going into excruciating detail not only about the shoddy facilities but also the policy background of the complaint.
Along with reports of rats, patchy Wi-Fi, “musty smells” and inadequate security, there are references to Resolution 2010.08.05.12, the ALAC/At-Large Improvements Implementation Project Plan, and Section 3.2.2.5 of the Travel Policy of the ALAC Review Final Report.
According to the letter, from marketing chief Barbara Clay, ICANN had received assurances that the hotel rooms would be renovated before the Dakar meeting kicked off.
Clay wrote that the hotel’s failure to follow up on its promises “damaged ICANN’s reputation as well as the reputation of the Hotel and Senegal” and she asks for compensation.
I’m guessing Rod Beckstrom’s not going to be on President Wade’s Christmas card list after all.
(*As anyone who has attended more than one ICANN meeting knows, they’re nothing but a week-long orgy of beach limbo parties, $20 cocktails and sordid sexual encounters with exotic prostitutes, all paid for by the humble internet-using public.)

GAC new gTLD veto refuses to die

ICANN’s Governmental Advisory Committee seems to be trying yet again to resurrect the government right of veto over controversial new top-level domain applications.
The GAC has proposed changes to the new gTLDs Applicant Guidebook that – at least on the face of it – would remove ICANN’s power to overrule GAC objections.
The changes would also make it much more likely that a gTLD application could be killed off due to the objections of a single nation.
If adopted, they would also make the already unpredictable process of anticipating the result of GAC objections considerably more ambiguous.
The supposedly “complete” Guidebook published by ICANN last month currently includes a warning that the GAC is working on its objecting rules, and that these will be included in future.
The GAC Communique (pdf) issued at the ICANN meeting in Dakar on Friday includes these proposed rules as an annex, and they’re not great if you’re a likely new gTLD applicant.
Consensus objections
If the GAC issues a consensus objection to an application, the Guidebook currently states that a “strong presumption” would be created that the application should fail.
But ICANN’s board would be able to overrule it with a so-called “Bylaws consultation”, the same process it used to approve .xxx earlier this year.
In its proposed revisions, the GAC inexplicably wants to delete the references to the Bylaws consultation.
My understanding is that the GAC is not proposing a change to the Bylaws, so the right of the board to initiate a consultation and overrule a GAC objection would still exist.
But the GAC seems to be asking for applicants to be given far less information about that process than they need, making its own powers appear greater than they are.
This could raise the psychological barrier to initiating a Bylaws consultation and create the perception that a consensus GAC objection always kills an application, which may not be the case.
The Dakar communique defines GAC consensus as “the practice of adopting decisions by general agreement in the absence of any formal objection”, which creates its own set of worries.
Non-consensus objections
A much bigger change is proposed to the way ICANN handles GAC “concerns” about an application.
This is GAC code for a non-consensus objection, where one or more governments has a problem with an application but the GAC as a whole cannot agree to object.
This is the objection mechanism that will very likely capture applications for gTLDs such as .gay, but it could basically cover any string for any reason.
Using the Guidebook’s current wording, there would be no presumption that this kind of application should be rejected. It would be in ICANN’s discretion to initiate a Bylaws consultation.
But the GAC wants something that sounds rather a lot like a Bylaws consultation made mandatory.
“The ICANN Board is expected to enter into dialogue with the GAC to understand the scope of concerns,” it says. “The ICANN Board is also expected to provide a rationale for its decision.”
This basically means that an application for .gay that was objected to by just two or three governments would have to undergo the pretty much the same level of scrutiny as .xxx did.
The political pressure on ICANN to kill the application would be much more intense than it would under the Guidebook’s current rules.
Here’s a table of the GAC’s proposed changes.
[table id=2 /]
In summary, the GAC wants to give more weight to fringe objections and to make the whole process potentially much more confusing for applicants.
I can’t see ICANN sensibly adding the GAC’s text to the Guidebook without at the very least some edits for clarity.

Today’s new gTLDs decisions in full

ICANN’s board of directors passed two resolutions relating to new generic top-level domains at is meeting in Dakar, Senegal today.
While neither is particularly Earth-shattering, they are notable and therefore reproduced here in full.
The first relates to financial support for new gTLD applicants from developing nations.
ICANN has not figured out how to implement the recommendations of the JAS working group yet, but it hopes to do so before the end of the year.

Joint Applicant Support
Whereas, the Board has received the Final Report of the Joint Applicant Support Working Group (JAS WG), appreciates the work of the JAS WG created in April 2010 by the ALAC and GNSO, and thanks the entire ICANN community for the constructive dialogue leading up to and during this week in Dakar.
Whereas, the Board expresses its appreciation to the GAC and ALAC for their joint statement on the JAS WG report.
Whereas, the Board is committed to ensuring that the implementation of a support program for deserving applicants will be done in a manner to enable those applicants to effectively participate in and benefit from the first round of the New gTLD Program.
Resolved (2011.10.28.21), the Board takes the JAS WG Final Report seriously, and a working group of Board members has been convened to oversee the scoping and implementation of the recommendations arising out of that Report, as feasible.
Resolved (2011.10.28.22), the President and CEO is expected to commence work immediately and provide a detailed plan for consideration. If the plan is complete sufficiently in advance of its next scheduled Board Meeting set for 8 December 2011, the Board will seek to add a special meeting to its schedule prior to that date.
Rationale for Resolutions 2011.10.28.21 – 2011.10.28.22
In Singapore, the Board resolved that it would consider the report and recommendations of the Joint Applicant Support Working Group. The Board takes seriously the assertions of the ICANN community that applicant support will encourage diverse participation in the New gTLD Program and promote ICANN’s goal of broadening the scope of the multi-stakeholder model. In its deliberations, the Board is balancing its fiscal responsibility in launching the New gTLD Program, the desire to provide a support program in the first round, and the time required to obtain additional funding. While the Board solution is not complete, there is a vision for accomplishing each of those three goals.  As required for assessment within the Affirmation of Commitments, there is no security and stability impact on the DNS. Part of the further work required through this resolution will assess the affect of this work; however there is no affect on ICANN’s fiscal resources as a result of this immediate action.

The second resolution, which caused considerable debate among board members, relates to funding of the much-criticized new gTLDs communications campaign.
The board approved an additional $900,000 for outreach, much of which will apparently go into the pockets of newly hired PR firm Burson-Marsteller.

Budget Request – New gTLD Communications Plan
Whereas, at the Paris ICANN meeting in 2008, the Board adopted the GNSO policy recommendations to introduce new Generic Top-Level Domains (new gTLDs), including at least a four-month communications period to raise global awareness.
Whereas, the Draft New gTLD Communications Plan (link) describes the global outreach and education activities that will be conducted in each of the ICANN geographic regions.
Whereas, the FY 12 budget allocates US $805,000 to fund this effort.
Whereas, planning and subsequent execution of the Communications Plan has indicated the need for a full service global public relations firm to ensure ICANN effectiveness in this effort.
Whereas, funds can be re-allocated in the adopted ICANN Budget to support the augmented communications effort without materially affecting performance in other areas.
Whereas, at its 22 October 2011 meeting the Board Finance Committee approved a recommendation that the Board approve an additional expenditure of US$900,000 for the execution of the Communications Plan.
Resolved (2011.10.28.23), the Board approves an additional expenditure of up to US $900,000 for the remaining three months of the Communications Plan, to be used for the retention of Burson-Marsteller, a global public relations firm, to work towards the goal of raising global awareness of new Generic Top Levels Domains consistent with the terms of the Communications Plan.
Resolved (2011.10.28.24), the Board authorizes the President and CEO to enter into any contracts necessary to fulfill the objectives of the New gTLD Communications Plan to the extent those contracts do not exceed the budget for the Communications Plan.
Rationale for Resolution 2011.10.28.23 – 2011.10.28.24
The budget for the Board-mandated new gTLD communications program is currently US $805,000. That figure was based on an earlier draft communications plan.
The current plan is more expansive and ambitious. It is based on the premise that every potential applicant should be aware of the program’s opportunities and risks, and thus it is aimed at building maximum awareness through multiple communications channels. It also focuses more strongly on developing countries.
The Plan is built on four principal efforts:
1. Regional “road shows” and public events;
2. Earned media – broadcast, online and print;
3. Social media; and
4. Global information through paid advertising, and multiplying these efforts through the community.
The New gTLD Communications Plan is neutral in its presentation. ICANN is not promoting applications for new gTLDs or advocating that any organization apply for one. Rather, ICANN is providing essential information and raising awareness of the New gTLD Program.
The current efforts limited in scope. ICANN has determined that retaining a full-service worldwide public relations firm to further coordinate ICANN’s efforts will assure that ICANN is able to attain the goal of the New gTLD Communications Plan.
ICANN has identified a well-respected global public relations firm, Burson-Marsteller, that can provide a broad range of awareness-raising services. ICANN will have access to the firm’s extensive network with an established presence in 91 countries, over 40 of them developing nations. These local and regional assets are invaluable. ICANN also will benefit from the firm’s expertise in digital and social media. ICANN will retain editorial control over all implementation aspects of the New gTLD Communications Plan.
Securing a global public relations firm of this caliber will contribute greatly toward ensuring success of the New gTLD Communications Plan. And as the first deliverable of the New gTLD Program, success of the New gTLD Communications Plan is critical.
Approval of this resolution will positively affect ICANN’s accountability and transparency by globally maximizing the spread of information about ICANN itself. This action will have no effect on the security, stability and resiliency of the domain name system.
The New gTLD Communications Plan will be conducted within the existing ICANN budget. This effort will be funded out of contingency funds, so the expenditure will not affect ICANN’s ability to perform and accomplish its other goals and objectives.

More later.

Domain registrars pressured into huge shakeup

Domain name registrars have agreed to negotiate big changes to their standard contract with ICANN, after getting a verbal kicking from the US and other governments.
While the decision to revamp the Registrar Accreditation Agreement was welcomed by intellectual property interests, it was criticized by non-commercial users worried about diluting privacy rights.
The ICANN registrar constituency said in a statement today that it will enter into talks with ICANN staff in an effort to get a new RAA agreed by March next year.
It’s an ambitious deadline, but registrars have come under fire this week over the perception that they have been using ICANN’s arcane processes to stonewall progress.
So, what’s going to change?
The registrars said that the negotiations will focus on 12 areas, originally put forward by international law enforcement agencies, that have been identified as “high priority”.
They cover items such as an obligation to disclose the names of registrants using privacy services, to work with law enforcement, and to tighten up relationships with resellers.
Here’s a list of all 12, taken from a recent ICANN summary report (pdf).
[table id=1 /]
The changes were first suggested two years ago, and ICANN’s increasingly powerful Governmental Advisory Committee this week expressed impatience with the lack of progress.
There’s a US-EU cybercrime summit coming up next month, and GAC members wanted to be able to report back to their superiors that they’ve got something done.
As I reported earlier in the week, the GAC gave the registrars a hard time at the ICANN meeting in Dakar on Sunday, and it took its concerns to the ICANN board yesterday.
“We are looking for immediate visible and credible action to mitigate criminal activity using the domain name system,” US GAC representative Suzanne Radell told the board.
She won support from Steve Crocker who, in his first meeting as ICANN’s chairman, has shown a less combative style than his predecessor when talking with governments.
He seemed to agree that progress on RAA amendments through the usual channels – namely the Generic Names Supporting Organization – had not met expectations.
“One of the things that is our responsibility at the board level is not only to oversee the process, not only to make sure rules are followed and that everything is fair, but at the end of the day, that it’s effective,” he said.
“If all we have is process, process, process, and it gets gamed or it’s ineffective just because it’s not structured right, then we have failed totally in our duty and our mission,” he said.
An immediate result of the registrars’ decision to get straight into talks was the removal of an Intellectual Property Constituency motion from today’s GNSO Council meeting.
The IPC had proposed that the RAA should be revised in a trilateral way, between the registrars, ICANN, and everyone else via the GNSO.
Yanking the motion, IPC representative Kristina Rosette warned that the IPC would bring it back to the table if the RAA talks do not address the 12 high-priority items.
It would be unlikely to pass – registrars and registries vote against anything that would allow outside interests to meddle in their contracts, and they have the voting power to block such motions.
The ideas in the motion nevertheless stirred some passionate debate.
Tucows CEO Elliot Noss described the GAC’s heavy-handed criticisms as “kabuki theater” and “an attempt to bring politics as usual into the multi-stakeholder process” and said the RAA is not the best way to add protections to the DNS.
“Getting enforcement-type provisions, be they law enforcement or IP protections, into the RAA accomplishes only one thing. It turns the ICANN compliance department into a police department,” he said.
Wendy Seltzer, representing the Non-Commercial Users Constituency, said the changes proposed to the RAA “would reduce the privacy of registrants” and put them at increased risk of domain take-downs.
A broader issue is that even after a new RAA is negotiated registrars will be under no obligation to sign up to it until their current contracts expire.
Because many leading registrars signed their last contract after it was revised in 2009, it could be three or four years before the new RAA has any impact.
I’m not sure it’s going to be enough to fully satisfy the GAC.
Radell, for example, said yesterday that some items – such as the registrar obligation to publish an abuse contact – should be brought in through a voluntary code of conduct in the short term.
She also called for the 20% of registrars deemed to be bad actors (not a scientifically arrived-at number) should be de-accredited by ICANN.
UPDATE (October 27): Mason Cole of the registrars constituency has been in touch to say that the RAA talks will not only look at the 12 “high priority” or law enforcement recommendations.
Rather, he said, “there will be consideration of a broader range of issues.”
This appears to be consistent with the registrars’ original statement, which was linked to in the above post:

The negotiations are in response to the development of a list of recommendations made by law enforcement agencies and the broader Internet community to provide increased protections for registrants and greater security overall.

IANA contract only for US companies

The US Department of Commerce has announced the date of its RFP for the IANA contract, stating that only wholly US-based organizations are welcome to apply.
Commerce, via the National Telecommunications and Information Administration, said it intends to accept proposals from potential contractors between November 4 and December 4.
Among other things, the IANA contract is what gives ICANN its powers over the domain name system’s root – its ability to delegate gTLDs and ccTLDs to registries.
It is due to expire at the end of March next year, having been extended from its original expiry date of September 30. ICANN is of course the favorite candidate.
ICANN had asked for a longer-term or more arms-length contract, to dilute the perception that IANA is too US-centric, but NTIA has indicated that it intends to decline that request.
However, the duration of the contract has been changed.
The current IANA contract was a one-year deal, with four one-year renewal options. The next will be for a three-year base period, followed by two two-year renewal options, according to Commerce.
“The current unilateral structure of the IANA functions contract should evolve to meet the needs of the global community,” ICANN CEO Rod Beckstrom said during his opening remarks at ICANN’s 42nd public meeting in Dakar, Senegal yesterday.
He noted that the US government originally said, in a 1998 white paper, that ICANN would ultimately take over the IANA functions entirely, cutting it off from government.
“We hope that progress towards the vision articulated by the US government’s white paper will be made in the next agreement and we hope and we expect to see a roadmap for the realization of this vision in the future,” Beckstrom said.
Now that Commerce has made such a big deal out of the fact that only US-based organizations are welcome to apply to run IANA, that goal seems further away.
It’s also notable that the next IANA contract will be a single document.
The NTIA had previously floated the possibility of splitting it into three functions – protocol management, DNS root management and IP address allocation – but the idea was not well-received.

GAC slams registrars over “silly” crime domain moves

ICANN’s Governmental Advisory Committee is seriously annoyed with domain name registrars over what it sees as a failure to take the demands of law enforcement seriously.
The first official day of ICANN’s 42nd public meeting in Dakar, Senegal, was highlighted by a fractious discussion between the GAC and the Generic Names Supporting Organization.
Governments are evidently losing patience with the industry over what they see as incessant foot-dragging and, now, halfhearted bone-throwing.
The US, which is easily the most influential GAC member, was harshly critical of recent efforts by registrars to self-regulate themselves some law enforcement cooperation policies.
US GAC representative Suzanne Radell, saying she was speaking on behalf of the GAC, described a registrar move to start publishing legal service addresses on their web sites at some point in the future as as “paltry”, “mind-boggling” and “silly”.
She heavily implied that if the industry can’t self-regulate, the alternative is governments doing it for them. She was backed up by her counterparts from the UK, Australia and the European Commission.
Registrars have been talking to law enforcement for a few years about how to more effectively work together to prevent crime online.
In October 2009, agencies including the FBI and the UK Serious Organised Crime Agency publish a set of 12 recommendations about how to clean up the industry.
A lot of it was pretty basic stuff like a prohibition on registrar cybersquatting and an obligation to publish an abuse point of contact.
Despite a lot of talking at ICANN meetings, up until a couple of weeks ago there had not been a great deal of tangible progress.
The GNSO passed a resolution, proposed by registrars, to ask for an Issue Report to discuss whether registrars should be forced to post on their sites: a physical address for legal service, the names of key executives, and an abuse contact.
In ICANN’s world, an Issue Report usually precedes a Policy Development Process, which can take a year or more to produce results.
While the GNSO motion passed, it was opposed as inadequate by factions such as the Intellectual Property Constituency, which has close ties to the US government.
As the IPC seemed to correctly predict, the GAC was not amused.
“It is simply impossible for us to write a briefing memo for our political managers to explain why you need a policy to simply put your name on your web site,” Radell told the GNSO Council yesterday. “It is simply mind-boggling that you would require that.”
She pointed out that at a session during the Singapore meeting, registrars had indicated a willingness to address more of the law enforcement demands.
“That’s the context in which we are now coming to you saying this looks pretty paltry and actually it looks a little silly,” she said.
Mason Cole from the registrar constituency denied that they were “roadblocking” law enforcement’s demands, saying that a PDP is the fastest way to create a policy binding on all registrars.
“I think law enforcement was very clear when they made their proposals to us that what they were looking for was binding, enforceable provisions of policy that could be imposed on the registrars,” he said. “A code of conduct or a voluntary method would not arrive at binding, enforceable policy and therefore probably wouldn’t achieve the outcomes that law enforcement representatives were seeking.”
The debate didn’t end yesterday. Radell said she intends to take it up with the ICANN board of directors, presumably at their joint meeting tomorrow.
The implicit threat underlying the GAC’s protest is a legislative one, and Radell and other GAC members made it pretty clear that their governments back home regard domain names as a crucial tool in fighting online crime.

New gTLDs: no advantage to applying early

ICANN has confirmed that new top-level domain applications filed early in next year’s application window will not get priority over those filed right at the end.
The subject of “batching” – the way ICANN plans to divide applications into more easily managed chunks of 500 – has seen some debate recently.
Some applicants and consultants have said that filing your application January 12 rather than April 12 would be a wise move, despite the evidence to the contrary.
Now ICANN senior vice president of stakeholder relations Kurt Pritz has busted the myth, during a session on new gTLDs with the Generic Names Supporting Organization in Dakar today.
“There’s no advantage to applying early or later in the process,” he said. “As long as your application is in by the due date it has the same chance of being in any batch.”
It doesn’t come much clearer than that.
ICANN has said that it only plans to process 500 applications at a time. If there are significantly more than 500, then it will process them in batches.
Due to the length of time it is expected to take to process an application, finding yourself in dumped into the second batch could add a few quarters to your go-live runway.
If you’re a commercial gTLD applicant, there could be a significant first-mover advantage to being in the first batch. Revenues from speculative and defensive registrations could be higher, before the novelty of new gTLDs gives way to fatigue.
Applicants in that position are going to use every trick in the book to streamline their process through ICANN and maximize their chances of being in the first batch.
While ICANN has not yet decided how to create the batches, it has ruled out filing time from the criteria. Pritz talked the GNSO through some of its current thinking today.
The preferred option is random selection. The problem with this idea is that it may fall foul of US gambling laws if it fits the definition of a lottery.
It sounds stupid, but it’s happened before: when Neustar introduced a random element to its launch of .biz, it would up having to pay $1.2 million to settle claims that it ran an illegal lottery.
“The issue of random selection is that we just have to make sure it complies with all possible applicable laws,” Pritz said. “Our initial legal research points out that this is real risk… but it is the most attractive form of selection because it is objective and fair.”
The other option under consideration is a “secondary time stamp”, Pritz said. This unhelpful label caused some head-scratching during the GNSO session today.
Pritz explained by analogy: imagine every applicant was asked to send a letter to ICANN, and the order of the batches would be determined by the order in which the letters are received.
The important thing to note is that this secondary time stamp would not be based on the date the application itself was submitted to ICANN.
Pritz said that ICANN had also discussed a “charity auction” batching method, but that this idea has now been ruled out.
Whatever mechanism is decided upon, it seems that applicants will have the opportunity to opt in or opt out of the first batch. Some .brand applicants currently clueless about how to use their gTLD may not be super-interested in getting priority processing, for example.
“We think those numbers are non-negligible,” Pritz said.

Will ICANN approve cheap gTLDs for poor applicants?

One of the big questions at ICANN’s 42nd public meeting in Dakar next week is whether the board of directors plans to approve subsidized new gTLD application fees for worthy applicants.
A volunteer working group known as JAS came up with a set of recommendations last month that would lower the $185,000 fee for applicants from developing nations with public benefit missions.
It was a wide-ranging set of proposals that would stretch beyond the scope of the $1 million to $2 million ICANN approved for applicant support initiatives at its last meeting in June.
Chiefly, JAS wants the application fee reduced to $45,000 for qualified developing-world applicants, meaning ICANN would have to find the funds to cover the $140,000 shortfall elsewhere.
In addition, JAS wants ICANN to set up a fund to loan money to these same applicants. It also wants these applicants to be able to pay fees on a staggered schedule.
Whether it was deliberate or not (I suspect it was semi-deliberate), the JAS wish-list seems to me to go above and beyond the support the ICANN board said it was prepared to offer in June.
I don’t think the board will grant those wishes when it meets next Friday, and here’s a few reasons why.
First, CEO Rod Beckstrom has already basically ruled out blanket fee reductions, even for poorer applicants, and he did so after the board had already discussed them.
At an ICANN panel on new gTLDs in London last month, Beckstrom was asked by an audience member if the application fee could be reduced before January.

At roughly 32 minutes into the embedded video, this is what he said:

There’s no plans to reduce the fee and I could not contemplate that happening before the program opens. The fees have been determined and there’s no process to review them, and there would be no basis at the present time because the costing estimates in the program appear to be reasonably accurate.

He went on to say that economies of scale may lead to a reduction in fees in future rounds, but did not mention the JAS recommendations at all.
As I was also on the panel, I called him on the omission later in the discussion, roughly 45 minutes into the video above. He said:

The board of directors did make a directional indication in Singapore to set aside up to a million to two million dollars for financial support for applicants…
However, it’s not a repricing of the fees, it would be some type of support for those applicants. A reduction in the application fee or effectively subsidizing the application fee is one possible concept, but what I can tell you as the CEO and as a board member is that board’s indication is one to two million dollars, not an unlimited number, so can do math and figure out what might be possible and what might not.
We’re not going to change the program fees, it just means there might be some benefit to or some support for some applicants, but it may not come in the form of that subsidy for the fee.

What we have here is JAS asking for a fundamental restructuring of the application fee in certain circumstances, and ICANN’s CEO saying that’s not likely to happen.
At that time, the JAS report had not been formally submitted to the board, but it had nevertheless been seen and discussed by the board at its two-day retreat in mid-September.
The GNSO, which had been frustrated with the cross-constituency structure of the JAS for some time, didn’t even formally approve the report before forwarding it to the board, due to time constraints.
Another indication of the board’s thinking on the JAS recommendations comes from the minutes of its Finance Committee meeting, September 15. Here’s an extract:

Staff has initiated efforts to be ready for implementation if and when approved. Establishment of a fund – a short-term mechanism for earmarking funds for applicant support, and a long-term formal mechanism for several purposes. Meeting community expectations: Board had approved US $2mm, while the JAS/GAC-ALAC recommendations would be more costly. Four tasks: developing criteria based on the JAS report plus practical concerns, developing procedures, entity for considering applications, and mechanism for holding the funds. Discussed the need to stay within the mission and purpose of ICANN and the ability to set-up special funds.

There’s no mention of application fees, but there is an acknowledgment that the JAS recommendations would be more expensive to implement than just the $2 million ICANN has already set aside.
There’s also talk of “practical concerns” and the “need to stay within the mission and purpose of ICANN”, all of which says to me that there’s a worry JAS asked for too much.
We’ll have to wait until next Friday to find out for sure, but my guess is that the board will likely side with ICANN’s bean-counters and that the JAS will not get much of what it asked for.

The DI Dakar Drunk-Dial Domain Dirt Dropbox

For the first time since DomainIncite launched, I’m skipping an ICANN meeting.
While many regular readers will be landing in Dakar, Senegal, over the next few days, I’ve decided this time to cover the meeting remotely.
For a reporter, in many ways remotely participating in ICANN meetings is a far easier proposition than actually being on the ground.
There’s no running around looking for power points to charge the laptop, no sweltering heat or icy air-con to contend with, no risk of almost getting mugged because you could only afford a hotel in the cheap end of town, very little danger of being forced to speak French.
The drawback of course is that the true value of an ICANN meeting isn’t in the uniformly webcast or magically transcribed sessions themselves.
It’s in the furtive hallway conversations, the over-the-shoulder whispered comments, the drinking banter and the passionate after-hours debates in the hotel bar.
I’m going to miss all that this time around.
To compensate, I’d like to announce the launch of the DI’s very own “remote participation” mechanism.
Let’s call it the DI Dakar Drunk-Dial Domain Dirt Dropbox or, if you like acronyms, the DIDDDDDD.
Hear a bit of good gossip in the bar? Maybe there’s a rumor about a new gTLD applicant, rumblings about disquiet in the GAC, a potential new ICANN CEO candidate…
Simply email your nugget to drunkgossip@domainincite.com and I’ll treat it every bit as confidentially as I would if I was standing right next to you with a bottle of Bière la Gazelle in my hand.
To make things more interesting, for every email sent to this address during Dakar, I’ll chug two fingers or down a shot.
Day or night, I promise.