Changes

ANA emphasized that due to the high number of TLDs to be unveiled by ICANN's [[new gTLD Program]], policing TLDs on one-by-one basis will be difficult, and that taking precautions beforehand will be an important step in preventing future [[cybersquatting]] and fraud difficulties. Cited difficulties include the fraudulent use of brand names in secondary domains -- such as when any brand name is paired with the generic domain [[.sucks]] -- or single company ownership of generic domains -- such as if L'Oreal owned [[.hair]], [[.makeup]], or [[.beauty]].<ref name="marketingvox"></ref>

ANA emphasized that due to the high number of TLDs to be unveiled by ICANN's [[new gTLD Program]], policing TLDs on one-by-one basis will be difficult, and that taking precautions beforehand will be an important step in preventing future [[cybersquatting]] and fraud difficulties. Cited difficulties include the fraudulent use of brand names in secondary domains -- such as when any brand name is paired with the generic domain [[.sucks]] -- or single company ownership of generic domains -- such as if L'Oreal owned [[.hair]], [[.makeup]], or [[.beauty]].<ref name="marketingvox"></ref>

Continued Jaffe,  "The cost to companies that want to defensively register domains at the second level could mount easily into the multi-millions of dollars. The costs of defensive registrations also could be economically unfeasible for small and medium sized companies that will face enhanced risks of cybersquatting, typosquatting and phishing in the expanding top level domain universe."<ref name="marketingvox"></ref>], ntia.doc.gov.</ref>

Continued Jaffe,  "The cost to companies that want to defensively register domains at the second level could mount easily into the multi-millions of dollars. The costs of defensive registrations also could be economically unfeasible for small and medium sized companies that will face enhanced risks of cybersquatting, typosquatting and phishing in the expanding top level domain universe."<ref name="marketingvox"></ref>

===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>

Regardless of complaints and ICANN's approval, the decision first needs approval from the [[DOC|Department of Commerce]] before it can proceed.<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>

Regardless of complaints and ICANN's approval, the decision first needs approval from the DOC before it can proceed.<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>

== References ==

== References ==