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 Next Round
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
college	wf	View Comments 2015-12-04	2015-12-04			No
dental	wf	View Comments 2015-12-04	2015-12-04	View Mitigation dental Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
dentist	wf	View Comments 2015-12-04	2015-12-04	View Mitigation dentist Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
docs	wf	View Comments 2015-12-04	2015-12-04	View Mitigation docs Mitigation By Charleston Road Registry Inc. (d/b/a Google Registry) Please find attached Google Registry's proposed mechanisms to avoid confusion between the use of two-letter labels in its top level domains and the corresponding country codes. View Documents 2016-04-22	Charleston Road Registry Inc. (d/b/a Google Registry)	No
domains	wf	View Comments 2015-12-04	2015-12-04	View Mitigation domains Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
education	wf	View Comments 2015-12-04	2015-12-04	View Mitigation education Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
finance	wf	View Comments 2015-12-04	2015-12-04	View Mitigation finance Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
help	wf	View Comments 2015-12-04	2015-12-04			No
lawyer	wf	View Comments 2015-12-04	2015-12-04	View Mitigation lawyer Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
lotto	wf	View Comments 2015-12-04	2015-12-04	View Mitigation lotto Mitigation By Afilias Afilias has reviewed the comments submitted for the release of certain 2 character labels. We have taken these comments into consideration and will will continue to block the respective labels at the second level until further notice to avoid confusion. 2016-04-20	Afilias	No
navy	wf	View Comments 2015-12-04	2015-12-04	View Mitigation navy Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
pharmacy	wf	View Comments 2015-12-04	2015-12-04	View Mitigation pharmacy Mitigation By National Association of Boards of Pharmacy Background The National Association of Boards of Pharmacy® (NABP®), the impartial professional organization that supports state boards of pharmacy in protecting public health, is the exclusive Registry Operator for the .pharmacy Top-Level Domain (TLD). The .pharmacy TLD was established to provide a secure, verified, and trustworthy TLD where consumers around the globe can be sure the medications they buy online are safe. To that end, a global coalition of stakeholders, including NABP and the International Pharmaceutical Federation, developed policies and maintains standards to govern the .pharmacy TLD, ensuring those websites with a .pharmacy domain are safe and legal. Implementation Plan to Avoid Confusion To respond to the confusion concerns cited by several governments regarding the use of the second-level domains (SLDs) in the .pharmacy TLD, NABP notes that it currently implements a restricted registration policy for .pharmacy that recognizes the ongoing and critical need for patients’ medications to be managed by a licensed pharmacist and for their medications to be appropriately sourced in accordance with applicable standards of care. A copy of the policy can be found at http://safe.pharmacy/standards-policies. The very fact that .pharmacy verifies that each entity acquiring a .pharmacy SLD meets all applicable regulatory standards, including those addressing pharmacy licensure and valid prescription requirements, prior to allowing that entity to register a .pharmacy domain name avoids any potential confusion between the .pharmacy registration and a country code. In order to ensure that there will be no confusion between any two character registrations and a country code sharing the same two letters, NABP will administer its verified registry operation in a manner that avoids potential confusion by: • Continuing to implement a restricted registration policy for .pharmacy that verifies that each entity acquiring a .pharmacy SLD is an eligible member of the pharmacy community and meets all applicable regulatory standards to conduct pharmacy-related business. • Continuing to implement a restricted registration policy that ensures website content is relevant to pharmacy services and drug information, which provides the opportunity for NABP to proactively identify any potential confusing use of the domain name with a corresponding country code. • Maintaining, and continuing to create, ongoing “working relationship[s] with the relevant regulatory, or industry self-regulatory, bodies, including developing a strategy to mitigate as much as possible the risks of fraudulent, and other illegal, activities.” See Beijing GAC Communique. NABP will not issue a .pharmacy domain name in a given country until it has created a relationship with the appropriate health care regulators for a jurisdiction. • Clearly publishing this registration policy on .pharmacy’s registry homepage. • Including this registration policy in NABP’s Registry-Registrar Agreement with all accredited registrars for the .pharmacy TLD. • Enforcing this registration policy and ensuring continued compliance. The process for obtaining a .pharmacy domain name is described here: http://www.safe.pharmacy/apply. More detailed instructions and information are available here: http://www.safe.pharmacy/apply/application-instructions. NABP’s use of .pharmacy two-character domains would not, in and of itself and absent a verification process, cause any confusion with the corresponding two-letter country codes; nonetheless, NABP further contends that it avoids any potential confusion through its strenuous verification requirements and registration policies, which ensure only licensed and verified pharmacy-related entities are permitted to register and use .pharmacy domains. Request to ICANN in Accordance With Specification 5 of the Registry Agreement Based on public comments received, no government objecting to the release of its country code offered a specific explanation for the potential confusion arising from the use of a two-character SLD within a verified registry operation (as defined herein); therefore, based on the aforementioned proposal to avoid confusion as a verified registry operation and in accordance with Specification 5 of its Registry Agreement, NABP respectfully requests that Internet Corporation for Assigned Names and Numbers release the remainder of all second-level two-character country code domain names. View Documents 2016-04-25	National Association of Boards of Pharmacy	No
properties	wf	View Comments 2015-12-04	2015-12-04	View Mitigation properties Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
property	wf	View Comments 2015-12-04	2015-12-04			No
sarl	wf	View Comments 2015-12-04	2015-12-04	View Mitigation sarl Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
services	wf	View Comments 2015-12-04	2015-12-04	View Mitigation services Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
theatre	wf	View Comments 2015-12-04	2015-12-04			No
travelersinsurance	wf	View Comments 2015-12-04	2015-12-04			No
university	wf	View Comments 2015-12-04	2015-12-04	View Mitigation university Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
vote	wf	View Comments 2015-12-04	2015-12-04			No
academy	yt	View Comments 2015-12-04	2015-12-04	View Mitigation academy Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
accountant	yt	View Comments 2015-12-04	2015-12-04	View Mitigation accountant Mitigation By Famous Four Media Limited By Famous Four media Limited. Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following: 1. Registry Operator will commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant governments, and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS. 2. Registry Operator will enforce the terms of its Acceptable Use and Take down Policy against Registrants. 3. Should a Registrant fail to comply with the Acceptable Use and Take down Policy, the domain names may be cancelled, locked, placed on hold, transferred or deleted. Thus, all Registrants in the TLDs, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so. 2016-04-25	Famous Four Media Limited	No
accountants	yt	View Comments 2015-12-04	2015-12-04	View Mitigation accountants Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
agency	yt	View Comments 2015-12-04	2015-12-04	View Mitigation agency Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
airforce	yt	View Comments 2015-12-04	2015-12-04	View Mitigation airforce Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
archi	yt	View Comments 2015-12-04	2015-12-04	View Mitigation archi Mitigation By Starting Dot The proposed measure to avoid confusion for .ARCHI applies across all two-character labels. The proposed measure can be found in the file attached. View Documents 2016-04-25	Starting Dot	No
army	yt	View Comments 2015-12-04	2015-12-04	View Mitigation army Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
attorney	yt	View Comments 2015-12-04	2015-12-04	View Mitigation attorney Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
auction	yt	View Comments 2015-12-04	2015-12-04	View Mitigation auction Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
bank	yt	View Comments 2015-12-04	2015-12-04	View Mitigation bank Mitigation By fTLD Registry Services, LLC Please see the attached file that details fTLD Registry Services' implementation plan for .BANK and .INSURANCE to avoid confusion with corresponding country codes. View Documents 2016-04-20	fTLD Registry Services, LLC	No
beer	yt	View Comments 2015-12-04	2015-12-04	View Mitigation beer 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
bet	yt	View Comments 2015-12-04	2015-12-04	View Mitigation bet Mitigation By Afilias Afilias has reviewed the comments submitted for the release of certain 2 character labels. We have taken these comments into consideration and will will continue to block the respective labels at the second level until further notice to avoid confusion. 2016-04-20	Afilias	No
bid	yt	View Comments 2015-12-04	2015-12-04	View Mitigation bid Mitigation By Famous Four Media Limited By Famous Four media Limited. Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following: 1. Registry Operator will commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant governments, and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS. 2. Registry Operator will enforce the terms of its Acceptable Use and Take down Policy against Registrants. 3. Should a Registrant fail to comply with the Acceptable Use and Take down Policy, the domain names may be cancelled, locked, placed on hold, transferred or deleted. Thus, all Registrants in the TLDs, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so. 2016-04-25	Famous Four Media Limited	No
bingo	yt	View Comments 2015-12-04	2015-12-04	View Mitigation bingo Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
bio	yt	View Comments 2015-12-04	2015-12-04	View Mitigation bio Mitigation By Starting Dot This response applies across all two-character labels. PROPOSED MEASURE TO AVOID CONFUSION – .BIO StartingDot is the Registry Operator of the .BIO generic Top Level Domain string (gTLD) since June 2, 2014. The .BIO gTLD is generally available to all Registrants, and among others, to actors in the fields of agriculture, food and farming. The .BIO gTLD intends to serve all of these topics and areas, while ensuring that national and international organic standards are respected. The .BIO gTLD is established on the basis of the core organic agriculture principles that have been formulated by the International Federation of Organic Agriculture Movements (“IFOAM – Organics International”). IFOAM – Organics International is an official Partner of the .BIO Registry Operator. The Principles of Organic Agriculture (“POA”) aim to inspire the organic movement in its full diversity, and to help steer the development of positions, programs and standards in the organic community. They are used as the principal framework for defining the .BIO registration policies. In order to apply for a .BIO domain name, the registrant is required to comply with specific requirements related to organic agriculture compliance mechanisms. To address the confusion concerns cited by the relevant governments regarding the use of second-level domains (SLDs) in .BIO, StartingDot, has (i) implemented a registration policy for .BIO and (ii) established an Anti-Abuse Policy that mitigates the potential confusion addressed by the governments. Based on the above, StartingDot has: • Developped and implemented a restricted registration policy for .BIO included in the .BIO Domain Name Policy (“.BIO DNP”). According to the .BIO DNP, although a .BIO domain name can be registered by anyone, specific terms of use apply to Registrants who are producers, transformers and retailers, or otherwise involved in the field of agriculture, food and farming when there is: - A nexus with the European Union (i.e.: selling, exporting to or trading agricultural or food product in the European Union) or other relevant markets where the word “bio” may be used to refer to legally labeled and marketed organic, biological, ecological, biodynamic, or similarly named goods or intending to do so (“nexus with the European Union”); and - No nexus with the European Union. b. The Registrant who has no nexus with the European Union must commit to abiding by the POA. c. The Registrant who has a nexus with the European Union must commit to abiding by both: - The POA; and - The Council Regulation (EC) No 834/2007 of 28 June 2007 on organic production and labeling and its derived legislation, or any regulations in force in other relevant markets (the “E.C Regulations”). • Made public on StartingDot’s website (www.startingdot.com) the abovementioned .BIO DNP; • Included the .BIO Domain Name Policy in the StartingDot Registry – Registrar Agreement (RRA) signed with all the appointed registrars for .BIO; • Enforced the .BIO Domain Name Policy by monitoring registrations on a random basis. StartingDot performs quarterly controls of .BIO registrations together with IFOAM – Organics International and ensures that registrants meet the eligibility criteria established in the .BIO DNP. StartingDot has also developped an Anti-Abuse Policy published on its website, which establishes StartingDot’s actions in case of an abuse of the .BIO domain space. • Made public on StartingDot’s website (www.startingdot.com) the abovementioned Anti-Abuse Policy which contains specific text with regards to domain names that correspond to a country code described in the ISO 3166-1 alpha-2 standard. The .BIO Domain Name Policy would not prevent governments from registering domains in the .BIO TLD. However, if the latter register a .BIO domain name they must abide by the principles established under the .BIO DNP . Finally, as stated in the Anti-Abuse Policy, should a Registrant fail to comply with the Anti-Abuse Policy, the domain name may be subject to cancellation or other penalty measures (domain being locked, placed on hold, transferred or deleted). Thus all Registrants in the .BIO gTLD, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so. View Documents 2016-04-25	Starting Dot	No
broker	yt	View Comments 2015-12-04	2015-12-04	View Mitigation broker Mitigation By dotBroker Registry, dotCFD Registry, dotForex Registry, dotMarkets Registry, dotSpreadbetting Registry, dotTrading Registry [collectively, the "Boston Ivy Registry"] Please find attached a document which outlines the Registry's plans to avoid confusion in respect of the below TLDs: .Markets .Trading .Forex .Broker .Spreadbetting .CFD View Documents 2016-04-21	dotBroker Registry, dotCFD Registry, dotForex Registry, dotMarkets Registry, dotSpreadbetting Registry, dotTrading Registry [collectively, the "Boston Ivy Registry"]	No
casino	yt	View Comments 2015-12-04	2015-12-04	View Mitigation casino Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
clinic	yt	View Comments 2015-12-04	2015-12-04			No
clinique	yt	View Comments 2015-12-04	2015-12-04	View Mitigation clinique Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	Yes
cloud	yt	View Comments 2015-12-04	2015-12-04	View Mitigation cloud Mitigation By Aruba PEC SpA .cloud proposal for Mitigation Measures to Avoid Confusion in the use of domain names corresponding to ccTLDs Protections Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following: 1. Registry Operator will commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the government of a related country code, and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS. Furthermore, the Registry Operator considers the issue of domain name used in a way that generates confusion to be already covered in its Registration Policies (available for review at https://www.get.cloud/policies.aspx), for example in: 9.1 [...] Without limiting any other agreement or policy, by submitting an Application for a domain name an Applicant will be deemed to have warranted that: [...] d) it is not submitting the Application or Domain Name Registration request and, upon registration, will not use the Domain Name for an unlawful purpose, contrary to public policy or morality, for offensive purposes, to mislead the public and/or contrary to good and fair business practices; Should a Registrant fail to comply with the .cloud Registration Policies, the domain name may be canceled, locked, placed on hold, transferred or deleted. Thus all Registrants in the TLD, have an obligation to avoid misleading the public by generating confusion also with two letter country codes and there are clear penalties for any failure to do so. Registry Operator is however also open to further clarify this point by including in its Registration Policies a specific requirement for Registrants of domain names that are two letter Labels that correspond to a country code described in the ISO 3166-1 alpha-2 standard not to use them in a manner that generates confusion with the corresponding country code. 2016-04-25	Aruba PEC SpA	No
college	yt	View Comments 2015-12-04	2015-12-04			No
dental	yt	View Comments 2015-12-04	2015-12-04	View Mitigation dental Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
dentist	yt	View Comments 2015-12-04	2015-12-04	View Mitigation dentist Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
docs	yt	View Comments 2015-12-04	2015-12-04	View Mitigation docs Mitigation By Charleston Road Registry Inc. (d/b/a Google Registry) Please find attached Google Registry's proposed mechanisms to avoid confusion between the use of two-letter labels in its top level domains and the corresponding country codes. View Documents 2016-04-22	Charleston Road Registry Inc. (d/b/a Google Registry)	No
domains	yt	View Comments 2015-12-04	2015-12-04	View Mitigation domains Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
education	yt	View Comments 2015-12-04	2015-12-04	View Mitigation education Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
finance	yt	View Comments 2015-12-04	2015-12-04	View Mitigation finance Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
help	yt	View Comments 2015-12-04	2015-12-04			No
lawyer	yt	View Comments 2015-12-04	2015-12-04	View Mitigation lawyer Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
lotto	yt	View Comments 2015-12-04	2015-12-04	View Mitigation lotto Mitigation By Afilias Afilias has reviewed the comments submitted for the release of certain 2 character labels. We have taken these comments into consideration and will will continue to block the respective labels at the second level until further notice to avoid confusion. 2016-04-20	Afilias	No
navy	yt	View Comments 2015-12-04	2015-12-04	View Mitigation navy Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
pharmacy	yt	View Comments 2015-12-04	2015-12-04	View Mitigation pharmacy Mitigation By National Association of Boards of Pharmacy Background The National Association of Boards of Pharmacy® (NABP®), the impartial professional organization that supports state boards of pharmacy in protecting public health, is the exclusive Registry Operator for the .pharmacy Top-Level Domain (TLD). The .pharmacy TLD was established to provide a secure, verified, and trustworthy TLD where consumers around the globe can be sure the medications they buy online are safe. To that end, a global coalition of stakeholders, including NABP and the International Pharmaceutical Federation, developed policies and maintains standards to govern the .pharmacy TLD, ensuring those websites with a .pharmacy domain are safe and legal. Implementation Plan to Avoid Confusion To respond to the confusion concerns cited by several governments regarding the use of the second-level domains (SLDs) in the .pharmacy TLD, NABP notes that it currently implements a restricted registration policy for .pharmacy that recognizes the ongoing and critical need for patients’ medications to be managed by a licensed pharmacist and for their medications to be appropriately sourced in accordance with applicable standards of care. A copy of the policy can be found at http://safe.pharmacy/standards-policies. The very fact that .pharmacy verifies that each entity acquiring a .pharmacy SLD meets all applicable regulatory standards, including those addressing pharmacy licensure and valid prescription requirements, prior to allowing that entity to register a .pharmacy domain name avoids any potential confusion between the .pharmacy registration and a country code. In order to ensure that there will be no confusion between any two character registrations and a country code sharing the same two letters, NABP will administer its verified registry operation in a manner that avoids potential confusion by: • Continuing to implement a restricted registration policy for .pharmacy that verifies that each entity acquiring a .pharmacy SLD is an eligible member of the pharmacy community and meets all applicable regulatory standards to conduct pharmacy-related business. • Continuing to implement a restricted registration policy that ensures website content is relevant to pharmacy services and drug information, which provides the opportunity for NABP to proactively identify any potential confusing use of the domain name with a corresponding country code. • Maintaining, and continuing to create, ongoing “working relationship[s] with the relevant regulatory, or industry self-regulatory, bodies, including developing a strategy to mitigate as much as possible the risks of fraudulent, and other illegal, activities.” See Beijing GAC Communique. NABP will not issue a .pharmacy domain name in a given country until it has created a relationship with the appropriate health care regulators for a jurisdiction. • Clearly publishing this registration policy on .pharmacy’s registry homepage. • Including this registration policy in NABP’s Registry-Registrar Agreement with all accredited registrars for the .pharmacy TLD. • Enforcing this registration policy and ensuring continued compliance. The process for obtaining a .pharmacy domain name is described here: http://www.safe.pharmacy/apply. More detailed instructions and information are available here: http://www.safe.pharmacy/apply/application-instructions. NABP’s use of .pharmacy two-character domains would not, in and of itself and absent a verification process, cause any confusion with the corresponding two-letter country codes; nonetheless, NABP further contends that it avoids any potential confusion through its strenuous verification requirements and registration policies, which ensure only licensed and verified pharmacy-related entities are permitted to register and use .pharmacy domains. Request to ICANN in Accordance With Specification 5 of the Registry Agreement Based on public comments received, no government objecting to the release of its country code offered a specific explanation for the potential confusion arising from the use of a two-character SLD within a verified registry operation (as defined herein); therefore, based on the aforementioned proposal to avoid confusion as a verified registry operation and in accordance with Specification 5 of its Registry Agreement, NABP respectfully requests that Internet Corporation for Assigned Names and Numbers release the remainder of all second-level two-character country code domain names. View Documents 2016-04-25	National Association of Boards of Pharmacy	No
properties	yt	View Comments 2015-12-04	2015-12-04	View Mitigation properties Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
property	yt	View Comments 2015-12-04	2015-12-04			No
sarl	yt	View Comments 2015-12-04	2015-12-04	View Mitigation sarl Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
services	yt	View Comments 2015-12-04	2015-12-04	View Mitigation services Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
theatre	yt	View Comments 2015-12-04	2015-12-04			No
travelersinsurance	yt	View Comments 2015-12-04	2015-12-04			No
university	yt	View Comments 2015-12-04	2015-12-04	View Mitigation university Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
vote	yt	View Comments 2015-12-04	2015-12-04			No

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.

Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Two-Character Letter/Letter Label Comments and Mitigation Measures

dental Mitigation

dentist Mitigation

docs Mitigation

domains Mitigation

education Mitigation

finance Mitigation

lawyer Mitigation

lotto Mitigation

navy Mitigation

pharmacy Mitigation

properties Mitigation

sarl Mitigation

services Mitigation

university Mitigation

academy Mitigation

accountant Mitigation

accountants Mitigation

agency Mitigation

airforce Mitigation

archi Mitigation

army Mitigation

attorney Mitigation

auction Mitigation

bank Mitigation

beer Mitigation

bet Mitigation

bid Mitigation

bingo Mitigation

bio Mitigation

broker Mitigation

casino Mitigation

clinique Mitigation

cloud Mitigation

dental Mitigation

dentist Mitigation

docs Mitigation

domains Mitigation

education Mitigation

finance Mitigation

lawyer Mitigation

lotto Mitigation

navy Mitigation

pharmacy Mitigation

properties Mitigation

sarl Mitigation

services Mitigation

university Mitigation

fr Comments

fr Comments

A note about our terms of service: