About ICANN
- Acronyms and Terms
- Courses and Learning
- ICANN for Beginners
- Participate
- President's Corner
- ICANN Management Organization Chart
- Staff
- Careers
- In Focus
- Media Resources
Board Activities and Meetings
Accountability
- Accountability Mechanisms
- Reviews
- Expected Standards of Behavior
- Employee Practices and Resources
- Enhancing ICANN Accountability – Work Stream 2 Implementation
Governance
- Governance Documents
- Evolving ICANN’s MSM
- Agreements
- Annual Reports
- Financials
  - Financial Reports
  - Policies, Guidelines and Procedures
- Planning
  - Strategic Plan
- Presentations
- RFPs
- Litigation
- Newsletter
- Correspondence
  - 2023
  - 2022
  - 2021
  - 2020
  - 2019
  - 2018
  - 2017
  - 2016
  - 2015
  - 2014
  - 2013
  - 2012
  - 2011
  - 2010
  - 2009
  - 2008
  - 2007
  - 2006
  - 2005
  - 2004
  - 2003
  - 2002
  - 2001
  - 2000
  - 1999
  - 1998
- Quarterly Reports
Groups
- 2023 ICANN CEO Search Committee
- RSSAC
  - Charter
- SSAC
- GAC
- At-Large
- ASO
- ccNSO
- GNSO
- Technical Liaison Group
  - Technical Experts Group (TEG)
- NomCom
  - Past NomComs
- Customer Standing Committee
- Root Zone Evaluation Review Committee (RZERC)
Business
Civil Society
Complaints Office
- Complaints Report
Domain Name System Abuse
Contractual Compliance
- About
- Programs
- Complaint Submission & Learn More
- Reporting & Performance Measurement
Registrars
- Accreditation Agreement
  - Global Amendments
    - 2024 Global Amendment to the RAA
    - 2023 Global Amendment to the RAA
- Registrar Library
- News & Communications
- How to Become a Registrar
- Changes to Existing Accreditation
- Privacy and Proxy Service Providers
- Registrar Resources
Registry Operators
- Advisories & Consensus Policies
  - Advisories
  - Consensus Policies
    - Registration Data Policy
      - Registration Data Policy Implementation Resources
    - Registry Service Evaluation Policy (RSEP)
- News & Events
- Registry Agreements
  - Global Amendments
- Registry Resources
- Services for Registry Operators
Domain Name Registrants
- About Domain Names
- ICANN Policies
- Registration Data Policies
  - WHOIS and Registration Data Directory Services
    - The Domain Name Registration Process
      - Using Domain Name Registration Data
      - Keeping Registration Data Accurate
    - Access and the Evolution of the WHOIS System
- Domain Name Industry
- Registering Domain Names
- Managing Domain Names
  - Contact Information and WDRP
  - Securely Managing Your Domain Name
- Transferring Domain Names
- Renewing Domain Names
- Rights and Responsibilities
- Spam, Phishing, and Website Content
- Trademark Infringement
GDS Metrics
Identifier Systems Security, Stability and Resiliency (OCTO IS-SSR)
- IS-SSR Team Blogs
- Security Terminology
- Document Archive
ccTLDs
- Background Materials
- Agreements
- Delegation
- Root Zone Database
- Model MOU
- Workshops
- ICANN and ISO
Internationalized Domain Names
- Root Zone Label Generation Rules (LGR)
- IDN Variant TLD Implementation
- LGR Toolset
- IDN ccTLD Fast Track
- IDN Implementation Guidelines
- Second-Level LGR Reference
- Resources
- Announcements and Blogs Posts
New gTLD Program
Universal Acceptance Initiative
- Make your systems UA-ready
- Universal Acceptance Steering Group (UASG)
- UA Training
- UA Day
- UA Readiness Evaluations
- Announcements and Blogs Posts
Policy
- Policy Mission
- Policy Staff Goals
- Presentations
- Global Addressing
- Policy Updates
Operational Design Phase (ODP)
Implementation
Public Comment
- Open
- Upcoming
- Archive
Root Zone KSK Rollover
Technical Functions
- Tech Day Archive
ICANN Locations
- Report Security Issues
- PGP Keys
- Certificate Authority
- Registry Liaison
- Ombudsman
I Need Help
- Dispute Resolution
- Domain Name Dispute Resolution
- Name Collision
- Registrar Problems
- Whois Data Correction
- Independent Review Process
- Request for Reconsideration
- Document

Two-Character Letter/Letter Label Comments and Mitigation Measures

As of 13 December 2016, this page is no longer active. Please visit here for more information.

For comments submitted before 6 October 2015, view the archive of comments received.

TLDs

RO Names

TLD	Two Characters	Comments from Government	Last updated	RO Mitigation Plan	RO Name	BRAND TLD
aarp	tw	View Comments 2015-10-14	2015-12-02	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	in	View Comments 2015-12-01	2015-12-01	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	sg	View Comments 2015-11-11	2015-12-03	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	ln	View Comments 2015-12-01	2015-12-01	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	fk	View Comments 2015-12-02	2015-12-08	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	pt	View Comments 2015-11-30	2015-11-30	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	gs	View Comments 2015-12-02	2015-12-02	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	vn	View Comments 2015-12-02	2015-12-02	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	pn	View Comments 2015-12-02	2015-12-02	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	bm	View Comments 2015-12-02	2015-12-08	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	io	View Comments 2015-12-02	2015-12-08	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	ky	View Comments 2015-12-02	2015-12-08	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	ms	View Comments 2015-12-02	2015-12-08	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	sh	View Comments 2015-12-02	2015-12-08	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	tc	View Comments 2015-12-02	2015-12-08	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	gi	View Comments 2015-12-02	2015-12-08	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	ac	View Comments 2015-12-02	2015-12-08	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	il	View Comments 2015-12-03	2015-12-03	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	kr	View Comments 2015-12-04	2015-12-04	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	ng	View Comments 2015-12-04	2015-12-05	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	ru	View Comments 2015-12-07	2016-08-15	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	su	View Comments 2015-12-07	2016-08-15	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	gb	View Comments 2015-12-08	2015-12-08	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	it	View Comments 2015-12-08	2015-12-08	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
aarp	uk	View Comments 2015-12-08	2015-12-08	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
abb	tw	View Comments 2015-10-14	2015-12-02	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	aa	View Comments 2015-11-02	2015-11-02	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	in	View Comments 2015-12-01	2015-12-01	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	sg	View Comments 2015-11-11	2015-12-03	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	ln	View Comments 2015-12-01	2015-12-01	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	fk	View Comments 2015-12-02	2015-12-08	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	pt	View Comments 2015-11-30	2015-11-30	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	gs	View Comments 2015-12-02	2015-12-02	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	vn	View Comments 2015-12-02	2015-12-02	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	pn	View Comments 2015-12-02	2015-12-02	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	bm	View Comments 2015-12-02	2015-12-08	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	io	View Comments 2015-12-02	2015-12-08	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	ky	View Comments 2015-12-02	2015-12-08	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	ms	View Comments 2015-12-02	2015-12-08	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	sh	View Comments 2015-12-02	2015-12-08	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	tc	View Comments 2015-12-02	2015-12-08	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	gi	View Comments 2015-12-02	2015-12-08	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	ac	View Comments 2015-12-02	2015-12-08	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	il	View Comments 2015-12-03	2015-12-03	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	kr	View Comments 2015-12-04	2015-12-04	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	ng	View Comments 2015-12-04	2015-12-05	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	ru	View Comments 2015-12-07	2016-08-15	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	su	View Comments 2015-12-07	2016-08-15	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	gb	View Comments 2015-12-08	2015-12-08	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	it	View Comments 2015-12-08	2015-12-08	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	uk	View Comments 2015-12-08	2015-12-08	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	jo	View Comments 2015-12-17	2015-12-17	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abb	ng	View Comments 2015-12-18	2015-12-18	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abbott	in	View Comments 2015-12-01	2015-12-01	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	sg	View Comments 2015-11-11	2015-12-03	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	ln	View Comments 2015-12-01	2015-12-01	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	fk	View Comments 2015-12-02	2015-12-08	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	pt	View Comments 2015-11-30	2015-11-30	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	gs	View Comments 2015-12-02	2015-12-02	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	vn	View Comments 2015-12-02	2015-12-02	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	pn	View Comments 2015-12-02	2015-12-02	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	bm	View Comments 2015-12-02	2015-12-08	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	io	View Comments 2015-12-02	2015-12-08	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	ky	View Comments 2015-12-02	2015-12-08	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	ms	View Comments 2015-12-02	2015-12-08	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	sh	View Comments 2015-12-02	2015-12-08	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	tc	View Comments 2015-12-02	2015-12-08	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	gi	View Comments 2015-12-02	2015-12-08	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	ac	View Comments 2015-12-02	2015-12-08	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	il	View Comments 2015-12-03	2015-12-03	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	kr	View Comments 2015-12-04	2015-12-04	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	ng	View Comments 2015-12-04	2015-12-05	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	ru	View Comments 2015-12-07	2016-08-15	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	su	View Comments 2015-12-07	2016-08-15	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	gb	View Comments 2015-12-08	2015-12-08	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	it	View Comments 2015-12-08	2015-12-08	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbott	uk	View Comments 2015-12-08	2015-12-08	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abbvie	sn	View Comments 2016-04-29	2016-04-29			Yes
abbvie	sg	View Comments 2016-04-25	2016-07-28			Yes
abbvie	tw	View Comments 2016-05-05	2016-08-03			Yes
abbvie	pt	View Comments 2016-05-13	2016-07-22			Yes
abbvie	pt	View Comments 2016-05-27	2016-07-22			Yes
abc	pt	View Comments 2016-05-27	2016-07-22			Yes
abc	sg	View Comments 2016-05-30	2016-07-28			Yes
abc	tw	View Comments 2016-06-23	2016-08-03			Yes
abc	pt	View Comments 2016-07-22	2016-07-22			Yes
able	ir	View Comments 2016-08-17	2016-08-17			No
able	vn	View Comments 2016-08-17	2016-08-17			No
able	mx	View Comments 2016-08-17	2016-08-17			No
able	ir	View Comments 2016-08-17	2016-08-17			No
able	pk	View Comments 2016-08-23	2016-08-23			No
able	it	View Comments 2016-09-06	2016-09-06			No
able	tw	View Comments 2016-09-22	2016-09-22			No
able	sg	View Comments 2016-10-06	2016-10-06			No
able	bn	View Comments 2016-10-14	2016-10-14			No
abogado	in	View Comments 2015-12-01	2015-12-01	View Mitigation abogado Mitigation By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse. c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name. 2016-04-22	Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH	No
abogado	sg	View Comments 2015-11-11	2015-12-03	View Mitigation abogado Mitigation By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse. c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name. 2016-04-22	Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH	No
abogado	ln	View Comments 2015-12-01	2015-12-01	View Mitigation abogado Mitigation By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse. c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name. 2016-04-22	Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH	No
abogado	fk	View Comments 2015-12-02	2015-12-08	View Mitigation abogado Mitigation By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse. c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name. 2016-04-22	Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH	No
abogado	es	View Comments 2015-11-20	2015-11-20	View Mitigation abogado Mitigation By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse. c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name. 2016-04-22	Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH	No

tw Comments

By Lin, Mao-Shong, Deputy Director, Ministry of Transportation and Communications

I’m writing hereby to submit Taiwan government’s comments on the release of the “tw” label under the New gTLDs.

We object to the release of “tw” as SLD under all the above-mentioned New gTLDs for their registration by the corresponding Registry operators. We reserve the right to change position in this regard in the future.

The rationale of our objections are below:
Since “tw” label is the country code for Taiwan, the use of “tw” as SLD under these diverse New gTLDs would create confusion or concerns at multiple levels on our part, which include, but not limited to, ”dwarfing national dignity”, “violation of public order or good social custom”, “affecting the rights of domestic enterprises”, and “being prone to produce perplexity to our disadvantage”.

in Comments

By Rahul Gosain, Director, Department of Electronics and Information Technology, Ministry of communication and Information Technology

India is not favouring the release of Two-Character ASCII labels "in", "1n" and deceptively similar as the ccTLD ".in" at the second level. ICANN is requested that India's objection on release of Two-character ASCII labels "in" and "1n" at the second level should apply to all current and future requests from new gTLD's

sg Comments

By Queh Ser Pheng, Deputy Director, Internet Resource Management, Policy & Competition Development Group, Infocomm Development Authority of Singapore

We hereby respectfully submit our comment regarding the release of letter/letter two-character labels as second level domains.

At this stage, we are unable to agree to the release of the two-character "sg" label at the second-level under gTLDs because of the concern that such use would create confusion with the ccTLD "sg" representing Singapore. Until further notice, this policy is to be applied to all gTLDs who have requested or will be requesting for the release of letter-letter two-character labels at the second level.

To elaborate further, we are open to considering the release of "sg" to registry operators who have robust framework in place to address concerns of government. We recognise there are legitimate and valid reasons for such use. However, we are of the view that it is prudent for ICANN to first put in place a holistic and robust framework before approvals can be given. More thoughts need to be given to the evaluation process and in particular the remedies available should a registry operator use the approved names in an undesirable manner. Besides possible confusion with the corresponding country code and/or country/territory name, we are also concerned with:

(a) The possible reputational harm if ".sg." is associated with illegal or objectionable content and/or manner-of-use; and

(b) The direct harm if ".sg." content or manner-of-use targets Singapore as a nation or Singapore entities (e.g., websites could masquerade as Singapore Government agencies).

ICANN's current policy focuses only on the "initial release" process. There needs to be considerations given to "post-release" issues. As such, the ICANN framework should include:

(a) A recourse for the government/country code manager to issue a notice to object to the content and/or manner-of-use that is misleading, questionable, objectionable or contrary to the country’s reputation and laws. There should be an effective and robust process acceptable by the government/country code manager for the registry operator to address the concern; and

(b) Provisions to require the registry operator to re-seek approval from government/country code manager should there be material changes in ownership or organisational control (for example merger with or acquisitions by another entity).

In addition, ICANN must be committed to take actions against the registry operator should they fail to comply with the framework (e.g. implement a process for country/territory to raise objections to ICANN and for ICANN to take appropriate remedial actions such as remove/delete/revoke affected names).

in Comments

By Rahul Gosain, Director, Department of Electronics and Information Technology, Ministry of communication and Information Technology

India is not favouring the release of Two-Character ASCII labels "ln" and "1n" and deceptively similar as the ccTLD ".in" at the second level. ICANN is requested that India's objection on release of Two-character ASCII labels "ln" and "1n" at the second level should apply to all current and future requests from new gTLD's

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

The administration of the Falkland Islands (UK overseas territory) have no objection to the use of two character domains which coincide with their ccTLD at the second level, and do not wish to be notified of such requests by registries.

pt Comments

By Ana Cristina Ferreira Amoroso das Neves, Director, Department Information Society, Fundação para a Ciência e a Tecnologia, Ministry of Science, Technology and Higher Education

I request previous comments to objections to the release of the ".pt" as the SLD signalling 1) consumer protection concerns and confusion; 2) some gTLD correspond to a regulated market in EU countries, so their release might generate possible abuses and confusion at the end-users level and therefore must be subject to authorization by the Portuguese Government; 3) others should remain reserved so that can only be assigned to a person, entity or corporation proposed or accepted by the Portuguese Government, which demands consultations with the Portuguese Government. These comments are due to the ICANN's new process launched on the 6th October 2015 on the use of the 2-letter CC and CN at the SLD, taken into account nonetheless GAC's advice from Dublin Communiqué (October 2015). Confusability exists in all instances since the PT code is widely recognized both on and off the Internet as an identifier for Portugal. In this regard, we are concerned that consumers assume that persons or undertakings operating under "pt.string" not only offer their services in Portugal or products or services related to Portugal but that they comply with applicable regulations. As this may not be warranted by registration policies and contracts, we would request Portuguese Government is consulted before any registration, regardless of the grounds for objection. Portugal reserves the right to change position in this regard in the future.
The Portuguese Government will continue to closely follow the evolution of the market and of the technical and political framework to collect data and evidence to better understand the consequences of such release.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

The administration in South Georgia and the South Sandwich Islands (UK overseas territory) have no objection to the use of two character domains which coincide with their ccTLD at the second level, and do not wish to be notified of such requests by registries.

vn Comments

By Le Thi Ngoc Mo, Deputy Director General of Vietnam Telecommunications Authority (VNTA), Ministry of Information and Communication (MIC)

Dear ICANN,
“vn” is the country code for Viet Nam. The release of the two-character ".vn" label at the second-level under new gTLDs would create confusion with the ccTLD ".vn". On behalf of Viet Nam government, I would like to submit an objection to the release of the “.vn” at the second level under all new gTLDs.
Viet Nam is seting up the accurate criteria for releasing this two character at the second level domain names under new gTLDs . This is sensitive issue for government so it is taking some time for government to consider.
To reiterate, our objections are applied to all new gTLDs who have requested or will be requesting for the release of “.vn” at the second level until we set up the accurate criteria for releasing and send notice to ICANN.
Thank you and best regards,

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

The administration in the Pitcairn Islands (UK overseas territory) have no objection to the use of two character domains which coincide with their ccTLD at the second level, and do not wish to be notified of such requests by registries.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion and any unintended consequences, the administration of Bermuda (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion and any unintended consequences, the administration of British Indian Ocean Territory wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion and any unintended consequences, the administration of Cayman Islands (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion and any unintended consequences, the administration of Montserrat (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion and any unintended consequences, the administration of Saint Helena (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion and any unintended consequences, the administration of the Turks and Caicos Islands (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion and any unintended consequences, the administration of Gibraltar (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion and any unintended consequences, the administration of Ascension Island (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

il Comments

By Dr. Amir Adler, Chief Scientist, Ministry of Communications, Ministry of Communications

Request that “il” will be assigned under these TLDs only to a person, entity or
corporation proposed or accepted by the Israeli Government, due to the following concerns:

(1) Unproper or offensive utilization in conjuction with ".il".

(2) Missleading association with the State of Israel.

(3) Interference, or violation of the rights of domestic businesses and organizations.

kr Comments

By Seonyoung Jeong, Assistant Director, Internet Policy Division, Internet Convergence Policy Bureau Ministry of Science, ICT and Future Planning

KR is the country code for the republic of Korea. On behalf of the .kr registry and Korean government, we would like to submit a temporary objection to the release of the '.kr' at the second level under all new gTLDs UNTIL we, Korea government, set up the accurate criteria for releasing. This is sensitive issue for government so it is taking some time for government to consider.
To reiterate, our objections are applied to all new gTLDs who have requested or will be requesting for the release of .kr at the second level until we set up the accurate criteria for releasing. Thank you.

ng Comments

By Nkiru Ebenmelu, GAC Rep, Nigerian Communications Commission

Nigeria does not support the release of Two-Character ASCII Labels ".ng" or the use of "NIGERIA", in the context of any/all of the gTLD(s) at the second level. This should apply to all current and future requests. It is against Nigerian law and strictly prohibited to use the word "Nigeria" or code representing Nigeria without proper authorization by the Government. This assists the Country forestall the abuse and misuse of reserved names associated with the Government; the release would be a breach of our laws. We also wish to inform you that Nigeria reserves the right of authorization for use of “NGR” and “NGA”. As these are also reserved for use by Nigeria. (ISO 3166). We will appreciate it if we are informed of the decision(s) taken.

ru Comments

By Yulia Elanskaya, Deputy Director of International Cooperation Department, Ministry of Telecom and Mass Communications of the Russian Federation

Russia objects the release of Two-Character combination “.ru” at the second level under any kind/all gTLD.
We are concerned that the deceptive similarity of these two-letter combinations with country codes ccTLDs creates the risk of confusion and misleading of Internet users.
This requirement should apply to all current and future requests.

su Comments

By Yulia Elanskaya, Deputy Director of International Cooperation Department, Ministry of Telecom and Mass Communications of the Russian Federation

Russia objects the release of Two-Character combination “.su” at the second level under any kind/all gTLD.
We are concerned that the deceptive similarity of these two-letter combinations with country codes ccTLDs creates the risk of confusion and misleading of Internet users.
This requirement should apply to all current and future requests.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

The UK government notes that gb is a reserved ccTLD string. In order to avoid the potential for confusion, any unintended consequences and consistency within the DNS, the UK requests that this two character code must not be delegated for use as a second-level domain.

it Comments

By Rita Forsi, Italia GAC Representative, Ministry of Economic Development

With reference to the process for Considering Comments for Two-Character Letter/Letter Labels launched by ICANN on October 6, 2015, Italy restates its position expressed on March 25, 2015 (http://mm.icann.org/pipermail/twochar_comments/2015/000063.html) and on May 14, 2015 (email attached).

Italy does not object tout-court to the delegation of our ccSLD, but wants to exercise the right to evaluate the delegation of “it” as a SLD on a case-by-case basis.

The evaluation process takes into account not only the confusion risks, but also the national and international legal framework (e.g. IPR) and opportunity considerations (e.g. it.sucks).

We would like to recall that both the Singapore and Dublin GAC Communiqué advise the Board that comments submitted by the relevant Governments be fully considered regardless of the grounds for objection.

For the abovementioned reasons, we reiterate our position expressed in March 25 2015 for the release of the two‐character “it” label at the second level under new gTLDs.

In general, “it” label string may be released to the extent that the registry operator reaches a formal agreement with the Italian government (included our ccTLD registry “.it”) as per Specification 5 of the Registry Agreement.
This policy is to be applied to all new gTLDs, including, but not limited to, those falling within Category 1 and Category 2 of the Beijing Communiquè. who have requested for the release of “it” labels at the second level.
The authorization requests should be sent to the Italian GAC representatives.

Furthermore, we would like to underline that these “lines-to-take” are agreed with the “.it” Registry.

Rita Forsi

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion, and any unintended consequences, the UK government wish to be notified of all registry requests to use the two characters of its country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

aa Comments

By testing, testing, testing

this is a test - do not post

jo Comments

By Jowin V Pattamukkil, Student, Technical

I need Jo.win
Under .win domains
For technical website purposes.

It will not be confused with any other govt or other agencies.. It locked only becoz of icann policy of two letter domain reserved... And it is on release option..I need it it urgently.. Becoz of my company needs.. Kindly allow me to register..

ng Comments

By Temitope FASHEDEMI, Director, e-Government, Ministry of Communications

Many of the gTLDs have corresponding names similar to existing businesses, organisations and other entities in Nigeria and allowing registration of 'ng' will lead to confusion and/or misrepresentation with any similar local entity.

Also, some of the gTLDs connote names that are considered abusive, foul, distasteful and otherwise prohibited; allowing 'ng' registration on such domains will imply that Nigeria is associated with and/or implicitly sanctioning the liberal use of such names/words.

It is our expectation that any and all request to register the above mentioned names require express permission from the relevant government organization in Nigeria.This will assist the country forestall the abuse and misuse of reserved names associated with the Government.

sn Comments

By Alex Corenthin, Administrateur, NIC senegal, .sn registry

Senegal is not favouring the release of Two-Character ASCII labels ""sn"" deceptively similar as the ccTLD "".sn"" at the second level. ICANN is requested to notice than SEnegal's objection on release of Two-character ASCII labels ""sn"" at the second level should apply to all current and future requests from new gTLD's" to avoid any confusion with the geographic domain name .SN.

sg Comments

By Queh Ser Pheng, Deputy Director, Internet Resource Management, Policy & Competition Development Group, Infocomm Development Autority of Singapore

tw Comments

By Lin, Mao-Shong, Deputy Director, Ministry of Transportation and Communications

pt Comments

By Ana Cristina Ferreira Amoroso das Neves, Director, Department Information Society, Fundação para a Ciência e a Tecnologia, Ministry of Science, Technology and Higher Education

I request previous comments to objections to the release of the ".pt" as the SLD signaling 1) consumer protection concerns and confusion; 2) some gTLD correspond to a regulated market in EU countries, so their release might generate possible abuses and confusion at the end-users level and therefore must be subject to authorization by the Portuguese Government; 3) others should remain reserved so that can only be assigned to a person, entity or corporation proposed or accepted by the Portuguese Government, which demands consultations with the Portuguese Government. These comments are due to the ICANN's new process launched on the 6th October 2015 on the use of the 2-letter CC and CN at the SLD, taken into account nonetheless GAC's advice from Dublin Communiqué (October 2015). Confusability exists in all instances since the PT code is widely recognized both on and off the Internet as an identifier for Portugal. In this regard, we are concerned that consumers assume that persons or undertakings operating under "pt.string" not only offer their services in Portugal or products or services related to Portugal but that they comply with applicable regulations. As this may not be warranted by registration policies and contracts, we would request Portuguese Government is consulted before any registration, regardless of the grounds for objection. Portugal reserves the right to change position in this regard in the future. The Portuguese Government will continue to closely follow the evolution of the market and of the technical and political framework to collect data and evidence to better understand the consequences of such release.

pt Comments

By Ana Cristina Ferreira Amoroso das Neves, Director, Department Information Society, Fundação para a Ciência e a Tecnologia, Ministry of Science, Technology and Higher Education

sg Comments

By Queh Ser Pheng, Deputy Director, Internet Resource Management, Policy & Competition Development Group, Infocomm Development Autority of Singapore

tw Comments

By Lin, Mao-Shong, Deputy Director, Ministry of Transportation and Communications

pt Comments

By Ana Cristina Ferreira Amoroso das Neves, Director, Department Information Society, Fundação para a Ciência e a Tecnologia, Ministry of Science, Technology and Higher Education

ir Comments

By Alireza Saleh, Director .ir ccTLD, ccTLD registry of .ir

.ir ccTLD, would like to express its concern about the likelihood of confusion between "ir" and the corresponding ccTLD. .ir ccTLD, hereby, asks the related authorities to inform us of any request including "ir" in order to concluding an explicit agreement with the related Registry Operator.

vn Comments

By Le Thi Ngoc Mo, Deputy Director General of Vietnam Telecommunications Authority (VNTA), Ministry of Information and Communication (MIC)

Dear ICANN,

In response to ICANN’s proposal of measures for Letter/Letter Two-Character ASCII Labels to Avoid Confusion with Corresponding Country Codes, we do not agree with the Exclusive Availability Pre-Registration Period as a measure to avoid confusion. The proposed measure is not clear that whether names would be made available to governments at a fee or no charge. In case governments have to pay fees for the protection of their names, it is not resonable and it is impossible to developing countries.

We would like to ask ICANN to keep the reservation of the two character label strings specified in the ISO 3166-1 alpha-2 standard. Those strings are released only if the Registry Operator reaches a formal agreement with the related government or country-code manager. Moreover, we believe that every mitigation plan proposed to avoid confusion with the corresponding country code should be subjected to the approval by ICANN only after being approved by the respective government/ccTLD manager.

Best Regards,
Le Thi Ngoc Mo (Ms)
Deputy Director General,
Viet Nam Telecommunications Authority (VNTA)
Ministry of Information Communications (MIC), Viet Nam.

mx Comments

By Miguel Ángel Muñoz Petrichole, Deputy Director of International Affairs Telecommunications, Secretariat of Communications and Transport

Comments of the Mexican Administrations to the document “Proposed Measures for Letter/Letter Two-Character ASCII Labels to Avoid Confusion with Corresponding Country Codes.”

Mexico considers that the proposed measures are not enough to avoid confusion with corresponding country codes. In contrast, we believe that the release of country codes in the Second Level Domain (SLD) could destabilize the domain name system.

Regarding the proposed measures, Mexico considers the following:

• To maintain the exclusivity of a country code for a 30-day period in favor of the related government does not necessarily contributes to consumer choice or competitiveness. Besides, it could produce additional costs to governments or country code managers who wish to obtain a country code under a new gTLD.
• Likewise, it will require additional efforts and resources to review each new policy that every new gTLD operator publishes.

Mexico considers that the protection of the country codes in the ISO-3166 list should not be released. Having the offer to register a country code as a SLD would foster combinations of domain name registrations in the third level of new gTLDs. This does not contribute to the objective of this round for new gTLDs, in which it sought to increase the available options only at the root level, taking into account that other options of registration already were available and covered by other top level domains (TLDs).

It is worth noting that the initial conception of the DNS, sought to foster the registration of new domain names with a specific orientation of diverse nature: some community-territorial, some other with technical or network orientation, military, commercial, among others*, and the new gTLDs were equally conceived in this sense.

Based on the principle of parsimony, which implicates that entities should not multiple needlessly and should use the available resources; given the existence of ccTLD, which purpose is the identification of a country or community, there would be no need to have it in the SLD under new gTLDs.

*See Postel, J. (1994). RFC1591, available on: https://www.ietf.org/rfc/rfc1591.txt , among other reference documents.

ir Comments

By H.S.Shahhoseini, Advisor of Information Technology Organization of Iran, International Office

Please find following comment which is official statement of Iran ICT Deputy Minister and Head of Information Technology Organization of Iran. Also similar letter has been sent to GAC Secretariat by email.

Dear GAC Secretariat

Re: Requests for Release of Two-Letter Second-Level Domains in gTLDs

As Islamic Republic of IRAN GAC Representative, I would like to express our concerns about the likelihood of confusion between "ir" and the corresponding ccTLD. We, hereby, ask the related authorities to inform us of any request including "ir" and other possibly two character labels which are similar to "ir" in order to concluding an explicit agreement with us for releasing Two-Letter Second-Level Domains in gTLDs.
So again we categorically reject any such release unless our explicit agreement is obtained.

Sincerely yours,
Nasrollah Jahangard
I.R. Iran GAC Representative
Deputy Minister of ICT and
Head of Information Technology Organization of Iran

pk Comments

By Syed Iftikhar H Shah, Director IT, Ministry of IT, Government of Pakistan

With reference to subject matter our Pakistan’s instance is that we also have the same issue as some government has already raised to the concerned quarters. In this regard, the major issue is that such subject proposal will create confusion in the domain name system for the internet community particularly for out internet community due to lack of awareness and capacity building of our users for such domain name schemes of. So, it is suggested that ICANN, GAC and the relevant bodies, local communities of the world may further deliberate on the subject matter and then proceed accordingly In this regard, awareness program may also be launched by the ICANN globally and in developing countries as a special case.

In view of the above, it is recommended that GAC may take the subject matter with ICANN. In current situation we would ask ICANN not to proceed with releasing Pakistanis country code and names at 2nd level for all new gTLDs.

lt Comments

By Rita Forsi, Italian GAC Representative, Ministry of Economic Development

By Rita Forsi, Italia GAC Representative, Ministry of Economic Development

With reference to the process for Considering Comments for Two-Character Letter/Letter Labels launched by ICANN on October 6, 2015, Italy restates its position expressed on March 25, 2015 (http://mm.icann.org/pipermail/twochar_comments/2015/000063.html) and on May 14, 2015 (email attached).

Italy does not object tout-court to the delegation of our ccSLD, but wants to exercise the right to evaluate the delegation of “it” as a SLD on a case-by-case basis.

The evaluation process takes into account not only the confusion risks, but also the national and international legal framework (e.g. IPR) and opportunity considerations (e.g. it.sucks).

We would like to recall that both the Singapore and Dublin GAC Communiqué advise the Board that comments submitted by the relevant Governments be fully considered regardless of the grounds for objection.

For the abovementioned reasons, we reiterate our position expressed in March 25 2015 for the release of the two‐character “it” label at the second level under new gTLDs.
In general, “it” label string may be released to the extent that the registry operator reaches a formal agreement with the Italian government (included our ccTLD registry “.it”) as per Specification 5 of the Registry Agreement.
This policy is to be applied to all new gTLDs, including, but not limited to, those falling within Category 1 and Category 2 of the Beijing Communiquè. who have requested for the release of “it” labels at the second level.
The authorization requests should be sent to the Italian GAC representatives.

Furthermore, we would like to underline that these “lines-to-take” are agreed with the “.it” Registry.

Rita Forsi

tw Comments

By Lin, Mao-Shong, Deputy Director, Ministry of Transportation and Communications

sg Comments

By Queh Ser Pheng, Deputy Director, Internet Resource Management, Policy & Competition Development Group, Infocomm Development Autority of Singapore

bn Comments

By Haji Hairul Mohd Daud Bin Haji Abd Karim, Senior Assistant Chief Executive, Regulatory & Resource Management Group, Authority for Info-communications Technology Industry for Brunei Darussalam, Regulatory & Resource Management Group

As Brunei Darussalam GAC Representative, we hereby respectfully submit our comment with regards to the release of “bn” labels as second level domains.
Currently, we do not agree to the release of "bn" label at the second-level under New gTLDs.

We are concerned that the use of “bn” would create confusion in representing Brunei Darussalam. This applies to all Registry Operators who have requested or will be requesting for the release of “bn” labels at the second level domains.

Additionally, the use of “bn” at second level domain of any new gTLDs may inflict damaging or reputational harm to Brunei Darussalam if associated with illegal or objectionable content and the manner of its use. We wish to protect “bn” from such abuse.

To conclude, we wish to be notified of all Registry Operators request to use “bn” labels at the second level domains of all new gTLDs.

es Comments

By GEMA CAMPILLOS GONZALEZ, Deputy Director on Information Society Services, Ministry of Industry, Energy and Tourism

I request previous comments (signalling consumer protection concerns in most cases and demanding consultations with the Spanish Government before assigning them to second level domain name registrants) be taken into account as the GAC has recommended in its recent Dublin Communiqué (2015).

Confusion with the country identified by the label ".es" underlies comments submitted. Were there not be such an association between the country and the string, there would be no grounds for objecting. Confusability exists in all instances since the ES code is widely recognized both on and off the Internet as an identifier for Spain. Our Government only deems necessary to interfere in the allocation of second level domains with the "es" label where other concerns arising from the association of the string with our country come out.

In this regard, we are concerned that consumers asumme that persons or undertakings operating under "es.string" not only offer their services in Spain or products or services related to Spain but that they comply with applicable regulations. As this may not be warranted by registration policies and contracts, we would request Spanish Government is consulted before these names are registered.

We are open to consider other mitigation plans that effectively address concerns expressed successively by our Government.

Two-Character Letter/Letter Label Comments and Mitigation Measures

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

aarp Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abb Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abbott Mitigation

abogado Mitigation

abogado Mitigation