Changes

===DOC & Verisign===

===DOC & Verisign===

In June 2012, the [[ICANN Board]] went against community suggestions to approve Verisign's .com registry agreement for an additional seven years after its expiration on November 30th, 2012.<ref>[http://domainincite.com/9610-icann-gives-verisigns-com-contract-the-nod ICANN gives Verisign’s .com contract the nod], DomainIncite.com. Published 25 June 2012. Retrieved 28 November 2012.</ref> The new policy was highly contested, and in August 2012, three of [[ICANN]]'s Constituencies ([[ALAC]], [[GNSO]] [[Business Constituency]], [[GNSO]] [[Intellectual Property Constituency]]) sent a letter to ICANN complaining that the organization held its renewal talks with Verisign behind closed doors and the result is that there are no [[Whois|Thick Whois]] requirements for the .com TLD.<ref>[http://domainnamewire.com/2012/08/21/constituencies-blast-icanns-closed-door-verisign-com-contract-renewal/ Constituencies Blast ICANNs Closed Door Verisign Com Contract Renewal, DomainNameWire.com]</ref>

In June 2012, the [[ICANN Board]] went against community suggestions to approve Verisign's .com registry agreement for an additional seven years after its expiration on November 30th, 2012.<ref>[http://domainincite.com/9610-icann-gives-verisigns-com-contract-the-nod ICANN gives Verisign's .com contract the nod], DomainIncite.com. Published 25 June 2012. Retrieved 28 November 2012.</ref> The new policy was highly contested, and in August 2012, three of [[ICANN]]'s Constituencies ([[ALAC]], [[GNSO]] [[Business Constituency]], [[GNSO]] [[Intellectual Property Constituency]]) sent a letter to ICANN complaining that the organization held its renewal talks with Verisign behind closed doors and the result is that there are no [[Whois|Thick Whois]] requirements for the .com TLD.<ref>[http://domainnamewire.com/2012/08/21/constituencies-blast-icanns-closed-door-verisign-com-contract-renewal/ Constituencies Blast ICANNs Closed Door Verisign Com Contract Renewal, DomainNameWire.com]</ref>

The decision could not move forward without approval from the [[DOC|Department of Commerce]],<ref name="verisign2"></ref> which Verisign received on November 29th, 2012, with some changes to the original decision made by the [[ICANN Board]].<ref name="verisign3">[https://investor.verisign.com/releaseDetail.cfm?ReleaseID=724216 Verisign Announces US Department of Commerce Approval of Newly Revised .com Registry Agreement], Verisign.com. Published 30 November 2012.</ref>

The decision could not move forward without approval from the [[DOC|Department of Commerce]], which Verisign received on November 29th, 2012, with some changes to the original decision made by the [[ICANN Board]].<ref name="verisign2">[http://domainincite.com/10865-breaking-us-probing-verisign-price-hikes-com-contract-extended US probing Verisign price hikes, .com contract may be extended], DomainIncite.com. Published 25 October 2012. Retrieved 28 November 2012.</ref><ref name="verisign3">[https://investor.verisign.com/releaseDetail.cfm?ReleaseID=724216 Verisign Announces US Department of Commerce Approval of Newly Revised .com Registry Agreement], Verisign.com. Published 30 November 2012.</ref>

Verisign is to serve as the registry operator for .com from December 2012 through November 2018, with new terms and conditions, including:

Verisign is to serve as the registry operator for .com from December 2012 through November 2018, with new terms and conditions, including: