27,652
edits
Changes
Jump to navigation
Jump to search
Line 150:
Line 150: − + + + + + + + + + + + + + + +
→Reaction on Batching Process (Digital Archery)
[[DotHealth, LLC]] confirmed that Neustar will provide the back-end registry solutions for the [[.health]] TLD. It will also use the Neustars threat mitigation and compliance monitoring services to prevent [[DDoS|distributed-denial-of-service]] (DDoS) attacks to ensure safety and security of the .health domain name space.<ref>[http://www.marketwatch.com/story/dothealth-llc-applies-for-health-new-generic-top-level-domain-2012-06-12 DotHealth, LLC Applies for .Health New Generic Top Level Domain]</ref>
[[DotHealth, LLC]] confirmed that Neustar will provide the back-end registry solutions for the [[.health]] TLD. It will also use the Neustars threat mitigation and compliance monitoring services to prevent [[DDoS|distributed-denial-of-service]] (DDoS) attacks to ensure safety and security of the .health domain name space.<ref>[http://www.marketwatch.com/story/dothealth-llc-applies-for-health-new-generic-top-level-domain-2012-06-12 DotHealth, LLC Applies for .Health New Generic Top Level Domain]</ref>
==Reaction on Batching Process (Digital Archery)==
==New gTLD Program Input==
===Reaction on Batching Process (Digital Archery)===
In June, 2012, [[Becky Burr]], Neustar's Deputy General Counsel & Chief Privacy Officer wrote to ICANN regarding the company's position on the implementation of the [[Digital Archery]] [[batching]] process for the initial evaluation of new gTLD applications. In her letter, Burr said that Neustar is supporting the position of other companies, requesting for the brief delay of the batching process. Burr pointed out that implementing batching as scheduled prior to publication of the actual list of applications will only create losers and winners, it would complicate the situation that might prevent the development of a better resolution. She also emphasized that a brief delay would enable ICANN to review the facts and the suggested alternatives presented by the affected community. Burr said, "We believe that there is ample time between now and ICANN's meeting in Prague to analyze the facts and to determine a course of action based on informed community input. Accordingly, Neustar urges a brief pause to review the need for "batched" consideration of new gTLD applications and if such [[batching]] is indeed necessary, to fine-tune the program in light of actual applications."<ref>[http://www.circleid.com/posts/20120607_neustar_urges_caution_to_icann_before_batching/ Neustar Urges Caution to ICANN Before Batching]</ref>
In June, 2012, [[Becky Burr]], Neustar's Deputy General Counsel & Chief Privacy Officer wrote to ICANN regarding the company's position on the implementation of the [[Digital Archery]] [[batching]] process for the initial evaluation of new gTLD applications. In her letter, Burr said that Neustar is supporting the position of other companies, requesting for the brief delay of the batching process. Burr pointed out that implementing batching as scheduled prior to publication of the actual list of applications will only create losers and winners, it would complicate the situation that might prevent the development of a better resolution. She also emphasized that a brief delay would enable ICANN to review the facts and the suggested alternatives presented by the affected community. Burr said, "We believe that there is ample time between now and ICANN's meeting in Prague to analyze the facts and to determine a course of action based on informed community input. Accordingly, Neustar urges a brief pause to review the need for "batched" consideration of new gTLD applications and if such [[batching]] is indeed necessary, to fine-tune the program in light of actual applications."<ref>[http://www.circleid.com/posts/20120607_neustar_urges_caution_to_icann_before_batching/ Neustar Urges Caution to ICANN Before Batching]</ref>
===Trademark Clearinghouse Model===
In October, 2012 a coalition of the world's most prominent registries, Neustar, [[ARI Registry Services]], [[Verisign]] and [[Demand Media]] jointly proposed two models for the mandatory new gTLD Sunrise period and Trademark Claims service involved in the [[Trademark Clearinghouse]] that differ from ICANN’s. To excerpt their letter:
"This proposed model simplifies the ICANN model by decreasing the coupling between the Trademark Clearinghouse (TMCH) and registries. The model is as follows:
# The TMCH generates and maintains a global public-private key pair and provides the public key to the registrars and registries. This can be done simply by publishing the public key on the TMCH website. This website should be provided over HTTPs using a digital certificate from a reputable certificate authority. The DNS records associated with this website should be protected using DNSSEC. We believe that there are no issues with security of the public key and anyone in the world can have access to it.
# Once the TMCH has authenticated the trademark information provided by the trademark holder, and validated the use requirements for eligibility to participate in sunrise, the TMCH signs the sunrise (trademark) data with its private key. The digitally signed information is referred to as the ‘Signed Mark Data’ (SMD) and is provided to the mark holder. Typically, this would be in the form of a file download from the TMCH website. The SMD includes all of the domain labels (domain names) possible to be used in registrations for the validated trademark (IDN variants excluded).
# As each TLD begins its sunrise phase, the mark holder selects a registrar and provides the registrar with the SMD as part of an application for a name within the applicable sunrise period. The registrar (or its reseller) has the ability, if it chooses to, to validate the information using the TMCH public key and then forward the information to the registry to create the application.
# The registry verifies the signature of the SMD with the public key and verifies that one of the labels within the SMD matches the domain label being registered. The registry may also then verify any other information in the SMD to ensure it is consistent with the registry’s sunrise eligibility policies. The application, or domain name, is then created.
# At the closure of the sunrise round, the registry operator will then make allocations of domain names.
# The registry notifies the TMCH of the registered domain names for the purpose of notifying mark holders about the fact that a name was registered that matches their mark as well as reporting purposes. These notices will be referred to as ‘Notification of Registered Name’ notices (NORN). We believe that a daily upload of registered names to the TMCH is sufficient for the purpose of generating NORN notices.
This solution also works for those that are conducting ‘first come – first served’ style sunrise processes."<ref>[http://domainincite.com/10694-ip-interests-should-join-the-trademark-clearinghouse-meeting-on-tuesday IP interests Should Join The Trademark Clearinghouse Meeting, DomainIncite.com]</ref>
== External links==
== External links==