Latest news of the domain name industry

Recent Posts

US gov: we can’t support ICANN accountability plan

Kevin Murphy, September 24, 2015, Domain Policy

The US National Telecommunications and Information Administration has waded into the ICANN accountability debate, possibly muddying the waters in the process.

In a blog post last night, NTIA head Larry Strickling said that community proposals for enhancing accountability were not yet detailed enough, and had not reached the desired level of consensus, for the NTIA to support them.

He urged everyone involved to simplify the proposals and to work on areas where there is still confusion or disagreement.

The comments were directed at the Cross Community Working Group on Enhancing Accountability (CCWG), a diverse volunteer committee that has been tasked with coming up with ways to improve ICANN accountability after the US government severs formal oversight of the IANA functions.

That group spent a year coming up with a set of draft proposals, outlining measures such as stronger, harder-to-change bylaws and improvements to the Independent Review Process.

But the main organizational change it proposed is where the most conflict has emerged.

CCWG thinks the best way to give the community a way to enforce accountability is to change ICANN into a membership organization, a certain type of legal entity under California law.

It would have a Sole Member, a legal entity peopled by members of each part of the community, which would have to right to take ICANN to court to enforce its bylaws.

The ICANN board doesn’t dig this idea one bit. Its outside attorneys at Jones Day have counseled against such a move as untested, overly complex and potentially subject to capture.

On a recent three-hour teleconference, the board proposed the Sole Member model be replaced by a “Multistakeholder Enforcement Mechanism”.

The MEM would create a binding arbitration process — enforceable in California court — through which ICANN’s supporting organizations and advisory committees could gang up to challenge decisions that they believe go against ICANN’s Fundamental Bylaws.

Since this bombshell, a key question facing the CCWG has been: is the board’s view being informed primarily by its lawyers, or has Strickling been quietly raising NTIA concerns about the proposal via back-channels?

If it’s the former, the CCWG and its own outside counsel could robustly argue the community’s corner.

If it’s the latter, it’s pretty much back to the drawing board — because if the NTIA doesn’t like the plan, it won’t be approved.

Unfortunately, Strickling’s latest blog post avoids giving any straight answers, saying “it is not our role to substitute our judgment for that of the community”.

But his choice of language may suggest a degree of support for the board’s position.

As I stated in Argentina in June, provide us a plan that is as simple as possible but still meets our conditions and the community’s needs. Every day you take now to simplify the plan, resolve questions, and provide details will shorten the length of time it will take to implement the plan and increase the likelihood that the plan will preserve the security and stability of the Internet. Putting in the extra effort now to develop the best possible consensus plan should enhance the likelihood that the transition will be completed on a timely schedule.

The emphasis on “simplicity” could be read as coded support for the board, which has repeatedly said that it thinks the Sole Member model may be too complicated for the NTIA to swallow.

Both the board and Strickling’s latest post refer back to a speech he made in Buenos Aires in June, in which he said:

If a plan is too complex, it increases the likelihood there will be issues that emerge later. Unnecessary complexity increases the possibility that the community will be unable to identify and mitigate all the consequences of the plan. And a complex plan almost certainly will take longer to implement.

Strickling certainly knows that the board has been citing these comments in its objection to the Sole Member model, so the fact that he chose to repeat them may be indicative of which way he is leaning. Or maybe it isn’t.

Either way, I think it’s going to be tough for the CCWG to easily dismiss the board’s concerns.

CCWG members are currently on planes heading to ICANN headquarters in Los Angeles for a two-day face-to-face meeting at which the chairs “expect that a large portion of our time… will be reserved to answering the tough questions”.

Many believe that unless this meeting is extraordinarily successful, it’s going to be tough for an IANA transition proposal to be approved by the NTIA under the current US administration.

Anger as ICANN’s member flops before board

Kevin Murphy, September 4, 2015, Domain Policy

ICANN’s board of directors came to blows with its key accountability working group this week, over proposals that would give ICANN the community the right to sue ICANN the organization.

An extraordinary three-hour teleconference between the board and the Cross Community Working Group on Enhancing Accountability (CCWG) Wednesday night came across like some kind of weird, Orwellian, passive-aggressive piece of emotional domestic abuse.

The CCWG, a group of volunteers coming from all parts of the ICANN community, has created a set of proposals for improving ICANN’s accountability to the community as part of its transition process away from US government oversight.

The idea is to create sufficient accountability mechanisms so that if in future the entire ICANN board grows goatee beards and turns Eeevil, the community will still be able to hold them to their bylaws commitments.

The CCWG, following the advice of an independent law firm, decided that the best way to do this was to turn ICANN into a membership organization with a “Sole Member”.

This member would be a legal entity run by community members that would have the right under California law to sue ICANN if it ever failed to live up to its bylaws.

For example, if ICANN refused to implement the decisions of an Independent Review Panel, the member could seek to have the ruling enforced by a court.

This is just one of many proposals made by the CCWG currently open for public comment.

Highly unusually for a public comment period, the ICANN board is going to be a commenter in this case. While its comments have not been published yet, it has taken advice from its lawyers at Jones Day that may give an indication of how it is leaning.

Wednesday night’s call was designed to give the board the chance to bring its initial thinking to the CCWG.

Instead, it wound up being almost entirely about the proposed membership model and the board’s statements that while it supported the CCWG’s proposals 100% it also wanted them fundamentally rewritten.

The board wants the idea of a Sole Member model thrown out and replaced with a new arbitration process that would be legally enforceable in California courts.

So, instead of a legal-entity “member” suing ICANN, some as-yet unidentified community entity would take ICANN to arbitration. The decision of the arbitration panel could then be enforced by the courts if ICANN failed to abide by it.

When CCWG members asked who, in the absence of a legal entity, would take ICANN to arbitration and then sue it, the board had no answer. Instead, directors said the CCWG’s legal advisers should talk to Jones Day to hammer out the “technical” details.

Some members claimed that it would be “impossible” to give the community legal standing to sue ICANN without a membership model. Others said that the board’s 11th hour suggested rewrites would make it “impossible” to hit the deadline for a final proposal by the Dublin meeting next month.

At least a third of the 2-hour 47-minute call was wasted as the CCWG struggled to understand the doublespeak the board had brought into the discussion.

Directors continually insisted that they “completely supported” CCWG’s proposals on enforcement “without reservation”, while simultaneously saying the Sole Member model should be thrown out.

Half way through the call, CCWG co-chair Thomas Rickert reflected exasperation among members: “There is obviously difficulty to understand by many on this call how you fully support what we are doing while proposing something which appears like a complete rewrite.”

Shortly thereafter, Chehade responded:

Why don’t we just agree that we are agreeing with you that the community must be able to get enforcement in California courts, that we will ensure that they have the standing to do it without question. And if we are all in agreement that we are in agreement with each other let’s then let the technical people go solve this. If they call come back and tell us that frankly that advice was flawed, then let’s deal with it then in good faith. But that’s what we’re sharing with you.

Directors said that the proposed member model might have unintended consequences, and that the US government may not approve a proposal that overly complicates ICANN’s legal structure.

An hour later, the CCWG was still scratching its head, nerves were beginning to wear, and the tone was getting increasingly testy as the CCWG repeatedly asked the board to explain how it could express support and simultaneously propose an alternative solution.

“There is absolutely no new proposal,” Chehade said, eventually. “We are embracing your proposal and the objectives of the community. Please hear me on this. There is no new proposal.”

He said:

Take your work and break it down: board removal, standing reconsideration, enhancing – getting the IRP back on the track we set, you know, fundamental bylaw, binding arbitration or mechanisms of enforceability. All of the things you have come up with, we are accepting. So when your reaction to our two last hours is that we’re refusing to add any accountability, I don’t know how you come to that frankly…

you yourself in the proposal say that this proposal is not finished, it needs a lot of work. So what we’re saying to you is let’s take this proposal which is not finished and let’s figure out ways to make it real, and real in the next few weeks so we can move forward…

The only area where we are telling you we would like to propose a different mechanism to achieve the same goal is the enforceability.

The whole three hours reminded me of a nightmare-scenario interview where the interviewee has been media-trained up the wazoo and refuses to sway from a set of vaguely scripted talking points.

But which proposal is the right one for ICANN?

Beats me. What does seem quite clear to me is that the board and CCWG are at odds now, despite what ICANN says, and that the expected delivery of a final accountability proposal by Dublin is in serious doubt.

Following the call, ICANN chair Steve Crocker posted a blog post that sought to clarify the board’s position, characterizing it as agreement in principle but disagreement on implementation. He wrote:

We have suggestions on how these [CCWG proposals] could be operationalized. With regards to the mechanisms for community enforceability, where the current proposal still warrants much detail that may not be achievable we have a suggestion on how to deliver on it in a stable way, as increased enforceability must not open up questions of, for example, capture or diminishing of checks and balances.

The Wednesday meeting’s audio, transcript and other notes can all be found here.

US gives ICANN an extra year to complete transition

Kevin Murphy, August 18, 2015, Domain Policy

US government oversight of ICANN and the domain name system will end a year later than originally expected.

The National Telecommunications and Information Administration said last night that it has extended ICANN’s IANA contract until September 30, 2016, giving the community and others more time to complete and review the transition proposals.

NTIA assistant secretary Larry Strickling wrote that “it has become increasingly apparent over the last few months that the community needs time to complete its work, have the plan reviewed by the U.S. Government and then implement it if it is approved.”

Simultaneously, NTIA has finally published a proposal — written by ICANN and Verisign — for how management of the DNS root will move away from hands-on US involvement.

The extension of the IANA contract from its September 30, 2015 end date was not unexpected. The current contract allows for such extensions.

As we recently reported, outgoing ICANN CEO Fadi Chehade had guessed a mid-2016 finalization of the transition.

Regardless, expect op-eds in the coming days to claim this as some kind of political victory against the Obama administration.

Part of the reason for the extension, beyond the fact that the ICANN community hasn’t finished its work yet, is legislation proposed in the US.

The inappropriately named DOTCOM Act, passed by the House but frozen for political reasons in the Senate by Tea Party presidential hopeful Sen Ted Cruz, would give Congress 30 legislative days (which could equal months of real time) to review the IANA transition proposals.

There are basically three prongs to the transition, each with very long names.

The “Proposal to Transition the Stewardship of the Internet Assigned Numbers Authority (IANA) Functions from the U.S. Commerce Department’s National Telecommunications and Information Administration (NTIA) to the Global Multistakeholder Community” is the first.

That was created by the multistakeholder IANA Stewardship Transition Coordination Group (ICG) and deals with how the IANA contract will be managed after the US government goes away.

The second prong comes from the Cross Community Working Group on Enhancing ICANN Accountability, which deals with how ICANN itself can improve its accountability to the internet community without the Damoclean sword of US intervention hanging over it.

The CCWG’s latest draft report would strengthen the ICANN board against capture by, for example, making certain bylaws harder to amend and giving the community the right to fire directors.

Both of these proposals are currently open for public comment here.

The third prong, which only appears to have been published this week, deals with the nuts and bolts of how changes to the DNS root zone are made.

The current system is a tripartite arrangement between IANA, NTIA and Verisign.

When a TLD operator needs a change to the DNS root — for example adding a name server for its TLD — the request is submitted to and processed by IANA, sent to NTIA for authorization, then actually implemented on the primary root server by Verisign.

Under the new proposal (pdf) to phase the NTIA out of this arrangement, the NTIA’s “authorization” role would be temporarily complemented by a parallel “authentication” role.

The proposal is not written in the clearest English, even by ICANN standards, but it seems that the current Root Zone Management System would be duplicated in its entirety and every change request would have to be processed by both systems.

The output of both would be compared for discrepancies before Verisign actually made the changes to the root.

It seems that this model is only being proposed as a temporary measure, almost like a proof of concept to demonstrate that the NTIA’s current authorization role isn’t actually required and won’t be replaced in this brave new world.

Chehade confirms he’ll be gone before IANA transition is done

Kevin Murphy, June 22, 2015, Domain Policy

ICANN CEO Fadi Chehade has laid out his current best thinking for the timeline of the IANA’s transition from US government oversight, and he’ll be gone well before it’s done.

At the opening ceremony of the ICANN 53 meeting in Buenos Aires today, Chehade described how June 2016 is a likely date for the divorce; three months after his resignation takes effect.

Chehade said:

I asked our community leaders, “Based on your plans and what you’re seeing and what you know today, when could that finish?” The answers that are coming back to us seem to indicate that by ICANN 56, which will be back in Latin America in the middle of 2016, a year from today, the contract with the US Government could come to an end.

He showed a slide that broke the remaining work of the transition into three phases.

Work being carried out within ICANN is not entirely to blame for the length of time the process will take.

The US National Telecommunications and Information Administration needs 60 to 90 days to review the final community-developed transition proposal.

And under forthcoming US legislation, 30 legislative days will be required for the US Congress to review the NTIA’s approval of the plan.

Thirty legislative days, Chehade explained, could mean as many as 60 actual days, depending on the yet-unpublished 2016 Congressional calendar.

He urged the community focus hard on Phase One in his graphic — actually producing a consensus transition plan.

The target for delivery of this is the next ICANN meeting, 54, which will take place in Dublin, Ireland from October 18 to October 22 this year.

The IANA transition in a nutshell

Kevin Murphy, February 27, 2015, Domain Policy

The US plan to remove itself from its unique DNS oversight role is about creating a coalition of nations to thwart attempts by Russia and other “authoritarian” countries to increase government control of the internet.

That’s according to Larry Strickling, assistant secretary at the US National Telecommunications and Information Administration, who delivered a beautifully succinct explanation to confused senators at a hearing in Washington DC this week.

Despite unnecessary diversions into issues such as net neutrality and copyright protection — which I’m sure was not at all due to senators trying to score points with their corporate paymasters — the Commerce Committee hearing was surprising well-informed and not nearly as angry as it could have been.

Senators, mostly Republicans, reiterated their concerns that for the US to give up its role in the IANA functions contract could invite a takeover of ICANN by unfriendly nations such as China and Russia, thereby harming internet freedom.

At one point, Strickling was asked by a senator: “If there’s not a problem, what are we trying to fix here?”

His answer was one the best explanations of the political back-story of the transition that I’ve heard, so I’m going to quote it in full here.

There has been a problem, sir. At the end of 2012 when the world’s governments got together in Dubai for the ITU WCIT — World Conference on International Telecommunications — you had around 80 countries who voted to say the ITU needs to be more involved in internet governance. These were largely countries in the developing world siding with the more authoritarian regimes.

Part of the impetus for this was the continued irritation that many governments have, that has been exploited by authoritarian countries, that the United States with its special role with ICANN is in a position to control the internet in these developing counties and to turn it off in these countries and to otherwise interfere with the ability of countries to manage their own affairs with respect to the internet.

After this [IANA transition] announcement was made the next two large international meetings at which governments came together you saw a major change in position among the developing countries. We didn’t see any change in position from the authoritarian countries — and you’re not, they’re not going to change their views on this. But the key to succeeding in this on the global stage is to bring the rest of the world along with us, and that’s what we saw at the NETmundial conference in Brazil last April where the only countries who spoke out against the multi-stakeholder model of internet governance were Russia and Cuba.

We then flash forward to the ITU plenipotentiary conference in Busan last November and again you had Russia with the same proposals it’s been making for 10 years: that these functions ought to be transferred to the ITU and managed by governments. And that was beaten back by a coalition of developed and developing countries. So we’ve seen immediate results, or significant results, by the basis of our having been able to take this issue off the table for these countries, to get them to look at what’s really best for them without this overhang of a US role that was unique among governments and which was a source of irritation to governments and was being exploited to our detriment by foreign governments.

The fact of the matter is that the role we play with respect of the IANA functions is a clerical role. It’s truly stewardship. As I said before, we don’t provide any oversight of the policy judgments that ICANN and the multi-stakeholder community make. We participate as a government in the Governmental Advisory Committee, and we will continue to do that in future and will be vigorous advocates for a free and open internet.

The special role we play with respect of the IANA functions is totally administrative and clerical, yet it has been exploited by other governments — authoritarian governments — to our detriment. We’ve taken that off to the table by announcing this transition and as we complete it we will continue to see the benefits of that through the continued adoption and support for this model by the developing world.

His views were echoed by ICANN CEO Fadi Chehade more than once during the hearing, talking about how the transition process is designed to bring on board the “middle countries”, rather than already-allied nations or the fringe, minority authoritarian countries.

He cited Brazil as the key example of a government once in favor of more ITU control of the internet that is now, largely due to Chehade’s outreach and its key role in the NETmundial conference, firmly in the multi-stakeholder model camp.

The entire archived hearing can be viewed here.

Chehade to face Congressional grilling this week

Kevin Murphy, February 23, 2015, Domain Policy

ICANN CEO Fadi Chehade is heading to Washington DC this week to defend plans to decouple the organization from formal US oversight in front of a potentially hostile committee of Congresspeople.

The Senate Committee on Commerce, Science, and Transportation will meet this Wednesday at 1000 local time to grill Chehade and others on the plan to remove the US government from the current triumvirate responsible for managing changes to the DNS root zone under the IANA arrangements.

He will be joined by Larry Strickling, who as head of the National Telecommunications and Information Administration is the US government’s point person on the transition, and Ambassador David Gross, a top DC lawyer formerly with the Department of State.

All three men are pro-transition, while the Republican-tilted committee is likely to be much more skeptical.

The blurb for the Wednesday hearing reads:

As the U.S. government considers relinquishing control over certain aspects of Internet governance to the private sector, concerns remain that the loss of U.S. involvement over the Internet Assigned Numbers Authority (IANA) could empower foreign powers — acting through intergovernmental institutions or other surrogates — to gain increased control over critical Internet functions.

Republicans and right-leaning media commentators have warned that handing over IANA oversight to a multistakeholder body risks giving too much power to governments the US doesn’t like, such as Russia and China.

Several bills introduced in the House and Senate over the last year would have given Congress much more power to delay or deny the transition.

An amendment to an appropriations bill approved in December prevents the NTIA from spending any taxpayer money on relinquishing its DNS root oversight role until after September 30 this year, the same day that the current IANA contract expires.

This effectively prevents a transition during the current IANA contract’s run. Strickling recently said that the NTIA is complying with this legislation, but noted that it does not prevent the agency participating in the development of the transition proposal.

ICANN community working groups are currently working on plans for ICANN oversight post-NTIA and for addressing ICANN accountability.

These documents are hoped to be ready to sent to the NTIA by July, so the NTIA will have enough time to consider them before September 30.

Strickling recently addressed this date in a speech at the State of the Net conference in Washington, saying:

I want to reiterate again that there is no hard and fast deadline for this transition. September 2015 has been a target date because that is when the base period of our contract with ICANN expires. But this should not be seen as a deadline. If the community needs more time, we have the ability to extend the IANA functions contract for up to four years. It is up to the community to determine a timeline that works best for stakeholders as they develop a proposal that meets NTIA’s conditions, but also works.

Opponents of the transition say that because the NTIA is prevented from terminating the IANA contract before October 1, the NTIA will have no choice but to extend it until September 30, 2017.

Given that 2016 is a presidential election year in the US, Barack Obama would be a private citizen again by the time the next opportunity to transition comes around, they say.

Which presidential hopeful — from either party — would not buckle if asked whether he supports a plan to let Iran run the internet? That’s the political logic at work here.

Chehade himself told the AFP news agency earlier this month that the transition would have to happen before the 2016 elections, to avoid political distractions.

I’m not so sure I agree with the premise that, due to the restraints imposed by the appropriation bill, the transition now has to happen under the next president’s administration.

In my layman’s reading of the current IANA contract, the NTIA is able to terminate it for the “convenience of the government” pretty much whenever it wants.

There’s also an option to extend the contract by up to six months. The NTIA exercised this option in March 2012 when it did not approve of ICANN’s first renewal proposals.

Community proposes way to replace US oversight of ICANN

Kevin Murphy, December 2, 2014, Domain Policy

The process of removing the US government from management of the DNS root system took a significant step forward today, with the publication of a community proposal for a transition.

The Cross Community Working Group, which convened itself earlier this year, has published a proposal to replace the US with a new contracting company and a bunch of committees.

The DNS community has been tasked with coming up with a way to transition stewardship of the IANA functions from the US National Telecommunications and Information administration, which said in March this year that it intends to relinquish its historic, but largely symbolic, Damoclean role.

After discussions which by any measure of ICANN policy-making have been forcibly swift, the 119-member CWG has now presented two broad options.

The first, a description of which forms the bulk of its report, would see ICANN overseen by a new, lightweight non-profit company managed by multi-stakeholder committees.

The other, which doesn’t get much airplay in the document, would see ICANN simply take over the NTIA’s responsibilities entirely. Accountability would be provided by enhanced accountability processes within the existing ICANN structure.

Under the primary proposal, the CWG was keen to avoid creating something ICANN-like to oversee ICANN, due to the complexity and cost, but it also decided that ICANN remains the best place to house the IANA function for the foreseeable future.

It’s proposed a new company, known currently as “Contract Co”, that would be replace the NTIA as the party that contracts with ICANN to run IANA. It would have “little or no staff”.

The contract itself would be developed and overseen by a Multistakeholder Review Team, comprising people drawn from each area of the ICANN community.

The precise make-up of this MRT is still open to discussion and will be, I suspect, the subject of some pretty fierce debate as the various competing interest groups wrestle to have themselves with the strongest possible representation.

Like the NTIA, the MRT would have the power to pick another entity to run IANA in future, should ICANN screw up.

A new Customer Standing Panel would comprise executives from gTLD and ccTLD registries — the “customers” of IANA’s naming functions — and would have the job of relaying the concerns of registries to the MRT, keeping ICANN accountable to its primary users.

Finally, there’d be an Independent Appeals Panel. Any IANA decision — presumably including the delegation or redelegation of a TLD — could be appealed to this IAP. This function would very probably be outsourced on a case-by-case basis to an existing arbitration body.

Is this worrying? Arbitration panels handling new gTLD disputes haven’t exactly inspired confidence in their ability to provide consistent — or even rational — decisions over the last year or so. Should the last word on what goes into or stays out of the DNS root really go to the same folk who think .通販 and .shop are too confusingly similar to coexist on the internet?

There doesn’t appear to be anything massively surprising in the proposal. When ICANN or its community try to solve a problem the answer is usually a new committee, and the ideas of MRTs, CSPs and IAPs do seem to mirror existing structures to an extent.

The whole thing can be downloaded and read over here.

There’s a December 22 deadline for comment. It will be submitted to the IANA Stewardship Transition Coordination Group by the end of January, with a view to getting a final proposal to the US government next summer in time for the hoped-for September 30 handover date.

Unanimous support for new ICANN appeals process

Kevin Murphy, June 30, 2014, Domain Policy

The Generic Names Supporting Organization has issued an “unprecedented” statement of “unanimous” support for a new way for ICANN community members to appeal ICANN decisions.

All seven constituency groups signed onto a statement that was read by representatives of registries, non-commercial users and intellectual property interests at the ICANN 50 public forum last week.

“It only took us 50 meetings, but I think the rarity of what you’re witnessing this afternoon sends a very strong message about our views,” the Registries Stakeholder Group’s Keith Drazek said.

This is the meat of the demand:

The entire GNSO joins together today calling for the Board to support community creation of an independent accountability mechanism that provides meaningful review and adequate redress for those harmed by ICANN action or inaction in contravention of an agreed upon compact with the community.

Rafik Dammak of the Non-Commercial Users Constituency added that the creation of such a mechanism is “a necessary and integral element of the IANA stewardship transition.”

“The Board’s decisions must be open to challenge and the Board cannot be in a position of reviewing and certifying its own decisions,” he said.

“We need an independent accountability structure that holds the ICANN Board, Staff, and various stakeholder groups accountable under ICANN’s governing documents, serves as an ultimate review of Board/Staff decisions,” said Kristina Rosette of the Intellectual Property Constituency.

What they’re basically looking for is a third way to appeal ICANN decisions beyond the existing Independent Review Process and Request for Reconsideration mechanisms.

IRP is considered too time-consuming and expensive for anyone other than well-funded commercial stakeholders. It cost ICM Registry millions in legal fees to win its IRP in 2010.

RfR, meanwhile, sees the ICANN board review its own decisions, and is only successful (in 15 years it’s only happened once, a week ago) when a requester can bring new evidence to the table.

What the GNSO seems to be looking for is a third way — independent review of ICANN decisions that doesn’t cost a bomb and can be used to reexamine decisions on the merits.

In many ways the demand represents the low-hanging fruit of the amorphous “accountability” discussion that took place at length at the London meeting last week.

ICANN accountability is being examined simultaneously with the proposed transition of the IANA stewardship functions from the US Department of Commerce to a yet-undefined mechanism.

There seems to be broad community consensus that the transition should be linked to improvements in accountability.

During the “constituency day” sessions on Tuesday, during which the ICANN board visits in turn with each GNSO constituency, accountability was the theme common to each and every session.

Time and again, CEO Fadi Chehade pushed the constituency he was addressing to provide some specifics.

“What is accountability and how accountable are we today?” he asked the RySG. “Who are we accountable to for what? We need to get precise before you ask us to answer a question that says when you finish accountability, then you can move to the transition.”

The GNSO statement two days later, which still needs fleshing out with details, appears to be the first step toward providing the precision Chehade wants.

Chehade said multiple times that the accountability review and the IANA transition discussions are “interrelated” but not “interdependent.”

If one were dependent on the other, it would be easier for opponents to stonewall the IANA transition by delaying the accountability review, he said.

“There are people in this community would like the transition from the US government to never happen,” he told the RySG. “They won’t admit it, but there are several, in this room even, who want this to never happen.”

He later told the NCUC that these bogeymen were “not in this room”, highlighting perhaps his belief that one or more gTLD registries is preparing to throw a spanner in the works.

Suspicion immediately fell on Verisign, forcing Drazek to issue a separate statement at the public forum on Thursday denying that the company (his employer) opposes the transition:

VeriSign supports NTIA’s March 14th, 2014 announcement. VeriSign supports NTIA’s four key principles. VeriSign Supports the bottom-up multistakeholder process that is now under way and that we have already been very much engaged. VeriSign supports the target date of September 2015 for transition. We support these things provided the multistakeholder community recommendations for ICANN’s accountability reforms are accepted by NTIA before the final transition, and sufficiently implemented by ICANN subject to measurable deliverables.

It’s not much of a denial, really, more of a clarification of where Verisign stands and confirmation that it wants, as Chehade alluded to, accountability reform prior to the IANA transition.

In my view, accountability is the more important of these two threads.

The Department of Commerce doesn’t actually do much in terms of its hands-on role as steward of the IANA functions as they related to domain names. It merely checks that ICANN’s proper procedures have been followed before signing off on DNS root zone changes.

If sanity prevails in the ICANN community’s transition discussions (and I have no reason to believe it will) whatever replaces the US should be similarly mute and invisible.

However, Commerce’s arguably more important role has been to act as a constant Sword of Damocles, a threat that ICANN could lose its IANA powers if it goes rogue and starts acting (in the US government’s view) against the best interests of the internet community.

That’s a very crude accountability mechanism.

What ICANN needs in future is not a direct replacement of that existential threat, but a mechanism of accessible, independent third-party review that will give the ICANN community and internet users everywhere confidence that ICANN isn’t a loose cannon with its hand on the internet’s tiller.

US House passes anti-ICANN bill

Kevin Murphy, May 27, 2014, Domain Policy

The US House of Representatives has passed the DOTCOM Act, which would prevent the Department of Commerce from walking away from its oversight of the DNS root zone.

The bill was approved as an amendment to a defense authorization act, with a 245-177 vote that reportedly saw 17 Democrats vote in line with their Republican opponents.

The DOTCOM Act has nothing whatsoever to do with .com. Rather, it’s a response to the National Telecommunications and Information Administration’s plan to relinquish its role in root zone management.

The bill as passed (pdf) would prevent NTIA from agreeing to any multistakeholder community-created IANA transition proposal until the Government Accountability Office had issued a study on the proposal.

The GAO would have one year from the point ICANN submits the proposal to come up with this report.

That means that if ICANN and NTIA want to stick to their September 2015 target date for the transition, either the ICANN community would need to produce a proposal at unprecedented and unlikely speed or the GAO would need to take substantially less than a year to write its report.

I don’t think it’s an impossible target, but it’s certainly looking more likely that NTIA will have to exercise one of the two-year automatic renewal options in the current IANA contract.

That’s all assuming that a matching bill passes through the Democrat-controlled Senate and then receives a presidential signature, of course, which is not a certainty.

Assuming a bloc vote by the 47 Republican Senators, only four Democrats (or independents) would need to switch sides in order for the DOTCOM Act to become, barring an unlikely presidential veto, law.

To the best of my knowledge there is not currently a matching bill in the Senate.

Congress may block funding for IANA transition

Kevin Murphy, May 11, 2014, Domain Policy

A US House of Representatives committee has voted to de-fund the IANA transition process.

On Thursday, the House Appropriations Committee approved the fiscal year 2015 Commerce, Justice, Science Appropriations bill, which includes the $36.7 million budget for the NTIA’s running costs.

The National Telecommunications and Information Administration is the part of the Department of Commerce responsible for oversight of the IANA functions, which it plans to relinquish.

The committee noted its “concern” at this prospect, and said that no money would be made available to fund this process. Notes to the appropriations bill (pdf) include the following text:

The Committee is concerned by NTIA’s announcement of its intent to transition certain Internet domain name functions to the global multistakeholder community. Any such transition represents a significant public policy change and should be preceded by an open and transparent process. In order for this issue to be considered more fully by the Congress, the recommendation for NTIA does not include any funds to carry out a transition of these functions. The Committee expects that NTIA will maintain the existing no-cost contract with ICANN throughout fiscal year 2015.

Other bills currently up for discussion in Congress would delay the IANA transition pending further review by the Government Accountability Office.

The appropriations bill has passed a committee vote, but it still has other legislative stages to pass through before it becomes law.