29 Rights Protection Mechanisms
|gTLD||Full Legal Name||E-mail suffix||Detail|
1 MECHANISMS DESIGNED TO PREVENT ABUSIVE REGISTRATIONS
Rights protection is a core objective of ICE. ICE will implement and adhere to any rights protection mechanisms (RPMs) that may be mandated from time to time by ICANN, including each mandatory RPM set forth in the Trademark Clearinghouse model contained in the Registry Agreement, specifically Specification 7. ICE acknowledges that, at a minimum, ICANN requires a Sunrise period, a Trademark Claims period, and interaction with the Trademark Clearinghouse with respect to the registration of domain names for the .ice gTLD. It should be noted that because ICANN, as of the time of this application submission, has not issued final guidance with respect to the Trademark Clearinghouse, ICE cannot fully detail the specific implementation of the Trademark Clearinghouse within this application. ICE will adhere to all processes and procedures to comply with ICANN guidance once this guidance is finalized.
As described in this response, ICE will implement a Sunrise period and Trademark Claims service with respect to the registration of domain names within the .ice gTLD. Certain aspects of the Sunrise period and⁄or Trademark Claims service may be administered on behalf of ICE by ICE-approved registrars or by subcontractors of ICE, such as its selected backend registry services provider, Verisign.
ICE plans to administer the .ice gTLD as a closed corporate brand and will not accept registration of second-level domains and⁄or records from external sources. ICE expects a very modest number of domain registrations - fewer than 100 per year. As such, ICE expects to be readily able to adhere to any rights protection mechanisms during the registration process.
Sunrise Period. As provided by the Trademark Clearinghouse model set forth in the ICANN Applicant Guidebook, the Sunrise service pre-registration procedure for domain names continues for at least 30 days prior to the launch of the general registration of domain names in the gTLD.
During the Sunrise period, holders of marks that have been previously validated by the Trademark Clearinghouse receive notice of domain names that are an identical match (as defined in the ICANN Applicant Guidebook) to their mark(s). Such notice is in accordance with ICANN’s requirements and is provided by ICE either directly or through ICE-approved registrars.
ICE requires all registrants, either directly or through ICE-approved registrars, to i) affirm that said registrants meet the Sunrise Eligibility Requirements (SER) and ii) submit to the Sunrise Dispute Resolution Policy (SDRP) consistent with Section 6 of the Trademark Clearinghouse model. At a minimum ICE recognizes and honors all word marks for which a proof of use was submitted and validated by the Trademark Clearinghouse as well as any additional eligibility requirements as specified in Question 18.
During the Sunrise period, ICE and⁄or ICE-approved registrars, as applicable, are responsible for determining whether each domain name is eligible to be registered (including in accordance with the SERs).
Trademark Claims Service. As provided by the Trademark Clearinghouse model set forth in the ICANN Applicant Guidebook, all new gTLDs will have to provide a Trademark Claims service for a minimum of 60 days after the launch of the general registration of domain names in the gTLD (Trademark Claims period).
During the Trademark Claims period, in accordance with ICANN’s requirements, ICE or the ICE-approved registrar will send a Trademark Claims Notice to any prospective registrant of a domain name that is an identical match (as defined in the ICANN Applicant Guidebook) to any mark that is validated in the Trademark Clearinghouse. The Trademark Claims Notice will include links to the Trademark Claims as listed in the Trademark Clearinghouse and will be provided at no cost.
Prior to registration of said domain name, ICE or the ICE-approved registrar will require each prospective registrant to provide the warranties dictated in the Trademark Clearinghouse model set forth in the ICANN Applicant Guidebook. Those warranties will include receipt and understanding of the Trademark Claims Notice and confirmation that registration and use of said domain name will not infringe on the trademark rights of the mark holders listed. Without receipt of said warranties, the ICE or the ICE-approved registrar will not process the domain name registration.
Following the registration of a domain name, the ICE-approved registrar will provide a notice of domain name registration to the holders of marks that have been previously validated by the Trademark Clearinghouse and are an identical match. This notice will be as dictated by ICANN. At a minimum ICE will recognize and honor all word marks validated by the Trademark Clearinghouse.
2 MECHANISMS DESIGNED TO IDENTIFY AND ADDRESS THE ABUSIVE USE OF REGISTERED NAMES ON AN ONGOING BASIS
In addition to the Sunrise and Trademark Claims services described in Section 1 of this response, ICE implements and adheres to RPMs post-launch as mandated by ICANN, and confirms that registrars accredited for the .ice gTLD are in compliance with these mechanisms. Certain aspects of these post-launch RPMs may be administered on behalf of ICE by ICE-approved registrars or by subcontractors of ICE, such as its selected backend registry services provider, Verisign.
These post-launch RPMs include the established Uniform Domain-Name Dispute-Resolution Policy (UDRP), as well as the newer Uniform Rapid Suspension System (URS) and Trademark Post-Delegation Dispute Resolution Procedure (PDDRP). Where applicable, ICE will implement all determinations and decisions issued under the corresponding RPM.
After a domain name is registered, trademark holders can object to the registration through the UDRP or URS. Objections to the operation of the gTLD can be made through the PDDRP.
The following descriptions provide implementation details of each post-launch RPM for the .ice gTLD:
• UDRP: The UDRP provides a mechanism for complainants to object to domain name registrations. The complainant files its objection with a UDRP provider and the domain name registrant has an opportunity to respond. The UDRP provider makes a decision based on the papers filed. If the complainant is successful, ownership of the domain name registration is transferred to the complainant. If the complainant is not successful, ownership of the domain name remains with the domain name registrant. ICE and entities operating on its behalf adhere to all decisions rendered by UDRP providers.
• URS: As provided in the Applicant Guidebook, all registries are required to implement the URS. Similar to the UDRP, a complainant files its objection with a URS provider. The URS provider conducts an administrative review for compliance with filing requirements. If the complaint passes review, the URS provider notifies the registry operator and locks the domain. A lock means that the registry restricts all changes to the registration data, but the name will continue to resolve. After the domain is locked, the complaint is served to the domain name registrant, who has an opportunity to respond. If the complainant is successful, the registry operator is informed and the domain name is suspended for the balance of the registration period; the domain name will not resolve to the original website, but to an informational web page provided by the URS provider. If the complainant is not successful, the URS is terminated and full control of the domain name registration is returned to the domain name registrant. Similar to the existing UDRP, ICE and entities operating on its behalf adhere to decisions rendered by the URS providers.
• PDDRP: As provided in the Applicant Guidebook, all registries are required to implement the PDDRP. The PDDRP provides a mechanism for a complainant to object to the registry operator’s manner of operation or use of the gTLD. The complainant files its objection with a PDDRP provider, who performs a threshold review. The registry operator has the opportunity to respond and the provider issues its determination based on the papers filed, although there may be opportunity for further discovery and a hearing. ICE participates in the PDDRP process as specified in the Applicant Guidebook.
Additional Measures Specific to Rights Protection. ICE provides additional measures against potentially abusive registrations. These measures help mitigate phishing, pharming, and other Internet security threats. The measures exceed the minimum requirements for RPMs defined by Specification 7 of the Registry Agreement and are available at the time of registration. These measures include:
• Rapid Takedown or Suspension Based on Court Orders: ICE complies promptly with any order from a court of competent jurisdiction that directs it to take any action on a domain name that is within its technical capabilities as a TLD registry. These orders may be issued when abusive content, such as child pornography, counterfeit goods, or illegal pharmaceuticals, is associated with the domain name.
• Anti-Abuse Process: ICE implements an anti-abuse process that is executed based on the type of domain name takedown requested. The anti-abuse process is for malicious exploitation of the DNS infrastructure, such as phishing, botnets, and malware.
• Authentication Procedures: Verisign, ICE’s selected backend registry services provider, uses two-factor authentication to augment security protocols for telephone, email, and chat communications.
• Malware Code Identification: This safeguard reduces opportunities for abusive behaviors that use registered domain names in the gTLD. Registrants are often unknowing victims of malware exploits. As ICE’s backend registry services provider, Verisign has developed proprietary code to help identify malware in the zones it manages, which in turn helps registrars by identifying malicious code hidden in their domain names.
• DNSSEC Signing Service: Domain Name System Security Extensions (DNSSEC) helps mitigate pharming attacks that use cache poisoning to redirect unsuspecting users to fraudulent websites or addresses. It uses public key cryptography to digitally sign DNS data when it comes into the system and then validate it at its destination. The .ice gTLD is DNSSEC-enabled as part of Verisign’s core backend registry services.
3. RESOURCING PLANS
ICE maintains a dedicated Information Security department of 10 full-time employees and a dedicated legal staff of more than 10 in-house attorneys including specialists in intellectual property. Additionally, ICE retains external counsel to augment specific legal disciplines. Rights protection is within the current remit of these groups and they have adequate capacity to process any claims that may arise from .ice registration activity.
Resource Planning Specific to Backend Registry Activities
Verisign, ICE’s selected backend registry services provider, is an experienced backend registry provider that has developed a set of proprietary resourcing models to project the number and type of personnel resources necessary to operate a TLD. Verisign routinely adjusts these staffing models to account for new tools and process innovations. These models enable Verisign to continually right-size its staff to accommodate projected demand and meet service level agreements as well as Internet security and stability requirements. Using the projected usage volume for the most likely scenario (defined in Question 46, Template 1 – Financial Projections: Most Likely) as an input to its staffing models, Verisign derived the necessary personnel levels required for this gTLD’s initial implementation and ongoing maintenance. Verisign’s pricing for the backend registry services it provides to ICE fully accounts for cost related to this infrastructure, which is provided as Line IIb.G, Total Critical Registry Function Cash Outflows, within the Question 46 financial projections response.
Verisign employs more than 1,040 individuals of which more than 775 comprise its technical work force. (Current statistics are publicly available in Verisign’s quarterly filings.) Drawing from this pool of on-hand and fully committed technical resources, Verisign has maintained DNS operational accuracy and stability 100 percent of the time for more than 13 years for .com, proving Verisign’s ability to align personnel resource growth to the scale increases of Verisign’s TLD service offerings.
Verisign projects it will use the following personnel roles, which are described in Section 5 of the response to Question 31, Technical Overview of Proposed Registry, to support the implementation of RPMs:
• Customer Affairs Organization: 9
• Customer Support Personnel: 36
• Information Security Engineers: 11
To implement and manage the .ice gTLD as described in this application, Verisign, ICE’s selected backend registry services provider, scales, as needed, the size of each technical area now supporting its portfolio of TLDs. Consistent with its resource modeling, Verisign periodically reviews the level of work to be performed and adjusts staff levels for each technical area.
When usage projections indicate a need for additional staff, Verisign’s internal staffing group uses an in-place staffing process to identify qualified candidates. These candidates are then interviewed by the lead of the relevant technical area. By scaling one common team across all its TLDs instead of creating a new entity to manage only this proposed gTLD, Verisign realizes significant economies of scale and ensures its TLD best practices are followed consistently. This consistent application of best practices helps ensure the security and stability of both the Internet and this proposed gTLD, as Verisign holds all contributing staff members accountable to the same procedures that guide its execution of the Internet’s largest TLDs (i.e., .com and .net). Moreover, by augmenting existing teams, Verisign affords new employees the opportunity to be mentored by existing senior staff. This mentoring minimizes start-up learning curves and helps ensure that new staff members properly execute their duties.
Similar gTLD applications: (98)
|gTLD||Full Legal Name||E-mail suffix||z||Detail|
|.BOFA||NMS Services, Inc.||fairwindspartners.com||-3.57||Compare|
|.MERCK||Merck Registry Holdings, Inc.||fairwindspartners.com||-3.56||Compare|
|.MERCK||Merck Registry Holdings, Inc.||fairwindspartners.com||-3.56||Compare|
|.LIAISON||Liaison Technologies, Incorporated||fairwindspartners.com||-3.52||Compare|
|.一号店||Wal-Mart Stores, Inc.||fairwindspartners.com||-3.51||Compare|
|.SAMSCLUB||Wal-Mart Stores, Inc.||fairwindspartners.com||-3.51||Compare|
|.GEORGE||Wal-Mart Stores, Inc.||fairwindspartners.com||-3.51||Compare|
|.ASDA||Wal-Mart Stores, Inc.||fairwindspartners.com||-3.51||Compare|
|.WALMART||Wal-Mart Stores, Inc.||fairwindspartners.com||-3.51||Compare|
|.GROCERY||Wal-Mart Stores, Inc.||wileyrein.com||-3.49||Compare|
|.GUARDIAN||The Guardian Life Insurance Company of America||fairwindspartners.com||-3.49||Compare|
|.GUARDIANLIFE||The Guardian Life Insurance Company of America||fairwindspartners.com||-3.48||Compare|
|.CAPITALONE||Capital One Financial Corporation||fairwindspartners.com||-3.48||Compare|
|.BUY||PVT Registry, LLC||fairwindspartners.com||-3.47||Compare|
|.bloomberg||Bloomberg IP Holdings LLC||bloomberg.net||-3.46||Compare|
|.FAIRWINDS||FairWinds Partners, LLC||fairwindspartners.com||-3.45||Compare|
|.TIFFANY||Tiffany and Company||fairwindspartners.com||-3.44||Compare|
|.MSD||MSD Registry Holdings, Inc.||fairwindspartners.com||-3.43||Compare|
|.MERCKMSD||MSD Registry Holdings, Inc.||fairwindspartners.com||-3.43||Compare|
|.TIAA||Teachers Insurance and Annuity Association of America||fairwindspartners.com||-3.42||Compare|
|.pictet||Pictet Europe S.A.||agencevirtuelle.com||-3.41||Compare|
|.LLC||LLC Registry, LLC||fairwindspartners.com||-3.39||Compare|
|.LTD||LTD Registry, LLC||fairwindspartners.com||-3.39||Compare|
|.LLP||PLL Registry, LLC||fairwindspartners.com||-3.39||Compare|
|.OMEGA||The Swatch Group Ltd||fairwindspartners.com||-3.37||Compare|
|.SWATCH||The Swatch Group Ltd||fairwindspartners.com||-3.37||Compare|
|.FUJIXEROX||Xerox DNHC LLC||fairwindspartners.com||-3.2||Compare|
|.XEROX||Xerox DNHC LLC||fairwindspartners.com||-3.2||Compare|
|.OFF||Johnson Shareholdings, Inc.||fairwindspartners.com||-3.18||Compare|
|.RAID||Johnson Shareholdings, Inc.||fairwindspartners.com||-3.18||Compare|
|.MRMUSCLE||Johnson Shareholdings, Inc.||fairwindspartners.com||-3.18||Compare|
|.GLADE||Johnson Shareholdings, Inc.||fairwindspartners.com||-3.18||Compare|
|.AFAMILYCOMPANY||Johnson Shareholdings, Inc.||fairwindspartners.com||-3.18||Compare|
|.RIGHTATHOME||Johnson Shareholdings, Inc.||fairwindspartners.com||-3.18||Compare|
|.DUCK||Johnson Shareholdings, Inc.||fairwindspartners.com||-3.18||Compare|
|.SCJOHNSON||Johnson Shareholdings, Inc.||fairwindspartners.com||-3.18||Compare|
|.glean||Lifestyle Domain Holdings, Inc.||wolfe-sbmc.com||-3.17||Compare|
|.lifestyle||Lifestyle Domain Holdings, Inc.||wolfe-sbmc.com||-3.17||Compare|
|.cityeats||Lifestyle Domain Holdings, Inc.||wolfe-sbmc.com||-3.16||Compare|
|.hgtv||Lifestyle Domain Holdings, Inc.||wolfe-sbmc.com||-3.16||Compare|
|.frontdoor||Lifestyle Domain Holdings, Inc.||wolfe-sbmc.com||-3.16||Compare|
|.cookingchannel||Lifestyle Domain Holdings, Inc.||wolfe-sbmc.com||-3.16||Compare|
|.travelchannel||Lifestyle Domain Holdings, Inc.||wolfe-sbmc.com||-3.16||Compare|
|.foodnetwork||Lifestyle Domain Holdings, Inc.||wolfe-sbmc.com||-3.16||Compare|
|.diy||Lifestyle Domain Holdings, Inc.||wolfe-sbmc.com||-3.16||Compare|
|.vana||Lifestyle Domain Holdings, Inc.||wolfe-sbmc.com||-3.16||Compare|
|.living||Lifestyle Domain Holdings, Inc.||wolfe-sbmc.com||-3.16||Compare|
|.food||Lifestyle Domain Holdings, Inc.||wolfe-sbmc.com||-3.16||Compare|
|.CORP||PROC Registry, LLC||fairwindspartners.com||-3.16||Compare|
|.GMBH||GMBH Registry, LLC||fairwindspartners.com||-3.15||Compare|
|.crs||Federated Co operatives Limited||mlt.com||-3.08||Compare|
|.thehartford||Hartford Fire Insurance Company||thehartford.com||-3.07||Compare|
|.theatre||Key GTLD Holding Inc||wolfe-sbmc.com||-3.07||Compare|
|.bway||Key GTLD Holding Inc||wolfe-sbmc.com||-3.07||Compare|
|.theater||Key GTLD Holding Inc||wolfe-sbmc.com||-3.07||Compare|
|.broadway||Key GTLD Holding Inc||wolfe-sbmc.com||-3.07||Compare|