Home / Blogs

Now Begins the Third Stage of ICANN’s TLD Triathlon

The ICANN community here in Singapore is celebrating after the historic vote to expand top-level domains (TLDs). And while I wouldn’t begrudge anyone a few Singapore Slings, I think it’s a little early to start celebrating. The marathon effort ICANN began 5 years ago isn’t even close to reaching the finish line.

Actually, marathon is probably the wrong analogy. Try this:

A month from now, our host city of Singapore will welcome competitors to the 10th International Triathlon. What makes a triathlon so uniquely challenging is that after you complete a grueling swim and punishing bike race, you still have the hardest stage ahead of you: a long-distance run.

That’s where the ICANN community is now—just off the starting line for the longest and hardest stage of the race. How we run this stage will determine whether or not new TLDs succeed from the standpoint of the stakeholder groups that really matter: domain registrants and Internet users.

The first stage of the TLD triathlon—the open-water swim—was a painstaking, community-driven policy development process that took the better part of five years. It had all the feeling of a swim in the open sea, requiring constant movement without much forward progress. But we eventually stumbled onto the beach only to begin an unexpectedly contentious stage two.

The second stage of the TLD triathlon—the bike race—was the ICANN Board’s six-month saga of high-pressure, high-stakes negotiations with the Government Advisory Committee. Like a bike race, it was fast and dangerous, putting at risk everything that was accomplished in the prior stage. Monday’s 13-1 vote in favor of TLD expansion was like the race stage, where you feel grateful just for having survived.

That brought us to what I and several board members called “the end of the beginning”. Now ICANN faces stage three: the long-haul work of implementing the most ambitious undertaking yet.

This next stage is no victory lap. The global Internet community—including many stakeholders who weren’t satisfied with the outcome of the policy development process—will be watching ICANN’s every move to find an excuse to supplant its multi-stakeholder model with traditional multi-government models like the UN.

ICANN board resolution leaves enough unfinished business for stakeholders to spend the next year tweaking the “final” guidebook, even as ICANN’s foot-weary staff does the difficult work of putting it into effect.

During this stage of the race, ICANN must uphold its signature commitments to accountability and transparency. As the process evolves in keeping with today’s resolution, ICANN must also uphold the multistakeholder model and avoid any closed-door, staff-driven shortcuts that might seem expedient as the running gets harder.

Given the timeline approved this week, we’re likely to see our first new gTLDs sometime in 2013. If we all start running now, we can finish the TLD Triathlon and throw a real party—in about two years.

By Steve DelBianco, Executive Director at NetChoice

Filed Under

Comments

You just don't give up, Steve! Steve Goldstein  –  Jun 21, 2011 8:32 PM

More FUD, Steve!  In your recent House testimony, you counseled “Mind the GAC,” a play on words of the London Tube’s “Mind the gap!”. Might I very indelicately suggest that you mind something else ending in “-ap?”

I would expect that, if not harried by last ditch attempts to round up compliant Congress-critters or other governmental officials in order to delay the process further, ICANN will proceed with dispatch to honor all its obligations for implementing new gTLDs.  Spreading FUD, however subtly, just doesn’t help.

—Steve G.

Don't forget the year 2000 applicants Karl Auerbach  –  Jun 21, 2011 11:37 PM

There are 40 applications that are still pending from year 2000.  Those people paid their application fee ($50,000 each) and ICANN did not refuse them but, rather, told them to wait - and they are still waiting.

Simply refunding the application fee or giving a discount on a new application is *not* an appropriate resolution.

Rather those applicants deserve to have their applications handled, and handled according to the rules that were in place when they filed those applications and paid their money.

At least one of those applicants - for .web - was operational pending their application and had customers (I was among them) here in California.  (I have had a website operating under my name in .web since before year 2000.)

So those who aspire for .web - should be aware that there is an existing .web registry here in California and that anyone who aspires to .web TLD might find themselves precluded from operating in California because there is an established business registering under the name .web that has more than a decade of priority.

(I have no relationship to the .web people except as a long time customer, but I do dislike watching them - and my existing name registration in .web - get royally scrod.)

Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

VINTON CERF
Co-designer of the TCP/IP Protocols & the Architecture of the Internet

Related

Topics

IPv4 Markets

Sponsored byIPv4.Global

DNS

Sponsored byDNIB.com

Cybersecurity

Sponsored byVerisign

Threat Intelligence

Sponsored byWhoisXML API

Domain Names

Sponsored byVerisign

Brand Protection

Sponsored byCSC

New TLDs

Sponsored byRadix