Archive for the ‘Contract’ Category

ICANN Public Comment Period for .com Registry Agreement with Verisign ends Tomorrow

April 25th, 2012 Comments off

The ICANN public comment period for the .com Registry Agreement renewal with VeriSign ends tomorrow on Thursday April 26th at 23:59 UTC.

You can submit comments via to In the second “reply” phase replies to the comments can be submitted limited to those who commented in the first phase – this phase will end on May 17th 2012.

The 14 comments submitted to date can be read on the site here.

The proposed agreement suggests to keep the .COM contract with VeriSign without opening it to competitive bidding, a process that when done with the .NET registry in 2005 resulted in lower .NET registry pricing ($5.89 per Domain Name Year). The proposed extension would allow VeriSign to increase registrations fees by 7% in four of the next six years, potentially bringing up the price from the current $7.85 to $10.29 by 2016.

In case some of you feel strongly about the anti-competitive nature of the .com renewal, you may also want to consider a submission to the US Department of Justice.

[Hat tip to George Kirikos]

Related posts:

IANA contract opened again for re-bid by the US government

April 18th, 2012 Comments off

After the US National Telecommunications and Information Administration (NTIA) had canceled the first RFP for a new IANA contractor because they “received no proposals that met the requirements“, the RFP was opened again for bids two days ago. ICANN had submitted a bid, which was not accepted by  NITA. The deadline for bids to the new RFP, which doesn’t seem to deviate from the previous one by much, is May 31st, 2012.

The current contract was to expire on March 31st of this year, but was extended by six months just before ICANN’s 43rd meeting.

As reported by DomainIncite, ICANN is to report on a debriefing as to why their previous bid was not accepted:

Over a month ago, at an ICANN press conference in Costa Rica, CEO Rod Beckstrom said: “We were invited to have a debriefing with [the NTIA] to learn more about this. Following that discussion we will share any information we are allowed to share.”


Related posts: