Changes

We specifically examined more restrictive registration policies, such as limiting registration to members of organizations with a specific tie to cooking. We rejected such limitations because they would interfere with .COOKING’s primary mission, purpose and goals--which is to encourage as many registrants as possible to associate themselves with cooking for any legal purpose. Factors that we took into account when considering a more restrictive registration policy included:

We specifically examined more restrictive registration policies, such as limiting registration to members of organizations with a specific tie to cooking. We rejected such limitations because they would interfere with .COOKING’s primary mission, purpose and goals--which is to encourage as many registrants as possible to associate themselves with cooking for any legal purpose. Factors that we took into account when considering a more restrictive registration policy included:

* Our recognition that registrants of a .COOKING domain name will self-select because they have an interest in cooking, naturally reducing the number of potential registrants; and, because restrictive policies such as, for example, requiring membership in a specific organization or organizations, would exclude many legitimate registrants from obtaining a .COOKING domain name. For example, and by way of illustration, if membership an organization were required for registration, businesses and charitable organizations that would find a .COOKING top-level domain name an effective marketing tool would be excluded from registering a .COOKING domain name as they might not be eligible to be members in an organization that accepted only natural persons for membership.

* Our recognition that registrants of a .COOKING domain name will self-select because they have an interest in cooking, naturally reducing the number of potential registrants; and, because restrictive policies such as, for example, requiring membership in a specific organization or organizations, would exclude many legitimate registrants from obtaining a .COOKING domain name. For example, and by way of illustration, if membership an organization were required for registration, businesses and charitable organizations that would find a .COOKING top-level domain name an effective marketing tool would be excluded from registering a .COOKING domain name as they might not be eligible to be members in an organization that accepted only natural persons for membership.

With respect to protecting registrant privacy and confidential information, we will comply with all applicable ICANN rules, including Whois policies, and all applicable laws, rules and regulations of appropriate jurisdictions. Registrant privacy and use of confidential information are set forth in our Privacy & Whois Policy. Information concerning updates and changes to the Privacy & Whois Policy will be promptly and prominently displayed on the .COOKING web site."<ref>[http://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/1404 Application Download, gTLDresult.ICANN.org] Retrieved 27 Feb 2013</ref>

With respect to protecting registrant privacy and confidential information, we will comply with all applicable ICANN rules, including Whois policies, and all applicable laws, rules and regulations of appropriate jurisdictions. Registrant privacy and use of confidential information are set forth in our Privacy & Whois Policy. Information concerning updates and changes to the Privacy & Whois Policy will be promptly and prominently displayed on the .COOKING web site."<ref>[http://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/1404 Application Download, gTLDresult.ICANN.org] Retrieved 27 Feb 2013</ref>

==References==

==References==

{{reflist}}

{{reflist}}