Skip to main content
Resources

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.

Download Excel
TLD  Two
Characters  		Comments from GovernmentLast
updated  		RO Mitigation PlanRO NameBRAND TLD
rexrothptView Comments
2016-02-05
2016-07-22View Mitigation

rexroth Mitigation

By Robert Bosch GMBH

Provide a brief explanation of the TLD:
Robert Bosch GMBH has applied for .REXROTH to run a closed .brand environment.

Protections
Robert Bosch GMBH for the .REXROTH TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Robert Bosch GMBH will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .REXROTH is identical to a qualifying registered trademark;
2. .REXROTH is not a Generic String, as this is defined in Specification 11;
3. .REXROTH TLD has developed and will implement a closed registration policy for .REXROTH that requires that all domain names in the .REXROTH TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .REXROTH TLD will clearly publish this registration policy;
5. .REXROTH TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the .REXROTH TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .REXROTH TLD is a proprietary space in which all second-level domains in the TLD are being operated by Robert Bosch GMBH, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator.
By this letter Robert Bosch GMBH confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-25

Robert Bosch GMBHYes
shangrilaptView Comments
2016-02-05
2016-07-22Yes
wolterskluwerptView Comments
2016-02-05
2016-07-22View Mitigation

wolterskluwer Mitigation

By Wolters Kluwer N.V.

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)

Provide a brief explanation of the TLD:

.WOLTERSKLUWER TLD is a closed Brand new gTLD operated by Wolters Kluwer N.V.

Protections:

Wolters Kluwer N.V. for the .WOLTERSKLUWER TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Wolters Kluwer N.V. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

1. .WOLTERSKLUWER is identical to a qualifying registered trademark;
2. .WOLTERSKLUWER is not a Generic String, as this is defined in Specification 11;
3. .WOLTERSKLUWER TLD has developed and will implement a closed registration policy for .WOLTERSKLUWER that requires that all domain names in the .WOLTERSKLUWER TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .WOLTERSKLUWER TLD will clearly publish this registration policy;
5. .WOLTERSKLUWER TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the .WOLTERSKLUWER TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .WOLTERSKLUWER TLD is a proprietary space in which all second-level domains in the TLD are being operated by Wolters Kluwer N.V., its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this Wolters Kluwer N.V. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-05

Wolters Kluwer N.V.Yes
xn--5su34j936bgsgptView Comments
2016-02-05
2016-07-22Yes
amicaptView Comments
2016-03-03
2016-07-22Yes
appptView Comments
2016-03-03
2016-07-22No
bmsptView Comments
2016-03-03
2016-07-22View Mitigation

bms Mitigation

By Bristol Myers Squibb

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: BRISTOL-MYERS SQUIBB COMPANY has applied for .BMS to run a closed .brand environment.
Protections
BRISTOL-MYERS SQUIBB COMPANY, for the .BMS TLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that BRISTOL-MYERS SQUIBB COMPANY will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .BMS is identical to a qualifying registered trademark;
2. .BMS is not a Generic String, as this is defined in Specification 11;
3. .BMS has developed and will implement a closed registration policy for .BMS that requires that all domain names in the .BMS TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .BMS TLD will clearly publish this registration policy;
5. .BMS TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.
Compliance with Specification 13 prohibits the .BMS TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .BMS TLD is a proprietary space in which all second-level domains in the TLD are being operated by BRISTOL-MYERS SQUIBB COMPANY. - its Affiliates and Trademark Licensees and not the Government or the corresponding country code operator.
By this letter, BRISTOL-MYERS SQUIBB COMPANY confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-20

Bristol Myers SquibbYes
emersonptView Comments
2016-03-03
2016-07-22Yes
farmersptView Comments
2016-03-03
2016-07-22Yes
freeptView Comments
2016-03-03
2016-07-22No
gmbhptView Comments
2016-03-03
2016-07-22View Mitigation

gmbh Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
insuranceptView Comments
2016-03-03
2016-07-22View Mitigation

insurance 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, LLCNo
juniperptView Comments
2016-03-03
2016-07-22Yes
lidlptView Comments
2016-03-03
2016-07-22No
locusptView Comments
2016-03-03
2016-07-22Yes
lupinptView Comments
2016-03-03
2016-07-22Yes
nationwideptView Comments
2016-03-03
2016-07-22Yes
onyoursideptView Comments
2016-03-03
2016-07-22Yes
promoptView Comments
2016-03-03
2016-07-22No
rexrothptView Comments
2016-03-03
2016-07-22View Mitigation

rexroth Mitigation

By Robert Bosch GMBH

Provide a brief explanation of the TLD:
Robert Bosch GMBH has applied for .REXROTH to run a closed .brand environment.

Protections
Robert Bosch GMBH for the .REXROTH TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Robert Bosch GMBH will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .REXROTH is identical to a qualifying registered trademark;
2. .REXROTH is not a Generic String, as this is defined in Specification 11;
3. .REXROTH TLD has developed and will implement a closed registration policy for .REXROTH that requires that all domain names in the .REXROTH TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .REXROTH TLD will clearly publish this registration policy;
5. .REXROTH TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the .REXROTH TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .REXROTH TLD is a proprietary space in which all second-level domains in the TLD are being operated by Robert Bosch GMBH, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator.
By this letter Robert Bosch GMBH confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-25

Robert Bosch GMBHYes
schwarzptView Comments
2016-03-03
2016-07-22No
statefarmptView Comments
2016-03-03
2016-07-22Yes
torayptView Comments
2016-03-03
2016-07-22Yes
weberptView Comments
2016-03-03
2016-07-22Yes
wolterskluwerptView Comments
2016-03-03
2016-07-22View Mitigation

wolterskluwer Mitigation

By Wolters Kluwer N.V.

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)

Provide a brief explanation of the TLD:

.WOLTERSKLUWER TLD is a closed Brand new gTLD operated by Wolters Kluwer N.V.

Protections:

Wolters Kluwer N.V. for the .WOLTERSKLUWER TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Wolters Kluwer N.V. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

1. .WOLTERSKLUWER is identical to a qualifying registered trademark;
2. .WOLTERSKLUWER is not a Generic String, as this is defined in Specification 11;
3. .WOLTERSKLUWER TLD has developed and will implement a closed registration policy for .WOLTERSKLUWER that requires that all domain names in the .WOLTERSKLUWER TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .WOLTERSKLUWER TLD will clearly publish this registration policy;
5. .WOLTERSKLUWER TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the .WOLTERSKLUWER TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .WOLTERSKLUWER TLD is a proprietary space in which all second-level domains in the TLD are being operated by Wolters Kluwer N.V., its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this Wolters Kluwer N.V. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-05

Wolters Kluwer N.V.Yes
amicaptView Comments
2016-03-22
2016-07-22Yes
appptView Comments
2016-03-22
2016-07-22No
axaptView Comments
2016-03-22
2016-07-22Yes
bmsptView Comments
2016-03-22
2016-07-22View Mitigation

bms Mitigation

By Bristol Myers Squibb

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: BRISTOL-MYERS SQUIBB COMPANY has applied for .BMS to run a closed .brand environment.
Protections
BRISTOL-MYERS SQUIBB COMPANY, for the .BMS TLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that BRISTOL-MYERS SQUIBB COMPANY will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .BMS is identical to a qualifying registered trademark;
2. .BMS is not a Generic String, as this is defined in Specification 11;
3. .BMS has developed and will implement a closed registration policy for .BMS that requires that all domain names in the .BMS TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .BMS TLD will clearly publish this registration policy;
5. .BMS TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.
Compliance with Specification 13 prohibits the .BMS TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .BMS TLD is a proprietary space in which all second-level domains in the TLD are being operated by BRISTOL-MYERS SQUIBB COMPANY. - its Affiliates and Trademark Licensees and not the Government or the corresponding country code operator.
By this letter, BRISTOL-MYERS SQUIBB COMPANY confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-20

Bristol Myers SquibbYes
emersonptView Comments
2016-03-22
2016-07-22Yes
extraspaceptView Comments
2016-03-22
2016-07-22Yes
farmersptView Comments
2016-03-22
2016-07-22Yes
freeptView Comments
2016-03-22
2016-07-22No
gmbhptView Comments
2016-03-22
2016-07-22View Mitigation

gmbh Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
groupptView Comments
2016-03-22
2016-07-22View Mitigation

group Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
insuranceptView Comments
2016-03-22
2016-07-22View Mitigation

insurance 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, LLCNo
lidlptView Comments
2016-03-22
2016-07-22No
locusptView Comments
2016-03-22
2016-07-22Yes
ltdptView Comments
2016-03-22
2016-07-22View Mitigation

ltd Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
lupinptView Comments
2016-03-22
2016-07-22Yes
mcdptView Comments
2016-03-22
2016-07-22Yes
mcdonaldsptView Comments
2016-03-22
2016-07-22Yes
menptView Comments
2016-03-22
2016-07-22View Mitigation

men 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 LimitedNo
promoptView Comments
2016-03-22
2016-07-22No
racingptView Comments
2016-03-22
2016-07-22View Mitigation

racing 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 LimitedNo
realtorptView Comments
2016-03-22
2016-07-22No
salonptView Comments
2016-03-22
2016-07-22View Mitigation

salon Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
schwarzptView Comments
2016-03-22
2016-07-22No
stadaptView Comments
2016-03-22
2016-07-22Yes
statefarmptView Comments
2016-03-22
2016-07-22Yes
torayptView Comments
2016-03-22
2016-07-22Yes
weberptView Comments
2016-03-22
2016-07-22Yes
williamhillptView Comments
2016-03-22
2016-07-22Yes
wolterskluwerptView Comments
2016-03-22
2016-07-22View Mitigation

wolterskluwer Mitigation

By Wolters Kluwer N.V.

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)

Provide a brief explanation of the TLD:

.WOLTERSKLUWER TLD is a closed Brand new gTLD operated by Wolters Kluwer N.V.

Protections:

Wolters Kluwer N.V. for the .WOLTERSKLUWER TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Wolters Kluwer N.V. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

1. .WOLTERSKLUWER is identical to a qualifying registered trademark;
2. .WOLTERSKLUWER is not a Generic String, as this is defined in Specification 11;
3. .WOLTERSKLUWER TLD has developed and will implement a closed registration policy for .WOLTERSKLUWER that requires that all domain names in the .WOLTERSKLUWER TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .WOLTERSKLUWER TLD will clearly publish this registration policy;
5. .WOLTERSKLUWER TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the .WOLTERSKLUWER TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .WOLTERSKLUWER TLD is a proprietary space in which all second-level domains in the TLD are being operated by Wolters Kluwer N.V., its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this Wolters Kluwer N.V. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-05

Wolters Kluwer N.V.Yes
amicaptView Comments
2016-04-01
2016-07-22Yes
appptView Comments
2016-04-01
2016-07-22No
axaptView Comments
2016-04-01
2016-07-22Yes
contactptView Comments
2016-04-01
2016-07-22No
emersonptView Comments
2016-04-01
2016-07-22Yes
extraspaceptView Comments
2016-04-01
2016-07-22Yes
farmersptView Comments
2016-04-01
2016-07-22Yes
feedbackptView Comments
2016-04-01
2016-07-22No
forumptView Comments
2016-04-01
2016-07-22No
gmbhptView Comments
2016-04-01
2016-07-22View Mitigation

gmbh Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
godaddyptView Comments
2016-04-01
2016-07-22Yes
groupptView Comments
2016-04-01
2016-07-22View Mitigation

group Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
lidlptView Comments
2016-04-01
2016-07-22No
locusptView Comments
2016-04-01
2016-07-22Yes
ltdptView Comments
2016-04-01
2016-07-22View Mitigation

ltd Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
lundbeckptView Comments
2016-04-01
2016-07-22Yes
mcdptView Comments
2016-04-01
2016-07-22Yes
mcdonaldsptView Comments
2016-04-01
2016-07-22Yes
menptView Comments
2016-04-01
2016-07-22View Mitigation

men 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 LimitedNo
pidptView Comments
2016-04-01
2016-07-22No
promoptView Comments
2016-04-01
2016-07-22No
racingptView Comments
2016-04-01
2016-07-22View Mitigation

racing 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 LimitedNo
realtorptView Comments
2016-04-01
2016-07-22No
realtyptView Comments
2016-04-01
2016-07-22No
rioptView Comments
2016-04-01
2016-07-22No
salonptView Comments
2016-04-01
2016-07-22View Mitigation

salon Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
schwarzptView Comments
2016-04-01
2016-07-22No
stadaptView Comments
2016-04-01
2016-07-22Yes
statefarmptView Comments
2016-04-01
2016-07-22Yes
tiffanyptView Comments
2016-04-01
2016-07-22Yes
torayptView Comments
2016-04-01
2016-07-22Yes
weberptView Comments
2016-04-01
2016-07-22Yes
williamhillptView Comments
2016-04-01
2016-07-22Yes
abbvieptView Comments
2016-05-13
2016-07-22Yes
axaptView Comments
2016-05-13
2016-07-22Yes
beautyptView Comments
2016-05-13
2016-07-22No
bestbuyptView Comments
2016-05-13
2016-07-22Yes
contactptView Comments
2016-05-13
2016-07-22No
dhlptView Comments
2016-05-13
2016-07-22Yes
epostptView Comments
2016-05-13
2016-07-22Yes
feedbackptView Comments
2016-05-13
2016-07-22No
fordptView Comments
2016-05-13
2016-07-22Yes
forumptView Comments
2016-05-13
2016-07-22No
godaddyptView Comments
2016-05-13
2016-07-22Yes
hairptView Comments
2016-05-13
2016-07-22No
lexusptView Comments
2016-05-13
2016-07-22Yes

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

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.

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

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

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.

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."