Latest news of the domain name industry

Recent Posts

US quietly revises IANA contract

Kevin Murphy, November 23, 2011, 08:44:37 (UTC), Domain Policy

ICANN will not be allowed to do business with groups designated by the US government as terrorists, according to one of many changes that have been quietly made to the IANA contract.
The IANA contract, which gives ICANN its ability to delegate top-level domains, is up for renewal following the publication of an RFP by the Department of Commerce earlier this month.
But Commerce substantially modified the RFP a week after its initial publication. It’s now about 20 pages longer than the original document, containing many new terms and conditions.
A few changes struck me as notable.
Among the changes is a ban on dealing with groups classified as supporting terrorism under the US Executive Order 13224, signed by President Bush in the aftermath of the the 9/11 attacks.
That Order bans US companies from working with organizations including the IRA, Hamas and Al Qaeda.
While the addition of this clause to the IANA contract doesn’t really change anything – as a US corporation ICANN is bound to comply with US trade sanctions – it may ruffle some feathers.
The new top-level domains Applicant Guidebook banned applicants involved in “terrorism” in its fourth draft, which caused complaints from some quarters.
It was revised over a year ago to instead make reference to US legal compliance and the US Office of Foreign Assets Control and its List of Specially Designated Nationals and Blocked Persons.
Khaled Fattal of the Mulitlingual Internet Group, who first described the unqualified Guidebook ban on “terrorism” as “racist”, continued to voice opposition to this rule, most recently at the ICANN public forum in Dakar, suggesting it betrays ICANN’s American bias.
Data Rights
The revised IANA RFP also contains a new section detailing the US government’s “unlimited rights” to data and software produced by the IANA contractor.
The new RFP states: “The Government shall have… Unlimited rights in all data delivered under this contract, and in all data first produced in the performance of this contract”
“Data,” it says, “means recorded information, regardless of form or the medium on which it may be recorded. The term includes technical data and computer software. The term does not include information incidental to contract administration, such as financial, administrative, cost or pricing, or management information.”
It’s not entirely clear what this clause could potentially cover.
By it’s very nature, much of the data produced by IANA is public – it needs to be in order for the DNS to function – but could it also cover data such as redelegation communications with other governments or private DNSSEC keys?
New gTLDs
There are no big changes to the section on new gTLDs, just one minor amendment.
Whereas the old RFP said that IANA must show that ICANN “followed its policy framework” to approve a gTLD, the new version says it must have “followed its own policy framework”, which doesn’t seem to change the meaning.
Other amendments to the RFP appear to be formatting changes or clarifications.
The more substantial additions – including the terrorism and data rights sections – appear to be standard boilerplate text designed to tick some boxes required by US procurement procedure, rather than being written specifically for ICANN’s benefit.
You can download the original and revised RFP documents here.

Tagged: , , , , ,

Comments (1)

  1. Jeff Neuman says:

    FYI, the Data Rights provision is standard in government contracts pursuant to the Federal Acquisition Rules ( – Special Works. The intention is to make sure that if the IANA functions needed to be transferred to another entity at any time (since all US government contracts have termination for convenience in them), they could get access to the data and transfer that data to the successor entity.
    I would not read into the Data Rights provision any more than the US Government inserting its standard clause that it must insert by law.

Add Your Comment