“Beware of Hookers”, ICANN attendees told

ICANN has published a security guide for delegates planning to attend its meeting in Cartagena, Colombia, this December, which makes quite entertaining reading.
A highlight of the report (pdf), prepared by outside consultants Control Risks, warns attendees to steer clear of bar prostitutes who plan to take advantage of them.

All travelers should avoid bars which have public touts (or “spruikers”) standing outside encouraging them to enter. Many of these bars attract high levels of local prostitutes, some who intend to rob tourists by drugging them in the bar or in their hotel rooms.

Sage advice.
The report also recommends staying off the streets after 11pm, using official taxis, keeping your wallets clean of identifying information, and not resisting muggers/abductors.

Fight for your life, but not your possessions.

I’m cherry-picking the scary stuff here, obviously. In general, the report says Cartagena is fairly safe. Last year, there were only two kidnappings in the city.

Cartagena enjoys a mostly deserved reputation as one of the safe destinations for foreign travelers in Colombia. Certainly, violent crime rarely affects foreign visitors to the city.

ICANN has said that it will commission such reports when there is a concern that security at its chosen meeting locations may not be up to scratch.
I believe the new meetings security plan was introduced in response to the vague terrorism threats that clouded the Nairobi meeting earlier this year, keeping many flighty Americans at home.

IPv4 pool to dry up in 2011

ICANN has confirmed that it will run out of unassigned IPv4 address space some time next year.
In an update to its Plan for Enhancing Internet Security, Stability and Resiliency, published yesterday, ICANN said it “expects to make the last allocations of IPv4 unicast space to the Regional Internet Registries (RIRs) during the calendar year 2011.”
While this means ICANN will largely be out of the IPv4 business, it does not of course mean that there will be no IPv4 address space left to be allocated to ISPs and businesses.
ICANN points out that the RIRs will still have their pools of unallocated addresses, and that they’ve been drawing up plans to hand out smaller blocks to new ISPs as well as allowing the transfer of IPv4 addresses between networks.
The confirmation that 2011 is the year that IPv4 dries up is not unanticipated. ICANN has been flagging it up as the likely timeframe for a few years now.
The solution to the problem is IPv6, which is large enough to never run out of addresses. The trick is making sure the new protocol is universally supported, so IPv6 networks can talk to IPv4 networks and vice versa.
The updated security plan document contains a few other nibbles of interest.
For instance, the security budget for the next year is down slightly on the last, $11.52 million versus $12.8 million, largely due to a requirement last year to build out a secure data center.
There’s also the admission that ICANN has developed an as-yet unpublished “Meetings Security Plan”, presumably in response to the terrorism fears that kept many constituents at home for the Nairobi meeting in March.

New TLD guidebook could be finalized at ICANN retreat

ICANN’s Draft Applicant Guidebook for new TLDs could become the Final Applicant Guidebook at an ICANN retreat before the next ICANN meeting.
Chairman Peter Dengate Thrush said at a press conference here in Brussels earlier that a private two-day board retreat this year, focused entirely on new TLDs, could “clear up any remaining issues” with the DAG.
I believe he was referring to the ICANN board’s scheduled September 24-25 retreat, although he may have had something else in mind.
Dengate Thrush said that we should not expect the board to pass as many resolutions relating to the DAG at the end of the Brussels meeting as it did at the end of Nairobi three months ago.
But he still expects DAG v4 will be the final draft published before the guidebook is finalized.
“The reality is that there are a number of overarching issues where the community has to reach consensus, and it’s difficult for us to put time limits on the community,” he said.
A few minutes ago, during an open mic session on new TLDs, Jon Nevett of Domain Dimensions questioned whether there should be a special ICANN meeting, before the retreat, to give the community a chance to help with the finalization process.

Will ICANN punt .xxx in Brussels?

Is ICANN set to delay approval of the proposed .xxx top-level domain – again – in Brussels?
That’s my reading of ICANN’s latest document concerning ICM Registry’s long-running and controversial battle for a porn-only TLD.
This week, ICANN submitted its summary of the public comment period that ran to May 10. It’s a fair bit shorter than the one Kieren McCarthy compiled for ICM last month.
As usual, it’s written in a fairly neutral tone. But, if you’re feeling conspiratorial, the mask does slip on occasion, perhaps giving a sense of where the .xxx application could head next.
The ICANN summary occasionally breaks from reporting what a commenter actually said in order to highlight a potential problem they did not address.
Example (my emphasis):

Only two commenters directly addressed the question of further interaction with the Governmental Advisory Committee (GAC) on the .XXX sTLD Application. Both of those commenters were against seeking any further input from the GAC outside of any public comment period. Neither of these commenters – nor any other – addressed the potential violation of the ICANN Bylaws that could result from the Board’s failure to properly consider the advice of the GAC

This suggests, to me, that the ICANN board will be receiving advice to the effect that further GAC input needs to be forthcoming before it can move forward with .xxx.
If this is the case, the GAC might have to produce some advice before next Friday’s board meeting if ICM has any hope of getting back around the negotiating table prior to Cartagena in December.
That’s not the only reason to believe ICANN may punt .xxx again, however. Elsewhere in the report, we read (my emphasis again):

For those in favor of proceeding with the .XXX sTLD Application, many created an alternative option – that ICM and ICANN should proceed to a contract right away. There was substantial discussion on this point in the ICM submissions. Few commenters addressed the technical realities identified within the Process Report ‐ that prompt execution of the agreement negotiated in 2007 is not feasible.

The Process Report referenced says that it is not possible to go straight into contract talks because ICM first applied for .xxx more than six years ago.
This has been a bone of contention. ICM points to .post, which was applied for at the same time as .xxx and only approved late last year, as proof that the passage of time should be no barrier.
But ICANN president Rod Beckstrom doesn’t buy that comparison. He wrote to ICM (pdf) at the end of March noting that .post was backed by the International Postal Union, whereas .xxx is “sponsored” by IFFOR, an organization created by ICM purely to act as its sponsor.
In that letter, Beckstrom talks about due diligence to make sure ICM and IFFOR still satisfy financial and technical criteria, and a review of whether .xxx “can still satisfy the requisite sponsorship criteria”.
I’ll admit that I’m breaking out the crystal ball a bit here, and I’ve been wrong before, but I don’t think it’s looking great for ICM in Brussels.

ICANN picks Colombia for December meeting

ICANN chief Rod Beckstrom has just confirmed via Twitter that Cartagena, Colombia has been picked for the organization’s December meeting.
Judging from US State Department reports, the country is nowadays not nearly as scary as it was when Joan Wilder made a flying visit to rescue her sister in 1984.
Still, I’m guessing we’ll still see a little bit of that nervousness and paranoia that usually rears its head when ICANN heads for cities with a reputation for violent crime.
Terrorism concerns in Kenya caused many US stakeholders to stay at home and brave unreasonably early mornings participating remotely.
Even the choice of Mexico City caused a bit of a stir last year.
Personally, I’d love to see ICANN hold a meeting in Oakland or Baltimore, just to see what the security advisory looks like.

ICANN may kick .xxx into new gTLD round

ICANN has chosen to deal with the controversial .xxx TLD application by leaving essentially all options, including urging it into the next gTLD round, wide open.
ICM Registry had pushed for a speedy resolution to its long-running application, following the Independent Review Panel decision that went in its favour last month, but it hasn’t got one.
In Nairobi, ICANN’s board asked ICANN’s staff to tell it what its options were for dealing with the ruling, and staff today responded with this flowchart. Oh, and this flowchart.
It seems that these options are still on the table: (continue reading)

Dot-XXX lights fire under ICANN’s feet

ICM Registry has urged ICANN to stop messing around and finalise the contract that would add .xxx to the domain name system.
“There is no legitimate obstacle to the approval of ICM’s registry agreement,” ICM chair Stuart Lawley said in a letter to ICANN yesterday. “We can see no reason for further delay in the process of approving ICM’s registry agreement”.
At its Nairobi meeting earlier this month, ICANN’s board decided to hand the problem of how to handle .xxx to its staff, saying it “wishes to create a transparent set of process options which can be published for public comment.”
ICM now claims that no such process options are necessary. The .post application, Lawley said, was approved last December, six years after it was made, without the need for any new processes.
There are some differences between .post and .xxx, of course. While the .xxx application has previously been approved, it has also previously been rejected.
It is back on the table following an Independent Review Panel decision that ICANN broke its fairness rules by singling out ICM for special treatment.
Lawley reminds ICANN of as much several times in his latest letter, which can be found here.
ICANN’s staff is expected to deliver its process options next week. There will be a period of public comment, and the board will have to make a call by its June meeting in Brussels.

ICANN: .xxx is not approved

ICANN never makes a decision if it can make a process instead, and that seems to be the case with the board’s latest call on .xxx.
The board voted this morning to kick ICM’s proposal until after the Brussels meeting in June, on the basis that it needs a process by which it can approve .xxx.
While this is mixed news for ICM – it’s not what it hoped for but the company still has a pretty good chance of getting what it wants – the language used in the resolution clearly indicates that the board believes .xxx is currently in an unapproved state: (continue reading)

Beckstrom: DNS is under attack

ICANN chief Rod Beckstrom has come in for a bit of criticism over “inflammatory” comments he made at the Government Advisory Committee meeting on Tuesday.
The headline quote: “The domain name system is more fragile and vulnerable today than it has ever been. It could stop at any given point in time, literally.”
Beckstrom described a DNS on its knees, then pointed the finger at unspecified nations for DNS abuses allegedly happening within their virtual borders, and said he would be writing to GAC members for more information and advice.
It was part call to arms, part Chicken Little.
If you missed it, here’s a full transcript. (continue reading)

Security faux pas in Nairobi

ICANN committed a diplomatic faux pas in its handling of the security scare before its meeting in Nairobi, according to the Kenyan Government Advisory Committee rep.
“We spent most of the months leading up to the meeting occupied and dealing with issues to do with security and I feel this was to do with badly handled communication,” Alice Munyua of the Communications Commission of Kenya said during a meeting on Tuesday.
“I feel that communicating people’s fears (continue reading)