Changes

Line 30: Line 30:  
Although ICANN has not specifically recognized a .BRAND gTLD specification in the current round, it is widely anticipated in the brand community that this will become a specialty subset of gTLDs. The .KIEHLS gTLD is intended to be one of those .BRAND gTLDs, with the goal of protecting L’Oréal’s online presence and identity, expanding its marketing and promotion efforts, providing a secure channel for online products and services, and offering a platform through which to consolidate many of the intellectual property activities of L’Oréal.
 
Although ICANN has not specifically recognized a .BRAND gTLD specification in the current round, it is widely anticipated in the brand community that this will become a specialty subset of gTLDs. The .KIEHLS gTLD is intended to be one of those .BRAND gTLDs, with the goal of protecting L’Oréal’s online presence and identity, expanding its marketing and promotion efforts, providing a secure channel for online products and services, and offering a platform through which to consolidate many of the intellectual property activities of L’Oréal.
   −
L’Oréal intends to initially limit registration and use of domain names within the .KIEHLS gTLD to L’Oréal and its qualified subsidiaries and affiliates. This initial limited use will allow L’Oréal to establish its operations and achieve full sustainability. This limited distribution coupled with the other requirements set forth in Specification 9 of the template Registry Agreement is intended to exempt L’Oréal from its annual Code of Conduct Compliance requirements.
+
L’Oréal intends to initially limit registration and use of domain names within the .KIEHLS gTLD to L’Oréal and its qualified subsidiaries and affiliates. This initial limited use will allow L’Oréal to establish its operations and achieve full sustainability. This limited distribution coupled with the other requirements set forth in Specification 9 of the template Registry Agreement is intended to exempt L’Oréal from its annual Code of Conduct Compliance requirements.<ref>[http://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/1033 Application Download, gTLDresult.ICANN.org] Retrieved 17 Feb 2013</ref>
    
==References==
 
==References==