Comment/Reply Periods (*)
Important Information Links
27 March 2012
26 April 2012
Close Time (UTC):
27 April 2012
17 May 2012
Close Time (UTC):
Contracted Party Agreements
ICANN is posting today for public comment Verisign's proposed agreement for renewal of the 2006 .com Registry Agreement between ICANN and Verisign. This proposal is a result of discussions between ICANN and VeriSign, and will be considered by the ICANN Board after public comment. The current agreement will expire on 30 November 2012. Public comment may be submitted through April 26, 2012.
The .com agreement will expire on 30 November 2012.
Once the public comments are reviewed, the ICANN Board will consider the proposal for renewal.
Section I: Description, Explanation, and Purpose
ICANN is posting today for public comment Verisign's proposed agreement for renewal of the 2006 .com Registry Agreement between ICANN and Verisign. This proposal is a result of discussions between ICANN and VeriSign, and will be considered by theICANN Board after public comment. The current agreement will expire on 30 November 2012. Public comment may be submitted through April 26, 2012 and viewed at: http://www.icann.org/en/news/public-comment/com-renewal-27mar12-en.htm
Section II: Background
Background with respect to the Proposed 2012 .com Renewal Agreement
The existing .com Registry Agreement, like other registry agreements, establishes the terms for the renewal of the Agreement. Other changes in terms require mutual agreement of the parties. In some cases, issues have been discussed but there is no update included in the proposed version of the agreement.
Section III: Document and Resource Links
ICANN and Verisign, Inc., entered into an Unsponsored Registry Agreement on 1 March 2006, under which Verisign operates the .com top-level domain. The current .com agreement and its appendices may be viewed at:http://www.icann.org/en/about/agreements/registries/com
Section IV: Additional Information
(*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses.
Proposed ALAC Statement
Original text from Holly Raiche developed April 13, containing revisions suggested by Alan Greenberg and Evan Leibovitch:
The ALAC welcomes many of the changes made to the .com contract, particularly those that will enhance security and consumer trust, and has no substantive comment on the proposed changes per se. However, the ALAC expresses extreme disappointment that ICANN has not yet taken this opportunity to require .com to use a Thick WHOIS model, the model that is required for all new gTLDs. This position is strengthened by the GNSO Council's recent decision to defer discussion on actually starting the Thick WHOIS PDP until, December 2012.
The Final Issue Report on ‘Thick” WHOIS identified many benefits including enhanced security and stability, and attractive archival and restoration properties in the case of business or technical failure of registrars. That report acknowledged that privacy may be an issue with a ‘thick’ WHOIS but noted that it has been dealt with in other ways. The Report, now over two months old, called for a PDP on Thick WHOIS issues raised or, because only Verisign maintains ‘thin’ WHOIS, direct negotiations between ICANN and Verisign.
The ALAC believes that the delay of the PDP runs counter to the global public interest in having the this important issue dealt with as quickly as possible. We urge ICANN and Verisign not to wait for the PDP in order to address this as an implementation matter, and to include a requirement for a Thick WHOIS in the current contract revision. This would efficiently provide all .com registrants with the benefits that ICANN has already stated to be important for any TLD.