Closed
Bug 702047
Opened 14 years ago
Closed 14 years ago
Adding .bg to list of IDN-enabled TLDs
Categories
(Core Graveyard :: Networking: Domain Lists, defect)
Core Graveyard
Networking: Domain Lists
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: iliya.bazlyankov, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
Build ID: 20110928134238
Steps to reproduce:
Registry rules: https://www.register.bg/user/static/rules/en/index.html
.bg IDN table: http://www.iana.org/domains/idn-tables/tables/bg_bg-bg_1.0.html
The registry can be contacted at: hostmaster@register.bg
Updated•14 years ago
|
Component: General → Networking: Domain Lists
OS: Windows 7 → All
QA Contact: general → networking.domain-lists
Hardware: x86_64 → All
Version: unspecified → Trunk
Comment 1•14 years ago
|
||
Iliya: are you an official representative of the .bg registry? If not, you will need to get them to make their own request, or endorse this one.
Gerv
| Reporter | ||
Comment 2•14 years ago
|
||
No, I am not
I will contact them and check with them.
Comment 3•14 years ago
|
||
I have an ask out to the registry to acknowledge this bug.
The registry DOES allow mixed script registrations but has a very interesting policy that they have listed which I think is quite responsible about protecting homographs, which is the requirement of the registry:
"When the LABEL is written in Cyrillic (IDN) it must contain only letters in Cyrillic and to include at least one letter which can be visually distinguished from the Latin alphabet (capital and/or small letters): б, г, д, ж, и, й, л, п, ф, ц, ч, ш, щ, ъ, ь, ю, я."
I think that is very helpful for reducing the potential of visually confusable strings.
Will watch for the registry to comment on this bug.
Comment 4•14 years ago
|
||
Resolving INCOMPLETE pending a comment from the .bg registry.
Gerv
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•